Resolve FX · ColorDaVinci Resolve 21

False Color

An exposure-analysis Resolve FX that replaces normal image colours with a level-coded map — either matched to supported Blackmagic camera false colour or driven by a Creative palette.

Plugin Mode

Creative / Camera

Camera Model

Sensor + mode

ISO Level

Exposure mapping

Scale / Legend

Readable overlay

What False Color actually measures

A spatial exposure map, not a colour grade

False Color takes luminance/exposure regions and replaces their normal appearance with diagnostic colours. The advantage over a scope-only view is spatial: you immediately see which exact parts of the face, window, practical, sky or shadow belong to each zone. In camera-specific mode the mapping is tied to a supported Blackmagic camera configuration, so Camera, Camera Mode, ISO and node placement all matter.

Exposure zones

Different brightness regions are replaced by diagnostic colours, making clipping, reference regions and deep shadows easy to locate spatially.

Camera matching

Specific Camera Model is intended to mirror supported Blackmagic camera false-colour behaviour rather than inventing a generic universal scale.

Diagnostic overlay

Scale, Values, Labels and Value Style make the map explainable, but they do not correct the signal. The grade still happens in separate exposure/colour tools.

Controls, one by one

The controls that change the mapping — and the controls that only change the legend

Two False Color workflows

Plugin Mode

Plugin Mode switches the effect between Creative and Specific Camera Model. Specific Camera Model reproduces the false-colour behaviour of a selected Blackmagic camera using its signal mode and ISO. Creative exposes preset/colour-band controls for a custom diagnostic or stylised map rather than a camera-matched one.

Specific Camera Model — for camera-matched monitoring
Creative — for preset/custom colour bands
Changing the mode changes the controls shown in the UI

Blackmagic camera sensor

Camera

Camera selects the Blackmagic Design model whose false-colour scale should be reproduced. The Resolve 21 menu shown here includes Cinema Camera, Pocket Cinema Camera 4K/6K, several URSA Mini and URSA Mini Pro generations, Studio Camera 4K and more. Use the actual source camera rather than a visually similar name.

The model affects how exposure zones are mapped
The camera list can vary by Resolve version
Unknown camera → do not treat the map as an exact camera meter

How the signal is encoded

Camera Mode

Camera Mode should match the camera's image mode. The current menu offers Film, Video and Extended Video. Film expects the flatter wide-dynamic-range signal, Video a more display-ready contrast response, and Extended Video sits between them. A mismatch shifts the relationship between luminance and false-colour zones.

Film / Video / Extended Video are not look presets
Match the signal state at the point where the node is placed
After a CST/LUT the signal may no longer match the camera mode

Profile sensitivity

ISO Level

ISO Level sets the ISO used for the camera-specific false-colour mapping. With the URSA Mini Pro 4.6K shown here, Resolve offers 200, 400, 800, 1600 and 3200. For technical evaluation it should match the capture setting; an arbitrary ISO changes the exposure-zone mapping and invalidates precise conclusions.

Read ISO from metadata/camera records
ISO 800 in the screenshot is an example, not a universal recipe
With a mismatch the image is still false colour, but no longer camera-accurate

Preparing the map

Pre-Processing · Blur

In the Specific Camera Model panel shown here, Pre-Processing exposes Blur. It smooths fine structure so the false-colour map is easier to read on noisy or highly detailed footage. It is not exposure correction: Blur cannot fix underexposure and should not be used as a substitute for noise reduction.

0.000 — no additional smoothing
A small amount can reduce distracting micro-zones
Judge exposure from levels, not map sharpness

How to read the map

Scale / Legend

Show Scale displays the legend, Show Values adds numeric values and Show Labels adds semantic labels for important zones. Contrast controls the readability/transparency of the legend underlay, while Value Detail changes how many numeric axis values are shown. These controls change the overlay, not the source exposure.

Show Scale — display the colour legend
Show Values / Labels — numeric and semantic annotations
Value Detail — density of numeric axis labels

Legend number format

Value Style

Value Style changes the numeric format of the legend only: Percentage uses 0–100%, Hundredths uses a 0–100 scale, and Normalized uses a 0.0–1.0 range. The false-colour mapping itself is not redefined by this display choice; only the legend's numeric notation changes.

Percentage — convenient for exposure explanations
Hundredths — 0–100 scale without the % sign
Normalized — familiar 0.0–1.0 notation

Mix with the original

Global Blend

Blend mixes the false-colour result with the original image: 1.000 shows the effect fully and 0.000 returns the original. Keep it at 1.000 when reading exposure zones. Partial blending can help as a visual comparison or creative look, but it is no longer a clean diagnostic map.

1.000 — full false-colour map
0.000 — original image
For measurement-oriented work, do not reduce Blend without a reason

False Color vs neighbouring tools

Use the map to locate exposure zones, then use the right tool to correct them

False Color

Paints exposure/luminance zones directly onto the image so their spatial location is obvious.

Waveform

Shows continuous signal levels across image width and is better for exact level relationships, clipping and matching.

Zebras

Usually flags one or two selected exposure thresholds rather than dividing the whole tonal range into a multi-colour map.

HDR / Primaries

These are correction tools. Use them after False Color shows where exposure placement needs to move.

Production workflow

A six-step False Color workflow that keeps camera context intact

The biggest mistake is not an ugly palette — it is interpreting a camera-specific map after the signal has already been transformed into a different state. Establish the signal contract first, then read the colours.

Decide whether you need camera-matched or creative false colour

Use Specific Camera Model when you need to reproduce a supported Blackmagic camera's false-colour behaviour. Use Creative when the objective is a custom palette, teaching graphic or stylised diagnostic view rather than a camera-specific exposure reference.

Match Camera, Camera Mode and ISO to the source

For Specific Camera Model, all three selections matter. Read metadata or production notes instead of guessing. A correct camera with the wrong mode or ISO can still produce a misleading exposure interpretation.

Place the effect where the signal still matches that camera state

False Color analyses the signal present at that point in the node tree. If a CST, LUT or colour-managed output transform has already changed the encoding, a camera-specific false-colour profile may no longer correspond to the original on-set monitoring relationship.

Turn on the legend and read zones before making corrections

Show Scale plus Values/Labels makes the map self-explanatory. Check clipping, near-clipping, middle-grey/reference zones and the placement of important subjects before touching exposure controls elsewhere in the grade.

Use Blur and legend controls only for readability

A little Blur can calm noisy micro-zones; Contrast and Value Detail can simplify the legend. None of these is a substitute for correcting exposure, dynamic range or noise in the actual grade.

Bypass the diagnostic node before delivery

False Color is usually a monitoring/analysis tool. Keep it in a labelled diagnostic node or branch, compare against scopes, then disable it before export unless the false-colour image is intentionally part of the final creative result.

Common failures

Most False Color mistakes come from a wrong signal assumption, not the palette itself

Symptom

The map does not match what the camera showed on set

Cause: Camera, Camera Mode, ISO or the signal state at the node does not match the original camera-monitoring configuration.

Fix: Verify metadata, select the exact supported camera profile and place the FX before transforms that change the camera encoding.

Symptom

The image is a noisy mosaic of tiny colours

Cause: Fine texture, sensor noise or compression noise is producing rapidly changing local zones.

Fix: Use a small Pre-Processing Blur for readability, but do not use it to hide an actual underexposure/noise problem in the footage.

Symptom

Legend numbers are interpreted as video IRE without checking the style

Cause: Percentage, Hundredths and Normalized are display formats for the legend and are easy to confuse with another scope's numeric convention.

Fix: Check Value Style first and use the colour zones together with Waveform/Parade when exact signal-level verification is required.

Symptom

A partially blended image is treated as a measurement

Cause: Global Blend below 1.000 mixes original colours back into the diagnostic palette.

Fix: Return Blend to 1.000 for exposure evaluation. Use lower Blend only when the mixture itself is the intended comparison or creative presentation.

Exposure as a spatial map

False Color: the signal-level model

False Color does not correct exposure and is not a LUT. It recolours the current signal into luminance/exposure zones so you can immediately see where shadows, reference regions, high levels and clipping sit within the image. In Specific Camera Model, the map is meaningful only when Camera, Camera Mode, ISO and the signal state at the node are matched correctly.

Blackmagic's official Resolve 17 New Features Guide describes Plugin Mode as the switch between Specific Camera Model and Creative. Camera-specific mode selects the exact Blackmagic sensor, dynamic-range Camera Mode and ISO, while Scale/Legend separately controls the scale, numbers and labels. These are two different layers: signal mapping and legend presentation.

Camera-specific false colour does not automatically analyse the source metadata; it analyses the RGB signal that actually reaches the FX. If a CST, LUT, RCM output transform or other normalisation already precedes it, the selected Film/Video/Extended Video profile may no longer describe the current signal.

Use it when

fast spatial exposure checks for faces, windows, practicals, sky and deep shadows
reproducing supported Blackmagic camera false-colour monitoring when Camera Mode and ISO are known
teaching and technical demonstrations where Scale/Values/Labels make levels understandable directly on the image

Choose another tool when

camera/mode/ISO are unknown but you want exact camera-specific conclusions
you need precise continuous signal-level measurement — use Waveform/Parade alongside False Color
you need to actually change exposure or tonal balance — that belongs to Primaries/HDR/Curves, not the diagnostic overlay

Control → signal meaning → verification

Layer	What it means	How to verify
Plugin Mode	Specific Camera Model enables camera-matched mapping; Creative exposes preset/custom Colour Bands for a freer false-colour visualisation.	Decide the task first: on-set camera reference or a creative/teaching palette.
Camera + Camera Mode + ISO	The three controls together describe the camera-specific exposure scale: sensor/model, dynamic-range response and sensitivity setting.	Verify against the real camera, Film/Video/Extended Video mode and ISO from metadata/production notes.
Pre-Processing · Blur	Smooths fine structure/noise for a calmer map. In the shown Resolve 21 Specific Camera Model panel, this is the visible pre-processing control.	Do not confuse overlay readability with fixing noise/exposure in the source itself.
Scale / Legend	Show Scale, Show Values and Show Labels control the legend; Contrast affects legend readability/underlay and Value Detail changes the number of numeric labels.	These settings should not be interpreted as tonal correction of the image.
Value Style	Chooses the legend's numeric notation: Percentage 0–100%, Hundredths 0–100, or Normalized 0.0–1.0.	Check the selected format before comparing legend numbers with a scope.
Global Blend	Mixes the full false-colour result with the original: 1.000 is the full overlay and 0.000 is the original image.	For diagnostic zone reading use 1.000; partial Blend changes the perceived map colours.

Production workflow

01Decide whether you need camera-matched Specific Camera Model or a Creative palette.
02For camera-specific mode, set the real Camera, Camera Mode and ISO.
03Place the FX where the node-tree signal still matches the selected camera mode; audit any CST/LUT/RCM stages around it.
04Enable Scale/Values/Labels, read the zones, then change exposure on a separate correction node.
05Verify the decision on Waveform/Parade and disable the diagnostic FX before delivery unless false colour is intentionally part of the final look.

Diagnostics: symptom → cause → fix

Resolve shows different false-colour zones from the camera on set

Likely cause: Camera/Mode/ISO mismatch, or the FX is placed after a transform that already changed the camera encoding.

Fix: Verify metadata and move the FX before normalisation/output transforms, or use a mode that actually matches the current signal state.

The map is excessively speckled on noisy footage

Likely cause: Noise/fine detail crosses several colour zones and creates micro-flicker in the overlay.

Fix: Add a small Pre-Processing Blur for readability only; solve the real noise problem separately in the grade.

Legend numbers do not match the expected scope convention

Likely cause: A different Value Style is selected, or legend numbers are being interpreted as IRE/another scale.

Fix: Check Percentage/Hundredths/Normalized and use Waveform for exact signal-level verification.

The map becomes hard to read below Blend 1.0

Likely cause: Original colour is mixing with the diagnostic palette and reducing zone clarity.

Fix: Return Blend to 1.000 for analysis; reserve partial Blend for presentation/creative use.

Node placement

For camera-specific analysis, False Color should sit where the current RGB signal still corresponds to the selected Camera Mode. In a manual YRGB pipeline this is often before a display/output CST or LUT. In RCM/ACES, know whether you are analysing camera-encoded, working-space or display-referred data; the same camera profile cannot be moved blindly between those states.

Scopes / validation

False Color answers 'where in the image is this zone?', while Waveform/Parade answers 'what signal level is actually there?'. Use them together for confident exposure work. Vectorscope is secondary here and is more relevant when checking colour behaviour after the actual grade correction.

Managed-pipeline warning

False Color does not perform colour management. It visualises the signal state it receives. RCM/ACES/CST must therefore be configured independently, and a camera-specific profile must correspond to the exact stage being analysed. Creative mode is safer when you need a general visual diagnostic without claiming camera-matched thresholds.

Do not confuse the roles

False Color versus the neighbouring Color FX

Color Space Transform

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

False Color

A spatial exposure map, not a colour grade

Exposure zones

Camera matching

Diagnostic overlay

The controls that change the mapping — and the controls that only change the legend

Plugin Mode

Camera

Camera Mode

ISO Level

Pre-Processing · Blur

Scale / Legend

Value Style

Global Blend

Use the map to locate exposure zones, then use the right tool to correct them

False Color

Waveform

Zebras

HDR / Primaries

A six-step False Color workflow that keeps camera context intact

Decide whether you need camera-matched or creative false colour

Match Camera, Camera Mode and ISO to the source

Place the effect where the signal still matches that camera state

Turn on the legend and read zones before making corrections

Use Blur and legend controls only for readability

Bypass the diagnostic node before delivery

Most False Color mistakes come from a wrong signal assumption, not the palette itself

The map does not match what the camera showed on set

The image is a noisy mosaic of tiny colours

Legend numbers are interpreted as video IRE without checking the style

A partially blended image is treated as a measurement

False Color: the signal-level model

Use it when

Choose another tool when

Control → signal meaning → verification

Production workflow

Diagnostics: symptom → cause → fix

Node placement

Scopes / validation

Managed-pipeline warning

False Color versus the neighbouring Color FX

Primary references used for this technical layer

Practical questions about False Color in Resolve

Is False Color more accurate than the Waveform?

Can I use Specific Camera Model on footage from another brand?

Does Value Style change the exposure thresholds?

Should False Color stay in the render?

Build False Color into a repeatable exposure-check workflow

Despill

Scopes

Color Management

Gamut Limiter