Audio-Visual Latency & Sync
How to measure millisecond audio-video delay on a webcam
Quick answer: Record a single clap on camera, then step through the recording frame by frame to find where your hands meet and where the audio waveform spikes. The gap between those two points is your measured delay in milliseconds. Estimating without a reference does not work.
The only reliable way to measure this is with a real-world synchronised event as ground truth — a single clap gives you both a visual spike and an audio spike at the exact same instant.
Everything else on this page follows from that one measurement, because you cannot correct an offset you have not quantified.
Try It Yourself
Measure the offset without manual frame-stepping
Produces a synchronised reference and reports the gap in milliseconds directly, which saves scrubbing through a recording by hand.
Run the Audio/Video Sync TestWhy guessing does not work
Audio and video take separate paths through your hardware and software before reaching the screen — different USB controllers, different driver stacks, different buffering.
There is no way to reliably estimate the gap without measuring it directly, and an offset applied by guesswork usually overshoots in the opposite direction.
The clap test method
Record yourself clapping once, clearly, in frame. Then step through the recording to find the exact moment your hands visually meet, and check the audio waveform for the moment the clap peaks.
Skip the manual frame-stepping with the Audio/Video Sync Test, which reports the gap directly.
- Clap once, sharply, well inside the frame and close to the microphone.
- Step frame by frame to the frame where your hands first touch, and note the timestamp.
- Find the audio peak in the waveform and note that timestamp.
- Subtract one from the other — at 30fps each frame is roughly 33 milliseconds.
What counts as noticeable
Broadly, an offset under roughly 30 milliseconds is imperceptible to most viewers. Between 30 and 100 milliseconds it is noticeable to some but not distracting to most.
Beyond about 100 milliseconds it reads as clearly wrong and becomes distracting, which is the point at which correcting it is worth the effort.
Audio-lags-video and audio-leads-video are both possible
Do not assume the direction. Depending on your camera and microphone processing pipelines, either audio can arrive late or, less commonly, video can be the side lagging behind.
Getting the direction wrong means applying a correction that doubles the problem rather than removing it, so establish it before adjusting anything.
If a capture card or DSLR is in the chain, measure that stage with the Capture Card & DSLR Latency Auditor.
Test with your actual setup, not a simplified one
If you normally use a USB microphone with a webcam, or a Bluetooth headset, measure with that exact combination.
Swapping to a different microphone for testing tells you nothing about the setup you actually use, because the latency belongs to the specific devices in the chain.
Re-test after any hardware or driver change
A driver update, a different USB port, or a new microphone can all change this number.
It is worth re-checking periodically rather than assuming a value measured once still holds, particularly after a system update.
To check whether the microphone is adding processing delay, run the Advanced Microphone & Room Acoustics Test.
Where to apply a measured offset in each tool
Once you have the number, only some tools let you use it. These are the ones that do.
OBS Studio
Audio Mixer → gear → Advanced Audio Properties → Sync Offset (ms)
Enter the measured figure directly against the relevant audio source; the correction applies at capture.
Video editors
Timeline → unlink audio, then nudge the track
Most editors let you enter an offset numerically rather than dragging, which is more precise and repeatable.
Zoom
No manual sync offset
The only levers are removing Bluetooth audio and reducing video encode load.
Microsoft Teams
No manual sync offset
Switching to a wired headset is the practical fix, since no correction control exists.
The table below shows which tools let you apply that measured offset directly, and which offer no correction at all:
| App | Practical ceiling | Manual control |
|---|---|---|
| OBS Studio | Per-source millisecond offset | Full manual correction |
| Video editors | Frame-accurate or sub-frame correction | Full manual correction |
| Zoom | None | Reduce processing load only |
| Microsoft Teams | None | Device choice and noise suppression |
Troubleshooting checklist: measuring A/V delay accurately
A clean measurement first, then the correction. Rushing the first step wastes the second.
- Set up with the exact camera, microphone and connection you normally use.
- Record a single sharp clap well inside the frame and close to the microphone.
- Step frame by frame to the frame where your hands first touch and note it.
- Find the audio peak in the waveform and note that timestamp.
- Subtract the two and convert frames to milliseconds using your recording frame rate.
- Note the direction — whether audio or video is the late one.
- Repeat the measurement two or three times and take the median.
- Re-measure after any driver update, port change or new microphone.