Resolve FX · ColorFree · hard gamut limitDaVinci Resolve 21

Gamut Limiter

A technical Resolve FX that hard-limits colour values to a specified gamut — useful when a large delivery gamut must contain content restricted to a smaller QC gamut.

Current Gamut
Describe input primaries
Current Gamma
Describe current encoding
Limit Gamut to
Hard target boundary

What the limiter actually does

It enforces a boundary; it does not gracefully compress colour into it

Blackmagic describes Gamut Limiter as a hard-clipping operation. Values outside the selected target gamut are forced to the boundary. That makes the FX predictable for compliance, but it also means colour differences beyond the boundary can be destroyed. It should therefore be treated as a late technical guard, not as the first tool for taming difficult saturation.

1. Describe current signal

Current Gamut + Current Gamma tell Resolve how to interpret the RGB values entering the FX.

2. Define the legal boundary

Limit Gamut to is the smaller target gamut demanded by the mastering or delivery specification.

3. Clip excursions

Colours outside that target are hard-clipped, so the result cannot exceed the selected gamut boundary.

Practical example only: Rec.2020 container / P3 content boundary

If a real mastering or delivery specification uses a Rec.2020 signal/container but restricts mastered chromaticities to a particular P3 boundary, Gamut Limiter can enforce that boundary at the appropriate output stage. This is an example of how the FX is used, not a replacement for the Rec.2020 or P3 theory: the exact P3 variant, white point, transfer function and measurement method still come from the specification.

The standards themselves are already covered in the Color Science section. Follow the chapters below when you need the underlying colourimetry rather than the operation of this Resolve FX.

Inspector controls

Only three fields — but all three are part of one technical contract

The tool is simple only when the signal state is known. Current Gamut and Current Gamma describe the input; Limit Gamut to defines the legal output boundary. A mistake in either current-state field changes what the limiter thinks is out of gamut.

Where the RGB coordinates live now

Current Gamut

Current Gamut describes the colour gamut of the signal at the exact point where Gamut Limiter is placed. Use timeline is convenient when the image really is in the Timeline Colour Space. If a CST, DCTL, LUT or another transform before the limiter has moved the signal into a different gamut, Use timeline is no longer automatically correct — Current Gamut must describe the actual node input.

Use timeline — inherit the timeline gamut when that is genuinely the current state
ACES AP0/AP1, Adobe RGB, ARRI Wide Gamut, Blackmagic and others — explicit current-gamut descriptions
A wrong Current Gamut makes the limiting boundary mathematically wrong
How RGB luminance is encoded

Current Gamma

Current Gamma specifies the current signal transfer function: ACEScc/ACEScct, Apple Log, ARRI LogC, HLG, Blackmagic Design Film and other options. The limiter needs the encoding as well as the primaries/gamut so it can interpret RGB correctly before testing the boundary. Use timeline is valid only when the gamma at this point in the node tree genuinely matches Timeline Gamma.

Gamma is part of the signal contract, not a look preset
After an output CST/PQ/HLG transform, describe the new current encoding
Gamut and Gamma must be treated as one coherent pair
Hard boundary for the allowed gamut

Limit Gamut to

Limit Gamut to chooses the gamut within which the final colours must remain. This is not a soft compression model: Resolve FX Gamut Limiter is a limiting operation and hard-clips values that fall outside the selected boundary. The key point here is the limiter behaviour and the correct target from the delivery/QC specification; Rec.2020, P3 variants and gamut mapping are covered separately in the Color Science chapters rather than duplicated here.

This is a hard clip, not perceptual gamut compression
Choose the target from the delivery/QC specification, not by eye
After clipping, downstream nodes cannot recover the lost out-of-gamut differences

Limiter vs neighbouring tools

Use clipping for compliance; use mapping and grading to preserve appearance

Gamut Limiter

Hard-clips values outside a specified gamut. Predictable boundary, but it can destroy separation beyond that boundary.

Gamut Mapping

Remaps/compresses problematic colours into a target gamut to preserve more hue and saturation relationships.

Color Compressor

Targeted creative/technical compression around a selected colour; useful upstream when only a local hue region is causing trouble.

CST / RCM

Transforms between colour-space descriptions. A transform may also contain gamut mapping, but it is not automatically the same as a final compliance limiter.

Compliance workflow

Six steps from delivery spec to a verified gamut boundary

Do not start by choosing a smaller gamut from the dropdown. Start by documenting the required output, then prove the signal state entering the limiter and verify the result on appropriate scopes.

01

Read the delivery requirement first

Use Gamut Limiter because a specification requires a hard gamut boundary — not because saturated colours simply look uncomfortable. Write down the container/output gamut and the smaller allowed content gamut before touching the FX.

02

Identify the signal at this exact node

Ask what gamut and gamma the pixels have here, after every upstream CST, LUT, DCTL and colour-management stage. The limiter does not infer a custom manual transform chain for you.

03

Set Current Gamut and Current Gamma

Use timeline only when the current signal really matches timeline state. Otherwise choose the explicit current gamut/gamma pair that describes the node input.

04

Choose the required target gamut

Set Limit Gamut to the actual QC boundary: for example P3-D65 inside a Rec.2020 deliverable when the specification says so. Do not substitute Rec.709, P3 or another standard just because it is familiar.

05

Inspect saturated edge cases on scopes

Use CIE Chromaticity when available to see gamut excursions directly, then check RGB Parade/Viewer for hard-channel behaviour, hue discontinuities and gradients in LEDs, neon, graphics and synthetic colours.

06

Keep the limiter near the end

Because out-of-bounds colours are hard-clipped, do creative saturation, hue shaping and smooth gamut mapping before the limiter. Use the limiter as a final compliance guard rather than an early grading tool.

Common failures

Most Gamut Limiter problems are either a signal-state mismatch or too much hard clipping

Symptom

Colours change far more than expected

Cause: Current Gamut or Current Gamma does not describe the actual signal at the limiter input.

Fix: Audit the node tree from the previous technical transform forward. Replace Use timeline with an explicit pair when the signal has already left timeline space.

Symptom

Neon/LED gradients posterise or flatten

Cause: The target gamut is much smaller and the limiter is hard-clipping a large cloud of colours onto the boundary.

Fix: Use gamut compression/mapping upstream to preserve separation, then keep Gamut Limiter only as the final guard if QC still requires a strict boundary.

Symptom

The CIE scope still shows an unexpected excursion

Cause: The limiter is not the last colour-changing operation, or the scope is viewing a different processing stage/output than the limiter target.

Fix: Check timeline/clip node order, group/timeline nodes and output transforms. Confirm what stage the scope is actually monitoring.

Symptom

The image looks legal but saturated detail is gone

Cause: Compliance was achieved by hard clipping rather than by preserving colour relationships through mapping.

Fix: Treat the limiter as a compliance test/guard. Shape problematic colours upstream with Gamut Mapping, Color Compressor, curves or targeted grading before the final limit.

A compliance boundary, not a creative saturation tool

Gamut Limiter: the signal-level model

Think of Gamut Limiter as a late technical barrier: it receives RGB described by a known Current Gamut + Current Gamma pair, tests those values against the selected Limit Gamut to boundary and hard-clips values outside the target. That makes compliance predictable, but clipping is irreversible — colour differences beyond the boundary can disappear.

The effect has a three-field contract. Current Gamut and Current Gamma must describe the real signal state entering the node, while Limit Gamut to must match the delivery/QC specification. Use timeline is convenient inheritance of timeline state, but it stops being true after a manual CST/DCTL/LUT if that transform changed gamut or gamma before the limiter.
Blackmagic explicitly describes Gamut Limiter as a hard-clipping limiting operation and recommends keeping it among the last operations in the node tree. If the goal is to preserve colour relationships inside a smaller gamut, use gamut mapping/compression first and keep the limiter only as a final guard.

Use it when

  • delivery in a large container gamut with a smaller allowed content gamut — for example a Rec.2020 container with a P3 QC boundary
  • a final guard after gamut compression when the specification requires a strict chromaticity boundary
  • a manual node-based pipeline where an explicit local gamut limit is needed independently of RCM

Choose another tool when

  • you need to preserve smooth hue/saturation relationships artistically — hard clipping is too blunt for that
  • Current Gamut/Gamma are unknown or the node sits at an ambiguous point between technical transforms
  • the project output transform already performs sufficient gamut limiting/compression and a second limiter is unnecessary

Control → signal meaning → verification

LayerWhat it meansHow to verify
Current GamutDescribes the primaries/gamut of RGB entering the effect. Use timeline inherits the timeline gamut; explicit options are needed when an upstream transform has already changed the state.Audit upstream CST/DCTL/LUT, Group/Timeline nodes and project colour management. Do not choose a camera gamut by name if the signal has already been normalised.
Current GammaDescribes the transfer function of the current RGB values. A gamut boundary cannot be applied correctly if the numeric encoding is interpreted incorrectly.Check whether Log has already been converted to PQ/HLG/display gamma or another working gamma before this node.
Limit Gamut toChooses the smaller gamut that chromaticities must not exceed. Out-of-bound values are hard-clipped to the boundary.The target must come from the mastering/QC specification: Rec.709, P3-D65, P3-DCI or another exact standard are not interchangeable.
Hard clippingSeveral different out-of-gamut colours can collapse onto the same boundary, so local colour separation can disappear after the limiter.Test neon, saturated LEDs, synthetic gradients, graphics and skin near saturated sources in the Viewer + CIE scope.
PlacementBecause clipping is irreversible, creative hue/sat work, gamut compression and most look operations should happen earlier.There should be no unexpected saturation/colour transform after the limiter that pushes chromaticities outside the required boundary again.

Production workflow

  1. 01Write down the delivery container/output gamut and the separately allowed content/QC gamut.
  2. 02Trace the signal state to the Gamut Limiter input and identify the actual Current Gamut + Current Gamma.
  3. 03Use Use timeline only when the signal genuinely matches timeline state; otherwise set an explicit pair.
  4. 04Choose Limit Gamut to strictly from the specification, not from how saturated the image looks.
  5. 05Check CIE Chromaticity, RGB Parade and problematic saturated shots; if clipping looks ugly, perform gamut mapping/compression upstream first.
  6. 06Keep the limiter among the final colour-changing stages and re-check the final monitored/output state.

Diagnostics: symptom → cause → fix

Enabling the limiter unexpectedly changes much of the colour palette

Likely cause: Current Gamut/Gamma do not match the signal, so Resolve is evaluating the boundary in the wrong system.

Fix: Audit the previous technical transform and explicitly set the current pair instead of Use timeline if the signal state has changed.

Neon/LED colours become legal but flatten into similar hue/saturation

Likely cause: A large cloud of colours is being hard-clipped onto the same target boundary.

Fix: Compress the gamut smoothly upstream and use the limiter only for remaining excursions.

The scope is legal at the limiter but excursions return at output

Likely cause: A saturation/transform stage exists after the limiter, or the scope is monitoring a downstream stage with another colour-space conversion.

Fix: Check Group Post-Clip, Timeline nodes, output CST/DRT and the scope monitoring point; move the limiter later if necessary.

P3 is selected but QC still fails

Likely cause: The wrong P3 variant/white point is selected, Current Gamma is wrong, or the delivery spec is checking a different signal-stage/metadata combination.

Fix: Verify the exact target standard, white point, transfer function, output metadata and QC measurement method.

Node placement

Gamut Limiter belongs among the final colour-changing operations. In a manual YRGB pipeline it often sits after an output transform, or at the stage where the signal is already in the delivery container gamut and must be restricted to a smaller content gamut. In managed RCM/ACES, first check whether the Output Transform/Limit Output Gamut To function already handles the requirement at project level. Do not duplicate hard limiting without a reason.

Scopes / validation

CIE Chromaticity is the primary diagnostic scope for the gamut boundary itself because it shows chromaticity positions relative to primaries/standards. RGB Parade helps reveal channel clipping/flattening and Vectorscope shows general saturation/hue structure, but a normal Vectorscope does not replace exact target-gamut verification. Use the Viewer to find posterisation and lost colour separation.

Managed-pipeline warning

Resolve FX Gamut Limiter can be used whether RCM is enabled or not. However, RCM also offers project-level Limit Output Gamut To and CST can perform gamut mapping. Assign one stage responsibility for appearance-preserving mapping, then one final stage for strict limiting if the specification actually requires it. Avoid stacking multiple unknown compressors/limiters.

Do not confuse the roles

Gamut Limiter versus the neighbouring Color FX

Color Space Transform

explicit conversion between colour-space/gamma descriptions, including tone/gamut mapping

Open guide
ACES Transform

node-level input/output through the standardised ACES transform set

Open guide
Chromatic Adaptation

conversion between white points / illuminants through a CAT model

Open guide
Color Compressor

compressing hue/saturation/luminance variation around a selected Target Color

Open guide
Color Stabilizer

temporal matching of unwanted brightness/white-balance drift around a chosen reference and analysis region

Open guide
Contrast Pop

selective increase or reduction of local contrast at a chosen structure scale and within a controlled tonal range

Open guide
DCTL

programmable host for custom transform code whose maths, UI and signal contract are defined by the selected DCTL/DCTLE

Open guide
Dehaze

depth-weighted reduction of smog/airlight/haze through a simulated depth matte and coupled colour/contrast correction

Open guide
Despill

suppression of reflected red/green/blue screen spill after the subject has already been isolated by key/matte/roto

Open guide
False Color

spatial display of exposure zones through camera-matched or creative false-colour mapping and a legend

Open guide
Gamut Mapping

tone/gamut remapping through luminance roll-off, saturation compression/clip and OOTF without a separate input/output colour-space conversion

Open guide
Invert Color

simple independent inversion of Red/Green/Blue/Alpha channels for creative and technical channel/key operations

Open guide
NVIDIA RTX Video HDR

AI-assisted SDR→HDR mapping with an explicit input/output signal contract, Middle Gray, target peak luminance and creative shaping

Open guide
Camera Shake

procedural Pan/Tilt/Rotation/Zoom motion with waveform, randomness, pauses and blanking handling

Open guide
ColorTone Diffuser

creative optical-look effect combining spatial diffusion, coloured Tone Lights, tonal protection, a falloff mask and a LUT-compatible subset

Open guide
Film Damage

procedural texture/look effect combining blur/colour drift, vignette, changing dirt and up to five scratches with motion/flicker

Open guide
Film Grain

procedural film-style texture with gauge presets, grain geometry, composite modes, tonal/RGB weighting and final mix

Open guide
Film Look Creator

integrated scene-referred film-emulation environment combining a baked-in Blackmagic film response, colour shaping, halation/bloom/grain/flicker/gate weave and a LUT-compatible subset

Open guide
Flicker Addition

dedicated temporal exposure modulation with tonal flicker modes, RGB selection, smoothness, randomness, pauses and a deterministic seed

Open guide
Halation

film-style highlight scatter using an isolation matte, chromatic dye-layer reflections, secondary glow and optional grain

Open guide
Split Tone

creative shadow/highlight colour separation through Natural/Strong/Custom modes, Pivot, Hue Angle, neutral protection and colour-space overrides

Open guide
Vignette

edge framing and visual-attention control through Basic/Advanced geometry, position, colour and compositing

Open guide
Color Generator

solid-colour generation for Layer Mixer, masks, fills and simple colour washes

Open guide

FAQ

Practical questions about Gamut Limiter

Is Gamut Limiter the same as Gamut Mapping?

No. Gamut Limiter enforces a hard boundary by clipping out-of-gamut values. Gamut Mapping/compression attempts to remap colours into the target gamut while preserving more relationships and gradation. They can be used together, with mapping first and a limiter last when a strict QC boundary is required.

What does Use timeline mean?

It tells the FX to use the project/timeline gamut or gamma as its description of the current signal. That is correct only if the signal at this node still matches timeline state. A manual CST or other transform before the limiter can make an explicit setting necessary.

Why is Current Gamma needed if the tool limits gamut?

Because RGB values must be interpreted in their actual encoding before a colour-space boundary operation can be applied correctly. Primaries without the transfer function are an incomplete description of the signal state.

Should I always place it on a Timeline node?

Not always. A Timeline node is useful when one output compliance rule applies to the whole program, but the correct position depends on your output transform and node architecture. The key rule is that the limiter should see the signal state you describe in Current Gamut/Gamma and should be after most creative colour operations.

Does Gamut Limiter have a Blend control?

The panel shown in Resolve 21 exposes Current Gamut, Current Gamma and Limit Gamut to. There is no Global Blend control in this UI; the effect is intended as a deterministic technical limiting stage rather than a creative mix.

Can I use it without Resolve Color Management?

Yes. Blackmagic documents the Resolve FX Gamut Limiter as usable whether Resolve Color Management is enabled or not. In a manual DaVinci YRGB pipeline, however, you are responsible for describing the current gamut/gamma correctly.