DaVinci Resolve Export Looks Washed Out? Fix the Review Copy Before Sending

I'm going to say something slightly unpopular, right, which is that most of the advice you find when your DaVinci Resolve export looks washed out is solving the wrong problem. The usual fix is to push more contrast into the grade and pull the blacks down until the file looks okay in QuickTime, and then that same file looks crushed and muddy on every other screen it lands on.

To be very honest, I did exactly that for a while in my own agency, and it cost us rounds we didn't need to spend. The grade was fine all along, and the real fault sat in the little bits of metadata that tell QuickTime or Chrome or a phone how to decode the pixels, so when those tags and the player disagree you get that flat, milky look that makes a colorist want to throw the laptop.

So this is the version I give my own team, which starts with finding where the image actually goes flat and ends with the step most YouTube fixes stop short of, watching the review copy in a browser before the client does.

Why a DaVinci Resolve export looks washed out on other screens

The way I explain it to new editors is that every video file carries the pixel values you graded plus a small label saying what color space and gamma those pixels were made for, right. The player reads that label and decides how to show the pixels, so when you grade on a Rec.709 Gamma 2.4 timeline and a Mac player reads the file's label as a lighter curve, the shadows lift and the image looks like someone breathed on the glass.

The catch here is that the pixels themselves are usually fine. Pull the file back into Resolve and the scopes match your grade, and I'm pretty sure that's why so many forum threads go in circles, because one person checks the scopes, another opens QuickTime, and both are describing exactly what they see.

So before touching anything, I find out where the image goes flat, because each answer points at a different cause:

• Flat in the Resolve viewer as well: a source problem, usually HDR footage on an SDR timeline
• Flat only in QuickTime or Safari on a Mac: the gamma tag
• Grey blacks in every player, Windows included: a levels mismatch
• Fine on your machine but flat after upload: the platform's re-encode

The first one catches a lot of people with phone footage, right, because recent iPhones record HDR in HLG with Dolby Vision by default. On a Rec.709 timeline without a conversion that footage looks washed out before you render anything, so the fix is a Color Space Transform node from Rec.2100 HLG to Rec.709 Gamma 2.4, or proper color management on the project, and no export tag will rescue it later.

Levels are the sneaky one. Video files normally store black slightly above zero and white a bit below the maximum, which is video or legal range, and if a player reads that as full range the blacks come out grey, while the opposite mistake crushes them, you see what I mean here. I covered the same problem from the other side in why Premiere Pro export colors look different, and it's almost identical, it's just that Resolve gives you more knobs to get it very very wrong.

The pixels are usually fine

A washed out export normally carries the right values with a label the player reads differently, so check tags and levels before you touch the grade.

Color space and gamma tags behind the DaVinci Resolve gamma shift

Inside the file there are basically three tags that matter, the color primaries, the transfer characteristic, which is the gamma part, and the matrix coefficients. Resolve writes them from your output color space unless you override them on the Deliver page, under Advanced Settings in the Video tab, where Color Space Tag and Gamma Tag both sit on Same as Project by default, right.

So for instance, a Rec.709 Gamma 2.4 timeline gets tagged as standard Rec.709, and Apple's color management reads that tag with a lighter curve, usually quoted at around 1.96. That's the QuickTime gamma shift in one sentence, the grade was made for a darker curve and it's being shown on a lighter one, so everything below the midtones floats up.

Rec.709-A is the option Blackmagic added for exactly this, and depending on which version of DaVinci Resolve from Blackmagic you run, it sits in the output color space list under Color Management or in the Gamma Tag dropdown on the Deliver page. That Rec.709-A export tag makes Apple players show the file much closer to your viewer, and if you also switch on the preference to use Mac display color profiles for viewers, the viewer and QuickTime finally agree on a Mac.

The thing to remember is that Rec.709-A is really really a Mac answer, because on Windows, in some browsers and after a platform re-encode the tag can be read differently or ignored. Some colorists I respect grade web deliverables in Gamma 2.2 and skip the tag games entirely, so does that make sense, right, there isn't one magic setting, and the honest answer depends on where the file will be watched.

Render settings that keep the review copy honest

For the review copy, which I always keep separate from the master, I render H.264 or H.265 and set the tags on purpose instead of leaving them on Same as Project and hoping. The full recipe lives in Resolve export settings for review links, so here I'll stick to color.

The output tag should match the audience, so Rec.709-A for a client I know is on a MacBook, and standard Rec.709 with Gamma 2.4 for broadcast or another colorist on a calibrated monitor. If the piece ends up on YouTube, I check the render against YouTube's recommended upload encoding settings so I'm not reviewing one thing and publishing another, right. Data Levels on that same panel stays on Auto, because forcing Full on a file that players expect in video range is the fastest way to a color shift after render that nobody can explain.

And the boring habit that, trust me on any level, saves arguments is writing the tag into the file name next to the version number, so when the client says the second version looks different, I know straight away whether to check the tag or their screen.

A worked example with a MacBook client

Say the timeline is Rec.709 Gamma 2.4, the piece is a 90-second interview with a dark office behind the speaker, and the client reviews everything in Safari on a MacBook. Rather than render the whole thing and hope, I set a 20-second range on the Deliver page covering the darkest shadows and some skin, and render it twice, once on Same as Project and once with the Gamma Tag on Rec.709-A.

Both go up to PlayPause on the same card, and I open my share link in Safari, pause each on the same frame and compare the shadow side of the face against the Resolve viewer with Mac display color profiles on. In my experience the Rec.709-A render holds its shadows in a setup like this while the other floats up, and once I've seen that with my own eyes I set the tag for the full render, which costs about five minutes and saves a whole round.

• Output tag chosen for where the client will watch
• Gamma tag set on purpose, never left to chance
• Data levels on Auto unless you know why
• Review copy in H.264 or H.265 with the master kept separate
• Tag written into the file name

Testing the review copy in a browser before the client sees it

This is the step I think matters more than any tag, and almost every guide skips it, because your client is going to click a link and watch in whatever browser is open on their laptop, so the only honest pre-send check is to watch it that way yourself first.

With Resolve the flow is export, upload, review, so the review copy goes up to PlayPause and plays in the browser from a streaming copy while the original stays untouched, which the proxy and transcoding page explains properly. The client watches that same streaming copy, so it's the version worth checking, and I open my own share link in Safari, in Chrome and then on my phone, because browsers don't all handle color tags the same way.

If the browser version looks lifted compared with my reference, I fix the tag or the levels before the client has formed an opinion, because once a client has seen a washed out version and called it cheap, you're fighting that first impression for the rest of the project. The PlayPause page for DaVinci Resolve shows how this loop fits around a color pass.

1Render the review copy with a chosen tag

2Upload it and open your own share link in two browsers

3Compare it against your reference on the same screen

4Fix the tag and upload the next version

5Send the link once it matches

Once it's sent, who-watched analytics on the Creator plan and up tells me when the client opened the link and from which city, so I know whether silence means a problem or just a client who hasn't watched yet.

Review_Cut_v4.mp4In Review

212160p · ProRes

00:34 / 02:18

SR

Sarah 0:34

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

Explaining display differences to clients without losing trust

Even with perfect tags, the client is still watching on a screen you don't control, with brightness at forty percent, True Tone on, Night Shift warming everything and so on. I've had grades that looked right in the browser on my end come back with a note saying too yellow, and the cause turned out to be the client's laptop settings.

So I say it early, in the message with the first link, something like this grade was checked in a browser, and if anything looks off on your screen, draw on the frame and tell me what you see, and we'll work out together whether it's the display or the grade. Clients respond really well to that compared with a lecture about gamma curves, and the trust stays on your side because you raised it first, right.

I went deeper on this in clients approving grades on uncalibrated laptops, and at the end of the day nobody can make every screen match, so the realistic goal is keeping the conversation about the grade instead of a tag nobody chose.

“

Say the display caveat before the client finds it, and the trust stays on your side.

Getting grade notes with drawings instead of vague adjectives

The worst grade notes I get are single words like warmer or more cinematic, and they hurt because nobody knows which part of the frame they mean, so you end up spending a full round just finding out.

With PlayPause the client pauses on the exact frame, leaves a frame-accurate comment and draws on it, so they circle the face and write that it feels a little green, and now I know where to look and which way to push, right. The drawing and markup tools are on every plan, and the client does all of this from one link without making an account.

When I fix the tag or the grade, the new export goes up as MV2 on the same card, so the version stack keeps MV1 and MV2 together instead of two random links in a chat thread. On the Agency plan and up I open them in side-by-side version compare to show exactly what changed, which I wrote about in side by side grade comparisons, and getting the notes back into your timeline is covered in timestamped notes in Resolve. If you're coming from a Premiere house, the Premiere to Resolve review workflow shows where this check sits at every hop.

Old way

a client texts that the grade looks washed out and nobody knows which file, screen or frame they mean

With PlayPause

the note sits on the exact frame with a drawing, and the retagged MV2 stacks under MV1 for a clean comparison

Frequently asked questions

Should I export every DaVinci Resolve project with Rec.709-A?

I wouldn't, to be very honest. Rec.709-A is great when you know the client watches on Apple devices, because QuickTime and Safari then show something much closer to your viewer, but on Windows, in some browsers and on platforms that re-encode, the tag can be read differently. I pick the tag per delivery based on where the file will be watched, and I write it into the file name.

Why does my export look fine in VLC but washed out in QuickTime?

Because the two players treat the tags differently, right. QuickTime uses Apple's color management and reads the standard Rec.709 tag with a lighter curve than the Gamma 2.4 you graded in, while VLC and many Windows players basically ignore that part of the metadata. The pixels are the same in both, so before you regrade anything, render a short test with the Rec.709-A tag and check your data levels.

Will YouTube or a social platform fix a washed out export?

In my experience it won't, because platforms re-encode your upload with their own handling, so a file that looks lifted on your Mac can look fine after upload and the other way round. The safer habit is reviewing the file the way it will actually be watched, in a browser, and checking your render against the platform's published upload settings.

Can I see PlayPause comments inside DaVinci Resolve?

Not inside Resolve itself, and I'd rather be straight about that, because the only native PlayPause panel is the one for Premiere Pro. For Resolve, Final Cut Pro and After Effects the loop is export, upload, review and then use the notes in your editor, so for colorists the value sits in the browser review, the drawings on the frame and the version stacks.

Where I'd start on your next export

If your next Resolve export is going to a client, render it with a tag you chose on purpose, upload it, watch it in a browser before they do and let the notes come back as drawings on the frame. If you're still weighing tools, I laid out the options in a Frame.io alternative for Resolve colorists, and every PlayPause plan comes with a 7-day free trial, with the Creator, Agency and Enterprise details on the PlayPause pricing page, priced flat per workspace rather than per member.

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