Color Space Transform Node in DaVinci Resolve

The Color Space Transform (CST) node is a Resolve FX OFX plugin that converts image data from one color space and gamma to another, directly inside a grade node. It is the primary tool for clip-level color space management when working in DaVinci YRGB — not in DaVinci Resolve Color Managed (RCM).

Understanding when and how to use CST nodes is one of the most common sources of confusion in Resolve workflows, and one of the most misrepresented topics in online tutorials.

What is the CST Node and When Do You Use It

The CST node is found in Effects > Resolve FX Color > Color Space Transform. Applied to a grade node, it performs a mathematical color space and gamma conversion on the image at that point in the node tree.

It is the correct tool when:
- You are working in DaVinci YRGB (not RCM)
- You need to convert individual clips with different input color spaces
- You want explicit control over where in the node pipeline the conversion happens
- You are preparing an image for a specific LUT that expects a defined input color space

As the Colorist Guide explains, with node-based color management via CST, "you can add more grade adjustments and effects after the color map, such as vignettes, halation, and grain" — unlike project-level RCM where the output color space is always the final step. (DaVinci Resolve 20 Colorist Guide, p. 303)

The Three Main CST Configurations

1. CST In + CST Out (Two-Node Architecture)

The most common configuration uses two CST nodes bookending the grade:

• CST In (first node): converts from camera color space → working color space
  Example: BRAW 4.6K Cinematic (Blackmagic Design Film, Blackmagic Design 4.6K Film Gen 5) → DaVinci Wide Gamut / DaVinci Intermediate
• Grade nodes in the middle: primary and secondary corrections
• CST Out (last node): converts from working color space → delivery color space
  Example: DaVinci Wide Gamut / DaVinci Intermediate → Rec. 709 / Gamma 2.4

This architecture gives you the best of both worlds: you grade in a wide-gamut scene-referred space, then deliver to a standards-compliant output.

2. Single CST Node (Grade in Camera Color Space)

Sometimes you want to work directly in the camera's native color space — keeping the log response available to your primaries — and only normalize at the output. In this case, you use a single CST node at the end of the node tree:

• Grade nodes: corrections in native camera space (log response, full gamut)
• CST Out (last node): Camera log → Rec. 709 / Gamma 2.4

This approach is particularly effective for cameras with well-characterized log formats (BRAW, ARRIRAW, Sony S-Log3) where working in log gives you more latitude in the grade.

3. CST as LUT Preparation (Gateway Node)

A less documented but powerful use case: using a CST node to convert the image into the expected input color space of a creative LUT — before applying that LUT.

Many film emulation LUTs (Kodak 2383, Fujifilm 3510) are designed to receive a Cineon Film Log input signal, not Rec. 709. If your timeline is in Rec. 709 and you apply one of these LUTs directly, the result will look wrong — washed out or oversaturated.

The correct workflow:
1. Grade node with your primary corrections (in Rec. 709)
2. CST node: Rec. 709 Gamma 2.4 → Cineon Film Log (Input: Rec. 709, Output: Cineon/Log)
3. LUT node: apply your Kodak 2383 or Fujifilm print film LUT
4. Optional final CST: Cineon Film Log → Rec. 709 (if the LUT does not already include output normalization)

This is what separates a technically correct film look from a YouTube "cinematic LUT" slapped over footage.

Key Settings in the CST Node

The CST node has four main controls:

Important: the CST node reads the image as it arrives at that point in the node pipeline. If you have already made Lift/Gamma/Gain corrections upstream, those corrections were made in whatever color space the image was in at that point — not necessarily the camera's original space. Order matters.

Common Mistakes

Mistake 1 — Using CST in a Color Managed project
If your project is set to DaVinci Resolve Color Managed (RCM) or ACES, the project itself is already handling input and output transforms. Adding a CST node on top will double-transform your image. CST nodes are for YRGB projects only, unless you explicitly want to override the project-level management for a specific clip.

Mistake 2 — Wrong Input Color Space
The CST node does not read clip metadata. You must set the Input Color Space manually to match what is actually in the clip. If your BRAW clip has been decoded in a specific color space by the RAW decode settings, that decoded output — not the camera's native format — is what the CST node receives.

Mistake 3 — Applying a print film LUT without CST preparation
A Kodak 2383 LUT applied to a Rec. 709 timeline will not look like film. It will look like a bad grade. Use the CST-to-Cineon workflow described above.

FAQ

Can I use CST nodes in DaVinci Resolve Free?
Yes. The Color Space Transform OFX plugin is available in the free version of DaVinci Resolve.

Is CST better than RCM for professional work?
Neither is objectively better. RCM simplifies multi-camera workflows with automatic input detection. CST gives you explicit per-clip control. For mixed-camera projects without a consistent camera format, CST gives you more surgical precision.

Does the CST node affect performance?
Yes, CST nodes are GPU-accelerated OFX operations. On modern hardware the impact is minimal, but on older systems or when stacking multiple CST nodes per clip, render times will increase.

Sources: DaVinci Resolve 20 Colorist Guide, p. 303 — DaVinci Resolve 20.3 Reference Manual, pp. 231–232, 265
Luca Giussani — Blackmagic Design Certified Trainer (6 modules) — lab.dcvisuals.fr