Resolve FX · Color · Color Space Transform

Color Space Transform

Color Space Transform, usually shortened to CST, is the technical Resolve FX for converting an image from one colour-space/gamma description to another. It is the core manual transform tool on the Color page when you need an explicit node-level conversion rather than a broad project-wide colour-management shortcut.

This page documents the effect itself: Input Color Space, Input Gamma, Output Color Space, Output Gamma, Tone Mapping, Gamut Mapping and related advanced switches. Broader project workflow remains on the Color Management page, while ACES Transform and Chromatic Adaptation keep their own focused references.

Controls

CST is built around one honest question: what are you converting from and to?

The panel looks longer than Color Compressor or Blur FX, but the logic is straightforward: describe the input correctly, describe the output correctly, then decide how Resolve should handle luminance range and out-of-gamut colours.

Input Color Space

Input Color Space defines the colour space of the incoming signal. This is where you describe the source honestly: use the timeline settings or choose an explicit option such as ACES, Adobe RGB, Apple Log 2 or ARRI Wide Gamut from the Resolve list. A wrong choice undermines every downstream decision.

Use timeline — inherit the project context
An explicit choice is useful for local technical transforms
Always evaluate Colour Space and Gamma together

Input Gamma

Input Gamma describes the tonal encoding of the source. Resolve 21 exposes options such as Use timeline, ACEScc, ACEScct, Apple Log, ARRI LogC3, ARRI LogC4 and Blackmagic Design Film. If gamma does not match the actual signal, CST calculates the transform from the wrong tonal model.

Gamma here is technical signal description, not creative contrast
Do not guess it from the picture alone
A common mistake is to confuse log gamma with display gamma

Output Color Space

Output Color Space defines the destination space CST should convert into. That can be Use timeline or an explicit destination such as ACES, Adobe RGB, Apple Log 2 or ARRI Wide Gamut. Choose it according to the actual pipeline rather than whatever looks nicer on screen.

The output must match the purpose of the node
Do not confuse working space with display/output space
CST is best kept on a dedicated technical node

Output Gamma

Output Gamma completes the description of the destination signal. Resolve exposes Use timeline, ACEScc, ACEScct, Adobe RGB, Apple Log, ARIB STD-B67 HLG, ARRI LogC3, LogC4 and more. Together, Output Colour Space and Output Gamma define what state the image should leave the node in.

Read Output Gamma together with Output Colour Space
A wrong pair leads to strange contrast and colour behaviour
A display-oriented output is not the same as camera log

Tone Mapping Method

Tone Mapping Method controls how Resolve remaps luminance when converting between different gammas and dynamic ranges. Resolve 21 offers None, Clip, Simple, Luminance Mapping, DaVinci and Saturation Preserving. It becomes especially important when translating HDR to SDR or moving between different display contexts.

None — no tone mapping
DaVinci — a common practical choice in Resolve
Saturation Preserving aims to preserve perceived saturation more gracefully

Gamut Mapping Method

Gamut Mapping Method defines what happens when colours fall outside the destination gamut. The Resolve panel shows None, Saturation Compression and Clip. This is not about luminance but about how saturated colours are brought into the destination space without harsh failures.

None — no additional gamut remapping
Saturation Compression — gentler behaviour for saturated colours
Clip — hard-clips values that exceed the destination gamut

Gamut Mapping + Advanced

The lower part of the panel contains Gamut Mapping and advanced switches such as Apply Forward OOTF, Apply Inverse OOTF and Use White Point Adaptation. These belong to more exact technical configuration and should be enabled only when you understand the node’s role in the wider project pipeline.

White Point Adaptation can help align white points more coherently
The OOTF options require real display-pipeline understanding
If unsure, start with a cleaner basic CST setup

Workflow

The cleaner the node intent, the safer the transform

01

Describe the input honestly

Set the real Input Color Space and Input Gamma. If the project context already describes them correctly, Use timeline can be appropriate; otherwise choose explicit values.

02

Define the output state

Choose the destination Output Color Space and Output Gamma according to the actual downstream workflow: a working space, a display space or a delivery transform.

03

Handle tone and gamut consciously

Use Tone Mapping and Gamut Mapping only when the conversion actually needs them. They are not decorative extras but technical choices about dynamic range and saturated colours.

04

Keep CST isolated in the node tree

A dedicated technical node makes CST easier to bypass, compare and debug. That is safer than hiding a transform inside broader creative grading.

CST and neighbouring tools

Do not mix node-level conversion with broader colour-management topics

CST

General node-level conversion

CST is the general-purpose effect for converting between colour-space and gamma descriptions on a specific node. It is the clean answer when you need an explicit local transform.

Color Management

Broader project pipeline

The Color Management page explains managed workflows, project-wide ACES ideas and when CST belongs in the larger pipeline. It is broader than this single FX page.

ACES Transform

ACES-specific transform logic

ACES Transform is a dedicated effect built around ACES Version plus Input/Output Transforms. Use it when the pipeline itself is ACES-centric rather than merely requiring a generic colour-space conversion.

Chromatic Adaptation

White-point adaptation inside the pipeline

Chromatic Adaptation solves a narrower problem: adapting between illuminants or white points. It can sit beside CST, but it is not a replacement for explicit input/output colour conversion.

Common mistakes

Most CST failures are context errors, not slider errors

01

Guessing the input

The most common problem is choosing Input Color Space or Input Gamma by eye instead of using real source information.

02

Mixing CST with hidden transforms

If the clip, timeline or LUT chain already transforms the image, another CST can produce double-conversion artefacts.

03

Confusing tone mapping with creative grading

Tone Mapping is about technical range handling, not about making the picture simply more pleasing.

04

Ignoring gamut behaviour

Very saturated colours can break badly when Gamut Mapping is left unresolved for the chosen destination.

Signal state, not a look

Color Space Transform: the signal-level model

The most useful mental model for CST is a contract: the node expects one specific Colour Space + Gamma pair at its input and promises another pair at its output. If either side is described incorrectly, a mathematically valid transform will still produce the wrong-looking image.

The official Colorist Guide uses CST exactly this way: Input Colour Space / Input Gamma describe the real source, while the first CST can map it into a working space such as DaVinci Wide Gamut rather than directly to a deliverable. Tone Mapping and Gamut Mapping are separate decisions layered on top of the base conversion, not mandatory enhancement switches.
Use timeline is safe only when the timeline/project really describes the signal state at that exact point in the node tree. In a manual YRGB pipeline, do not assume that automatically.

Use it when

  • manual camera input transform into a common working space
  • an explicit output transform on a dedicated technical node
  • a local conversion for one clip/branch that should not change the entire project

Choose another tool when

  • the project is already fully and correctly managed by RCM/ACES and CST would duplicate an existing transform
  • you do not know the real input gamut/gamma and are trying to guess the pair by eye

Control → signal meaning → verification

LayerWhat it meansHow to verify
Input Colour Space + GammaDefines the RGB coordinate system and transfer function of the input. This is one signal-state description, not two independent creative controls.Verify against camera metadata/documentation, not the viewer alone.
Output Colour Space + GammaDefines the signal state leaving the node: working, interchange or display/output.The next node/stage must expect exactly this pair.
Tone MappingRedistributes luminance when source and target dynamic ranges differ. None keeps the base transform without additional display-range mapping.Inspect highlight roll-off, reference white and unwanted contrast changes.
Gamut MappingDetermines what happens to colours outside the target gamut: compression and clipping behave fundamentally differently.Inspect saturated LEDs/neon/skin edges on CIE scope and RGB Parade.
OOTF / White Point AdaptationAdvanced switches alter the more exact scene↔display and white-point behaviour. They are not universal recipe switches.Document why the switch is enabled and which neighbouring transform expects it.

Production workflow

  1. 01Identify the real source state: camera gamut + camera log/transfer function.
  2. 02Decide where this node specifically should lead: working space, interchange or display/output.
  3. 03Set the four core Input/Output fields first, without creative grading or unnecessary mapping.
  4. 04Add Tone Mapping only for a real dynamic-range mismatch and Gamut Mapping only for a real gamut problem.
  5. 05Check bypass, scopes and downstream state; label the node INPUT CST / OUTPUT CST.

Diagnostics: symptom → cause → fix

Log becomes too contrasty or display output too flat

Likely cause: Input/Output Gamma is wrong or the transform is being applied twice.

Fix: Check clip tags, RCM/ACES and neighbouring CST/LUT nodes; bypass technical transforms one at a time.

Saturated colour breaks while exposure is fine

Likely cause: The target gamut is smaller than the source gamut and mapping is disabled or set to Clip.

Fix: Compare None / Saturation Compression on the problem colours and inspect the CIE scope.

Two clips from the same camera differ after CST

Likely cause: Their pre-node decode/tag state differs: RAW settings, clip colour space or camera mode.

Fix: Verify Camera Raw / clip attributes before the grade, then compare CST.

Node placement

In a manual scene-referred workflow, a common architecture is Input CST before the creative grade, grading in a wide working space, and Output CST after creative nodes. But in an RCM/ACES-managed project, the same CST can become a double transform.

Scopes / validation

Waveform/Parade reveal unexpected contrast/channel behaviour; CIE Chromaticity helps expose target-gamut excursions; HDR scopes matter when CST participates in HDR↔SDR conversion.

Managed-pipeline warning

The key question before adding CST is: ‘who already performs the input transform and who performs the output transform?’ If the answer is RCM, ACES project settings, clip tagging or another node, rule out duplication first.

Primary references used for this technical layer

Panel names are cross-checked against the Resolve 21 screenshots already shown on each page. Where Blackmagic does not publish proprietary implementation math, the article describes documented signal semantics and observable behaviour rather than inventing an algorithm.

FAQ

Color Space Transform in DaVinci Resolve: common questions

1

What does Color Space Transform do in DaVinci Resolve?

Color Space Transform converts an image from one colour space/gamma description to another. It gives explicit node-level control over input, output, tone mapping and gamut mapping.

2

How is CST different from project Color Management?

Project Color Management defines the broader colour pipeline for the whole timeline or project. CST is a local Resolve FX on a specific node, used when a manual technical transform is needed in one place.

3

Why do Input Color Space and Input Gamma matter so much?

Because they tell Resolve what the incoming signal really is. If either one is wrong, the transform starts from incorrect assumptions and the result cannot be trusted.

4

When should I use Tone Mapping?

Use Tone Mapping when the conversion has to reconcile different luminance ranges or display expectations, for example HDR-to-SDR style situations. The right method depends on the destination and the behaviour you need.

5

What is Gamut Mapping Method for?

It controls how colours that exceed the destination gamut are handled. Resolve 21 exposes None, Saturation Compression and Clip, which represent different strategies for containing saturated colours.

6

How is CST different from ACES Transform or Chromatic Adaptation?

CST is the general-purpose colour-space/gamma conversion effect. ACES Transform is centred specifically on ACES transforms, while Chromatic Adaptation focuses on illuminant or white-point adaptation inside a colour pipeline.