Premiere Pro color management settings, explained

Sequence color space, display color management, auto tone mapping, and log detection. What each setting actually changes on screen, checked against Premiere Pro 26.3.

Color management in Adobe Premiere Pro is the system that converts every clip from the color space it was recorded in to the color space of your sequence, then to your display. Since the 2025 release (version 25.x), it is set per sequence, not per project. This guide is checked against Premiere Pro 26.3.

Most articles ranking for these questions describe the old system, the one before Adobe rewrote it. If a tutorial tells you to stack an input LUT on every log clip as step one, it predates the rewrite. Here is what the current settings do, one at a time.

What does color management do in Premiere Pro?

Adobe Premiere Pro's color management does three jobs. It reads what color space each clip was recorded in. It converts every clip into one working color space for the sequence. And it converts the sequence to whatever your monitor and your export need.

The point is that a Sony S-Log3 clip, an iPhone HLG clip, and a plain Rec.709 clip can sit on the same timeline and all look like normal video, without you touching a single slider. Conversion happens under the hood, before the Lumetri Color panel's controls are applied.

One sentence to keep: color management makes each clip individually correct, and that is all it does. Two clips can both be perfectly converted and still not look like each other. We wrote about why in what actually happens between log and your display.

What is sequence color management?

Sequence color management is the tab in Sequence Settings where you pick the working color space and how footage gets converted into it. In Premiere Pro 26.3 you choose a preset, and the preset sets everything else.

If you cut for YouTube, Instagram, or a client screening room, Direct Rec.709 (SDR) is the right answer and you can stop reading this section. Pick a wide gamut preset when you deliver HDR, or when you grade heavily and want highlight data to survive until the end.

Display color management: on or off?

Display Color Management is a checkbox in Premiere Pro's preferences. On, Premiere Pro reads your monitor's ICC profile and converts the picture so that Rec.709 actually looks like Rec.709 on your screen. Off, Premiere Pro sends the raw values to the display and lets the monitor do whatever it does.

On a Mac with a P3 wide gamut display, which is every recent MacBook Pro and Studio Display, leave it on. With it off, the same file can look different in Premiere Pro and in QuickTime Player, and you end up grading against a picture nobody else will see. That mismatch is behind most "my export looks washed out" complaints, and the full catalogue of washed-out-export causes, player by player, is in Premiere Pro export looks washed out: the gamma shift, explained.

The one time to turn it off is when you monitor through dedicated video output hardware onto a calibrated grading monitor. That signal path manages itself.

What does auto tone mapping do?

Auto tone mapping in Adobe Premiere Pro compresses the extra brightness range of HDR and log footage so it fits standard dynamic range without clipping. On screen, an iPhone HDR clip that looked blown out and gray on a Rec.709 timeline instead looks like normal, contained video.

It is a squeeze, not a match. Tone mapping decides how to fold, say, ten stops of highlights into the top of an SDR signal, and it makes that decision per clip, from the clip's own metadata. It does not look at the clip next door. Input against output, the three presets and the method switch each get a longer treatment in Premiere Pro tone mapping: input, output and what changes.

Does Premiere Pro auto detect log footage?

Yes: with color management on, Adobe Premiere Pro reads clip metadata and tags Sony S-Log3, Canon Log variants, Apple Log, camera raw and HLG sources with their color space, tone mapping already applied. What detection fixes, where it misreads, how to override it per clip or in bulk, and why two detected clips still do not match is its own post: Premiere Pro auto-detects log footage: what it fixes.

What color management cannot do

Color management normalises. It does not match. After Premiere Pro has converted every clip correctly, your Sony still renders skin warmer than your Canon, and your drone still leans magenta, because those differences were baked in by each camera's color science, not by a wrong color space tag.

So the working order of operations is: let color management make every clip individually correct, then make the clips agree with each other, then grade. The middle step is the one Premiere Pro only does one clip at a time. It is also the step MOVON was built for: one grade computed per clip and applied in the panel, straight from the footage you already have. See what MOVON does for the mechanics.

Common questions

Which Premiere Pro version has the new color management?

The rewrite shipped with the 2025 release, version 25.x, and has been refined since. Everything in this post is checked against Premiere Pro 26.3. If you are on 24.x or earlier, update before following any current tutorial, including this one.

Should color management be on or off?

On, for almost everyone. Turn pieces of it off only when you have a reason you can name, like a calibrated external monitor chain or a facility pipeline that manages color elsewhere.

Why does my footage look different in Premiere Pro than in QuickTime?

Usually Display Color Management is off, so Premiere Pro and macOS are interpreting the same file differently. Turn it on and compare again before touching any grade.

Does color management replace grading?

No. It gets every clip to a correct, neutral starting point. Matching clips to each other and building a look are separate steps that come after, and they are still your call.