Audio Latency Test

Estimate how far sound lags or leads the picture on your screen. Press Start clicks, then move the Offset slider until the flash lines up with each click. It works with Bluetooth headphones, speakers, soundbars and TVs, and every number is an estimate.

Lower your volume before starting, especially with headphones. Nothing plays until you press a button.

Move right if the click comes after the flash, left if it comes before.
Fine tune

Every figure here is an estimate.

Your offset
0 msNo offset: the flash shows when the browser expects you to hear the click.
Average
No saved triesPress Save offset each time the flash and the click line up.
Output latency
Not read yetRead when the clicks start
Base latency
Not read yetRead when the clicks start
Estimated total
Not read yetNeeds the output latency, which the browser reports only on some systems

The result covers this output and this screen together: the browser, the system, the audio device and the display. Lining up by eye and ear is approximate, so repeat it a few times and use the Average. The page does not change any delay, and the result does not predict every app or player.

Stopped

Runs entirely in your browser. Test results, audio and video never leave your device.

How to test audio latency

  1. Choose the output to check, such as Bluetooth headphones, a soundbar or TV speakers, in your system's sound settings, and turn the volume down.
  2. Press Start clicks. A short click plays every 1 second, and the circle flashes when the browser expects you to hear it.
  3. Watch the circle and listen. If the click comes after the flash, move the Offset slider right; if it comes before, move it left. Fine tune moves it in 1 ms and 10 ms steps.
  4. When the flash and the click seem to happen at the same moment, press Save offset.
  5. Move the slider away, line it up again and save again. After a few tries, read the Average.
  6. Use the Average as the starting value for the A/V sync, audio delay or lip sync setting in your player, TV or game, then fine-tune it while watching. A negative Average means the sound comes first, so delay the audio.

What is audio latency?

Audio latency is the delay between an app playing a sound and the sound reaching your ears. Wired headphones and speakers usually add little. Bluetooth usually adds more, because the sound is buffered before it plays, and soundbars, receivers and TVs can add processing time. A TV can delay the picture too, so sound may arrive before it. Either way, a large gap makes voices stop matching lips.

What a positive or negative offset means

Your offset compares when you hear the click with when the browser expected you to, judged against this screen. Sound can lag the picture or arrive before it.

OffsetWhat it meansWhat to change
Above 0 msSound lags the picture: the browser's estimate leaves out part of the delay, for example a Bluetooth device's.Delay the picture or move the sound earlier in the A/V sync, audio delay or lip sync setting.
About 0 msWhat you hear matches the browser's estimate, compared with this screen.Usually nothing. To compare outputs, test each one and compare the Estimated total.
Below 0 msSound arrives before the picture: the screen is slower, for example a TV that delays the picture for processing while a soundbar plays the sound straight away.Delay the audio in the audio sync setting of your receiver or soundbar.

Why Bluetooth audio lags behind the picture

Bluetooth headphones and speakers buffer the sound before they play it, and that takes time. How much depends on the headphones and the phone or computer they are paired with, and the page does not know which codec is in use. Bluetooth LE Audio needs fewer buffers than classic Bluetooth audio, so its delay can be shorter when both devices support it.

The latency the browser reports may leave out a Bluetooth device's own delay, and that missing part shows up as a positive offset. If one earbud is silent or quieter, check it with the Headphone Test before timing it.

How to reduce audio delay

  • Use the A/V sync, audio delay or lip sync setting on your TV, soundbar, receiver or player, with your offset as the starting value.
  • Turn on the TV's Game mode for games. It may shorten picture processing, which changes your offset, so test again afterwards.
  • Use wired headphones or speakers when timing matters, or a low-latency mode if your Bluetooth headphones offer one in their app.
  • Test again after any change: an offset belongs to one output and one screen.

What this test can detect

  • How much later or earlier the sound reaches you than the browser expects, as an offset in milliseconds that you set by eye and ear.
  • Delay the browser does not account for, which can come from Bluetooth headphones and speakers, soundbars and receivers.
  • Sound that arrives before the picture because the screen is slower, as with a TV processing the picture, which shows as a negative offset.
  • The output latency and base latency your browser reports, or Not reported where it gives 0 or no value.
  • How outputs compare: the Estimated total for wired headphones, built-in speakers and Bluetooth, tested one after another.

How it works

The page loops a 1-second Web Audio buffer, so a 12 ms click at 2 kHz sounds every 1 second on the audio clock. Each frame it reads getOutputTimestamp(), which pairs the audio and page clocks, and lights the circle for 100 ms from when the browser expects the click to leave your output, moved by your Offset (−200 to +500 ms).

Output latency and Base latency are the browser's outputLatency and baseLatency, shown as Not reported when missing or 0. Estimated total adds your offset to Output latency. Nothing is recorded.

Limitations

  • Lining up by eye and ear is approximate, so every result is an estimate. Repeat it a few times and use the average; no accuracy figure is given, because none has been measured for this method.
  • The result is end-to-end: the browser, the system, the audio device and the screen together, relative to this screen. It is not the latency in a headphone's specifications, and the flash can change only when the screen refreshes, every 16.7 ms at 60 Hz. The Refresh Rate Test shows your rate.
  • The latency the browser reports may leave out a Bluetooth device's own delay. The page does not fix delay or change any setting, and it does not predict every app or player: use the number as an A/V offset in your player, TV or game, then fine-tune it while watching.
  • The cue is a small gray circle inside the test area, never the whole screen. It lights once a second, well under WCAG 2.3.1's limit of 3 flashes in any 1-second period, and with reduced motion on it is dimmer. Keep the volume low: the clicks are short but sharp, especially in headphones.
  • Echo or delay on calls is not tested here, because the page never uses the microphone. To hear what your microphone picks up, record yourself with the Mic Test with Playback.

Frequently asked questions

How much delay do my Bluetooth headphones add?

Test wired headphones or the built-in speakers first, then the Bluetooth headphones, and compare the Estimated total. The difference is roughly the delay Bluetooth adds on this device. It can change with the headphones and the phone or computer they are paired with.

Why does it say Not reported?

The browser gives no value, or gives 0, which the page treats as no value. Current Chrome, Edge, Firefox and Safari support both; older versions may lack Output latency, older Safari especially. Your offset does not depend on them; only the Estimated total needs Output latency.

Can I test a TV or a soundbar?

Yes. Open the page on the device that sends the picture and sound, such as a laptop connected over HDMI or the TV's own browser, then watch the TV and listen to the soundbar. The result includes the TV's picture processing, so test in the picture mode you normally use.

Does it work on a phone?

Yes, with the phone's speaker or with wired or Bluetooth headphones. On iPhone, the page asks to play the clicks even in Silent mode, where the browser allows it; if you hear nothing, turn Silent mode off. Starting the clicks may pause other audio, and they stop when you switch apps or tabs.

Why is my offset different each time?

Because you judge the line-up by eye and ear, and a difference of a frame or two is hard to see. Save several tries, use the Average, and compare results only on the same screen.