Audio Latency Testbrowser sound delay lab
English
ROUND-TRIP AUDIO CHECK

Mic Latency Test

Use this mic latency test to estimate speaker-to-microphone round-trip delay for recording, streaming, video calls, instrument practice, and troubleshooting.

browser test bench

Run the mic latency test

Use this mic latency test to estimate speaker-to-microphone round-trip delay for recording, streaming, video calls, instrument practice, and troubleshooting. The tool above is usable on this page, so you can test first and read the guidance below after you have a result.

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. Repeat this mic latency test after changing one device setting so the average and jitter show whether the change helped.

when to use it

What the mic latency test measures

The mic latency 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 setups

Run the same test on wired, wireless, laptop, and speaker outputs.

Watch consistency

A low jitter result is more trustworthy than one lucky tap.

how to interpret

How to read your mic latency 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 ms

Usually comfortable for calls and casual listening.

Over 100 ms

Often 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 needed

The test logic runs in your browser.

Use professional tools for certification

DAW loopback and hardware rigs are better for final studio calibration.

round-trip checklist

How to make the mic latency test more reliable

A browser mic latency test depends on the microphone hearing the speaker pulse clearly. Use speakers rather than closed headphones, place the microphone close enough to hear the pulse, and reduce room noise before starting. If the tool misses pulses, raise the playback volume slightly, move the microphone closer, or disable aggressive noise suppression in the browser or operating system when possible.

The mic latency test estimates a round-trip path: browser playback, speaker output, air travel, microphone pickup, input processing, and browser analysis. That makes it useful for troubleshooting calls, streaming, recording checks, and monitoring delay, but it is not identical to a direct cable loopback test inside a DAW. Use the average as a practical field estimate and the jitter value as a confidence signal.

If you are testing a recording setup, run the mic latency test before and after changing buffer size, sample rate, audio interface driver, USB port, or monitoring mode. A smaller buffer can reduce delay but may cause clicks or instability. A stable medium result is often better than a low result with high jitter and dropouts.

A final mic latency test pass should be done with the same microphone pattern, speaker volume, and room position you plan to use. Moving the microphone even a short distance can change pulse detection and room reflection timing. If the mic latency test result matters for recording or streaming, keep a note of the browser permission state, echo cancellation setting, and input device name.

For a clean mic latency test comparison, keep the same gain, distance, browser, and speaker volume for every run so the final average reflects the audio path rather than setup changes.

Use audible speakers

The microphone must hear the pulse for round-trip detection to work.

Watch jitter

Large jitter suggests unstable input processing or unclear pulse detection.

quick answers

Mic Latency Test FAQ

How accurate is this mic latency test?

It is a practical browser estimate. Repeated runs and device comparisons are more reliable than one isolated number.

Should I use Tap Test or Mic Round-Trip?

Use Tap Test for headphones and earbuds. Use Mic Round-Trip only when your microphone can hear the speaker output.

Why is Bluetooth usually slower than wired audio?

Bluetooth devices often buffer and encode audio before playback. That buffering can add noticeable lag, especially without a low-latency mode.

Can I fix audio delay after measuring it?

Often yes. Try wired audio, game mode, low-latency Bluetooth settings, a different browser, or an A/V offset in your player or TV.

Does the test upload recordings?

No. The browser analyzes timing locally. Mic mode uses permission only while the test is running.

How do I compare two results from this mic latency test?

Run the same mic latency test mode twice with only one setting changed. Compare the average first, then use jitter to decide which result is more stable.