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.
New to the subject? What color grading means gives the short definition, distinguishes video from photo grading, and shows a measured source-and-result frame. Our full before-and-after breakdown shows the reference too, including a shadow flaw we would correct before delivery. A still comparison demonstrates a look change; it cannot prove that the grade holds through a moving shot or across a cut. The seven passes below are the work needed to check and finish the video.
Working in Premiere? Follow the Premiere Pro color grading workflow for source color settings, Lumetri adjustments, shot matching, and an SDR export check.
What you need before you start
A monitor whose color 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 color 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: log footage often appears lower in contrast and saturation before conversion, but its code values depend on the camera profile and exposure. After the correct input transform, inspect whether shadows and highlights retain detail. A hard ceiling or floor can be a sign of the wrong transform, a doubled transform, or clipping already present in the source.
The commonest failure here is applying two normalisations — a camera LUT plus a color-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 balance each clip before you build the look. Check exposure and white balance, then inspect black point and contrast. The aim is a usable, consistent starting image rather than one prescribed waveform value for every scene.
On the scopes: check whether the black trace stacks flat at the floor or the highlights stack at the ceiling; either may signal clipped detail. Compare important faces and neutral objects across related shots. A skin-tone line can help identify an unintended cast, but lighting and the intended look determine where a face should sit. Check the image and the waveform together rather than grading to one universal IRE target.
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 creative 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. If you copy the grade from a green-tinted hero shot, that cast can follow it to other shots. Review the reference before you reuse its settings.
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: compare the shots' black levels, important highlights and skin traces alongside the actual cut. Similar scope readings can support continuity, but the story may deliberately change brightness or warmth between angles.
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 match uses a still image for the selected shot. Match shots uses a graded shot to match the rest of the edit; review and refine the sequence before export.
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 color 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 color 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, color 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
- Grading before correcting. The look becomes clip-specific and will not carry.
- Two normalisations at once. A camera LUT on a color-managed timeline gives you a contrasty, clipped picture that no amount of grading rescues.
- Matching to an uncorrected reference. Every error in the hero shot is propagated across the scene.
- Judging on a paused frame. Motion reveals drift that a still hides.
- Trusting your eyes on a cast. Adaptation happens in seconds. Scopes are the fix.
- Grading every clip individually. Normalise everything, then grade by scene — the argument is in do you have to color grade every clip.
- Blaming the grade for banding. Usually the source or the export.
Doing this without a color suite
You can choose a desktop or browser workflow for these color-grading steps. Leumos covers input transforms, selected-shot reference matching, creative and skin refinements, scopes, and finished-video export. The guide to grading without Resolve compares the workflow and its practical requirements.
If your deliverable is a finished graded video from a browser, the Leumos page on color grading online shows what to import, which controls you can use and what the Free plan can export. Review the footage and delivery specification before choosing an output.
Leumos is ours, so read this as disclosure rather than a recommendation: a browser color 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?
Review every shot, but you do not have to invent a new look for every clip. Normalize each source, establish a scene direction on a representative shot, then copy and refine it where appropriate. A copied grade does not independently rebalance a shot with different exposure or lighting.
How do I know if my exposure is right?
Use both the picture and waveform. Look for unintentionally crushed shadows or clipped highlights, and compare important faces and neutral objects across cuts. For log footage, confirm the input transform and compare exposure with the manufacturer's published reference where available. There is no single IRE value that makes every scene correctly exposed.
What do I look for on a vectorscope?
The vectorscope shows hue by angle and saturation by distance from the center. Its skin-tone line helps you spot an unintended cast on a face. Lighting and creative intent may move skin away from a neutral reference; compare the shot in context before correcting it. Check unusually dense traces near the edge for excessive saturation.
Do I need DaVinci Resolve to color grade?
No. Resolve is a capable desktop option, while Premiere, Final Cut and browser grading studios support different parts of the same process. In Leumos, you can match a selected shot to a still, refine the color and skin, review the sequence and export the finished graded video. Choose a tool that supports your footage and delivery format.
Why does my grade look different after export?
Usually an output transform mismatch, a player applying its own color 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.
Related reading
- How AI color grading works — what automation covers in steps 2 and 4, and what it does not
- Exposing S-Log3 correctly — step 2 against Sony's published reference values
- Why cameras don't match — when step 4 refuses to work
- Grading log footage without DaVinci Resolve — Premiere, Final Cut, mobile and browser routes
- Banding after grading and export — where banding is really introduced
- Log format reference — computed code values and stop ladders for nine formats
- DaVinci Resolve color grading — these seven steps on the color page's node graph
- Color grading in Final Cut Pro — the same order in Color Wheels and Curves
Related: log footage explained, how to read a waveform monitor, how to read a vectorscope, and teal and orange color grading for a worked look.
Source and authorship note: Published by Leumos AI, founded by Pravit Gandhi. Vendor features above are attributed to their own documentation, while the Leumos classroom comparison is our disclosed product example. This article explains a workflow; it does not claim a controlled comparison of grading tools or a guaranteed result on every shot.