Product Tour

See Nuke Studio Hub
in action

From a folder of .nk scripts to a clean handoff; here's the whole workflow, with screenshots of every step. A full video walkthrough is on the way.

How it works

Five steps, one browser tab

Scan a project, parse the scripts, audit the nodes and hand off clean; no plugin, nothing to install, and your scripts never leave your machine.

1

Scan your project folder

Point Nuke Studio Hub at a shot or project folder. Using the File System Access API in Chrome or Edge, it walks the tree, finds every .nk script and render, and checks the layout against your expected structure; or open individual scripts directly.

File System Access.nk discoveryRenders & elementsLocal only
nuke-studio-hub / scan
Project dashboard after scanning the demo shot
2

Parse the .nk scripts

A Nuke script is plain text, so the in-browser parser actually reads it; not just the filename. It pulls the real nodes, Write paths, version tokens and Read references out of every script, so the audit is based on what's inside the comp.

Plain-text parseNuke 14–16Nodes & knobsNo upload
nuke-studio-hub / script-audit
Script Audit; parsed .nk nodes and paths
3

Audit Write nodes & version tokens

Check every Write node's output path, file naming and version tokens against your studio convention; so renders land in the right place, correctly named and versioned every time, with no surprise overwrites.

Output pathsNaming rulesVersion tokensPer-Write report
nuke-studio-hub / write-nodes
Validation Center; naming and version checks
4

Catch broken Read media & gizmo issues

Flag Read nodes pointing at missing files, absolute or non-portable paths and broken frame ranges, then inventory the gizmos and ToolSets a script relies on; surfacing unknown or deprecated nodes that won't open on another machine.

Missing mediaAbsolute pathsFrame rangesGizmo / ToolSet
nuke-studio-hub / media-health
Script/media assets and gizmo inventory
5

Export reports & hand off clean

Export audit-ready CSV and PDF reports of naming issues, Write/Read problems and gizmo dependencies; clean documentation for clients, supervisors and finals handover, so every comp leaves your pipeline to the same standard.

CSV exportPDF reportFinals handoffShareable
nuke-studio-hub / reports
Audit summary and health score
Everything you need

One toolkit, scan to handoff

Parse .nk in the browser

A Nuke script is plain text, so we read the real nodes, paths and tokens; not just filenames.

Write-node audit

Output paths, file naming and version tokens checked against your studio convention.

Read-media health

Catch missing files, absolute or non-portable paths and broken frame ranges before the farm.

Naming & gizmo hygiene

Audit node names and inventory the gizmos and ToolSets a script depends on.

Project-structure check

Check the folder layout; scripts, renders, elements, comp; and flag missing or stray dirs.

CSV & PDF reports

Audit-ready documentation of every issue for clients, supervisors and finals handover.

A closer look

Screens from the hub

A look at the workspace; the real thing is just a click away.

Ready to clean up your comps?

Start your 14-day free trial; no credit card required. From A$9/mo for solo artists.