Premiere Pro Export Colors Look Different? Fix It Before Your Client Sees It

Most Premiere editors basically don't handle color shift at all, and I'm including my own agency in that for a good couple of years, right. We grade on our own screen, export, send the link, and then act really really surprised when the client writes back that the whole thing looks darker or flatter than what we showed them on the call.

And so when Premiere Pro export colors look different on the client's laptop, the usual reaction is to blame their screen, nudge the grade by feel and export again, which to be very honest is closer to a coin toss than a workflow. The client feels that too, because every round where the color wanders makes them trust the grade a little less.

So I'll walk you through why the shift happens inside Premiere Pro, the settings that decide it, how I prove the export is fine, and the review habit that catches whatever is left, right, because at the end of the day the client only ever sees your review copy and never your Program Monitor.

Why Premiere Pro export colors look different on other screens

The first thing to get straight is that the exported file is usually fine, right. What changes is how three things read the same numbers, your Program Monitor, whatever player or browser opens the file, and the client's physical screen, and each one makes its own assumption about gamma, which is basically the curve that turns stored brightness values into actual light.

Rec.709, the standard most of us deliver in, never settled on one display gamma that every device agrees with. Broadcast monitors in a dim grading room sit around 2.4, most computer screens and browsers behave closer to 2.2, and Apple's color pipeline, which QuickTime Player, Safari and Chrome on a Mac lean on, shows a Rec.709 tagged file at roughly 1.96, which lifts the shadows and makes everything look a touch milky. That is the classic premiere pro washed out export that half the forum threads are about, and it hits hardest when the client is on a MacBook.

Windows is its own story, right, because a lot of Windows browsers and players more or less ignore the color tags and show the file closer to 2.2, so the same export can look punchier there than on the Mac sitting next to it. Phones then add auto brightness, night modes, True Tone and so on, none of which you control from your edit suite.

So before I change anything, I work out which problem I actually have, right. If the file looks lifted in QuickTime and Safari on a Mac but fine on a Windows laptop, it's the gamma tag problem and the grade is probably fine. If it looks wrong everywhere, including back inside Premiere, the export or the sequence changed the picture. And if it only looks off on the client's phone, it's usually their brightness or night mode, which no export setting will fix.

That middle case is rarer, but not every gamma shift after export is a viewer problem. For instance, iPhone HDR footage in an SDR sequence gets tone mapped, and screen recordings often come in full range while your timeline expects limited range, which crushes or lifts the blacks. I wrote a separate piece on the Resolve version of this problem, since DaVinci Resolve has its own switches, so this post stays inside Premiere.

The file is usually fine

Most shifts come from the player and the screen reading the same file with a different gamma, so fix those assumptions before you touch the grade.

Display color management and viewer gamma explained simply

In the versions of Adobe Premiere Pro I use day to day, the two settings that matter live in Preferences under Color, though the wording in your build may differ a little. The first is Display Color Management, which needs GPU acceleration switched on and reads your monitor's profile so Rec.709 footage shows properly on a wide gamut screen, right. Without it, a P3 MacBook makes Rec.709 look oversaturated, so you grade the saturation down and the export looks dull everywhere else.

The second is Viewer Gamma, with three choices, 1.96 for QuickTime, 2.2 for web and 2.4 for broadcast, and this is basically you telling the Program Monitor which kind of viewer to imitate. The catch here is that it only changes what you see inside Premiere and does nothing to the exported file.

In my own agency we grade web and social deliverables at 2.2, because that's the closest thing to a middle ground across browsers and phones. Before any export goes to a client we know works on a Mac, we flip it to 1.96 for a minute and scrub the key shots, right, and if a shot falls apart, usually darker skin tones or a moody interior, we adjust until it holds up in both. My notes on a color correction workflow in Premiere go deeper into scopes and Lumetri.

And trust me on any level on this one, grade with your scopes open, because your eyes adapt to whatever gamma you're looking at within minutes and the waveform doesn't. If the shadows sit where they should on the scope and only look lifted on a Mac, the viewer is the problem and the grade is fine, does that make sense, right.

Export settings that keep color consistent across players

Once the monitor is telling you the truth, the export side is honestly pretty boring, right, and I've come to like that. For client review I export H.264 in Rec.709 and keep the sequence working color space at Rec.709 when the job is SDR, because a sequence that quietly inherited HDR settings from iPhone clips will tone map on export in a way you never previewed.

Keep the levels in video range unless you have a very very specific reason not to, and if screen recordings or graphics came in full range, fix the interpretation on the clip rather than pulling the whole grade around to hide it. YouTube's recommended upload encoding settings ask for BT.709 for standard dynamic range uploads, which is a nice sanity check when the client will post the file anyway.

What I don't do is bake a Mac compensation LUT onto the master or retag the file to trick Apple's pipeline, because I'm pretty sure those tricks only hold in the player someone tested and break on a Windows machine or a platform that re-encodes. My full preset is in the post on export settings for client review, and Premiere export settings explained walks through every tab of the dialog.

Proving the export matches your timeline

This is the test I run whenever someone tells me the export changed, right, because it settles the argument in a couple of minutes. Say the client says your 40 second brand film looks flatter than it did on the call. I make a throwaway sequence, drop the original edit in as a nest on V1, put the exported H.264 on V2 starting on the same frame, and set its blend mode to Difference in the Opacity controls.

Wherever the two pictures match, the Program Monitor goes black, so if I scrub through and see black with only faint speckles of compression noise, the file holds exactly what Premiere rendered and the shift is happening in the client's player. If I see a ghost of the image instead, usually strongest in the shadows, the export or sequence settings changed something, and I check color space, tone mapping and range before I touch the grade.

1Set the sequence to Rec.709 for SDR delivery

2Turn on display color management and pick a viewer gamma

3Export H.264 Rec.709 in video range

4Run a Difference blend test against the timeline

5Watch the uploaded review copy on a Mac and a Windows screen

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

Checking your review copy in a browser before the client does

This is the habit that actually changed things for us, right, and it's almost embarrassingly simple. Before I send any review link, I upload the export to PlayPause and open that link the way the client will, in a browser with no login, and watch the key shots there. PlayPause plays back from a streaming copy and leaves the original untouched, and since that streaming copy is exactly what the client presses play on, whatever their browser does to it, I've seen it first.

I do this on my MacBook in Safari, because that's where the 1.96 lift shows up, and if a Windows laptop or a phone is nearby I open the same link there too. If something looks off, I fix it in Premiere and export again before the client has seen anything, which is a much easier conversation than the one after they've written that it looks darker than on your screen. With the PlayPause panel for Premiere Pro, the upload goes straight from the timeline, and the comments later show up inside Premiere, where clicking one jumps the playhead to that frame.

For teams where a producer sends the links, I'd make this check part of the video proofing routine. That's really what a color accurate client review looks like for us, right, because the client's screen is never going to be calibrated, so the next best thing is watching the exact copy they'll watch before they do.

• Skin tones still read as skin on a MacBook
• Blacks are not lifted into grey
• Brand colors match the logo file
• Highlights on faces are not clipping
• Phone playback at mid brightness still looks right

Getting usable color notes by drawing on the frame

Even with all of that, some clients will still see a difference, because their laptop is at 40% brightness with night mode on, and I've made peace with that. The note I can't work with is "the color feels off" with no timestamp and no shot, so I ask every client to draw on the frame, right, circle the face or the logo that bothers them and write one word next to it, like darker or warmer.

In PlayPause that comment sticks to the exact frame, and if the problem runs across a whole shot they can leave a range comment instead. The drawing and markup tools are on every plan, with no account or install needed on the client's side. I also ask them to mention their device, because darker on an iPhone and darker on an office monitor lead me to very different decisions.

I've written more about grades approved on uncalibrated laptops, and the short version is that their screen will never match yours, so what you can improve is how specific their notes are, because color grading already involves enough judgment calls without the review adding guesswork on top.

“

A circle on the exact frame with the word darker next to it is worth more than a paragraph about the mood of the whole video.

Comparing the corrected export against the original version

Once I've made the fix, I don't send a fresh link with a new file name, because then the client is juggling two tabs and guessing what the first one looked like, right. I upload the corrected export onto the same card, so it stacks as MV2 on top of MV1 and the first round of comments stays with MV1.

On the Agency plan and up, side-by-side version compare lets me play MV1 and MV2 next to each other and check whether the shadows came down or the skin tone warmed up. When I walk a client through that view on a call, you see what I mean here, the question moves from whether it looks right in general to whether the right side beats the left, and clients are really good at answering that. There's a longer walkthrough on showing a client what changed between two Premiere versions, and it works a lot like version control in software, where you never throw away the old state.

Agency is $19 a month or $199 a year, flat for the workspace with up to 50 members, and I compared that with Frame.io's per user pricing, from $15 per user per month, in my Frame.io alternative for Premiere Pro post.

Old way

a second export with a new file name and the client guessing what changed

With PlayPause

MV2 stacks on the same card and Agency plans play both versions side by side

Frequently asked questions

Why does my Premiere Pro export look washed out on a Mac?

Most of the time it's gamma, right. Apple's color pipeline, which QuickTime, Safari and Chrome on a Mac use, shows a Rec.709 tagged file at around 1.96, while you probably graded at 2.2 or 2.4, so the shadows lift and everything looks milky. Set viewer gamma to 1.96 in Premiere's color preferences for a quick preview of what Mac viewers see, and adjust any shot that falls apart.

Should I set viewer gamma to 2.2 or 2.4?

It depends on where the video will actually be watched. For web, social and client review I use 2.2, because it sits in the middle of how browsers and phones behave. For broadcast delivery, or a grade that will be watched in a dim room on a proper reference monitor, 2.4 is the better call. Either way, I still check at 1.96 before sending to clients on a Mac.

Can PlayPause fix the color shift for me?

No, and I'd rather be straight about that, because PlayPause doesn't regrade or retag your file and the fix lives in Premiere. What PlayPause does is give you browser playback of the exact copy the client will see, a way for them to draw on the problem area, and a version stack so the corrected export sits next to the original for a fair comparison.

Does my client need an account to leave color notes?

No, the client opens one link in a browser, with no account and no install, and can leave frame-accurate comments, range comments and drawings straight away. Links can also be password protected and revoked instantly, which helps when a review copy travels further than you planned.

If your exports keep drifting between your screen and the client's, start with the viewer settings and the Difference test, right, and then make the browser check a habit before any link goes out. Every PlayPause plan comes with a 7-day free trial, so you can run your next color round through it and see whether the notes get clearer, and all the plans are laid out on the pricing page.

So yeah. That's my way of saying it.