Audio Latency Testbrowser sound delay lab
English
LOCAL SOUND DELAY LAB

Audio Latency Test

Measure audio delay in your browser with tap timing, microphone round-trip checks, and A/V sync calibration. Use it for headphones, Bluetooth earbuds, speakers, video calls, gaming, and recording setups.

browser test bench

Run the audio latency test

Choose a test mode, start the signal, and compare repeated results. Tap mode estimates perceived delay, Mic mode tries a speaker-to-microphone round-trip check, and A/V Sync mode helps tune an offset by eye and ear.

Current result -- ms Pending
Tap when you hear the beat Use Space or click the pad after each sound.
Example result

A 35 ms average is usually comfortable for video calls and casual gaming. A 140 ms Bluetooth delay is easy to notice when watching lips, rhythm games, or live instrument monitoring.

three useful ways to test

How this audio latency test works

The Tap Test follows a simple reference workflow: the page plays a steady beat, records the exact browser time when each beat is triggered, and compares that with the moment you press Space or tap the target. The average of repeated responses gives a practical estimate of perceived audio delay. It includes your listening chain and your reaction consistency, so repeat the test and compare trends rather than trusting one number.

The Mic Round-Trip mode uses your browser microphone when permission is granted. It plays short pulses and listens for the same pulse through the microphone. This can estimate speaker-to-room-to-microphone delay, but it works best with speakers in a quiet room. Sealed headphones usually prevent the microphone from hearing the signal.

The A/V Sync mode flashes the canvas and plays a beep so you can tune an offset by eye and ear. This is useful when a video player, TV, Bluetooth codec, capture card, or game lets you enter an audio delay correction.

For the best audio latency test score, run one baseline with wired audio, one run with your normal headphones, and one run after changing a setting such as game mode, sample rate, Bluetooth profile, or browser output device. Keeping the same BPM and test mode makes the comparison fair. If the average delay drops but jitter rises, the device may feel less predictable even when the headline number looks better.

Run this audio latency test online before you change hardware, then run this audio latency test online again after the change so the comparison is fair. If you run this audio latency test online with the same BPM, browser, and device path each time, the average and jitter become a clear record of what actually improved.

10tap samples for a stable average
5mic pulses in round-trip mode
60-180supported BPM range
0uploads required for the test
quick workflow

How to use the audio latency test

1

Choose a mode

Use Tap Test for headphones, Mic Round-Trip for speaker and microphone setups, or A/V Sync for video alignment.

2

Set a comfortable BPM

120 BPM is a good default. Slower values help if you are new to the tap test.

3

Run repeated samples

Tap exactly when the sound reaches your ears, or keep the room quiet while mic pulses are detected.

4

Read average and jitter

Average shows the main delay estimate. Jitter shows how consistent the samples are.

5

Compare devices

Run the same mode on wired headphones, Bluetooth earbuds, speakers, or different browser/device setups.

read the result

What is a good audio latency result?

Latency tolerance depends on the task. Music monitoring needs very low delay, video calls can tolerate more, and Bluetooth video watching often needs an offset correction rather than perfect zero latency.

LatencyRatingBest understood as
Under 20 msExcellentLive monitoring, rhythm-sensitive work, tight gaming setups.
20-40 msGoodCalls, casual gaming, most headphone listening.
40-100 msNoticeableVideo watching may still feel fine, but timing tasks can suffer.
100-200 msHigh delayBluetooth lag, TV sound delay, or video sync issues become obvious.
200 ms+Very highUse wired audio, low-latency mode, or an A/V offset correction.
accuracy notes

Browser audio latency limits and privacy

Browser audio timing is useful for real-world comparison, not laboratory certification. Operating systems, drivers, Bluetooth codecs, browser scheduling, room noise, device buffers, and human reaction time can all affect the result.

The tool runs locally in your browser. It does not upload recorded audio for the normal test flow. Microphone permission is used only for the Mic Round-Trip mode, and the stream is stopped when the test ends.

For professional recording, use this page as a quick diagnostic before confirming values inside your DAW, audio interface control panel, or a dedicated loopback measurement tool.

A good audio latency test page should also explain what the number means after the tool finishes. Treat under 40 ms as a comfortable everyday target, 40-100 ms as a range where timing-sensitive users may notice lag, and anything above 100 ms as a sign to check Bluetooth mode, TV processing, driver buffers, or monitoring settings. The exact threshold depends on whether you are watching video, playing rhythm games, recording vocals, or joining calls.

If you are troubleshooting a difficult setup, write down the audio latency test average, minimum, maximum, jitter, device name, browser, and connection type. Those notes make it easier to compare a wired headset against Bluetooth earbuds, test a new USB interface, or decide whether an A/V offset correction actually improved sync.

quick answers

Audio Latency Test FAQ

What is an audio latency test?

An audio latency test estimates the delay between a sound being triggered and when it is heard, detected by a microphone, or aligned with a visual event.

Can this test measure Bluetooth headphone latency?

Yes. Use Tap Test or A/V Sync mode with your Bluetooth headphones connected. Compare the result against wired headphones to see the added lag.

Why are my results different each run?

Human tapping, browser scheduling, device buffering, and Bluetooth radio conditions vary. Use the average and jitter from several runs instead of one sample.

Does the Mic Round-Trip test work with headphones?

Usually no. The microphone must hear the test pulse from a speaker. Closed headphones keep the sound away from the microphone.

Is a lower audio latency always better?

Lower is better for monitoring, rhythm games, and live performance. For video watching, a stable offset that can be corrected may matter more.

Is my microphone audio uploaded?

No. The browser analyzes the microphone signal locally for pulse detection and stops the stream when the test ends.