A comp is only as portable as the files it points at. Nuke Studio Hub reads your .nk and builds a single dependency manifest - every path the script relies on - so you can collect everything it needs before you hand it off, not after a vendor calls you about a missing plate.
Everything the script points at
The manifest walks every node and pulls out the files the comp cannot live without:
- Read & Write media - plates, renders and elements, including padded frame sequences.
- LUTs and CDLs -
.cube,.cc,.cccand grade files referenced by colour nodes. - Vector fields -
.vffiles used by VectorDistort and friends. - Fonts - typefaces a Text node needs to render the same on another machine.
- Geometry -
.obj,.abcand other geo pulled into a 3D setup.
Portability and folder-resolve status
Each entry is graded for portability. Absolute paths tied to one artist's drive, references to a local disk, and anything outside the project root are flagged, because those are the paths that break the moment a script travels. If you scan the real project folder, Nuke Studio Hub goes a step further and checks each file against disk - so the manifest shows not just what the script expects, but what actually resolves and what is already missing.
A real collect-files list
The output is a practical checklist, not a wall of text. It is the list you would otherwise assemble by hand - every file, grouped by type, with its source node - ready to gather into a delivery, a farm submission or a vendor package. Because it is built from the parsed script rather than a folder guess, it catches the LUT buried in an OCIOFileTransform and the font on a Text node that a filename-only tool would miss entirely.
Why it matters for handoffs
The classic Nuke handoff failure is a script that opens fine on your box and red on theirs. A dependency manifest turns that into a solved problem: you know exactly which files must travel with the script, which paths need rewriting to stay portable, and whether anything is already broken before you ship. Freelancers use it to package a clean delivery; studios use it to standardise what leaves the building; farm wranglers use it to confirm every dependency will resolve before a job spends render hours failing.
Parsed locally, nothing uploaded
The manifest is built entirely in your browser by parsing the .nk as text. Your media and paths never leave your machine, and the tool never copies or moves a file - it just tells you what to collect. It runs on Nuke 14 to 16 scripts and starts at A$9/mo with a 14-day free trial.
Frequently asked questions
What files does the manifest include?
Everything the script points at: Read and Write media, LUTs, CDLs, vector fields (.vf), fonts and geometry. Each entry shows its path, node, portability and - when you scan the folder - whether it resolves on disk.
Does it copy or move my files?
No. It reads the .nk as text and lists what the script needs. You get a collect-files list to gather the files yourself, so nothing is copied, moved or uploaded by the tool.
Which Nuke versions are supported?
Scripts from Nuke 14, 15 and 16. Because it parses the .nk text directly, it does not need Nuke installed to build the manifest.