ACES vs DaVinci Resolve Color Management: Which Color Workflow Fits Your Project?

Quick answer: choose Resolve Color Management when the project is built around Resolve, needs a clear camera-to-timeline-to-output setup, and benefits from native Resolve tools. Choose ACES when a wider production pipeline, shared interchange standard or cross-application handoff is the main requirement. Neither system is automatically more “professional,” and neither fixes a badly identified camera input.

The real decision is about ownership. Which system will identify the source, convert it into a working space, show the image through a display transform and prepare the output? Once both ACES and RCM are active in the same project without a clear reason, the grade becomes hard to audit and LUTs begin to behave unpredictably.

What both systems are trying to solve

Camera files arrive with different primaries, transfer curves and metadata. A color-managed workflow converts those inputs into a common working space, keeps grading operations predictable and maps the result to the target display or file. The simplified chain is:

camera input → working space → grade → display/output transform

ACES and RCM use different ecosystems and naming, but the reader-facing problem is the same: preserve useful image information, make mixed cameras manageable and produce a reliable output.

Blackmagic’s DaVinci Resolve 21 Reference Manual documents Resolve Color Management, while the ACES documentation and community resources describe the ACES framework and its application across production tools. Treat the manual as the source for Resolve menu behavior and ACES documentation as the source for ACES terminology and transforms.

Resolve Color Management in plain terms

RCM is Resolve’s native color-management workflow. You select the input color space for media, a timeline working space and an output color space. Resolve then manages the transforms around the grade according to the project settings.

A common current setup uses a wide-gamut, scene-referred timeline such as DaVinci Wide Gamut with DaVinci Intermediate, then maps the result to Rec.709, HDR or another delivery space at the output. The exact choice depends on the footage and delivery, but the key idea is consistent: the project owns the transform chain instead of each clip receiving an unrelated technical LUT.

RCM is often the clearest choice when you are finishing inside Resolve. It works naturally with Resolve’s Color page tools, output presets and camera identification. It also makes it easier to explain the project to another Resolve user: input, timeline and output are visible in one place.

ACES in plain terms

ACES is a color-encoding and workflow framework used across applications and production stages. A project can use ACES input transforms to bring cameras into an ACES working space, grade there, then apply an output transform for the display or delivery.

ACES becomes attractive when the project moves between Resolve, compositing, visual effects, animation, dailies or other applications that share an ACES workflow. It gives the team a common vocabulary for input and output transforms, provided everyone agrees on the ACES version, configuration and expected handoff.

That shared vocabulary comes with its own learning curve. Names such as ACEScct, ACEScg, IDT and ODT are not interchangeable menu labels. A project can be technically “in ACES” while still being wrong because a camera input, display transform or LUT expects a different stage.

The practical comparison

Choose RCM when the project looks like this

• You are finishing a Resolve project and the handoff is mainly a Resolve project archive or final render.
• The project mixes camera sources but does not require 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 the same grade, such as SDR and HDR versions, and want 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 is not “automatic color correction.” You still have to assign inputs correctly, decide how tone mapping should behave and check the output on the intended display. The advantage is that the system makes those responsibilities part of a Resolve project model.

Choose ACES when the pipeline looks like this

• Resolve is one stage among several tools and the team has already selected 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 are inheriting an ACES-managed project and changing the color system would create more risk than it removes.

Do not introduce ACES late in a project just because a grade feels difficult. A workflow change can alter contrast, saturation, highlight behavior and LUT response. If the current project is coherent, solve the actual image problem before replacing its color-management system.

Where DaVinci Wide Gamut fits

DaVinci Wide Gamut and ACES are often compared because both provide a broad working space. They are not the same color-management system and should not be treated as interchangeable labels.

The working space affects how grading operations distribute values and how tools respond near gamut boundaries. A wide gamut gives the grade room, but it does not guarantee a correct image. Input transforms, tone mapping, output transforms and the display still determine what the viewer sees.

If you move from ACES to RCM or the other way around, rebuild the transform chain deliberately. Do not simply keep every old CST and LUT enabled while changing the project mode. The site’s BRAW workflow guide shows the same ownership principle for Camera RAW: one stage should own the technical conversion.

LUTs are where the two workflows often collide

A LUT expects a particular input and produces a particular output. A LUT made for log footage can look crushed or over-saturated when fed a display-referred image. A creative LUT designed for an ACES stage may not behave correctly 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 documented conversion to feed the LUT exactly what it expects, then convert the LUT result back into the project working space if required. Remove the bridge when the managed workflow already performs the same operation. The site’s LUT guide covers technical versus creative LUT jobs.

How to compare the workflows safely

1. Duplicate the project or timeline before changing color management.
2. Choose representative clips: a normal exposure, a difficult highlight, saturated color, skin and a mixed-light shot.
3. Write down the current input, timeline and output settings.
4. Build one complete RCM or ACES chain without stacking the old transform on top.
5. Compare the image through the same viewing transform and on the same output target.
6. Check the grade, LUTs, qualifiers, keys, mattes and deliverables after the transform change.

A color-management comparison is not valid when one version uses 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 Resolve-centered choice; ACES is a strong shared-pipeline choice. The grade becomes reliable when the project has one transform owner, documented inputs and an output transform that matches the real delivery.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.