If your video plays smoothly in DaVinci Resolve but stutters after export, first check whether the exported frames contain the hitch or the player struggles to display them. A short comparison export can identify which settings deserve attention.

This workflow is for a Mac editor troubleshooting a completed movie. The controls below follow Blackmagic Design’s July 2026 DaVinci Resolve 21 Reference Manual, which includes Fusion and Fairlight. Earlier versions may place controls differently.

First, establish exactly what stutters

Choose a section where the problem is easy to recognize: a moving shape, scrolling neutral text, or a steady camera move. Include a few seconds before and after the hitch. Use this same section for every test, and keep the original export for comparison.

Watch once with sound, then again muted. Record whether the picture hesitates, the audio breaks up, or both happen together. Also note whether the interruption occurs at exactly the same point on repeated playback. A repeatable location is useful evidence, although it does not identify the cause by itself.

Open the exported movie in QuickTime Player and choose Window > Show Movie Inspector, or press Command-I. Record its frame rate, dimensions, and compression format. Apple documents these as file information available in the inspector. Compare the values with the delivery settings you intended to use. View information about a media file in QuickTime Player on Mac.

Pause just before the problem and advance through it with the Right Arrow key. Use Left Arrow to step back. These are Apple’s documented controls for moving one frame at a time. Look for a held moving object, a sudden position jump, or a distorted intermediate image. A repeated frame in a deliberately static shot tells you little. Keyboard shortcuts and gestures in QuickTime Player on Mac.

Import the export into Resolve and inspect the same passage there, preferably in a separate inspection timeline with matching frame rate. Compare its frames with the original edit. This is a diagnostic comparison: agreement between applications strengthens the evidence that the defect is in the file.

What you observe What to investigate next
Frame stepping looks correct, but normal playback hesitates Playback conditions and the encoded format
The same unexpected hold or jump appears in both applications Source timing, retiming, or rendered effects
Only a transition, title, or composite misbehaves That effect and its inputs
Picture movement is correct, but sound interrupts Audio export and the Fairlight mix

Make one controlled comparison export

Before changing several settings, write down the current export format, codec, dimensions, frame rate, and quality setting. Preserve a copy of the timeline for experiments. Give test files descriptive names, such as test-original-settings.mov and test-prores.mov, so you can compare the actual files without relying on memory.

Export the chosen section as a single movie using QuickTime and Apple ProRes 422, retaining the timeline’s frame rate and dimensions. Blackmagic’s July 2025 codec list documents ProRes encoding on macOS; it also lists H.264 and H.265 support. Check the macOS table rather than applying restrictions from another operating system. DaVinci Resolve 20 Supported Formats and Codecs.

ProRes is useful here as a comparison format. Apple describes it as designed for editing performance and documents several variants with different data rates. ProRes 422 provides a practical test without selecting the higher data rates of 422 HQ or 4444. Actual playback still depends on the file and Mac. About Apple ProRes.

Play both test files from the Mac’s internal storage, with other intensive work paused. Keep the viewing conditions consistent. If the original export was on an external drive, first copy that unchanged file locally and replay it; this separates a storage-location test from a codec change.

Interpret the results carefully:

  • ProRes is smooth; the original format hesitates: investigate the original encoding and playback combination. This does not establish a particular encoder defect.
  • Both contain the same frame-level hitch: investigate the edit, timing, and effects before adjusting compression quality.
  • Both step correctly, but hesitate during playback: continue comparing playback conditions. Avoid rebuilding the edit on that evidence alone.

If the ProRes comparison succeeds, make a new short export in your required delivery format. Change one relevant setting at a time. A lower-resolution comparison can be useful later, but it tests resolution as well as playback workload; keep that result separate from the same-resolution codec test.

Check source, timeline, and export timing

Build a small timing record for the problem section: the source clip’s reported frame rate, the timeline frame rate, any speed adjustment, and the exported file’s reported frame rate. Include fractional rates exactly as displayed. Do not casually substitute 30 for 29.97 or 24 for 23.976.

For timeline-specific settings, right-click the timeline in the Media Pool and choose Timelines > Timeline Settings. The Deliver page’s single-clip frame-rate setting defaults to the timeline rate. Inspect both before changing either. These controls are documented under “Creating and Working with Timelines” and “Rendering Media” in the Resolve 21 Reference Manual.

A frame-rate number alone cannot explain the motion. Consider an illustrative one-second animation containing 30 distinct positions. A 24-frame output has only 24 frame slots for that second. Preserving duration requires some treatment of those positions; it cannot retain all 30 as distinct output frames. This arithmetic illustrates why mixed-rate material needs inspection rather than an automatic “match everything” rule.

Decide which timing is intentional. If the finished movie must be 24 fps, a 30 fps source may need conversion. If the project was accidentally started at the wrong rate, test a fresh timeline at the intended rate before moving the whole edit. Resolve documents custom settings through Use Project Settings in the New Timeline dialog. Check cuts, titles, transitions, and audio alignment after transferring material. Resolve 21 Reference Manual.

Test interpolation on the affected clip

Select the clip and open Inspector > Retime and Scaling > Retime Process. Resolve offers Nearest, Frame Blend, and Optical Flow: these respectively drop or repeat frames, blend adjacent frames, or estimate new frames. Optical Flow can produce artifacts with complex movement. Resolve 21 Reference Manual, “Speed Effects”.

Export the short section with one alternative and compare the actual moving edges. For a synthetic square passing behind another shape, examine the overlap carefully. Choose the result that preserves the intended appearance and timing. If every option exposes the same pause already present in the source, further interpolation changes may not address the underlying material.

Isolate effects and cached media

When the hitch occurs only inside one title, Fusion composition, or transition, narrow the experiment to that element. In the test copy, remove one suspect effect and export the section again. Restore it before trying the next. For a Fusion composition, compare a simplified version with the original, preserving any inputs needed for the remaining nodes to work.

This process provides more useful evidence than disabling everything simultaneously. If one simplification removes the hitch, inspect that element’s animation and timing around the affected frames. If the simplified export still stutters, keep looking upstream rather than rebuilding the entire composition.

For a fresh-render comparison, disable Use optimized media, Use proxy media, and Use render cached images in the Deliver settings, where available. These options allow the final render to use alternate media or cached results. Ensure original media is online first. Resolve 21 Reference Manual, “Rendering Media”.

If that export differs from the earlier one, you have narrowed the investigation to a change in rendering inputs or processing. Re-enable only one option for the next comparison. A difference does not automatically prove that every cache file is faulty, and deleting all caches is unnecessary for this first test.

Follow a separate branch for audio interruptions

If the picture advances correctly while the sound breaks up, keep the video settings fixed. Listen to the same passage in the Fairlight timeline and exported movie. Note whether the interruption follows an edit, a particular track, or an effect.

Create an audio-only comparison: disable Export Video, choose WAVE, and use Linear PCM. Select the same output bus used by the movie export. Resolve documents audio-only rendering, codec selection, sample rate, and output-bus selection in the Deliver chapter. Resolve 21 Reference Manual, “Rendering Media”.

If the interruption remains in the PCM file, inspect the mix and contributing clips at that point. In the test copy, remove one suspect audio effect at a time and export again. If PCM is clean while the movie’s audio interrupts, compare the movie’s audio encoding and playback behavior next. Keep the selected bus consistent so that you are comparing the same mix.

Verify the complete export before finishing

Once a short test works, render the full movie using the successful settings. Open that exact file in the player where you intend to watch it. Inspect the original problem area, several other moving sections, transitions, and the ending. Listen through the audio passages that previously interrupted.

Retain the successful test settings alongside the final file until you finish checking it. The useful outcome is a repeatable export whose motion and sound hold up in the intended playback environment, with enough comparison evidence to explain which change resolved the observed stutter.

Sources