When your folders, your Write paths and your Read paths all agree, a comp hands off without a scavenger hunt. Start from a standard project structure and keep every project the same.
A standard Nuke project structure
SHOW/
SHOT010/
in/ incoming plates and elements
plates/ graded / prepped source plates
elements/ stock, mattes, renders from other depts
scripts/ .nk comp scripts
comp/ working comp files and caches
renders/ comp output, versioned
out/ approved deliveriesWhat each folder is for
- in / plates. Everything that comes into the shot, kept separate from anything you make.
- elements. Renders and assets from other departments or libraries.
- scripts. The
.nkfiles, so scripts are never lost among renders. - comp / renders. Working files and versioned output, cleanly split.
- out. Approved deliveries only, so the client-facing folder stays trustworthy.
Validate a project against the template
A template only helps if projects actually follow it. Nuke Studio Hub checks your project against a standard structure and flags where things drift - renders written into comp, plates on a local drive, scripts scattered outside scripts. Combined with the Write-node checker, it means your folders and your render paths always match, which is the foundation of a clean handoff.
Frequently asked questions
Is there one correct Nuke folder structure?
No single standard fits every studio, but the comp / renders / elements / scripts / in / out pattern above is a clean, common starting point you can adapt.
Can the tool check my folder structure?
Yes. Nuke Studio Hub validates a project against a standard structure and flags files that landed in the wrong place.