Why your DaVinci Resolve export looks washed out (and how to fix it)
In most cases nothing is wrong with your grade. The exported file is being shown with a different gamma than the one you graded for, so the shadows come up and everything looks flat. That's most common in QuickTime and Safari on a Mac. Less often, the cause is a levels mismatch (video versus full range), or Log footage that was never converted.
The good news: each cause has a clear sign, and a clear fix. Find yours first, then change one setting, not ten.
First, find out which problem you have
Export a short test (ten seconds is enough) and open it in two or three places. What you see tells you where to look.
| What you see | Most likely cause |
|---|---|
| Washed out in QuickTime or Safari, fine in VLC or on Windows | The gamma tag and how Apple's apps read it |
| Washed out everywhere, blacks look grey even in VLC | Data levels (video vs full range) |
| Flat and grey in the Resolve viewer too | Log footage that was never converted |
| Fine on your computer, different after upload | The platform re-encoding or reading the file differently |
Don't judge by eye alone. Put your timeline and your export side by side on the waveform: if the export's blacks sit higher and its whites sit lower, the levels have been squeezed.
Cause 1: the gamma tag (the classic Mac problem)
When you grade in Resolve for normal video, you're usually working to Rec.709 with a display gamma of 2.4, the standard for watching in a dim room. When you export, Resolve writes a small tag into the file that says, in effect, "this is Rec.709".
Apple's players (QuickTime, Safari, Final Cut, Photos) read that tag and manage colour themselves. They display a file tagged as standard Rec.709 with lighter shadows than Resolve's viewer does at gamma 2.4. Same pixels, different interpretation, and your careful contrast looks lifted and milky.
There are two honest ways to deal with it. Pick one.
Fix A: tag the export for Apple-style playback. If your film will mostly be watched online and on phones, tell Resolve to tag the file so Apple devices show it the way you graded it.
- Go to the Deliver page and open Advanced Settings in the Video tab.
- Set Gamma tag to Rec.709-A. Leave Color space tag on Rec.709 (or Same as Project if your project is already Rec.709).
- Export the test again and compare it in QuickTime.
If you work in DaVinci YRGB Color Managed, you can do the same at project level instead: in Project Settings → Color Management, set the output colour space to Rec.709-A.
Fix B: make your viewer show what Apple will show. If you grade on a Mac and mostly deliver to Mac and iPhone viewers, you can turn on Use Mac display color profiles for viewers in Resolve's Preferences. The viewer then matches QuickTime, and you grade to that.
Cause 2: data levels (video vs full range)
Video files normally store black at a value above zero and white below the maximum. That's "video" or "legal" range. Graphics and some cameras use the full range. If one side of the chain thinks the file is video range and the other thinks it's full, you get grey blacks and dull whites (or the opposite: crushed blacks and clipped highlights).
- In the Deliver page, under Advanced Settings, leave Data levels on Auto for almost every delivery. Resolve then uses video levels for normal video codecs, which is what players expect.
- If the problem starts before the export (the clip already looks washed out on the timeline), right-click the clip in the Media Pool, choose Clip Attributes, and check Data Levels. A clip recorded at video levels but marked as Full (or the other way round) needs correcting here, at the source.
- Check the waveform after the change. Footage with real blacks in it should reach down to the bottom of the scale.
Cause 3: Log footage that was never converted
If the image is flat and grey in the Resolve viewer too, you may simply be looking at Log. N-Log, S-Log3, V-Log, Apple Log and the rest are designed to look flat: they squeeze the camera's range into the file so you have room to grade. Exporting them without a conversion gives you exactly what the camera recorded.
Convert them on purpose, in one of these ways:
- a Color Space Transform node from the camera's colour space and gamma to your timeline space,
- colour management, with the right input colour space set on the clip,
- or the camera maker's official LUT, as a starting point.
Use one of them, not two. Stacking a camera LUT on top of a colour-managed clip converts twice, and the result looks wrong in a different way. I explain how to choose between these approaches in YRGB, Color Managed or ACES?.
Cause 4: the platform
YouTube, Instagram and others re-encode everything you upload. They also read your tags, and they don't all read them the same way. Before you upload the real thing:
- Upload a short private test.
- Watch it on the devices your audience uses: a phone, a laptop, a TV if it matters.
- Change one setting at a time, so you know which change fixed it.
My export checklist for web delivery
These are the settings I start from for a film that will mostly be watched online. Adjust them for your platform's own recommendations.
Format QuickTime (or MP4) Codec H.264 or H.265 Resolution Same as the timeline Frame rate Same as the timeline Quality Restrict to a high bitrate (e.g. 40,000 Kb/s for 4K) Advanced settings Data levels Auto Color space tag Rec.709 Gamma tag Rec.709-A (if most viewers are on Apple devices)
Then compare the test file against your timeline on the waveform, not just by eye.
Why this keeps happening
Washed-out exports aren't really an export problem. They're a colour management problem that shows up at the very end. Once you know what your project's colour space is, what the file is tagged as, and how the viewer will read it, the problem stops being mysterious. That chain, from camera to screen, is a big part of what I teach in Finishing and problem-solving and Colour management.
