Do not change every Deliver setting at once. Record the error and the point where rendering stops, then run a small test that separates a timeline problem from an output-path or encoder problem.

Official Resources#

Menu names and available encoders vary by Resolve version, operating system, GPU, and Free or Studio edition. Record those details before following instructions written for another system.

Capture the Evidence Before Retrying#

Save the project, then export a .drp backup from Project Manager. Create a project archive if the backup must include source media. Do not delete clips or a project database while diagnosing a render.

Write down:

the exact error text;
the percentage and timecode where rendering stops;
whether it stops at the same place each time;
the format, codec, encoder, resolution, and frame rate;
the output drive and available space;
whether Quick Export or the Deliver page was used.

Take a screenshot of the Render Queue details. A label such as “GPU processing error” narrows the test, but it does not identify a single cause by itself.

Choose the Failure Stage#

Does the job fail before rendering starts?
├─ Yes → Test the output path and a basic Deliver preset.
└─ No
   ├─ Stops at the same frame or percentage → Isolate that timeline range.
   ├─ Stops at changing positions → Test media, storage, GPU, and driver stability.
   └─ Reaches the end but produces no usable file → Test file finalization and audio.

1. Failure at the Start#

Export a short section to a local folder under a new filename. Avoid a network share, cloud-synced folder, or removable drive for this test.

Windows: C:\Users\YourName\Videos\ResolveTest
macOS: /Users/YourName/Movies/ResolveTest

Confirm that the drive has room for the output and temporary work. Check that you can create a normal file in the folder and that another application is not holding the previous output open.

Create a diagnostic job on the Deliver page:

Setting	Test value
Format	MP4
Codec	H.264
Resolution	1920 × 1080
Frame rate	Match timeline
Encoder	Native, software, or Auto where available
Audio	AAC, enabled
Render	Single Clip

This is a compatibility test, not a master-delivery recommendation. If it works, restore the required settings one at a time. The first change that reproduces the failure identifies the next setting to investigate.

If Quick Export fails but this job works, continue from the Deliver page and compare its destination and preset with Quick Export. Do not treat the project timeline as faulty yet.

2. Failure at the Same Frame#

Convert the percentage into an approximate position:

timeline duration × failure percentage = approximate failure time

A 20-minute timeline that fails near 65% points to roughly 13:00. Render workload is not uniform, so inspect several seconds on both sides rather than assuming that 13:00 is the exact bad frame.

Set In and Out points around that area, then set the Deliver page's render range to In/Out Range and render only that section. If it fails:

Duplicate the timeline.
Disable the top video track and retest.
Re-enable it, then bypass the color grade, OpenFX, or Fusion clip in that range.
Remove one transition or title at a time.
Replace the suspected source with a newly transcoded copy.

Possible triggers include a damaged frame, offline media, variable-frame-rate phone or screen footage, a large still, a speed change, temporal noise reduction, Fusion, or a nested clip. A repeatable percentage identifies an area to test, not a confirmed cause.

Test Fusion and Cache Separately#

For a Fusion composition, check for missing MediaIn sources or red error nodes. Bypass heavy nodes and reduce unusually large image inputs. On a duplicate timeline, Render in Place can show whether pre-rendering the composition allows the full job to finish.

If the same area has cached output, disable Use render cached images for one test or remove only the cache for the suspected clip using the commands available in your Resolve version. A successful uncached render suggests that cached data was involved. It does not prove the effect or source clip is healthy. Keep the editable composition and source media.

3. Failure at Changing Positions#

Changing failure points suggest a resource, storage, driver, or media-read problem more than one fixed timeline frame, although they do not prove it.

Test in this order:

Restart Resolve and close other GPU-heavy applications.
Render the same short range twice.
Copy the media used in that range to a local drive and relink it.
Switch from a hardware encoder to Native or software encoding where available.
Temporarily disable demanding OpenFX, noise reduction, or Fusion processing.
Check Blackmagic support information for the installed Resolve build and GPU driver.

GPU-related messages can reflect VRAM pressure, an unsupported encoder profile, a driver problem, or an effect. More system RAM does not increase GPU VRAM. If software encoding succeeds, the project passed that test; more evidence is still needed before blaming the hardware encoder alone.

If a phone recording, screen capture, or downloaded clip is suspect, create a constant-frame-rate intermediate and replace only that source. Confirm that the new clip passes the short-range render before attempting the whole timeline. Keep the original media until delivery is verified.

4. Failure Near Completion#

When progress reaches the end but the file is missing, tiny, or unplayable, test the output rather than dismantling the timeline first.

Render a short range to a new local path and filename.
Confirm the file size is plausible.
Play it in a second media player.
Check the destination drive for free space and connection interruptions.
Try a different container or the diagnostic MP4 preset.

The final container-writing stage can fail even after frames have rendered. A successful short file at a new path points toward destination or finalization settings, but the full-length job still needs verification.

If the video is present but audio is missing, enable Export Audio on the Deliver page. For an MP4 test, use AAC and verify the selected output bus. If only one track is absent, inspect its track and bus routing on the Fairlight page.

Collect Logs When the Tests Do Not Isolate It#

Reproduce the failure once, then use the diagnostic-log command available under Resolve's Help menu or the procedure documented for the installed version. Include the .drp, exact error, failing timecode, Resolve build, operating system, GPU and driver, source codec, Deliver settings, and the tests that passed or failed when contacting Blackmagic Design support.

Do not publish a log archive without checking it for usernames, file paths, project names, or other local details.

Verify the Output#

A Render Queue status of Complete is not enough. Play the beginning, several middle points, the former failure area, and the ending. Confirm duration, resolution, frame rate, audio sync, and playback on the actual delivery platform. Restore higher resolution, hardware encoding, or heavy effects only after the diagnostic file passes.