Quick answer: pick Resolve Color Management when the project lives in Resolve, needs a clear camera-to-timeline-to-output setup and gains from native Resolve tools. Choose ACES when the main requirement is a wider production pipeline, a shared interchange standard or handoffs between applications. Neither one is automatically more “professional,” and neither rescues a camera input that was identified wrong.
The real decision is about ownership. Which system identifies the source, converts it into a working space, shows the image through a display transform and prepares the output? In Project Settings that's a single Color science choice: DaVinci YRGB Color Managed for RCM, or ACEScc/ACEScct for ACES. Trouble starts when old ACES transforms or CSTs pile up on top of that choice without a reason. The grade gets hard to audit, and LUTs start behaving unpredictably.
What both systems are trying to solve
Camera files arrive with different primaries, transfer curves and metadata. A color-managed workflow converts them into a common working space, keeps grading operations predictable and maps the result to the target display or file. Stripped down, the chain is:
camera input → working space → grade → display/output transform
ACES and RCM come from different ecosystems and use different names, but they solve the same problem: keep useful image information, make mixed cameras manageable and produce an output you can trust.
Blackmagic's DaVinci Resolve 21 Reference Manual documents Resolve Color Management, and the ACES documentation and community resources cover the ACES framework across production tools. I treat the manual as the authority on Resolve menu behavior and the ACES material as the authority on ACES terms and transforms.
Resolve Color Management in plain terms
RCM is Resolve's own color-management workflow. With Color science set to DaVinci YRGB Color Managed, you either tick Automatic Color Management (choose SDR or HDR, and Resolve picks input color spaces from the file types and codecs in the Media Pool) or turn it off and choose a preset. The project then holds the input, timeline and output spaces, and Resolve manages the transforms around your grade.
The default preset is SDR Rec.709. Many colorists switch to the DaVinci Wide Gamut preset, which pairs DaVinci Wide Gamut with DaVinci Intermediate log encoding and, per the manual, keeps highlight detail up to 10,000 nits, then map the result to Rec.709, HDR or another delivery space at the output. The right choice depends on footage and delivery, but the idea holds: the project owns the transform chain, and no clip gets an unrelated technical LUT of its own.
RCM is usually the clearest choice when you finish inside Resolve. It fits the Color page tools, output presets and camera identification, and another Resolve user can read input, timeline and output in one place. The presets don't lock you in, either: change the Output Color Space later and export another version of the same grade.
ACES in plain terms
ACES is a color-encoding and workflow framework used across applications and production stages. ACES input transforms bring cameras into an ACES working space, you grade there, and an output transform serves the display or delivery. In Resolve you set Color science to ACEScc or ACEScct (the manual favors ACEScct for most colorists, since its toe roll-off makes lifting shadows feel closer to film scans) and pick an ACES Version from 1.0.3 up to 2.0, the latest.
ACES earns its place when the project moves between Resolve, compositing, visual effects, animation, dailies or other applications that share an ACES workflow. The team gets a common vocabulary for input and output transforms, provided everyone agrees on the ACES version, configuration and handoff. Resolve also reads and writes ACES AMF 2.0 sidecar files that carry each clip's transforms through the pipeline; they need ACES 1.3 or later.
That shared vocabulary has its own learning curve. ACEScct, ACEScg, IDT and ODT aren't interchangeable menu labels. A project can be technically “in ACES” and still wrong because a camera input, display transform or LUT expects a different stage. And Resolve won't choose the ODT for you; you match it to your workflow and room.
The practical comparison
| Question | RCM | ACES |
|---|---|---|
| Where is it strongest? | Resolve-centered finishing and clear native controls | Cross-application and multi-stage production pipelines |
| Working-space language | Resolve Color Management, often DaVinci Wide Gamut/Intermediate | ACES2065-1, ACEScct, ACEScg and related spaces |
| Input setup | Resolve input color-space assignment and camera metadata | ACES input transforms/IDTs and agreed configuration |
| Output setup | RCM output color space and tone mapping options | ACES output/display transform such as an ODT path |
| Handoff risk | Lower inside Resolve; document settings for other apps | Lower when the whole pipeline already uses the same ACES config |
| Main failure mode | Double transforms or wrong input assignment | Wrong ACES config, IDT/ODT mismatch or LUT at the wrong stage |
Choose RCM when the project looks like this
- You're finishing a Resolve project, and the handoff is mostly a Resolve project archive or a final render.
- The project mixes cameras but doesn't need a formal ACES pipeline across departments.
- You want the Resolve manual, camera presets and output settings to be the main reference.
- You need several deliverables from one grade, say SDR and HDR versions, and want the output transforms visible in Project Settings.
- Your existing Resolve grades and LUTs are documented for DaVinci Wide Gamut, DaVinci Intermediate or a known display-referred path.
RCM isn't “automatic color correction.” You still assign inputs correctly, decide how tone mapping should behave and check the output on the intended display. RCM simply gives those jobs a home inside the Resolve project. One warning from the manual: once every clip is graded, the grades depend on the preset you picked.
Choose ACES when the pipeline looks like this
- Resolve is one stage among several tools, and the team has already picked an ACES version and configuration.
- VFX, compositing or animation departments need the same interchange assumptions.
- The production has a defined process for IDTs, working spaces, looks and ODTs.
- You're inheriting an ACES-managed project, and changing the color system would add more risk than it removes.
Don't bring ACES in late just because a grade feels difficult. A workflow change can shift contrast, saturation, highlight behavior and LUT response. If the project is coherent, solve the actual image problem before you swap its color management.
Where DaVinci Wide Gamut fits
DaVinci Wide Gamut and ACES get compared a lot because both offer a broad working space. They're still different color-management systems, not interchangeable labels.
The working space shapes how grading operations distribute values and how tools behave near gamut edges. A wide gamut gives the grade room; it doesn't guarantee a correct image. Input transforms, tone mapping, output transforms and the display still decide what the viewer sees.
Moving from ACES to RCM or back? Rebuild the transform chain on purpose, and don't leave every old CST and LUT switched on while you change the project mode. The site's BRAW workflow guide shows the same ownership principle for Camera RAW: one stage owns the technical conversion.
LUTs are where the two workflows often collide
A LUT expects a particular input and produces a particular output. Feed a log LUT a display-referred image and it can look crushed or oversaturated. ACES adds its own rule: node LUTs should be CLF LUTs built for ACES, and Process Node LUTs in decides whether they run in ACEScc AP1 Timeline Space (the default) or ACES AP0 Linear. A creative LUT built for an ACES stage may misbehave in a DaVinci Wide Gamut node, even when the image “looks close” before the LUT.
Before applying a LUT, record:
- the LUT’s expected input color space and gamma;
- the stage where the LUT should sit;
- the output the LUT produces;
- whether RCM or ACES will apply another transform after it.
For a manual bridge, use a CST or a documented conversion to feed the LUT exactly what it expects, then convert the result back into the project working space if needed. In ACES that's one transform out and one back, and the manual admits it doesn't always give ideal results. Drop the bridge when the managed workflow already does the same job. The site's LUT guide covers technical versus creative LUT jobs.
How to compare the workflows safely
- Duplicate the project or timeline before you touch color management.
- Choose representative clips: a normal exposure, a difficult highlight, saturated color, skin and a mixed-light shot.
- Write down the current input, timeline and output settings.
- Build one complete RCM or ACES chain; don't stack the old transform on top.
- Compare the image through the same viewing transform and on the same output target.
- Check the grade, LUTs, qualifiers, keys, mattes and deliverables after the transform change.
A color-management comparison isn't valid if one version has an extra CST, a different display transform or a hidden LUT. Compare complete chains, not isolated menu screenshots.
Common mistakes
- Using ACES and RCM at the same time without a defined bridge. Decide which system owns each transform.
- Changing the working space but keeping LUTs untouched. Reconfirm every LUT input and output assumption.
- Calling a flat image wrong. Scene-referred images often need the correct output transform before they look familiar.
- Ignoring camera metadata. A wrong input assignment can look like a grading problem.
- Switching systems in the middle of a locked grade. Test the pipeline on a duplicate and preserve a rollback path.
Decision checklist
- Does the project leave Resolve for VFX, compositing or another finishing tool?
- Has the team already standardized on ACES?
- Which camera inputs and delivery spaces must the project support?
- Where will the grade be viewed and rendered?
- Which LUTs, CSTs and plugins assume a particular input?
- Can another operator understand the transform owner from the project settings and node labels?
Pick the system that makes the complete chain easiest to explain and hand off. RCM is a strong choice for Resolve-centered work; ACES is strong when the pipeline is shared. Either way, the grade gets reliable once the project has one transform owner, documented inputs and an output transform that matches the real delivery.
