
Overview
Every camera brand encodes color and log footage slightly differently, which is invisible until you mix cameras on the same project or hand footage off to a colorist who wasn't there for the shoot. ACES (the Academy Color Encoding System) is the industry-standard answer: a common color space every camera's footage gets translated into, so grading and delivery behave predictably regardless of source. This guide explains the pipeline in plain terms and, just as importantly, when you don't actually need it.
What You Need
- A color-managed NLE or grading tool (DaVinci Resolve has ACES support built in)
- Camera-native footage shot in a log or raw format
Steps
Understand the problem ACES actually solves
Different cameras (and different log profiles even from the same brand) encode brightness and color differently. Without color management, mixing footage from two camera models in one project means each clip needs separately hand-tuned correction just to match, before any creative grading even starts. ACES removes that mismatch at the source.
Learn the three pipeline stages
An Input Device Transform (IDT) converts each camera's native footage into ACES's common scene-linear working space. All grading happens in that shared space. An Output Device Transform (ODT) then converts the graded result to whatever the delivery target needs. Rec.709 for web, P3 for a digital cinema package, HDR for streaming, and so on.
Apply the correct camera-specific Input Transform
Each camera model has its own IDT matching its specific sensor and log encoding, using the wrong one (or a generic one) reintroduces the exact mismatch ACES is meant to prevent. Most modern color-managed NLEs auto-detect camera metadata and select the right IDT, but it's worth confirming manually on any unusual or older camera.
Grade in scene-linear space without baking in a look early
Scene-linear space is intentionally flat and neutral. It's a working reference space, not a look. Apply your creative grade (contrast, saturation, color balance) as a separate step on top, rather than trying to shortcut straight to a finished look before the footage is properly normalized.
Choose the right Output Transform for delivery
The ODT you pick has to match your actual delivery target. Rec.709 for a standard web export renders very differently from an HDR ODT for a streaming platform. Getting this wrong is the most common way an otherwise well-graded ACES project looks wrong once it's exported.
Decide if ACES is worth it for this project
ACES pays off clearly on multi-camera shoots, projects handed between multiple artists or facilities, or anything mastering for more than one delivery format from the same grade. A single-camera short edited and graded by one person often doesn't need the extra setup. A simpler camera-native log workflow can get there with less overhead.
Pro Tips
- Confirm your NLE's project color management settings before you start grading, not partway through, switching color spaces mid-project can shift every grade already applied.
- Keep a still-frame reference (a color chart shot, if you have one) from each camera on set. It's the fastest way to verify IDTs are actually matching cameras correctly before a full grading session.
- ACES version differences (1.x vs. 2.0) can produce different results from the same source. Confirm which version a facility or collaborator is standardized on before exchanging project files.
Knowledge Base
Scene-Linear Is a Reference Space, Not a Look
ACES's working space stores color and brightness values linearly, matching how light behaves physically rather than how a camera or display renders it. This makes it an excellent neutral space for compositing and cross-camera matching, but it looks flat and desaturated on its own. It's designed to be viewed through an Output Transform, never directly.
Why Multi-Camera and Multi-Facility Projects Benefit Most
The value of ACES scales with the number of variables in a pipeline, different camera brands, different colorists working on different tools, or delivery to multiple formats (theatrical, broadcast, streaming HDR) from one master grade. Each of those variables is a place where an unmanaged workflow can silently drift. ACES gives everyone a shared, camera-agnostic reference point.
Small Projects Pay a Real Setup Cost for Marginal Benefit
Setting up ACES correctly takes deliberate configuration: verifying IDTs, understanding which ACES version and Output Transform to target, and testing the round-trip end to end. For a single-camera, single-colorist, single-delivery project, that overhead often exceeds the problem it's solving. Matching footage from one camera to itself doesn't need a cross-camera color management system.
Where This Fits
This guide covers one specific part of colour and grading. The wider picture, grading in Resolve from a technically correct starting point through building a look that holds up across a sequence, is in Color Grading in DaVinci Resolve, which frames the discipline as a whole and links out to the detailed guides underneath it, including this one. If you are starting from scratch rather than solving a specific problem, read that first and come back here.
FAQ
Q: Do I need ACES for a simple single-camera project?
A: Usually not. ACES earns its setup overhead on multi-camera shoots mixing different camera brands, or productions with a long post pipeline touching several facilities or artists. A single-camera project graded by one person can often get consistent results with a simpler camera-native log-to-Rec.709 workflow instead.
Q: Does ACES replace LUTs?
A: Not exactly. ACES changes what a LUT is doing. Instead of a LUT trying to compensate for camera-specific color science on top of a creative look, ACES normalizes every camera into the same scene-linear space first, so a creative LUT applied afterward behaves consistently regardless of which camera shot the footage. You still use LUTs for looks. ACES makes them behave predictably across sources.
Translate this page
- Español
- 简体中文
- हिन्दी
- العربية
- Português
- Français
- Deutsch
- 日本語
- Русский
- Bahasa Indonesia
- 한국어
- Italiano
- Türkçe
- Tiếng Việt
- Polski
- Nederlands
Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.