This post contains affiliate links. If you buy through them, we earn a commission at no extra cost to you. It never changes what we recommend. How we test
You finish the grade, the program monitor looks right, you hit export — and the file plays back washed out. Or crushed. The shadows have lifted, the contrast has gone flat, and nothing you did in the timeline explains it. This is gamma shift, and it is not a bug in your grade.
It happens because Premiere and your playback application disagree about how to interpret the same pixel values. Fixing it means making them agree.
Why It Happens
Sponsored
Colour grading panels built for editors who work fast. Tangent →
Video is not stored as brightness. It is stored as a set of numbers with a transfer function that describes how those numbers map to light. Rec.709 — the standard for HD video — assumes one curve. sRGB, which most computer displays and browsers assume, uses a slightly different one.
When an application reads your file and applies the wrong assumption, every value shifts. Mid-tones move most, which is why the effect reads as “washed out” rather than simply brighter or darker.
The pixels did not change. Only the interpretation did.
Where it shows up
- QuickTime Player on macOS, historically the worst offender
- Some browser video players, depending on the codec
- Any app that ignores or misreads the colour tags in the file
It rarely shows up everywhere at once. That inconsistency is the clue: if the file looks correct in VLC and wrong in QuickTime, the export is probably fine and the player is the problem.
The Fix, In Order
Work through these in sequence. Most gamma shift resolves at step one or two.
- Turn on colour management in Premiere
- Confirm your sequence colour space matches your footage
- Export with explicit colour tagging
- Verify in more than one player before you conclude anything
Step one — colour management
In Premiere, open Preferences > Media and enable Display Colour Management. This makes the program monitor account for your display profile rather than pushing raw values to screen. Without it, what you see in Premiere is not a reliable reference, and you will grade against a moving target.


Step two — sequence settings
Check that your sequence working colour space matches what your camera actually delivered. Log footage placed in a Rec.709 sequence without a transform will behave unpredictably at export, and the resulting shift is easy to mistake for a gamma problem when it is really a colour-space problem.
Panels worth considering
The links below are affiliate links — we earn a commission if you buy.
- Tangent Ripple — entry-level grading panel
- Blackmagic Micro Panel — Resolve-native control
- Loupedeck CT — general-purpose alternative
Step three — export tagging
In the export settings, look for the colour management options and make sure the output is explicitly tagged rather than left to inherit. An untagged file is an invitation for every player to guess, and they do not all guess the same way.
H.264 and HEVC both carry these tags. If you are delivering ProRes, the tagging behaviour differs by variant, so check the specific flavour you are exporting rather than assuming.
What Not To Do
The tempting shortcut is to add a compensating adjustment layer — lift the gamma slightly so the export “looks right” in the player that was wrong. Resist it.
That fix is display-specific. You have not corrected the file; you have broken it in the opposite direction so that two errors cancel on one machine. Anywhere else — a different player, a phone, a client’s browser — it will now be wrong by exactly the amount you added.
Fix the interpretation, not the pixels.
One edit better,
every week.
Guides, reviews and workflows. Every Thursday, no filler.
Thurs Send It To


