A Nuke .nk script is plain text, and it stores each node's position on the graph. That means Nuke Studio Hub can rebuild the comp's node graph in your browser and lay it out exactly where the artist put it - no Nuke, no plugin, no waiting.
Real xpos / ypos layout
This is not an auto-arranged approximation. Every Nuke node carries an xpos and ypos value in the script, so Nuke Studio Hub reads those coordinates and draws each node where it lives in the real comp. Backdrops, dots and the rough shape of the tree land where you expect, so a script you have never opened still looks familiar. If you recognise a comp by its layout, you will recognise it here.
Edges from the stack model
Nuke does not store connections as a simple list of wires; it uses a stack-based model where nodes push and pop inputs as the script is read top to bottom. Nuke Studio Hub replays that model to reconstruct the edges between nodes - which Merge takes which A and B input, where a Dot branches, how a Read feeds through the tree - so the graph you see reflects the real flow of the comp, not just a scatter of boxes.
Pan, zoom and export
The graph renders as an SVG, so it stays crisp at any zoom. Pan around a big comp, zoom into a cluster of Merges, and export the whole layout as an SVG to drop into a review, a ticket or a handoff note. Because it is vector, it prints and scales cleanly - useful when a supervisor wants the tree on one page without opening the project.
Flagged nodes ringed
The viewer is not just cosmetic. Nodes the audit flags - a Write with a broken output path, a Read pointing at missing media, an unknown gizmo, a colourspace smell - are ringed on the graph, so you can see where a problem lives in the comp, not just that it exists in a list. Instead of hunting a node name through a report, you glance at the tree and go straight to it.
Where it helps
- Review & QA - eyeball an incoming script's shape and complexity before you commit to opening it on a licensed seat.
- Handoff - send a reviewer or client the SVG so they can see the tree without a Nuke install.
- Triage - when a render breaks, find the flagged node on the graph in seconds and skip the guesswork.
- Learning & audit trails - keep a visual record of how a shot was built, version by version.
Parsed locally, nothing uploaded
Everything happens in the browser. Nuke Studio Hub parses the .nk as text and draws the graph on your machine, so your comp is never sent to a server. It runs on Nuke 14 to 16 scripts and starts at A$9/mo with a 14-day free trial.
Frequently asked questions
Does it open my Nuke project?
No. It parses the .nk script as text in your browser and draws the node graph from the positions stored in the file, so you can read the whole tree without launching Nuke.
Is my script uploaded anywhere?
No. The graph is built locally in the browser; nothing about your project leaves your machine, and you can export the layout as an SVG.
Which Nuke versions are supported?
Scripts from Nuke 14, 15 and 16. Because a .nk stores each node's xpos and ypos as plain text, the viewer does not need Nuke installed.