A washed-out DaVinci Resolve export is almost always a data levels question: the file was written using one numeric range, and whatever you are viewing it in is reading it as another. The grade did not change. The interpretation did.
Blackmagic documents this directly, and the sentence that matters most is a warning buried in Chapter 9 of the DaVinci Resolve 21 Reference Manual, on full range output: "it is essential that the application you use to process this media is set to read it as "full range" data, otherwise the images will not look correct."
What data levels actually are
Resolve does not work in the range your file is stored in. The manual is explicit: "It's useful to know that, internally to DaVinci Resolve, all image data is processed as full range, uncompressed, 32-bit floating point data."
So every clip is mapped in on the way through and mapped back out on the way to disk. There are two standard ranges, and the manual defines both.
Video, quoted verbatim:
"Video: Typically used by Y'CBCR video data. All image data from 0 to 100 percent must fit into the numeric range of 64–940. Specifically, the Y' component's range is 64–940, while the numeric range of the CB and CR components is 64–960. The lower range of 4–63 is reserved for "blacker-than-black," and the higher ranges of 941/961–1019 are reserved for "super-white." These "out of bounds" ranges are recorded in source media as undershoots and overshoots, but they're not acceptable for broadcast output."
Full is where the official documentation gets interesting, because the same chapter gives two different upper bounds. On p.227 it says full range data is "simply fit into the full numeric range of 4 to 1023." On p.230, describing the Deliver page option, it says "Full: All clips are rendered as full range (10-bit 4–1019)."
Both numbers are official, three pages apart in the same chapter, and Blackmagic does not reconcile them. Treat the Video figures as solid and the Full upper bound as something to check in the official documentation.
The important part is that the conversion itself is supposed to be invisible. The manual again: "Simply converting an image from one data range to another should result in a seamless change. All "legal" data from 0–100 percent is always preserved and is linearly scaled from the previous data range to fit into the new data range."
Which is exactly why a washed-out export is a mismatch, not a loss. Nothing was destroyed — the two ends of the pipeline simply disagreed about the scale.
The fastest fix: leave the Deliver page on Auto
The control is in the Deliver page render settings. In the Deliver chapter, the manual describes it like this:
"Data levels: Defaults to "Auto," which simply renders all clips with the data level appropriate to the currently selected codec in the "Render to" dropdown menu, which is usually the preferred behavior. Choosing one of the other options ("Video" or "Full") outputs all clips using the selected data range."
Chapter 9 gives the same three options with slightly different wording — "Automatic: The output data level of all clips is set automatically based on the codec you select to render to in the "Render to" dropdown menu", "Video: All clips are rendered as normally scaled for video (10-bit 64–940)", and the Full line quoted above.
And it gives a clear recommendation: "For most projects, leaving this setting on "Automatic" will yield the appropriate results. However, if you're rendering media for use by another image processing application (such as a compositing application) that is capable of handling "full range" data, then full range output is preferable for media exchange as it provides the greatest data fidelity."
So the judgement is straightforward. If the export is going to a player, a viewer, or a delivery target, leave it on Auto. Force it to Full only when you are handing the file to another image processing application that can handle full range — and only if you can also set that application to read it as full range, per the warning at the top of this article. Forcing Full and then opening the result in something that assumes video range is precisely how you manufacture a washed-out file.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
If the file is fine and it is the size that is the problem, compressing it is a separate job from grading it — the compressor above runs in your browser rather than uploading anything, and compress video covers the same ground for non-Resolve sources.
Three more things the manual documents
1. Levels are assigned per clip, at import, based on codec. From Chapter 9: "When you first import media into the Media Pool, either manually in the Media page or automatically by importing an AAF or XML project in the Edit page, Resolve automatically assigns the "Auto" Levels setting. When a clip is set to Auto, the Levels setting used is determined based on the codec of the source media." In other words there is an input-side decision as well as an output-side one, and it is made from the codec.
2. The out-of-bounds data can be kept or clipped. The Deliver chapter documents a separate checkbox: "Retain sub-black and super-white data: Turning this checkbox on lets you choose to output media files that preserve overshoots and undershoots, data that's above the maximum and minimum data levels of the data level you've selected, assuming this is supported by the video format and codec you're exporting to. Otherwise, DaVinci Resolve clips these "out-of-bounds" parts of the signal in an effort to keep your deliverables from violating whatever QC standards you're adhering to in your grade." Note the condition — it only applies if the format and codec you are exporting to support it.
3. Resolve can embed colour metadata, and that is a different control. The manual describes "Color Space Tag: A dropdown menu that lets you choose a color space to embed as metadata in the rendered file. This setting defaults to Same as Project if your project's color science is set to DaVinci YRGB Color Managed, or the ACES Output Device Transform if your color science is set to ACEScc or ACEScct", plus a matching "Gamma Tag" dropdown. Blackmagic's documentation does not state how any particular third-party player interprets those tags, so do not treat tagging as a guaranteed fix.
One more practical note: the control has three different names in the official documentation. Chapter 9 calls it the "Set to video or data level" dropdown menu, the Deliver chapter calls it Data levels with a default of Auto, and Chapter 9 also mentions choosing "Unscaled full range data", which is not one of the three options it just listed. If you are searching the manual and coming up empty, that is why.
How to tell it worked
Since Resolve assigns Auto levels from the codec of the source media, dropping your finished render back into the Media Pool shows you what Resolve itself concludes about the file. Compare that against the timeline you exported from.
Beyond that, be careful about trusting any single viewer as a reference — the failure mode is two applications disagreeing about the range, and Blackmagic's documentation does not certify any specific player's behaviour. For anything you are delivering, check the destination's requirements in the official documentation rather than eyeballing it.
FAQ
Why does my DaVinci Resolve export look washed out compared to the timeline? Because the rendered file and the application you are viewing it in disagree about the numeric range. The manual warns that when you output full range, "it is essential that the application you use to process this media is set to read it as "full range" data, otherwise the images will not look correct."
Should Data levels be set to Auto, Video, or Full? Auto, for most work. Blackmagic writes that "for most projects, leaving this setting on "Automatic" will yield the appropriate results", and recommends Full specifically when rendering for another image processing application capable of handling full range data.
What are the actual numeric ranges? For Video, the manual gives 64–940 for the Y' component and 64–960 for CB and CR, with 4–63 reserved for blacker-than-black and 941/961–1019 for super-white. For Full, the same chapter gives two different figures — 4 to 1023 on one page and 4–1019 on another — so verify against the official documentation.
Where is the Data Levels setting?
In the Deliver page render settings, documented as the Data levels dropdown with a default of Auto. Chapter 9 of the manual refers to the same control as the "Set to video or data level" dropdown menu, which is the main reason people cannot find it.
Does re-encoding the file fix it? Blackmagic's documentation does not describe re-encoding as a remedy for this. The documented controls are the Data levels dropdown and the sub-black and super-white checkbox. If you need to re-encode for size or compatibility reasons, that is a separate task — see all Clapr tools.
Related: DaVinci Resolve bypass re-encode explained, 4K export and the Studio requirement, and more export troubleshooting in the fix guides. All quotes above are from the DaVinci Resolve 21 Reference Manual, checked 16 September 2026.
