Nuke Studio Hub
A browser tool that parses Foundry Nuke scripts to audit Write paths, version tokens, broken Reads and node hygiene, before a comp reaches the farm.
The challenge
Nuke scripts fail on the render farm for boringly avoidable reasons: a Write node pointing at the wrong folder, a missing version token, a Read pointing at media that no longer exists, or a tangle of unnamed nodes nobody can safely pick up. Each one can cost a night of render time.
Checking all of this by hand before every submission is slow and easy to skip when a deadline is looming, which is exactly when it matters most.
Our solution
Because Nuke .nk scripts are plain text, we could do something the desktop tools do not: parse them directly in the browser. Nuke Studio Hub reads a script and runs a Script Audit over it, flagging Write-node output paths, naming and version tokens, broken or absolute Read media, and node-naming and gizmo hygiene, alongside the usual folder, naming and project-structure checks.
It never needs to open Nuke, so a coordinator or a supervisor can sanity-check a script without a licence in front of them.
What we built
- An in-browser .nk script parser (js/modules/nkparser.js)
- A Script Audit for Write paths, naming and version tokens
- Detection of broken and absolute Read media
- Node-naming and gizmo/ToolSet hygiene checks
- Folder, naming and project-structure checks
- CSV and PDF audit reports
Tech stack
The outcome
A compositor or coordinator can now audit a Nuke script before submission and catch render traps early, without opening Nuke. The plain-text parsing approach is the key differentiator and the reason it can run entirely client-side.
It is the VFX-facing sibling of our Houdini and engine hubs, sharing the same reporting core tuned to the specifics of Nuke.
Need something similar?
We design and build browser-based tools and SaaS products end to end. Tell us what you are trying to make.
Start a project