How I Build a Compositing Workflow in Nuke for Animation Features
Over the last few years I've worked on the comp side of animated features and series at Skydance Animation, Illusorium Studios and Cocolilo Animation — sometimes as a shot artist, often as the person building the templates and tools the rest of the team relies on. This article is a practical summary of how I approach a Nuke compositing workflow for animation, and the decisions that matter most.
1. Start from the template, not the shot
In animation, comp is a volume game: hundreds of shots that share the same render structure. The single highest-leverage thing you can do is invest in a solid shot template — a Nuke script that already knows how to read the show's passes, rebuild the beauty, and route mattes and FX elements, so an artist opens a shot and starts making creative decisions immediately instead of wiring nodes.
A good template has three properties:
- Predictable structure — every shot looks the same, so anyone can open anyone's script and know where things are.
- Safe defaults — the un-touched template output should already look close to the lighting render. Comp adds, it doesn't repair.
- Escape hatches — artists must be able to break out of the template for hero shots without fighting it.
2. Respect the AOV structure
Having worked as a lighting assistant before moving to comp, I learned to treat the render's AOV structure as a contract between departments. The comp template rebuilds the beauty from light groups and AOVs, which gives comp enormous grading power — but only if the rebuild is mathematically exact. Verify it with a difference against the beauty on every show setup, and automate that check if you can.
3. Mattes are a workflow, not a node
On Swapped I owned the DiMatte workflow, and it changed how I think about mattes. Cryptomatte is great for ad-hoc picking, but a production needs named, versioned, consistent mattes that arrive in every shot the same way. Define naming conventions early, build the template to consume them automatically, and give artists one obvious tool to request or generate a matte that doesn't exist yet.
4. Move look decisions into comp when it's cheaper
Some look tweaks don't need a re-render. On the Blacksad fan-art piece I built a triplanar STMap tool that uses Position and Normal passes to apply 2D textures directly in comp, tracking the assets through the shot. That kind of tool turns a days-long texture/render round trip into minutes inside Nuke. Every show has a handful of these opportunities — find them.
5. Automate the boring 20%
As a TD on Pocoyó season 5 my job was essentially to remove friction: automatic script setup, read/write node management, versioning, delivery. Python inside Nuke pays for itself immediately in episodic work. My rule of thumb: if an artist does the same five clicks in every shot, that's a tool.
Closing thoughts
The artistic and technical sides of compositing aren't separate jobs — the best comp teams I've been part of treat the pipeline as part of the image. If the template is solid, the mattes are reliable and the boring parts are automated, artists spend their day on what actually shows up on screen.
Want to talk comp workflows, or see this thinking applied to real productions? Check my projects or get in touch.