Cutsio Blog

How to Fix an Out-of-Sync Timeline in DaVinci Resolve

Diagnose and fix audio/video sync issues in DaVinci Resolve, from a single slipped clip to VFR drift, playback lag, sample-rate mismatches, and external-monitor delay.

How do you fix an out-of-sync timeline in DaVinci Resolve?

The fastest way to fix an out-of-sync DaVinci Resolve timeline is to first establish whether the issue exists in the edit, only during playback, or only in the rendered file. A single slipped clip can usually be returned to sync directly in the timeline, while gradual drift points to the source media, frame rate, or audio clock. Before you transcode anything, use Cutsio's free Media Info tool to inspect the suspect file's duration, frame rate, codec, audio sample rate, and channel layout locally in your browser. That turns an assumed sync problem into a diagnosable one.

“Out of sync” describes several different failures. Dialogue may be late by the same amount throughout the edit. It may start in sync and slowly drift away. The timeline may look wrong only while Resolve struggles to play it back, even though the export is correct. Or a clip may have been nudged several frames away from its linked audio. Each needs a different fix, so do not start by changing project settings blindly.

Begin with a short test export of the affected section and play it through the computer's built-in speakers or wired headphones. If the export is correct, your project media and edit are likely fine; focus on playback performance or external hardware. If the export is wrong too, inspect the clip relationship, timeline frame rate, source media, and audio settings.

Is the clip actually out of sync, or is Resolve only playing it back poorly?

An actual sync error is visible in the timeline or present in the render; a playback issue disappears in a clean export or when the system can maintain the timeline frame rate. Making this distinction saves the most time because a slow computer can make a correctly aligned edit look broken.

Play the same section three ways: in the Resolve viewer, in a short exported file, and—if possible—through different audio hardware. Use a moment with an obvious visual cue, such as a clap, door close, spoken plosive, or a hand striking an object. Watch the waveform and the picture together at normal speed and frame by frame.

| Symptom | Most likely cause | First check |

| --- | --- | --- |

| One clip is early or late by a few frames | A manual nudge, slip, or broken link | Inspect the clip's out-of-sync indicator |

| Sync is correct at the start but drifts later | Variable frame rate or mismatched clocks | Inspect the original file and test a CFR transcode |

| Resolve playback looks late but the export is fine | Decode or GPU performance, Bluetooth, or external display latency | Test built-in audio and lower proxy resolution |

| Every clip is offset in the rendered file | Timeline/project settings or a global monitoring configuration | Check the timeline frame rate and audio routing |

| Only an external recorder track is wrong | Incorrect sample rate, timecode, or manual sync point | Check the original audio file and sync method |

Do not use a playback workaround to conceal an edit-level error. Conversely, do not retime or relink a project because a wireless headset adds noticeable latency. The test export provides the boundary between those two problems.

How do you fix a single slipped audio or video clip?

Fix a single slipped clip by returning its linked audio and video to their original relationship rather than manually guessing the number of frames. Resolve can display an out-of-sync indicator on linked clip segments when their relative positions have changed.

On the Edit page, zoom in around the affected clip and look for colored numeric indicators on the linked audio or video. A value indicates that one side has moved relative to the other. Right-click the indicator or the clip and use the available sync command—typically a “slip into sync” style option—to restore the original offset. The exact label can vary slightly by Resolve version, but the goal is the same: realign the linked segments without changing their shared source relationship.

If no indicator appears, turn on linked selection and confirm that both the audio and video are actually linked. A common failure is moving only the audio track because linked selection was off, a track was locked, or the clips were intentionally unlinked earlier in the edit. Undo is safest immediately after an accidental move. After additional edits, restore sync from the indicator or use a known visual/audio cue instead of dragging by eye.

For a clip that was recorded separately, do not assume it has an original linked offset to recover. Resync it from a clapper, scratch audio, waveform match, timecode, or an identified spoken/visual event. Mark the cue first, then align both sources to the same frame. This is more reliable than nudging repeatedly while playing back.

Why does audio drift farther out of sync over time?

Gradual drift usually means the source video's timing is not truly constant or the audio and video were recorded against different clocks. If the beginning is correct and the ending is increasingly wrong, moving the clip by a fixed number of frames only moves the error; it does not solve it.

Phone captures, browser recordings, video calls, and some screen-recording workflows can produce variable-frame-rate media. Variable frame rate changes the timing of individual frames to suit the capture conditions. It often plays acceptably in consumer players, but it can cause unreliable timing or decode behavior in an editing workflow that expects a stable frame cadence.

The durable fix is to create an editing-friendly, constant-frame-rate version from the original source, then replace the VFR clip in the Resolve project. Use a suitable transcode workflow for your system and keep the original file archived. Choose a constant frame rate that matches the intended project cadence and a codec appropriate for editing, such as ProRes or DNxHR when you need a robust intermediate. Do not change the project's frame rate mid-edit just to accommodate one problematic phone clip.

An external audio recorder can create a similar symptom even when the video is constant frame rate. A long take recorded by two independent devices may drift because their clocks do not run at precisely the same rate. Verify the recorder's sample rate and the production sync method. For long-form double-system work, use timecode or a controlled sync workflow at acquisition; for a one-off problem, create a corrected version of the source rather than introducing arbitrary speed changes throughout the timeline.

How do frame rate and sample rate affect DaVinci Resolve sync?

Timeline frame rate defines the edit's visual clock, while audio sample rate defines the audio clock. A mismatch is not automatically wrong, but careless conversions or incorrectly interpreted media can produce timing problems, especially in long sequences.

Check the timeline frame rate before editing begins and avoid changing it after media has been cut. Make sure the delivery frame rate matches the project requirement: 23.976, 24, 25, 29.97, 30, 50, and 59.94 are not interchangeable. A clip intended for one cadence can be conformed, retimed, or interpreted incorrectly if it is forced into another without a deliberate conversion plan.

For audio, use a consistent professional sample rate across the project where possible, commonly 48 kHz for video work. An audio file recorded at a different sample rate may still import, but a mistaken conversion or an incorrectly labeled file can affect timing and pitch. Inspect the source metadata before applying a fix. Cutsio's free Media Info tool can show sample rate, channels, codec, duration, and file-level video properties without uploading the file, which makes it a useful first check before you rebuild media or change a Resolve setting.

| Pattern | What to investigate | Safe response |

| --- | --- | --- |

| A short offset stays constant | Clip position or sync point | Restore the clip relationship or realign to a cue |

| Drift grows through a phone/screen capture | Variable frame rate | Make a CFR edit-friendly transcode and replace it |

| Drift grows through a long double-system take | Independent device clocks or sample-rate handling | Recheck the original audio and correct the source deliberately |

| A whole project looks wrong after a conform | Frame-rate interpretation or timeline setup | Verify project/timeline settings before recutting |

| Audio is late only on one output device | Monitoring latency | Fix the monitoring path, not the timeline |

How do you fix sync that is wrong only during Resolve playback?

If the export is in sync but Resolve playback is not, reduce the playback burden and test the output path. The source media and edit do not need correction when the render proves that they are aligned.

First, look at whether Resolve is sustaining the timeline frame rate. High-resolution H.264 or H.265, long-GOP camera media, Fusion effects, noise reduction, and heavy color nodes can exceed what the system can decode in real time. On the Playback menu, reduce Timeline Proxy Resolution or enable an appropriate proxy/optimized-media workflow. Lowering viewer quality does not alter the final render; it only gives the system a lighter preview to play.

Then test external hardware. Bluetooth speakers and headphones add latency by design. Some displays and televisions also process picture differently from audio, especially when connected over HDMI. Switch temporarily to built-in speakers or wired headphones. If the sync problem disappears, leave the timeline unchanged and adjust the monitoring setup, device delay settings, or display processing instead.

When using professional I/O hardware, confirm the video and audio are both routed through the intended device and review its monitoring-delay configuration. A mismatch between a laptop viewer, an external display, and a separate audio path can make a correct edit feel late even when the export is accurate.

What should you do before replacing or transcoding media?

Preserve the original, confirm the diagnosis, and test one clip before rebuilding a whole timeline. Transcoding can solve VFR or troublesome codecs, but it should not be the default response to every offset.

Use this sequence:

1. Duplicate the project or timeline and label the troubleshooting version.
2. Export a short affected section and test it outside Resolve.
3. Inspect the suspect source file's frame rate, duration, codec, sample rate, and channels.
4. Transcode one representative clip to a constant-frame-rate editing format if drift suggests VFR.
5. Import the test transcode and compare its timing against the original.
6. Replace media only after the test stays in sync through the affected duration.

Keep the original source and its filename intact. A transcode is working media, not a replacement for the camera original. This discipline lets you reverse course if a later conform, color grade, or export requires the original asset.

How can you prevent sync problems in the next Resolve project?

Prevent sync issues by standardizing the project clock, keeping source details visible, and treating playback hardware separately from editorial alignment. The best troubleshooting step is one you never need to run.

Set the timeline frame rate deliberately before cutting. Record or transcode problematic captures to a constant frame rate before importing. Keep external audio at the intended sample rate and use a clear sync method for double-system shoots. Generate proxies for media that cannot play reliably in real time. Finally, test the actual delivery path early—especially if the client will watch through a platform that re-encodes uploaded video.

For teams with large libraries, Cutsio can help make the source stage more searchable before the edit begins. Cutsio's Visual Intelligence analyzes the visual content of every frame alongside audio, creating a unified search index for any moment. That does not replace technical sync, but it helps an editor retrieve the clap, spoken phrase, or action needed to verify a sync point without scrubbing through hours of footage.

FAQ

Why is my DaVinci Resolve timeline out of sync but the export is correct?

Your edit is probably aligned and the issue is likely playback performance or monitoring latency. Test with built-in or wired audio, then reduce proxy resolution or use optimized media before changing clips.

Can variable-frame-rate footage cause audio drift in DaVinci Resolve?

Yes. Variable-frame-rate phone, screen, and browser captures can drift or behave inconsistently in an editing timeline, so a constant-frame-rate transcode is often the reliable fix.

How do I fix one audio clip that moved out of sync?

Use the linked clip's out-of-sync indicator and the corresponding sync command where available, or realign the clip to a known visual/audio cue. Do not repeatedly drag it by eye.

Should I change my project frame rate to fix one drifting clip?

No. Keep the project cadence stable and correct or transcode the individual problematic source unless the entire project was created with the wrong delivery frame rate.

Why is audio late only when I use Bluetooth headphones?

Bluetooth playback introduces latency, so the monitoring chain—not the timeline—usually causes the apparent offset. Verify with wired or built-in audio before making any editorial changes.