Audio Out of Sync? Common Causes and Fixes

Before fixing anything, identify which of the two problems you have, because they have completely different causes and cures. A constant offset means the audio is shifted by a fixed amount for the entire duration — the sound is always, say, 200 milliseconds early or late, from the first second to the last. This is usually a playback or latency issue and is fixed with a single delay adjustment. Progressive drift means sync is perfect at the start but steadily worsens, so a video that is fine in the first minute is a second off by minute thirty and several seconds off by the end. Drift is caused by a mismatch in timing — sample rate or frame rate — where the audio and video play at slightly different effective speeds, and it needs a speed or rate correction, not a simple offset. The quick test: check sync at the very beginning and again at the very end. Same error throughout equals offset; growing error equals drift. Getting this right saves you from applying an offset fix to a drift problem, which never works.

The most common cause of audio drift in editing: the audio and video have different sample rates. Your video timeline runs at 48 kHz, but your imported audio file is 44.1 kHz. If the editor does not resample correctly, it plays the 44.1 kHz audio at 48 kHz speed — about 9 percent fast — or mishandles the conversion, causing the audio to progressively drift out of sync. Over an hour the offset can reach several seconds. This is exactly why video and broadcast standardized on 48 kHz while music uses 44.1 kHz: mixing the two families invites drift. The fix is to convert your audio to match the video timeline's sample rate before importing — resample to 48 kHz with AudioUtils or FFmpeg ('ffmpeg -i audio.wav -ar 48000 audio48k.wav'). Better still, set your recording device to the project's sample rate from the start so no conversion is ever needed. If a whole project drifts and everything was 44.1 kHz audio in a 48 kHz timeline, re-importing correctly-resampled audio usually resolves it cleanly.

The other big drift cause is variable frame rate (VFR) video. Screen recorders (OBS, phone screen capture) and phone cameras frequently record VFR, where the frame rate fluctuates to save space or handle performance dips. Editing software assumes constant frame rate (CFR), so it misinterprets the timing and the audio drifts during the edit even though it was perfectly synced when recorded — a classic 'it looked fine on my phone but drifts in Premiere' situation. The fix is to convert the video to constant frame rate before editing: HandBrake does this with a checkbox (Framerate > Constant), and FFmpeg forces it with 'ffmpeg -i input.mp4 -r 30 -c:a copy output.mp4' (matching the source's nominal rate). Some editors tolerate VFR better than others — DaVinci Resolve handles it more gracefully than Premiere Pro — but converting to CFR first is the reliable, editor-agnostic fix. Doing this transcode up front prevents a whole category of maddening drift that is otherwise nearly impossible to correct once it is baked into an edit.

A huge share of sync complaints are not about editing at all but about watching — a movie on the TV or a stream where audio leads or lags the picture, usually a constant offset. On the TV itself, most sets have an Audio Delay or Audio Sync / Lip Sync setting (often under Sound > Expert or Advanced settings) that shifts audio forward or back in milliseconds until lips match; this is the first place to look when everything on the TV is off. A common culprit is a soundbar or AV receiver adding processing delay, or the TV's own picture processing lagging behind the audio — the delay setting on either the TV or the audio device compensates. For streaming apps (Netflix, Hulu, Disney+, Plex, and others), a persistent offset is often fixed by pausing and resuming, skipping back a few seconds, or restarting the app, which re-synchronizes the audio and video buffers; Plex and some players expose a per-playback audio-offset control in the playback menu. Bluetooth audio to headphones or speakers adds its own delay (below). If sync is wrong on one specific file rather than everywhere, the file's audio and video streams may genuinely be misaligned, which is a re-mux/edit fix rather than a settings fix.

Bluetooth introduces a constant delay of roughly 100-300 milliseconds between the picture on screen and the sound reaching wireless headphones or speakers — enough to make lips look out of sync during video. This is a hardware and protocol limitation, not a problem with the file, and it affects everything played over that Bluetooth link. For casual listening to music it is invisible; for video it is often noticeable. Fixes: many phones, TVs, and streaming devices apply automatic A/V sync compensation for their own Bluetooth output, so keeping firmware updated helps; some platforms and apps offer a manual audio-delay slider to compensate. For serious watching or any production monitoring, use wired headphones, which have negligible latency. Low-latency Bluetooth codecs (aptX Low Latency, and some LE Audio modes) cut the delay substantially but require both the source and the headphones to support them, and even then do not fully eliminate it. If your 'sync problem' disappears when you switch from Bluetooth to wired, Bluetooth latency was the cause.

When you record audio and video on separate devices — a camera plus a dedicated audio recorder, or two cameras — each device runs on its own internal clock, and no two clocks tick at exactly the same rate. Over a long recording those tiny differences accumulate into audible drift: a two-hour multi-cam shoot can end up several seconds out even though every device recorded 'the same' event. This is why professional sync workflows exist. The classic fix is a clapperboard or a sharp hand clap at both the start and end of recording: align the opening clap to sync the start, then check the closing clap — if it has drifted, you know the total drift and can stretch or compress the audio to match across the whole take. Software like PluralEyes, and the built-in sync in DaVinci Resolve, Premiere Pro, and Final Cut Pro, automates multi-camera alignment by matching audio waveforms. To avoid drift entirely, use devices that share a timecode source or genlock, or record a scratch audio track on the camera itself as a reference to conform the good audio against.

When the whole clip is shifted by a fixed amount, the fix is a single nudge. In any video editor, unlink the audio from the video (or drag the audio track independently) and slide it earlier or later until a sharp visual cue — a clap, a door slam, a consonant like a 'p' or 'b' — lines up with its sound; zoom in on the waveform for frame-accurate placement. Most editors let you type an exact offset in frames or milliseconds once you know the amount. For files where the audio and video streams themselves are misaligned, FFmpeg can shift audio during a re-mux with the '-itsoffset' option (for example, delaying audio by 200 ms) without re-encoding the whole file. For a recurring device offset, measure it once with a clap test and apply the same correction to every clip. The key is that offset correction is a one-time shift applied uniformly — if you apply it and sync is right at the start but wrong at the end, you actually have drift, not offset, and need the speed fix below instead.

Drift — sync worsening over time — is corrected by changing the audio's speed so its timeline matches the video's, not by shifting it. First measure the total drift: align the start, then find how far off the audio is at the end (say, 2 seconds late over 60 minutes). Then stretch or compress the audio by that ratio so it ends in sync. In Premiere Pro, the Rate Stretch tool or interpreting the audio at a slightly different rate does this; in Audacity, Change Speed (which alters tempo and pitch together, appropriate for tiny corrections) or the more transparent high-quality resampling stretches the track by a precise percentage; DaVinci Resolve offers speed/retime controls. For a sample-rate-caused drift, the cleaner fix is to correct the source: re-import audio resampled to the timeline rate rather than time-stretching after the fact. Because the required speed change is usually under one percent, it is inaudible in pitch. For dialogue or podcast audio with irregular timing problems rather than uniform drift, cut and realign segment by segment instead of stretching the whole thing.

Most sync trouble is avoidable with a few upfront habits. Match sample rates across the whole project: decide on 48 kHz for any video work and set every recorder, timeline, and export to it so nothing needs resampling. Convert VFR sources to constant frame rate before editing, especially screen recordings and phone footage. Record a common reference — a clap at the head and tail of every take, or a scratch audio track on the camera — so alignment is trivial later. Monitor on wired headphones during recording to avoid Bluetooth latency fooling performers into playing late. For multi-device shoots, use timecode sync or at least a slate, and keep takes short enough that clock drift stays negligible. Keep TV, soundbar, and streaming-device firmware updated, and know where your TV's audio-delay setting lives. Getting the sample rate and frame rate right at the source prevents the two hardest-to-fix problems (drift) entirely, leaving only simple constant offsets, which a single nudge resolves.