Why We Haven't Moved Our Color Grade to ACES Yet

We've looked at moving our color grade onto ACES twice now, and passed both times. Not because we don't trust it — the case for a single, standards-based color pipeline from set to DCP is a real one, and ACES 2.0's release at NAB Show 2025 made it a harder case to wave off than it used to be. We passed because we sat down with what it would cost us to run, against what problem it would actually solve for a shop our size — and the math didn't clear.

That's the whole piece. Not "ACES is bad" — it isn't — but a working answer to why a one-camera festival feature doesn't need what it was built to do.

What ACES Actually Solves

ACES exists to solve an interchange problem: a title moving across many cameras, many vendors, and many facilities, all needing to agree on the same color intent by the time it lands in a theater. The standard's footprint at SMPTE tells you who it's for before you read a word of the spec — a full family of specifications covering primary color encoding, printing-density metrics for film scans, file containers built on OpenEXR and MXF, an archival IMF application, and a scripting language (CTL) for writing the transforms themselves. That's infrastructure built for coordination at scale: a studio running six units on six continents, cutting together footage from a dozen camera systems, handing the whole thing off between a VFX house, a mix stage, and a DI facility that have never worked together before.

None of that describes a Stillfield feature. We shoot one camera body, sometimes two. We grade in the same room we edit in. There's no handoff between organizations that don't already know each other's monitors — the same colorist who pulled the primary on Tuesday is the one signing off the DCP on Friday.

That distinction matters more than it sounds like it should. ACES was never marketed as a quality upgrade you bolt onto an existing grade — it's a coordination layer, and coordination is only worth paying for when you actually have more than one party to coordinate.

The Overhead We'd Be Buying

Adopting ACES for real — not just opening a file that happens to carry ACES metadata, but running the color-managed pipeline as intended — means building or sourcing an Input Transform for every camera we use, moving to floating-point, OpenEXR-native storage and playback across the whole post chain, and standing up a CTL interpreter to execute the transforms consistently. None of that is optional once you're in — it's the price of the interchange guarantee, and it scales with the number of camera systems and facilities touching a title, not with runtime or shot count.

We think about post spend the way we think about everything else on a budget — which is part of why the post-production percentage rule we don't follow exists as its own piece. The honest version of that math here: the cost of standing up a color-managed pipeline buys us protection against a coordination failure between organizations. We don't have multiple organizations on a color grade. We have one colorist and one client review.

What We Do Instead

What we actually run is closer to what it's always been: camera-native footage, a LUT built for the job, one colorist, one suite, one calibrated monitor, and QC on that same calibrated monitor before anything ships. There's no handoff to lose color intent across, because there's no handoff. The place where a grade actually lives or dies on a festival feature isn't the color-management layer underneath it — it's the final ten percent, the part that needs a person sitting in the room making a judgment call a transform can't make for them.

The case for skipping a managed color pipeline doesn't only hold at our scale, either. Practitioner guidance aimed at independent creators in 2026 skips ACES entirely, recommending a plain three-layer grade — primary correction, creative look, secondary polish — in a tool like DaVinci Resolve's free tier. We're a level above that tier. But it's the same argument we keep landing on: a color-managed pipeline solves a coordination problem, and if you don't have that problem, you're paying for a guarantee you don't need.

There is a real trigger that would change our answer, and it isn't hypothetical: a VFX-heavy title, a genuine multi-camera shoot across different sensor types, or a delivery pipeline downstream that requires ACES on the way in. Any of those puts us on the other side of the math, and we'd stand up the pipeline the day it shows up on a call sheet — not as a hedge against a problem we might someday have, but because at that point the problem would already be sitting in the room with us.

Working note

We haven't skipped ACES out of inertia. We priced it against a coordination problem we don't have yet, and we'll keep pricing it that way every time a new title comes in the door. For now the room stays the same: one grade, one monitor, one person doing the part of the work that was never going to be automated regardless of which color space it happens in.