The DaVinci Resolve 21 Reference Manual is 4444 pages long and it never once reproduces the text of a render failure dialog. No "Render Job Failed", no "Unsupported format", nothing. If you came here hoping to find Blackmagic's own explanation of the exact words on your screen, there isn't one to find.
What Blackmagic does document is narrower and more useful: one preference that halts a render mid-job, three render-queue dialogs quoted word for word, and a set of encode restrictions published in a separate PDF. That is the honest inventory, and this page sticks to it.
What this error actually means, as far as the docs go
There is exactly one officially documented mechanism for a render stopping before it finishes. It lives in User Preferences, under UI Settings, and the manual describes it like this:
"Stop renders when a frame or clip cannot be processed: When enabled, this will halt a render if DaVinci Resolve detects an error in the encoding, rather than continue to try to process it."
That sentence tells you three things. Resolve has an internal notion of "an error in the encoding" and is watching for one. Halting is a choice controlled by a checkbox — with it off, the documented behaviour is to "continue to try to process it" instead. And the trigger is per frame or per clip, not per project.
So a render that stops partway is the expected behaviour of a working feature, not a mystery. Turning that preference off does not repair whatever the encoder choked on; it only changes whether Resolve gives up at that point.
Do not confuse it with the setting directly beneath it, which reads: "Stop playback when a dropped frame is detected: When enabled, sets DaVinci Resolve to stop playback whenever a frame is dropped on output, to warn you that there are performance issues on your workstation." That one is about playback. The two sit side by side in the same preferences panel and get mixed up constantly.
The fastest fix: render a format your platform is documented to encode
Blackmagic's Supported Formats and Codecs PDF (the July 2025 edition) lists encode support per operating system, and the differences are large enough to explain a lot of failed jobs.
- Windows, H.264 and H.265 — the encode column reads "8-bit OS-supported profiles. More profiles and GPU acceleration in Studio." So the free version does encode, but the profiles available to it come from the operating system, and the extra profiles plus GPU acceleration are Studio features.
- Rocky Linux 8.6 (CUDA), H.264 and H.265 — decode is listed as "Studio Only (GPU accelerated on Nvidia graphics)" and encode as "Studio and Nvidia graphics (GPU accelerated)". Both conditions apply, not one.
- Resolution — the same PDF's notes say: "Encoding video resolutions >= 4K is only supported with DaVinci Resolve Studio." Note that Blackmagic's product page separately says the free version lets you "edit and finish up to 60 fps in resolutions as high as Ultra HD 3840 x 2160". Those two sentences use different verbs and Blackmagic never defines whether UHD counts as ">= 4K", so check the official documentation before assuming which applies to you.
There is a second trap in the Format dropdown itself. The manual says it "gives access to the container formats that are currently available on your system", and that "the available options depend on whether you have Final Cut Pro and QuickTime installed, and on the operating system you're using." A format a tutorial told you to pick may simply not be backed by an encoder on your machine.
The reliable move is to render to something your platform is listed as encoding — Apple ProRes in a .mov or .mkv container, or DNxHR — and then handle delivery as a separate step:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs in your browser tab, so the mezzanine file never leaves your machine, and it takes the delivery encode out of Resolve's render queue entirely. If you need the container changed rather than the size, MOV to MP4 does that alone.
Other documented causes, in order of likelihood
Offline media in the timeline. Per the manual: "When you attempt to add a job to the Render Queue with a timeline that contains any offline material, DaVinci Resolve automatically gives you a warning. You may choose to either cancel adding the job, or to add it anyway, knowing you're about to render one or more offline clips." If you clicked past that warning, the job is rendering clips it cannot read.
Files overwriting each other. This one looks like a failure but isn't. The manual is blunt: "When rendering a clip, DaVinci Resolve automatically overwrites any other media files that have the same name... it's entirely likely that the clips you're trying to output will overwrite one another, leaving you with the last clip you rendered." Three documented options prevent it — "Use unique filenames", "Add source frame count to filename" (only when rendering Individual Clips with Filename uses set to Custom name), and "Place clips in separate folders" (when rendering Individual Clips).
Related dialogs you may have dismissed without reading: "This render may overwrite existing clips in this folder." and "Selected items contain already rendered items. Do you want to re-render them?" — clicking No on the second renders only the jobs not yet rendered.
Disk space. The Render Settings show "Disk space currently used" and "Disk space used after render". Worth knowing: the manual's description of the first label says it "Shows the amount of disk space available on the target volume", which does not match the label itself. Read the number, not the wording.
A mode conflict rather than an encoder problem. The manual flags this as IMPORTANT: "Whenever clip filtering is enabled (via the dropdown menu to the right of the Clips button), Single Clip rendering cannot be selected." Also: "You cannot render partial clips in Individual Clips mode, but you may do so in Single Clip mode."
A licence gate. Several outputs are documented as unavailable without the right licence — IMF is marked "(Studio Version Only)", third-party encoders fall under "Codec Plugins (Studio Version Only)", and remote rendering "does not work with the free version of DaVinci Resolve." CineForm is the sharpest example: "while DaVinci Resolve can read CineForm files, CineForm files cannot be rendered out of DaVinci Resolve unless you've purchased an encoding license for OS X or Windows from GoPro."
What the official documentation does not say
This is the part other pages skip. Across Blackmagic's product pages, the reference manual and the codec PDFs, there is no official statement connecting render failures to any of the following:
- how much VRAM a render needs, or VRAM shortfalls causing failures
- variable frame rate source footage causing a render to fail
- the FAT32 4 GB per-file ceiling breaking an export (a filesystem fact, but not a Blackmagic claim)
- which third-party OFX plugins crash renders
- why a render appears to stall at a particular percentage
Every one of those is repeated constantly in forums, and none of them is citable to Blackmagic. Treat them as things to test on your own machine, not as documented causes.
How to tell it worked
Render a short range first, not the full timeline. With "Stop renders when a frame or clip cannot be processed" left enabled, a range that completes tells you the encoder handled every frame in it; if the job halts, the timecode where it stopped points at the clip to investigate. Then confirm the output file actually plays end to end — a job marked complete in the queue is not the same as a file that opens.
FAQ
Is there an official DaVinci Resolve error list I can look up? Not in the reference manual. It contains no render error dialog text at all. The only render-queue messages quoted in it are the offline media warning, the overwrite notice and the re-render prompt.
Should I turn off "Stop renders when a frame or clip cannot be processed"? Only if you would rather Resolve keep going than halt. The manual's wording is that disabling it makes Resolve "continue to try to process it" — the underlying encoding error is unchanged, so you may get a finished file with a damaged section instead of a stopped job.
Does the free version fail at 4K? The codec PDF says "Encoding video resolutions >= 4K is only supported with DaVinci Resolve Studio", while the product page says the free version can finish up to Ultra HD 3840 x 2160. Blackmagic does not reconcile those, so check the official documentation for your version before planning a 4K delivery.
My render finished but the file is missing or wrong. Check filenames before assuming a failure. Resolve overwrites same-named media automatically, which can leave you with only the last clip rendered. Enable "Use unique filenames" or "Place clips in separate folders".
Can I avoid Resolve's render queue for delivery entirely? For simple size and format changes, yes — render a high-quality master once, then convert in the browser. See all Clapr tools, or compress video if the goal is just a smaller file.
Everything quoted here comes from the DaVinci Resolve 21 Reference Manual, the Supported Formats and Codecs PDF (July 2025) and Blackmagic's product pages, checked 20 September 2026. Hitting a similar wall in another editor? See Premiere Pro's error compiling movie, or browse every fix guide.
