Premiere Pro color grading works best as a sequence of separate decisions: identify what each source clip is, choose the sequence and output color spaces, balance the shots, match the scene, add the look, isolate any remaining problems, then inspect the exported file. When these jobs blur together, a conversion gets applied twice, a look LUT is asked to repair exposure, or a good grade changes after a sequence setting moves.
This guide follows the shipping Premiere 26.x Lumetri Color workflow for an SDR Rec.709 deliverable. Adobe says Premiere 27.0 will retire the Lumetri Color panel and move its controls while the Lumetri effect remains editable. The separate Color mode is currently in Premiere beta, and its directions are outside this guide. (Adobe: upcoming Lumetri changes)
1. Identify the source before touching Lumetri
Start in the Project panel, not with a contrast slider. Record the camera, transfer curve, gamut, and whether the file is camera-original or transcoded. If the clip is log and those details are unclear, use the camera and editor setup reference, the log code-value reference, or the short explanation of what log footage is before grading.
Premiere can use container and camera metadata, but that metadata may be absent or wrong. Adobe says to verify those clips through Clip Modify > Color. For camera raw identified incorrectly, use the Color Space control in Source Settings. (Adobe: how Color Management works; Adobe: Clip Modify color management)
Do this in batches by camera and recording mode. Do not infer a log curve from a flat-looking frame: underexposed Rec.709, a proxy with missing metadata, and a genuine log original can all look muted for different reasons.
2. Lock the sequence to an SDR Rec.709 destination
Open Sequence > Sequence Settings > Color before making creative adjustments. For a straightforward SDR job, Adobe's Direct 709 (SDR) setup uses a Rec.709 working space and Rec.709 output; SDR media passes through, while wide-gamut raw and log sources are mapped into the sequence. For a mixed-camera job with significant log or raw material, Wide Gamut (Tone Mapped) keeps a wider working space for grading and maps the result to the selected output. Set Output Color Space to Rec.709 for this deliverable. (Adobe: sequence color management)
Choose the working setup once. Adobe warns that Lumetri adjustments are working-space specific, so changing the working space after grading can change the result. The output space serves a different job: it defines what the Program Monitor, internal scopes, rendering, and export represent. (Adobe: output color space)
3. Separate a technical transform from a creative LUT
A technical transform answers, “What was recorded, and how should it be represented here?” A creative LUT answers, “What style should this already normalized image have?” They may both be LUT files, but they do different work.
Color management can perform the source-to-working conversion without a LUT. When an input LUT performs that conversion, set Media Color Space to the space the LUT produces; Premiere then converts that result into the working space. (Adobe: Clip Modify color management)
A look LUT belongs later. In Lumetri's Creative section, declare the color space the look expects. Adobe notes that many included looks were designed for Rec.709 and can appear different in another working space; the Creative Look control is color-space aware so the expected space can be specified. (Adobe: Lumetri and color management)
Color management and LUTs can therefore coexist. The failure is using two source conversions, such as automatic log normalization followed by a camera log-to-Rec.709 LUT. That often produces crushed shadows, hard highlights, and too much saturation. The companion guide to Premiere applying a LUT to log footage shows how to locate the extra transform.
4. Balance one representative shot per lighting setup
Pick a clear frame from each lighting setup. Open Window > Lumetri Scopes, then show at least a Waveform, RGB Parade, and Vectorscope. Adobe provides those scopes alongside Histogram, and the panel can display several at once. The Clamp Signal option changes only the scope display; it does not change the timeline or export. (Adobe: Lumetri Scopes)
Work in this order:
- White balance: Use a known neutral surface when the scene contains one. Confirm with the RGB Parade, but keep intentional colored light intentional.
- Exposure: Place important subjects and scene values where the image needs them, using the Waveform to see what the monitor can hide.
- Contrast and endpoints: Set black and highlight relationships without forcing every shot to touch 0 and 100 IRE. A foggy dawn and a product shot should not share the same endpoints by rule.
- Saturation: Watch the Vectorscope for direction and intensity. Treat skin as a range of plausible hues shaped by lighting, makeup, and camera response, not a mandatory point on one line.
For a fuller reading of those displays, use the waveform monitor guide and vectorscope guide.
5. Match the scene before building the look
Choose a hero shot for each scene: a well-exposed frame with the main subject and representative lighting. Balance it first. Open Lumetri Color > Color Wheels & Match, turn on Comparison View, set that hero frame as the reference, and move the playhead to a target shot.
Match brightness structure before hue. Compare the subject, neutral objects, and background separately. Premiere's Apply Match can provide a starting point: Adobe says it writes the result into Color Wheels and Saturation, with optional face weighting. Select a representative target frame because the current frame is what gets analyzed. Review the settings afterward; Adobe also cautions that applying a match when Lumetri adjustments already exist can reset some parameters. (Adobe: match color between shots)
Do not make every angle identical. A reverse shot facing a window may legitimately be cooler or brighter. The goal is continuity: cuts should feel motivated rather than calling attention to a change in exposure, white balance, or saturation.
A hypothetical mixed-camera example
Suppose a documentary scene combines Sony S-Log3/S-Gamut3.Cine, an HLG phone clip, and previously finished Rec.709 archive footage. This is a hypothetical setup, not a test report.
Tag each source according to what it actually is. Before grading, compare the finished archive clip with a trusted copy: Adobe warns that output tone mapping can slightly darken mastered SDR. If its appearance must be preserved, evaluate Wide Gamut (Minimal Tone Mapping) or plan a deliberate clip correction, then lock the setup. Balance the Sony and phone shots independently, avoid re-normalizing the archive, and match the second camera to the strongest interview angle. Apply the shared treatment only after the sources sit together convincingly. (Adobe: sequence color management)
6. Add the look, then isolate what remains
Once the scene cuts cleanly, add the creative look. A scene-wide Lumetri effect on an adjustment layer can hold shared contrast, color bias, or a look LUT. Keep clip-level balance beneath it so one camera correction does not become part of the whole scene's style.
Use Curves, HSL Secondary, or tracked masks for problems that cannot be solved globally: a bright window, a green wall contaminating one face, a wardrobe color that dominates the frame, or a saturation spike in highlights. Make the key or mask visible while refining it, soften its edge, and then check it through movement. A clean still frame can still chatter, lag, or reveal a halo during playback.
7. Export, reimport, and inspect the deliverable
Confirm the sequence output remains Rec.709. In Export settings, verify Export Color Space is Rec.709 rather than assuming the preset chose it; Adobe says most presets default there, but the field controls the exported file's color space. (Adobe: export settings) Reimport the file into a clean Direct 709 (SDR) inspection sequence with no added grade, adjustment layer, or transform. Compare its output with the original sequence's Rec.709 output at the same frames and on the same scopes. Check cuts, fades, gradients, titles, and the most saturated shot.
If the export shows steps in skies, walls, or fades, separate timeline banding from encode banding with the checks in banding after grading and export. If the reimport matches inside Premiere but another player looks different, investigate that player's display and color-tag handling before changing the grade.
Symptom, check, and fix
| Symptom | Check | Fix |
|---|---|---|
| Log clip stays flat | Source Clip color space and missing metadata | Assign the actual media color space or a documented input transform |
| Log clip is crushed and oversaturated | Automatic normalization plus a conversion LUT | Keep one source conversion and remove the duplicate |
| A look changes wildly between sequences | Working space and the look LUT's expected space | Use the intended look color space; do not change a graded sequence's working space |
| Two camera angles jump at the cut | Waveform, RGB Parade, and a representative hero frame | Balance each camera, then match exposure and color relationships |
| The LUT browser preview disagrees with the result | The applied output in Program Monitor | Judge the applied result; Adobe says the look preview thumbnail is not color-managed |
| Export looks different | Reimported export versus timeline and scopes | Verify the file in Premiere first, then isolate player or display handling |
Where a still reference can help
When a project has a clear reference still, Leumos can match one selected shot to that image in the browser. Use that result as another reference to evaluate, then continue checking the cut, scopes, and motion in context. Open Leumos Studio.
Frequently asked questions
Should I grade log footage before converting it to Rec.709?
Identify the log source first and decide where its source-to-working transform happens. In a color-managed wide-gamut sequence, Lumetri adjustments operate in the working space and Rec.709 is the output. In a display-referred setup, normalize once before applying a Rec.709 creative look.
Can I use a LUT with Premiere color management?
Yes. Use an input LUT when it is the chosen source conversion, or a creative LUT as a look after normalization. Tell Premiere which color space the LUT expects or produces, and avoid stacking two technical conversions.
Should every shot reach 0 and 100 IRE?
No. Scope limits are not composition targets. Set levels according to the scene, subject, and delivery requirement while protecting meaningful shadow and highlight detail.
Is Apply Match the finished grade?
Treat it as a starting point. Check the generated Color Wheels and Saturation changes, compare the whole shot through time, and refine the result against the scene's hero frame.
Sources and method
- Adobe: Color Management overview
- Adobe: How Color Management works
- Adobe: Configure clips using Clip Modify
- Adobe: Color Management and Lumetri Color
- Adobe: Configure sequence Color Management
- Adobe: Configure sequence output color space
- Adobe: Match color between shots
- Adobe: Display Lumetri Scopes
- Adobe: Upcoming changes to Lumetri Color
- Adobe: Overview of export settings
Source check: Adobe documentation was read on September 20, 2026. This guide is documentation-based; it was not produced from a Premiere desktop test session.