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

How to color grade video: a 7-step workflow (2026)

A tool-agnostic colour workflow: normalise, correct, pick a reference, match the scene, build the look, handle skin, then verify on scopes before export.

Color grade video in seven passes, in this order: normalise each clip with its input transform, correct exposure and white balance, pick one reference shot, match the rest of the scene to it, build the look on top, handle skin and secondaries, then verify on a waveform and vectorscope before you export. Order matters more than tooling.

Almost every "my grade looks wrong and I don't know why" is a step done out of sequence, not a missing plugin. The workflow below works in DaVinci Resolve, in Premiere's Lumetri panel, in Final Cut, or in a browser tool. Where a step has a specific name in a specific tool, the tool's own wording is quoted and linked.

What you need before you start

A monitor whose colour profile you have not changed mid-project, and scopes. A calibrated display is better, but scopes are the part you cannot substitute: they say where the picture sits while your eyes are busy adapting to it. Blackmagic describes the two you will use most — the waveform "displays the luminance and color values overlaid on top of each other at the current frame", and the vectorscope "displays a circular graph of your image data that represents its hue and saturation levels" (blackmagicdesign.com, read 12 September 2026). Adobe's equivalents are "hardware-accelerated Lumetri scopes like Vectorscope, Histogram, Parade, and Waveform" (adobe.com, read 12 September 2026).

Step 1 — Normalise: tell the software what the footage is

If you shot log or a flat picture profile, nothing you do downstream is valid until the clip is interpreted correctly. Apply the input colour space transform, input LUT, or camera-specific setting that matches what you actually shot — S-Log3, V-Log, C-Log3, N-Log, LogC, Apple Log — rather than reaching for a LUT somebody posted in a forum.

On the scopes: before normalising, log footage sits as a compressed band roughly between 5 and 75 IRE with almost no black or white, and the vectorscope trace is a small blob near the centre because saturation is low by design. After the correct transform, the trace should open out to use the full 0–100 range and the vectorscope should spread. If it opens out too far and clips at the top, your transform is wrong or doubled.

The commonest failure here is applying two normalisations — a camera LUT plus a colour-managed timeline — and wondering why everything is contrasty and clipped. Pick one route. If you want to know exactly what a given curve is doing to code values, our log format reference computes them for nine formats, and the differences between the routes are worked through in why CST, ACES and LUTs look different.

In Leumos: you choose the named transform for your source, including Sony S-Log3, Panasonic V-Log, Canon Log, ARRI LogC3 and LogC4, Nikon N-Log and Apple Log options (leumos.ai/llms.txt, read 12 September 2026).

Step 2 — Correct exposure and white balance

Now fix each clip so it is an honest record. Exposure first, then white balance, then black point, then contrast. This is the technical pass, and there is a right answer you can check.

On the scopes: put the black point at 0 without flattening the bottom of the trace — if the trace stacks up in a solid line along the floor, you have crushed detail that is gone. Put the brightest thing you care about near but not at 100. A typical face wants to land somewhere around 50–70 IRE depending on how you want it to read. On the vectorscope, skin should sit along the skin-tone line that runs between red and yellow; a face that points ten degrees off it is a white balance problem, not a look.

If you shot S-Log3 and the exposure was set by eye on a flat monitor, the number you should be checking against is the manufacturer's published reference value, not a guess — that is laid out in exposing S-Log3 correctly. Adobe names this pass in the panel itself: Basic Correction is for making "basic corrections to exposure, white balance, and contrast" (adobe.com, read 12 September 2026).

In Leumos: AI Color Correction handles the balance pass, with manual controls to take over.

Step 3 — Choose your reference shot

Before matching anything, choose one shot to be the target for the scene, and finish correcting that shot to a standard you are happy with.

Pick the shot with the most typical content and lighting for the scene, not the prettiest one. A tight close-up against a bright window is a terrible target for a wide of an empty room — there is no shared content for a match to reason about. A medium shot that contains some skin, some background and a recognisable neutral is close to ideal.

This step has no scope reading of its own, and it is the one people skip. It is also the single most expensive mistake in the workflow: whatever is wrong with your reference shot becomes the target every other shot is dragged toward. A green cast on the hero shot becomes a green scene.

Step 4 — Match the rest of the scene to it

Now bring the other shots into agreement. Every tool has a version of this. Resolve's is clip-to-clip: "Select a clip, right click on another clip, and select 'Shot Match to This Clip' from the menu", and for a chart it is "click on the color match icon in the toolbar, select the type of chart used, line it up on the image and click match!" (blackmagicdesign.com, read 12 September 2026). Premiere's is inside Basic Correction: "automatically match color between shots with Color Match" (adobe.com, read 12 September 2026).

On the scopes: put two shots side by side and compare black points first, then the top of the trace, then where skin sits on the vectorscope. Two shots that agree on black point and skin angle will cut together even if their midtones differ slightly. Two shots that disagree on black point will never cut together no matter what else you do.

Automatic matching underperforms for boring reasons far more often than for algorithmic ones: mismatched input transforms from step 1, footage exposed stops apart, or a reference clip that was never corrected in step 3. If two cameras simply will not sit together, why cameras don't match covers the post-only repair.

In Leumos: you select one shot and a still-image reference, run the match, and review it in motion. Reference matching runs on one selected shot at a time; automatic matching of a full timeline is not available in this release.

Step 5 — Build the primary look

Only now do you decide what the scene should feel like. Work on top of a corrected, matched base so the look carries across the scene instead of being welded to one clip's errors.

The usual moves, in rough order of how much they buy you: a contrast curve to separate midtones, a split between warm highlights and cool shadows (or the reverse), a global saturation adjustment, then a deliberate colour cast somewhere. Resolve's primary wheels "let you adjust balance and brightness in overlapping tonal ranges called lift, gamma and gain"; its curves "let you adjust luminance and color based on tonal areas you define" (blackmagicdesign.com, read 12 September 2026). Premiere's creative half offers "Lumetri looks to emulate different film stock" plus your own LUTs (adobe.com, read 12 September 2026).

On the scopes: grading deliberately moves you away from "accurate", so stop using the scopes as a target and start using them as a limit. Watch that you are not clipping the top of the waveform, not crushing the bottom into a flat line, and not pushing saturation so far that the vectorscope trace hits the outer graticule boxes. Everything between those limits is taste.

In Leumos: Smart Grade offers a shortlist of looks with a strength control, so you can pick a direction and then dial how far it goes.

Step 6 — Skin and secondaries

Faces are where human tolerance is narrowest, so they get their own pass. Isolate skin and adjust it separately from the rest of the frame: a look that reads beautifully on a wall can turn a face waxy or sunburnt.

Resolve does this with the qualifier — "the qualifier palette lets you select and adjust part of an image based on hue, saturation or luminance" — and with Power Windows, which "let you define a selection by drawing shapes around specific objects in a scene" (blackmagicdesign.com, read 12 September 2026). Premiere's is the HSL Secondary tab. The same logic applies to a distracting colour in the background: pull it down rather than fighting it globally.

On the scopes: put skin back on the skin-tone line unless you are moving it on purpose, and check that your secondary has not introduced a hard edge. If the qualifier's mask is buzzing, soften it rather than accepting the artefact.

In Leumos: the Skin tone control automatically selects skin, lets you inspect and refine the selection mask, then adjusts hue, warmth, colour boost, brightness and contrast. It is a skin-specific secondary, not a general HSL qualifier.

Step 7 — Verify, then export

Look away from the picture for thirty seconds, come back, and check the scopes before you commit. Your eyes adapt to a cast within seconds of looking at it; scopes do not adapt at all. Then play the scene at speed, in full screen, without pausing. A grade that holds on a paused frame can fall apart through a pan, an iris change, or a subject walking from sun into shade.

On export, keep the bit depth and codec as generous as the delivery allows. Most banding people blame on the grade is introduced at export or by a heavily compressed source, not by the wheels — banding after grading and export identifies which stage introduced it and which stage can fix it.

Common mistakes, in order of how often they cost time

  1. Grading before correcting. The look becomes clip-specific and will not carry.
  2. Two normalisations at once. A camera LUT on a colour-managed timeline gives you a contrasty, clipped picture that no amount of grading rescues.
  3. Matching to an uncorrected reference. Every error in the hero shot is propagated across the scene.
  4. Judging on a paused frame. Motion reveals drift that a still hides.
  5. Trusting your eyes on a cast. Adaptation happens in seconds. Scopes are the fix.
  6. Grading every clip individually. Normalise everything, then grade by scene — the argument is in do you have to color grade every clip.
  7. Blaming the grade for banding. Usually the source or the export.

Doing this without a colour suite

You do not need a workstation for any of the above. Resolve's free version runs on Mac, Windows and Linux. Lumetri is already inside Premiere. Browser tools can do the correction-and-match part without an install. The options and their trade-offs are laid out in grading log footage without DaVinci Resolve.

Leumos is ours, so read this as disclosure rather than a recommendation: a browser colour grading studio built around steps 1 to 7, with a Free plan of ten reference matches a month and 1080p export without a watermark. The honest test is to open the Studio on a shot you already know is difficult. Plans are on the pricing section. It is not a substitute for the ordering above — the order is the part that does the work.

FAQ

What is the correct order to color grade video?

Normalise with the right input transform, correct exposure and white balance, choose and finish one reference shot, match the rest of the scene to it, build the look on top, treat skin and secondaries separately, then verify on scopes and export. Doing any step early is the usual cause of a grade that will not carry.

Should I color grade every clip individually?

No. Normalise every clip, then grade by scene using one shot as the reference for the others. Clip-by-clip grading produces a timeline that flickers across cuts and is unmaintainable the moment the edit changes.

How do I know if my exposure is right?

Read the waveform rather than the picture. Black point at 0 without the trace stacking flat along the floor, the brightest thing you care about near but not at 100, and a typical face somewhere around 50–70 IRE. For log footage, check against the manufacturer's published reference value.

What do I look for on a vectorscope?

Skin. There is a skin-tone line running between red and yellow, and faces should sit along it unless you have moved them deliberately. Distance from that line is a white balance problem. The outer boxes mark where saturation starts clipping.

Do I need DaVinci Resolve to color grade?

No. Resolve's free version is the most capable free option, but Premiere's Lumetri panel, Final Cut, open-source editors and browser tools all cover the workflow above. The order of the steps matters far more than which of them you use.

Why does my grade look different after export?

Usually an output transform mismatch, a player applying its own colour management, or compression at export. Check the export settings against the delivery spec first, and look at the file in a second player before assuming the grade is wrong.