How to fix lips lagging behind voice in video recordings

Try It Yourself

Confirm the direction and size of the drift

Reports which track is late and by how many milliseconds, which determines both the fix and which track you shift.

Run the Audio/Video Sync Test

Lips lagging behind voice specifically means video is arriving late relative to audio, which is the opposite of the more common audio-delay case.

Confirming the direction matters because both the fix and the track you shift are different. Assuming the usual direction is the single most common mistake here.

Video effects add processing time. Background blur, virtual backgrounds and beauty filters all take real computation before a frame is ready, which pushes video behind audio specifically.

Confirm which track is late, and by how much, with the Audio/Video Sync Test.

1. Turn off background blur and virtual backgrounds, then re-measure.
2. Disable appearance filters and touch-up effects.
3. Re-enable them one at a time to identify which one costs the most.

Higher resolution and higher-quality encoding take longer per frame than audio does, so on an underpowered machine video is the side more likely to fall behind under load.

Dropping from 1080p to 720p, or switching to a faster encoder preset, often resolves this without any post-production work.

Nearly all video editors let you nudge the video track a small number of frames relative to the audio track.

Once you know the actual delay in milliseconds or frames, this is a five-second fix. Unlink the tracks, enter the offset numerically rather than dragging, and re-check.

If your machine falls behind only under sustained load, run the Hardware Stress & Headroom Test.

Nudging a track while watching lip movement is imprecise and slow, and it is easy to overshoot and then chase the error back.

Measuring against a synchronised reference event first tells you exactly how many frames or milliseconds to shift, which turns the correction into a single step.

If this happens consistently, the durable fix is reducing video-side processing load — fewer real-time effects, more efficient encoding settings — rather than correcting it after every recording.

A machine that keeps falling behind under load will keep producing the problem, and post-production correction is time spent repeatedly on the same fault.

To measure the camera stage of the pipeline on its own, use the Capture Card & DSLR Latency Auditor.

Settings → Output → Encoder, and Filters on the camera source

Switching to hardware encoding via NVENC or QuickSync frees the CPU and often removes the lag entirely.

Settings → Background & Effects, and Settings → Video

Turning off blur and HD together is the most effective combination on a machine without hardware encoding.

Effects and avatars → Background effects

Teams applies effects before encoding, so removing them shortens the video path directly.

Timeline → unlink audio and video, then offset numerically

Entering the offset as a number rather than dragging keeps the correction repeatable across a batch of clips.

1. Measure the offset and confirm video is genuinely the late track.
2. Turn off background blur and virtual backgrounds, then re-measure.
3. Disable appearance filters and touch-up effects.
4. Drop capture resolution from 1080p to 720p and re-check.
5. Switch to a hardware encoder such as NVENC or QuickSync if available.
6. Close other applications competing for CPU during the recording.
7. For existing recordings, unlink the tracks in your editor and offset the video numerically.
8. Re-measure after correcting to confirm you did not overshoot.