Skip to article
All posts
By Pravit Gandhi··10 min read

DaVinci Resolve color grading: a 2026 guide

Grade on the Resolve 21 color page: color management or CST nodes, a node order that holds up, primaries, Color Warper, Shot Match, five mistakes.

DaVinci Resolve color grading is a node graph, and almost every problem people have with it is a node-order problem rather than a taste problem. Decide how footage gets normalised, put that first, correct on the next node, match the scene, build the look above it, and keep secondaries downstream of all of it. The wheels are the easy part.

This guide is written against DaVinci Resolve 21, announced 14 April 2026 and updated to 21.1 on 8 September 2026, which added color profiles for "DJI D-Gamut2 and D-Log2, Leica L-Log IDT and LUT, and GoPro Log" (CG Channel, read 13 September 2026). Everything structural below applies to Resolve 18 onward.

Decide your color pipeline before the first node

Blackmagic frames color management as the thing that lets you "control conversion of color between digital film cameras, monitors" (Blackmagic Design, read 13 September 2026). In practice you are choosing between three routes, and mixing them is the single most expensive error on this page.

Route one — DaVinci YRGB with a transform node. Project color science stays on DaVinci YRGB. On each clip, the first node carries a Color Space Transform from the camera's own space and gamma to your timeline space. Explicit, visible in the graph, and easy to audit when a shot looks wrong. It is also the route that breaks most gracefully when a project has eight camera formats in it.

Route two — DaVinci YRGB Color Managed. Resolve handles input transforms from clip metadata and you grade in a managed space. Fewer nodes, less to forget, and a good default for single-camera work. The cost is that the transform is no longer something you can point at in the graph.

Route three — ACES. Right for projects that have to interchange with a facility pipeline, overkill for most independent work.

Pick one. A Color Space Transform inside a color-managed project is a double conversion, and it will produce exactly the over-contrasty, clipped image that sends editors to forums. The three routes genuinely produce different pictures from the same footage, for reasons worked through in why CST, ACES and LUTs look different. If your source is log and you are unsure what the curve is doing, what log footage is covers it.

Nodes: the part that makes Resolve worth learning

Blackmagic's own description is blunt: "Nodes are the building blocks of color correction in DaVinci Resolve." Each node is a full grade, and the image flows through them left to right.

A serial node order that survives contact with a real project:

  1. Normalise. Color Space Transform, or nothing at all if the project is color managed.
  2. Balance. Exposure, black point, white point, neutral. Nothing creative happens here.
  3. Match. Any correction that exists purely to make this shot agree with the hero shot of the scene.
  4. Look. Contrast shaping, hue moves, whatever gives the scene its character.
  5. Secondaries. Qualified selections, windows, masks — skin, sky, a loud jacket.
  6. Output trim. A last node for scene-wide adjustments you want to change without unpicking anything.

Keeping balance and look on separate nodes is not fussiness. It is the only way to disable the look and see whether your correction was actually right, and it is what lets you copy a look to another shot without dragging clip-specific exposure values along with it. Use parallel or layer nodes when two grades need to combine rather than stack — a common case is a sky adjustment that should not multiply against a skin adjustment.

Balance, match, look — on the color page

The order is the same one that works anywhere (the tool-agnostic version is here); these are Resolve's controls for it.

Balance on the primaries. Blackmagic describes the primary wheels as controls that "adjust balance and brightness in overlapping tonal ranges called lift, gamma and gain". Set lift so the bottom of the waveform reaches the floor without stacking into a line, gain so your brightest region of interest sits near but not at the top, then gamma for the midtones. Neutralise a surface you know is neutral. When you need finer work than a wheel allows, the primary bars are "an alternative to the primary wheels that allow for more subtle changes" to individual channels.

Match the scene. Two built-in routes. Chip charts: "if a shot contains a chip chart, click the color match icon", line it up, and Resolve computes the correction — the most exact option, and the reason experienced crews shoot a chart at each setup. Without a chart, Shot Match: "right click on another clip, and select 'Shot Match to This Clip'". Both fail for the same reason, which is not the algorithm — they fail when the clip you matched to was never corrected, or when the two clips are still being interpreted in different color spaces. Why Resolve's Shot Match underperforms is the longer diagnosis, and why cameras don't match covers the source-side causes.

Build the look. Curves for contrast shaping, and the Color Warper for hue work: it lets you "set a Hue vs. Hue color grade for specific saturations", which is the tool to reach for when you want the deep reds moved but not the pale ones. For HDR deliverables, the HDR palette will "address different tonal ranges from shadows and highlights to super blacks and specular whites". If you are after a specific published look rather than inventing one, cinematic color grading and teal and orange done well both break down how those grades are constructed.

Verify on scopes. "Professional scopes give you a consistent way to see image data," and on the color page they are one keystroke away. Use the parade to compare black points across a cut and the vectorscope to check that faces from two cameras sit on the same skin line. Reading a waveform and reading a vectorscope cover both.

Five mistakes colorists make in Resolve

Normalising twice. A camera LUT in the LUT slot plus a Color Space Transform plus a color-managed project is three interpretations of one curve. Symptoms: clipped highlights, crushed blacks, saturation that will not behave. Check the clip's whole chain before you touch a wheel.

Grading everything on node 01. It works until the client asks for the look warmer but not brighter, and you have no way to separate the two. Split balance from look on day one; it costs nothing and saves an evening.

Matching to an uncorrected shot. Shot Match propagates whatever is wrong with its target across the scene. Correct the hero shot to a standard you would sign off on, then match everything to that.

Using a LUT as a correction. A creative LUT is a fixed mapping applied identically to every clip under it. Two shots minutes apart need different corrections to reach the same place, so a LUT dropped on uncorrected footage produces a scene that is consistently wrong. Normalise, correct, then put the LUT on a node above.

Pushing saturation instead of fixing the neutral. Skin sitting off the vectorscope's skin line is a white balance problem. Saturation amplifies the error. Why your grade looks off lists the rest of the usual suspects.

When Resolve's built-in tools are enough

Nearly always, and the free version is not a crippled demo. Blackmagic states it "works with virtually all 8-bit video formats at up to 60fps", up to Ultra HD 3840 x 2160, and "includes multi-user collaboration and HDR grading". The full node graph, primaries, curves, Color Warper, scopes, Color Match and Shot Match are all there at no cost — which is why it is the first recommendation in our free software guide.

DaVinci Resolve Studio, at $295 one time, adds "the DaVinci AI Neural Engine, dozens of additional Resolve FX", temporal and spatial noise reduction, text based editing and magic mask, and supports "10-bit video up to 120 frames per second". Three things push people over that line: noise reduction on high-ISO material, Magic Mask for secondaries that would otherwise be tracked by hand, and 10-bit delivery. If none of those apply to your work, the free version is the whole tool.

What Resolve genuinely does not do is match a shot to an arbitrary reference photograph. Color Match wants a chip chart; Shot Match wants another clip. Neither takes a frame from a film you like as its target.

Where Leumos fits

Disclosure: Leumos is our product. This section describes what it does today and what it does not.

That last gap is the one Leumos addresses. It is a browser color grading studio: you import footage, it detects cuts, you select one shot and one still reference — a frame from a film, a graded still of your own, a photograph a client sent — and it computes the match. You review the result as moving footage rather than a frozen frame, fine-tune with Smart Grade, AI Color Correction and the creative controls, then export a graded Rec.709 file to bring back into your Resolve timeline.

What it is not: there is no Resolve integration or plugin, and no export of grade data, LUTs, XML, AAF or CDL — Leumos returns rendered video, so the conform still happens in Resolve. Reference matching runs on one selected shot at a time; there is no automatic pass across a whole timeline. The Free plan covers ten reference matches a month at 1080p, which is enough to test it on a shot you already know is difficult. Plans are on the pricing section, and how reference matching actually works covers the method and its failure modes.

FAQ

Is DaVinci Resolve free version good enough for color grading?

Yes, for most work. The free version carries the full node graph, primary wheels and bars, curves, the Color Warper, scopes, Color Match and Shot Match, and Blackmagic states it "includes multi-user collaboration and HDR grading". The paid Studio version adds noise reduction, Magic Mask, the Neural Engine features and 10-bit output above 60fps. If you are not delivering 10-bit or fighting noise, free is the whole tool.

How many nodes should a grade have?

As many as the grade has distinct jobs, usually four to six for a standard shot: normalise, balance, match, look, secondaries, trim. The number matters far less than the separation. One node holding everything is the problem; twenty nodes holding one adjustment each is a different problem.

Should I use Resolve Color Management or Color Space Transforms?

Either, never both. Color management is fewer decisions and works well on single-camera projects where clip metadata is reliable. A Color Space Transform on the first node is explicit and auditable, which matters when a project mixes six camera formats and one of them is mislabelled. The failure mode is running both, which double-converts and clips.

Why doesn't Resolve's Shot Match work?

Almost always preparation rather than the algorithm. The clip you matched to was never corrected, so its error propagated; or the two clips are still being interpreted in different color spaces; or they were exposed several stops apart and there is no single correction that reconciles them. Normalise both, correct the target shot properly, then match.

Can DaVinci Resolve match a shot to a reference image?

Not to an arbitrary photograph. Color Match is built around a chip chart in the frame, and Shot Match takes another clip in your timeline as its target. Grading toward a film still is done by eye with the still in a viewer, or by computing the match in a tool built for it and bringing the graded file back.

What order should I color grade in on the color page?

Normalise, balance, match the scene, build the look, then secondaries, with a trim node last. The reason is diagnostic rather than aesthetic: when the shot looks wrong, that order lets you disable one stage at a time and find the node responsible in seconds.

Sources

All read 13 September 2026.