Premiere Pro tone mapping: input, output and what changes

Input tone mapping, output tone mapping, the three Color Setup presets and the method switch, verified in Premiere Pro 26.3. What each choice does to the picture.

Tone mapping in Adobe Premiere Pro is the conversion that folds the wide brightness range of HDR and log footage into the smaller range of your sequence or your export. It runs in one of two places: on input, as each clip enters the timeline, or on output, on the way to the display and the delivered file. One menu decides which you get, the sequence's Color Setup, and each choice changes the picture in a way you can see.

This is current for Premiere Pro 26.3, checked in August 2026. The system arrived with the color management rewrite in the 2025 release, version 25.x. If your muscle memory says Auto Tone Map Media, that checkbox belonged to versions 23 and 24 and is gone; its job moved into the Color Setup presets and the sequence's Advanced color settings.

What is tone mapping in Premiere Pro?

Tone mapping in Adobe Premiere Pro exists because cameras record more than screens can show. A Sony S-Log3 or Apple Log clip carries stops of highlight that a Rec.709 sequence cannot display, and an iPhone clip in Rec.2100 HLG carries more still. Put those values on an SDR timeline unconverted and the picture displays lifted, gray and blown out. Tone mapping compresses the range that does not fit, rolling the top stops off gradually instead of slamming them into white.

The conversion has to lose information; the craft is in losing it well. Done well, highlights keep their texture and saturation survives the squeeze. Skipped, you get the washed-out iPhone problem, whose specific fix is in iPhone footage looks overexposed in Premiere Pro. Done crudely, skies clip and faces go plastic.

What is the difference between input and output tone mapping?

Input tone mapping in Adobe Premiere Pro converts each source into the working color space at the door; output tone mapping converts the whole working space at the end, for the display and the export. Same kind of math, opposite ends of the pipeline, different consequences.

With input tone mapping, the Direct Rec.709 (SDR) setup, an S-Log3 clip is folded into Rec.709 the moment it lands on the timeline. Everything afterwards lives in one small space, the Lumetri Color controls behave the way every Rec.709 tutorial assumes, and what you see is what exports.

With output tone mapping, the Wide Gamut setups, sources stay in a large working space and the compression happens after your corrections instead of before them. Grades that push hard hold together better, because the extra range is still there to push into, and Adobe's own guidance is that tone mapping at the end of the pipeline introduces fewer artifacts. The cost: the Program Monitor is showing you the image through an output transform, and a value past the output ceiling compresses instead of clipping, which surprises editors raised on SDR.

Input tone mapping is a per-clip decision made from that clip's own metadata, so it can make every clip presentable and still leave every camera disagreeing with the next.

Which Color Setup preset should I use?

The Color Setup menu in Adobe Premiere Pro sits in Sequence Settings and in the Lumetri Color panel's Settings tab, and its three main presets place the tone mapping for you.

For SDR delivery with mixed sources, Direct Rec.709 (SDR) is the default for a reason: fewest surprises, one space from ingest to export. Wide Gamut (Tone Mapped) earns its keep when you grade hard or master HDR alongside SDR. Wide Gamut (Minimal Tone Mapping) is for timelines that mix camera log with SDR material somebody already finished, because full output tone mapping would shift the finished material and minimal leaves it alone. Every setting around this menu, log detection, viewer gamma, per-clip overrides, is mapped in Premiere Pro color management settings, explained.

What does the tone mapping method in Advanced settings do?

Under the sequence's Advanced color settings, Adobe Premiere Pro lets you pick the algorithm doing the compression: Hue Preservation, By Channel, or Max RGB. Hue Preservation is the default and the most adjustable, with a knee control for where the rolloff begins; it holds a color's hue steady while its brightness compresses. By Channel compresses red, green and blue independently, which lands smoothly but can darken the image a touch and shift hues near the top. Max RGB drives the compression from the brightest channel, which keeps saturated highlights from skewing.

Do not choose from a description, including this one. Park the Program Monitor on your most highlight-heavy shot, open the Advanced settings, and switch methods while watching the sky, the windows and the skin. The differences live in the top two stops and they are clearly visible on the right shot. On most timelines the default never needs to move.

Does tone mapping happen on export too?

Export tone mapping in Adobe Premiere Pro is the output stage doing its job at render time: when the working color space is wider than the export color space, the conversion into the deliverable happens as the file is written. On a Direct Rec.709 (SDR) sequence there is nothing left to map, because everything was folded into Rec.709 on input; the export carries the timeline out as it is. On a Wide Gamut sequence, the export inherits the same output tone mapping you have been viewing through, so the file matches the Program Monitor.

Keep the export color space matched to the delivery, Rec.709 for the web and broadcast SDR, and resist forcing it elsewhere to rescue a look. An export that plays back flat and washed out is almost always a playback gamma disagreement, not a tone mapping failure; rule that out before re-exporting anything.

Does tone mapping make my cameras match?

No. Tone mapping in Adobe Premiere Pro normalizes each clip against a standard, one clip at a time, from that clip's own metadata; it never compares two clips. A tone-mapped iPhone and a tone-mapped Sony are both correct and still different, because the difference is in the cameras' color science, not in the encoding. That second job is matching, and it starts where tone mapping stops.

Do it by hand with Comparison View and the scopes, camera pair by camera pair, or run MOVON Match across the selection with one clip as the reference. Either way there is no conversion homework first; MOVON works from the clip's recorded values, so set the Color Setup for your delivery, not for the tool. The by-hand route is in how to color match different cameras in Premiere.

Common questions

Where did the Auto Tone Map Media checkbox go?

It was removed in the color management rewrite that shipped with the 2025 release, version 25.x. Its job now lives in the sequence's Color Setup preset, which decides whether wide sources are tone mapped on input or on output, and in the Advanced color settings, which expose the method. Nothing needs re-enabling in Premiere Pro 26.3; Direct Rec.709 (SDR) tone maps log and HDR sources by default.

Should I ever turn tone mapping off?

Only when a color-managed pipeline of your own already handles the conversions, for instance a facility workflow built on conversion LUTs, or when you master HDR and the sources already live in the output space. With tone mapping off, out-of-range values clip, and log footage displays flat and gray.

Why does my footage still look washed out with tone mapping on?

Usually the clip was misread. Tone mapping runs from the clip's detected color space, so a log clip detected as Rec.709 gets no conversion at all. Check the detected space and override it per clip; the detection system and its failure cases are in Premiere Pro auto-detects log footage.

Is input tone mapping better than output tone mapping?

Neither wins in general. Input keeps the whole edit in one small predictable space and suits SDR delivery. Output preserves range through the grade and suits heavy grading and HDR masters. The wrong choice is the one made by accident, which is what the Color Setup preset names try to prevent.