Nuke 17 is now in open beta, and at first glance, this looks like the most exciting Nuke release in years. Gaussian Splats. MaterialX shaders. Better reflections and refractions. Stronger USD workflows. More AI through CopyCat.
it feels like Foundry suddenly woke up and decided to ship everything at once.
But once you step back, Nuke 17 is not just a feature update. It is a statement. About where Nuke is going. And about what industry now expects from compositors.
From Nuke 13 to Nuke 16, Foundry did not ship many “wow” buttons most compositors could name maybe five features that actually changed their daily life. Five. And that is being generous. Yet somehow, every year, the license price found the motivation to level up.
Nuke is not “just compositing” anymore
For a long time, Nuke was the final stop.
RPM dependencies came in, CG came in. Plates and Elements came in. Compositors fixed and merged everything.
Nuke 17 breaks that idea.
Now Nuke works with USD stages. It respects MaterialX shaders. Reflections and refractions behave more like real scene interactions. Gaussian Splats turn captured environments into editable assets. CopyCat lets Nuke learn from your own data.
This means Nuke is moving closer to layout, look-dev, and lighting, even if it never fully replaces those departments.
Studios want fewer round trips. Fewer department handoffs. Faster iteration. Less waiting. If comp can solve it, production moves on.
Foundry is aligning Nuke with that reality.
That sounds powerful. but It also raises expectations.
Nuke 17 quietly asks compositors to understand more 3D, more scene logic, more technical details. The tool gets stronger, but the workload does not automatically get lighter.
This is the kind of features that supervisors/studios love because it reduces back-and-forth. The comp can solve things that previously required a relight or a re-render.
The risk is that expectations change faster than recognition, compensation, and job definitions.
When compositors are expected to understand 3D, USD, shading, AI, and traditional comp equally well, burnout becomes structural, not personal.
And Nuke Is a Monopoly. We All Know It. We Just Pretend It Isn’t.
That is not an opinion. That is the market.
Competition exists. Functionally, it doesn’t.
Fusion exists. Yes, there are lighter tools. Yes, open-source projects in production comp pipeline best of luck.
For two decades, Nuke has moved from being a powerful compositing tool to becoming the compositing tool. If you work in film, episodic, or high-end advertising, Nuke is not a choice you debate. It is a requirement you inherit.
Nuke did not become dominant because Foundry crushed competitors or blocked alternatives. It became dominant because studios standardized around it early, and then never left. Once pipelines, training, hiring, and production schedules are built around a single tool, switching stops being about software quality and starts being about operational risk.
Foundry’s real competitive pressure is not another compositor. It is studios trying to reduce dependency with AI tools!
The price question no one can ignore
The beta is free. The final release will not be.
Nuke 17 adds exactly the kind of features that justify higher prices in a meeting room. USD. MaterialX. 3D tools. AI. Volumetric workflows. All inside one application.
Studios will pay for this. They always do.
The real pressure will land on freelancers and small studios, who already feel stretched by Nuke’s licensing.
Technically, Nuke 17 is a strong release. Maybe the strongest in a long time.
But it also makes something very clear.
Foundry is no longer building Nuke mainly for individual compositors.
They clearly know they cant win a market through AI tools So they started is building Nuke as a central pipeline tool for studios. Compositors are expected to operate that tool and solve more problems inside it.
They are building infrastructure for studios.
Compositors are the operators of that infrastructure.
