when to use it
What the audio sync test measures
The audio sync test focuses on real playback delay rather than a theoretical device specification. Browser timing, operating-system buffering, USB or Bluetooth transport, driver settings, and your output device all shape the result. The page gives you a repeatable workflow for comparing one setup against another.
Tap mode is best when the sound is isolated in headphones or earbuds. Mic Round-Trip mode is best when a microphone can physically hear a speaker. A/V Sync mode is best when your problem is not a single number, but a correction value that makes picture and sound feel aligned.
Compare setupsRun the same test on wired, wireless, laptop, and speaker outputs.
Watch consistencyA low jitter result is more trustworthy than one lucky tap.
how to interpret
How to read your audio sync test result
Treat the average as the main estimate and jitter as the confidence signal. A low average with high jitter means the setup may be unstable or the tapping rhythm was inconsistent. A high average with low jitter means the delay is real enough to correct or compare.
For headphones and Bluetooth earbuds, repeat the test after changing low-latency mode, game mode, codec settings, sample rate, browser, or output device. For microphone and speaker tests, repeat after moving the microphone, reducing room noise, or disabling aggressive echo cancellation.
Under 40 msUsually comfortable for calls and casual listening.
Over 100 msOften noticeable in games, videos, and live monitoring.
edge cases
Why browser latency tests vary
The browser can schedule a sound accurately enough for comparison, but it cannot always know the exact moment the sound leaves the driver, codec, speaker, or earbud. Bluetooth devices add buffering, TVs may add video processing, and operating systems can change audio paths when devices reconnect.
That is why this page is designed for repeated measurements and practical decisions. If the result changes slightly, compare averages across several runs. If one device is consistently much higher than another, the difference is usually more meaningful than the exact single number.
No upload neededThe test logic runs in your browser.
Use professional tools for certificationDAW loopback and hardware rigs are better for final studio calibration.
sync checklist
How to use an audio sync test for real playback problems
An audio sync test is different from a pure latency measurement because the goal is alignment. A video can feel wrong when audio is early, audio is late, or display processing adds video delay. Use the flash and beep together, adjust the manual offset, and focus on the correction that makes the two events feel simultaneous rather than chasing a perfect zero number.
Run the audio sync test on the same screen and speakers you use for the problem content. A laptop speaker, Bluetooth earbuds, HDMI TV, soundbar, capture card, and streaming app can all add different delays. If the audio sync test feels aligned on one output but not another, the issue is probably in that device path rather than the media file itself.
After you find an offset, test it with real content: speech, claps, rhythm gameplay, or a scene with visible impacts. Some players accept positive or negative audio delay values, while TVs and soundbars may label the same control as lip sync, audio delay, or AV offset. The audio sync test gives you a starting value to try in those settings.
A final audio sync test pass should use the content type that exposed the problem. Speech reveals lip-sync errors, rhythm games reveal beat timing errors, and action scenes reveal impact timing errors. If the audio sync test offset works in the tool but still feels wrong in real content, the player, TV, console, capture card, or streaming app may be adding its own separate delay.
Align by feelThe best correction is the one that makes flash and beep land together.
Test the real device pathRun the same audio sync test through the TV, soundbar, or earbuds you actually use.
