RGB
Red, Green and Blue are independent switches, so full and selective channel inversions are both possible.
A deliberately simple Resolve FX: independently invert Red, Green, Blue and Alpha. Its power is not a large control panel but precise channel-level utility — from full RGB inversion to technical alpha/key workflows.
What the effect actually is
Blackmagic's Resolve FX documentation describes Invert Color as a small Color-category plugin that can invert any colour channel, including Alpha, and explicitly says it is not a film-negative plugin. That distinction matters: the tool performs a simple inversion, while real negative conversion is a broader colour-science problem.
Red, Green and Blue are independent switches, so full and selective channel inversions are both possible.
Alpha can be inverted without touching RGB — one reason the plugin is useful in technical matte/key workflows.
The operation is intentionally simple. Do not attribute film response, tone curves or gamut mapping to it.
The visual result depends on the values reaching the node, so placement around log/display transforms matters.
Control breakdown
RGB inversion changes colour components. Alpha inversion changes transparency/matte information. Keep those two layers conceptually separate.
The three checkboxes work independently. With Red, Green and Blue enabled, Resolve applies a simple inversion to all three colour channels. If only one or two channels are enabled, only those components are inverted, so the result is not merely a bright/dark ‘negative’ but a major change in RGB channel relationships. This is a technical channel operation, not a film-stock model.
Invert Alpha inverts the image's alpha component. In a conventional RGBA representation this reverses the transparency relationship: regions closer to opaque become closer to transparent and vice versa. Blackmagic specifically calls out advanced workflows where Alpha or Key channels need to be inverted. Do not confuse image alpha passing through the OFX with the node graph's separate Key Input/Output routing — verify which data actually reaches the effect.
Channel combinations
| Enabled | What changes | Typical reason | Main caution |
|---|---|---|---|
| R + G + B | All colour channels | Full RGB inversion / negative-like creative result | Still not a film-negative conversion model |
| R | Red only | Channel test, asymmetric transform, stylisation | Large hue shift is expected |
| G | Green only | Channel utility / creative colour separation | Do not mistake the result for colour correction |
| B | Blue only | Channel utility / creative colour separation | Node placement changes the visual meaning |
| Alpha | Alpha only | Invert transparency/matte while preserving RGB | Requires meaningful alpha/key data and composite verification |
Production workflow
The checkboxes are trivial; the important part is signal intent, node placement and verifying the correct channel or matte downstream.
RGB inversion, a single-channel utility and alpha inversion solve different problems. Do not start by enabling every checkbox merely because the default screenshot shows all RGB channels selected.
A dedicated node makes the channel operation explicit, easy to bypass and easy to place before or after other transforms without losing track of the signal state.
For a full mathematical colour inversion enable R, G and B. For channel diagnostics or an intentionally asymmetric transform, enable only the required channels and leave the others untouched.
If the goal is matte inversion, disable RGB inversion unless it is also required. Inspect the alpha/key result directly and verify the downstream composite instead of judging the colour image alone.
A simple numeric/channel inversion is signal-state dependent. Log, linear and display-referred values are different representations, so the same channel operation can look very different depending on where the node sits.
Compare the node on/off, inspect RGB/alpha or the composite as appropriate, and make sure a temporary technical inversion has not accidentally been left active in the final delivery chain.
What it is good for
Invert all RGB channels for a direct stylised negative-like image, then grade the result deliberately rather than calling it film emulation.
Invert an existing alpha/matte without rebuilding the isolation from scratch.
Temporarily invert a single component to expose channel-specific behaviour in a controlled technical test.
Use the effect as one explicit channel operation inside a larger node/composite workflow rather than expecting it to solve the entire look.
Common failures
Cause: Invert Color is a simple channel inversion. It does not model film density, orange mask, characteristic curves, spectral dye behaviour or scanner transforms.
Fix: Use Invert Color only for the inversion step. A real negative-conversion workflow requires the appropriate film/scanner colour model, curves or dedicated transform after/before it.
Cause: Only one RGB component was reversed while the other two stayed unchanged, so the channel relationships no longer resemble the original colour balance.
Fix: That is expected behaviour. Enable all RGB channels for full inversion, or keep the selective setup only when the asymmetric channel transform is intentional.
Cause: The current clip/node may not carry meaningful alpha, or the Viewer is showing RGB without a composite where transparency is visible.
Fix: Inspect alpha/highlight/key routing and test it in the downstream composite. Confirm that the data you intend to invert actually reaches the OFX.
Cause: The effect is operating on a different numeric/encoding state. Inverting camera-log values is not the same operation as inverting the display-referred result after a transform.
Fix: Choose the node position from the intended signal contract. Do not move a technical inversion across CST/DCTL/LUT stages without re-evaluating what the operation is supposed to mean.
Invert Color should be read literally: it performs per-channel inversion of Red, Green, Blue and Alpha. Blackmagic explicitly notes that the effect is not a film-negative plugin. A technically sound workflow therefore starts by asking which channel must be inverted and in which signal state the operation is supposed to happen, not by treating it as a generic negative-look tool.
| Layer | What it means | How to verify |
|---|---|---|
| Invert Red | Inverts only the Red component while Green/Blue remain uninverted. | RGB Parade + Viewer: a large hue shift from single-channel inversion is expected. |
| Invert Green | Inverts the Green component independently of the other RGB channels. | Compare the node on/off and inspect the green trace on Parade. |
| Invert Blue | Inverts the Blue component independently of Red/Green. | Check the blue trace and visual hue relationships, especially around log/display transforms. |
| RGB together | With Red + Green + Blue enabled, the result is full RGB inversion; it is mathematically negative-like but not film emulation. | Viewer + Parade; also verify node placement and the downstream transform. |
| Invert Alpha | Inverts the alpha component while RGB can remain unchanged. | Highlight/matte view, Key routing and the final composite — not only the regular RGB Viewer. |
Likely cause: A film/scanner colour model is being expected from a plugin that does not contain one.
Fix: Use Invert Color only as the inversion step; build the remaining negative-conversion stages separately.
Likely cause: One RGB component is inverted while the other two are not, radically changing channel relationships.
Fix: This is expected. Enable all RGB for full inversion; use selective mode only deliberately.
Likely cause: The pass has no meaningful alpha, or the Viewer is not showing a composite/transparency result.
Fix: Inspect matte/highlight/key routing and the downstream composite.
Likely cause: Values in a different encoding/domain are being inverted.
Fix: Define the signal contract and place Invert Color in the domain where the operation has the intended meaning.
Invert Color has no universal correct position. A creative display-referred negative-like look belongs where you intend to invert the visible display representation. A technical channel/alpha operation belongs near the stage whose data it must change. The key rule is not to move the inversion across colour-space/gamma transforms while assuming the meaning remains identical.
For RGB, the primary technical scope is RGB Parade because it shows Red/Green/Blue separately before and after selective inversion. Vectorscope is a secondary check for hue/saturation relationships. For Alpha, the decisive tools are matte/highlight view, Key routing and the final composite rather than an RGB waveform.
RCM/ACES does not automatically make Invert Color semantically colour-managed: the OFX still processes the values at its position in the pipeline. For creative channel inversion, deliberately choose the stage. For alpha/key utility, keep it outside unrelated transform stages as far as the specific composite routing allows.
explicit conversion between colour-space/gamma descriptions, including tone/gamut mapping
node-level input/output through the standardised ACES transform set
conversion between white points / illuminants through a CAT model
compressing hue/saturation/luminance variation around a selected Target Color
temporal matching of unwanted brightness/white-balance drift around a chosen reference and analysis region
selective increase or reduction of local contrast at a chosen structure scale and within a controlled tonal range
programmable host for custom transform code whose maths, UI and signal contract are defined by the selected DCTL/DCTLE
depth-weighted reduction of smog/airlight/haze through a simulated depth matte and coupled colour/contrast correction
suppression of reflected red/green/blue screen spill after the subject has already been isolated by key/matte/roto
spatial display of exposure zones through camera-matched or creative false-colour mapping and a legend
final hard-clipping of chromaticities to a specified delivery/QC gamut boundary
tone/gamut remapping through luminance roll-off, saturation compression/clip and OOTF without a separate input/output colour-space conversion
AI-assisted SDR→HDR mapping with an explicit input/output signal contract, Middle Gray, target peak luminance and creative shaping
procedural Pan/Tilt/Rotation/Zoom motion with waveform, randomness, pauses and blanking handling
creative optical-look effect combining spatial diffusion, coloured Tone Lights, tonal protection, a falloff mask and a LUT-compatible subset
procedural texture/look effect combining blur/colour drift, vignette, changing dirt and up to five scratches with motion/flicker
procedural film-style texture with gauge presets, grain geometry, composite modes, tonal/RGB weighting and final mix
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
dedicated temporal exposure modulation with tonal flicker modes, RGB selection, smoothness, randomness, pauses and a deterministic seed
film-style highlight scatter using an isolation matte, chromatic dye-layer reflections, secondary glow and optional grain
creative shadow/highlight colour separation through Natural/Strong/Custom modes, Pivot, Hue Angle, neutral protection and colour-space overrides
edge framing and visual-attention control through Basic/Advanced geometry, position, colour and compositing
solid-colour generation for Layer Mixer, masks, fills and simple colour washes
The underlying RGB theory already lives in Colour Science and is not duplicated here.
Key routing, mattes and alpha workflows on the Color page.
How to keep a technical channel operation on a clear dedicated node.
RGB Parade and Vectorscope for checking channel behaviour.
Why channel inversion before and after a transform is an operation on different signal states.
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
No. Blackmagic explicitly describes it as a simple inversion rather than a film-negative plugin. It can create a negative-like picture when RGB are all inverted, but it does not emulate film stock, base colour, density curves or scanning.
Only the red component is inverted while Green and Blue remain unchanged. The resulting hue relationships change dramatically; this is useful as a channel operation or stylisation, not as neutral colour correction.
Yes. Disable Invert Red/Green/Blue and enable only Invert Alpha. Then verify that the image actually carries the alpha/key data you expect and inspect the downstream composite.
The Resolve 21 panel in the supplied screenshot exposes only the four channel checkboxes. If a partial mix is needed, do it with node Key Output Gain, layer/composite routing or another explicit mixing stage rather than inventing a control that is not present in this panel.
Where the intended channel inversion has the correct meaning. For a creative display-referred negative, that may be late in the chain; for a technical channel/alpha operation, it may need to sit before a transform or composite. The signal state matters.
For RGB work, Parade is useful because it shows each channel separately. For alpha/key tasks, inspect the matte/highlight/composite directly. Scopes do not replace checking what alpha/key data is routed through the node.
Next steps
Previous FX
The previous documented Color FX: tone/gamut remapping and OOTF.
The underlying RGB channel model already lives in the Colour Science section; the FX page does not duplicate it.
Key routing, matte logic and where Alpha/Key operations fit into the Color-page node graph.
Next FX
Continue with NVIDIA's AI-assisted SDR→HDR mapping, explicit input/output colour states and HDR luminance controls.