Output
Available browser estimates, milliseconds
UserBenchmark / All Tools / Audio Latency Test
Audio
Audio Latency Test
Inspect browser audio latency estimates and measure a manual audio reaction time.
Free to useNo downloadNo sign-up
Audio Latency Test · At a glance
Quick answer: Inspect browser audio latency estimates and measure a manual audio reaction time. Values are browser estimates converted to milliseconds.
Audio Latency Test
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Inspect the reported base and output latency estimates.
- Keep the selected audio device fixed and use the auditory reaction drill separately if desired.
Input
Audio context capability inspection
Browser requirement
Web Audio baseLatency and outputLatency
Processing
Runs on your device; no tool-result upload
How it works and what the result means
Base latency and output latency are browser estimates in seconds converted to milliseconds. Some browsers do not report both values, and Bluetooth delay may be incomplete.
Reading the result
Values are browser estimates converted to milliseconds. Missing output latency is unavailable information, not zero delay.
What to check next
Restart the context after switching audio devices. Wireless buffering may not be fully represented by every browser.
These estimates are not a measured acoustic loopback. A physical loopback or dedicated instrument is needed for a complete audio round-trip measurement.
Frequently asked questions
Does adding the values give exact acoustic round-trip latency?
No. Complete round-trip measurement also involves input, converters and physical routing. It requires a suitable loopback method.
How do I start the Audio Latency Test?
Open the tool and inspect the audio context estimates. Use the auditory reaction test for a separate manual comparison.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.