🎧 Online audio delay checker
Audio Latency Test
Test your sound latency online and estimate audio delay in milliseconds. Use the Sound Latency Test to check whether your audio feels delayed, compare different devices, and understand whether the issue may come from Bluetooth headphones, speakers, HDMI, USB audio, an audio interface, browser playback, recording software, or A/V sync.
- Audio delay in ms
- Average latency
- Minimum latency
- Maximum latency
- Jitter / variation
- Bluetooth guidance
- A/V sync support
Example latency result
Sample estimateThis example shows noticeable delay. Your actual result depends on the test method, device path, Bluetooth mode, browser timing, room noise, and audio settings.
Delay context Noticeable
Important: For the button to work, your Main Tool section must include this exact ID: sound-latency-test-tool.
Online audio delay checker
Sound Latency Test
Estimate sound delay in milliseconds, compare device paths, and understand whether your result reflects click-response timing, round-trip latency, Bluetooth delay, or A/V sync issues.
Choose a mode and press Start.
Run the test to see your result context.
Useful for comparing devices, but results include your reaction time. Use multiple samples and compare averages.
Uses a microphone to listen for the test pulse. It estimates output plus input path delay when conditions are clean.
Use this when video and audio feel mismatched. For precise visual timing, compare with your AV Sync Test page.
Accuracy and privacy notes
This tool runs the test interaction in the browser session. Microphone mode asks for browser microphone permission only for the round-trip estimate. Results are educational estimates and can vary by browser, device, operating system, Bluetooth codec, room echo, microphone processing, and user reaction timing.
Start with the same audio setup
How to Use the Sound Latency Test
Use the Sound Latency Test when your audio feels delayed, out of sync, or slow to respond. For the most useful result, test the exact device path you normally use: Bluetooth earbuds, wired headphones, speakers, HDMI audio, USB audio, or an audio interface.
Use the same headphones, speakers, Bluetooth device, HDMI output, or interface you want to measure.
Reduce background sound, echo, and extra playback sources so the test instructions are easier to follow.
Click the start button and follow the selected mode: click-response, microphone round-trip, or A/V sync helper.
Multiple attempts help compare average latency, minimum latency, maximum latency, and variation.
A reaction estimate, round-trip estimate, and sync check do not all measure the same delay.
Compare results after switching devices, changing Bluetooth mode, lowering buffer size, or adjusting app settings.
Understand the measurement path
How Sound Latency Is Measured
Sound latency is the delay between an audio event and when that event is heard, captured, or noticed. A browser-based test can estimate this delay in milliseconds, but the meaning of the result depends on the test method and the audio path being tested.
A click-response test can include human reaction time. A microphone round-trip test can include speaker output, room path, microphone input, and browser timing. An A/V sync check focuses on whether picture and sound feel aligned.
- Click-response mode estimates perceived delay plus reaction timing.
- Round-trip mode estimates playback-to-microphone delay.
- A/V sync checks timing between picture and sound.
- Device path changes can produce very different results.
- Multiple samples help reveal consistency and jitter.
The test starts with a click, pulse, or visual/audio cue.
The sound travels through speakers, headphones, Bluetooth, HDMI, USB, or an interface.
The delay is detected by your response or by microphone input, depending on the mode.
The test calculates the delay in milliseconds based on the selected method.
Multiple samples can produce a clearer picture than a single result.
A changing result shows jitter or inconsistent timing across attempts.
Turn milliseconds into meaning
How to Read Your Latency Result
A latency result should not be judged from one number only. The most useful reading includes the test method, average latency, minimum latency, maximum latency, variation, confidence, and the device path you tested.
| Result field | Meaning | Why it matters |
|---|---|---|
| Latency | The estimated delay shown in milliseconds. | This is the main delay number users want to understand. |
| Average latency | The mean value across multiple attempts. | Usually more useful than a single test sample. |
| Minimum latency | The lowest result from the test run. | Shows the best detected attempt under the same setup. |
| Maximum latency | The highest result from the test run. | Shows the worst detected attempt and possible timing spikes. |
| Jitter / variation | How much the result changes across samples. | High variation can feel worse than a stable delay. |
| Test method | The way the delay was estimated. | Prevents confusion between reaction timing, round-trip timing, and sync checks. |
| Confidence | A practical reliability label for the current test. | Helps decide whether to retest or adjust the setup. |
| Device path | The headphones, speakers, interface, Bluetooth device, or output chain tested. | Makes before-and-after comparisons meaningful. |
Know which delay you are testing
Input Latency vs Output Latency vs Round-Trip Latency
Audio latency can happen at different points in the signal path. Output latency affects when you hear sound. Input latency affects when recorded sound reaches the system. Round-trip latency combines the path out and back in, which is common in recording, monitoring, and microphone-based testing.
| Latency type | What it means | Common example |
|---|---|---|
| Output latency | Delay before generated sound reaches your ears. | Bluetooth earbuds make game audio feel late. |
| Input latency | Delay before recorded sound reaches the system. | A microphone recording appears late in software. |
| Round-trip latency | Output delay plus input delay in one combined path. | You play a note, hear monitoring, and record the signal. |
| Monitoring latency | Delay while listening to yourself during recording. | Vocal or guitar monitoring feels behind the performance. |
| A/V sync offset | Mismatch between picture timing and audio timing. | Lips move before or after the voice is heard. |
| Reaction estimate | A practical delay estimate based on a user response. | You hear a click and tap as quickly as possible. |
Headphones, speakers, Bluetooth, HDMI, TV processing, and app playback can all add output delay.
Microphones, interfaces, browser settings, noise suppression, and recording software can affect input timing.
Round-trip latency is useful for recording and monitoring, but it does not automatically isolate each part.
Put the number in context
What Is a Good Audio Latency?
A good audio latency depends on what you are doing. Casual listening can tolerate more delay than live recording, rhythm gaming, or real-time monitoring. A stable result is also important, because latency that jumps up and down can feel worse than a slightly higher but predictable delay.
| Use case | What matters most | How to interpret the result |
|---|---|---|
| Casual listening | Comfort and stable playback. | Higher delay may be acceptable when there is no video or timing task. |
| Watching video | Audio and picture alignment. | Latency becomes obvious when speech and lip movement no longer match. |
| Gaming | Timing cues and reaction feel. | Lower and more consistent delay helps footsteps, rhythm, and positional cues feel responsive. |
| Music production | Real-time monitoring while recording. | Even moderate delay can feel distracting when singing or playing through software monitoring. |
| Streaming | Camera, microphone, game, and capture source sync. | One delayed source can make the entire stream feel out of sync. |
| Calls and meetings | Conversation flow and echo control. | Stable timing matters because delay can cause interruptions, overlap, and awkward pauses. |
The audio path changes the result
Bluetooth, Wired, HDMI, USB, and Audio Interface Latency
Sound latency is not only a browser problem. The device path can add delay before the sound reaches your ears or before audio returns to the system. Bluetooth, HDMI, USB audio, capture cards, audio interfaces, drivers, buffer size, and app processing can all change the result.
A laptop speaker result, Bluetooth earbud result, HDMI-to-TV result, and USB audio interface result may all be different. Use the same test method, then change only one part of the setup so your comparison is useful.
- Bluetooth can add codec and buffering delay.
- Wired headphones avoid wireless transmission delay.
- HDMI audio can be affected by TV or display processing.
- USB interfaces depend on drivers, buffers, and sample rate.
- Capture cards can add extra sync delay for streaming.
- DAW monitoring depends on the full input-output path.
Wireless headphones and earbuds can add codec, buffering, and connection delay.
Wired headphones are often simpler for timing-sensitive listening, gaming, and recording checks.
TV processing, receiver settings, and display modes can shift audio timing.
USB audio latency can change with driver type, buffer size, sample rate, and software setup.
Interfaces can reduce monitoring delay when configured well, especially with direct monitoring.
Capture cards can delay game audio, microphone audio, camera video, or stream output.
Use latency results in real workflows
Sound Latency for Gaming, Music Production, Streaming, and Calls
The same latency number can matter in different ways depending on the task. A delay that feels harmless for casual listening may be frustrating in rhythm games, vocal recording, livestreaming, screen capture, or video calls.
Delayed sound can affect footsteps, impact timing, rhythm cues, and reaction feel.
Monitoring delay can make vocals, guitar, MIDI, and live recording feel behind.
OBS, capture cards, camera video, game audio, and microphone audio may need sync adjustment.
Delay can cause people to talk over each other, pause awkwardly, or hear echo.
Movie, TV, and capture workflows need sound to line up with visible action.
Buffer size, driver mode, plugins, and monitoring path can change recording comfort.
- Gaming audio delay
- DAW monitoring
- OBS sync
- Zoom delay
- Teams audio delay
- Capture card sync
- Bluetooth lag
- A/V sync offset
Reduce delay step by step
How to Reduce Audio Latency
Reducing audio latency starts with identifying where the delay is likely coming from. Test a simple setup first, then change one thing at a time: headphones, Bluetooth mode, driver type, buffer size, sample rate, HDMI settings, app sync offset, or audio interface monitoring.
Wired audio can remove Bluetooth codec and wireless buffering from the signal path.
Some devices include gaming or low-latency modes that may reduce perceived delay.
Smaller buffers can reduce DAW delay, but settings that are too low may cause clicks or dropouts.
Driver choices such as ASIO, WASAPI, or Core Audio can affect recording and monitoring latency.
Game mode, audio delay settings, and receiver settings may help with HDMI or TV sync problems.
Change one setting, run the test again, and compare the new result with the old one.
Trust, method, and realistic results
Accuracy, Privacy, and Limitations
The Sound Latency Test is an educational audio-delay estimate, not a professional lab measurement system. Browser-based tests can help reveal timing problems and compare device paths, but the result may include browser timing, device buffering, Bluetooth processing, microphone behavior, room sound, user reaction time, or app-level delay.
A click-response result is different from a round-trip estimate. Bluetooth earbuds, HDMI audio, USB interfaces, DAWs, capture cards, and video-call apps can all add delay in different places, so the result should be read as a practical estimate for the setup being tested.
- Browser-based latency results are estimates.
- Click-response tests can include human reaction time.
- Round-trip tests combine output and input delay.
- Bluetooth devices can add codec and buffering delay.
- Echo cancellation and noise suppression may affect microphone tests.
- Different browsers, devices, and audio paths may produce different results.
The test is useful for practical comparison, but it should not be described as professional calibration.
Click-response testing can include how quickly the user hears and taps after the cue.
A round-trip result includes output and input behavior together, not each part separately.
Speakers, wired headphones, Bluetooth, HDMI, USB audio, and interfaces may all test differently.
Microphone and storage claims should always match the final plugin behavior exactly.
The tool should not be used for hearing, health, medical, or clinical decisions.
Quick answers
Sound Latency Test FAQ
These answers explain how the Sound Latency Test works, what the milliseconds result means, why different devices show different delay, and how to use the result for troubleshooting.
A sound latency test estimates the delay between an audio event and when that sound is heard, captured, or noticed. Results are usually shown in milliseconds.
Start the test, follow the on-page instructions, and run more than one sample. Keep the same device path during each test so the result is easier to compare.
It is the estimated delay for the test method and setup you used. A click-response result, round-trip result, and A/V sync result do not all mean the same thing.
Round-trip latency is the combined delay from audio output to audio input. It is useful for recording and monitoring, but it does not automatically isolate each part of the signal path.
Bluetooth audio can be delayed by codec processing, buffering, wireless transmission, app settings, device mode, and operating-system audio handling.
Wired audio often avoids Bluetooth codec and wireless buffering, but the final result still depends on the device, app, driver, and audio path.
A good latency depends on the activity. Gaming, live monitoring, and music production usually need lower delay than casual listening.
A/V sync problems can come from Bluetooth, HDMI, TV processing, capture cards, streaming software, editing software, or app delay.
Only if the method is designed to isolate output latency. Most browser-based tests estimate perceived, reaction-based, or round-trip timing instead.
Privacy wording should match the final plugin behavior. Do not claim local-only processing, no upload, or no storage unless the plugin truly works that way.
Learning hub
Learn More About Audio Latency
After using the Sound Latency Test, continue learning how audio delay works across Bluetooth headphones, wired audio, HDMI, USB devices, audio interfaces, DAWs, streaming software, video calls, capture cards, games, and A/V sync workflows.
Understand the basic delay between sound generation, playback, capture, and hearing.
How to Test Audio LatencyLearn practical methods for checking delay and comparing audio setups.
What Is Good Audio Latency?Put your milliseconds result into context for listening, gaming, recording, and calls.
Why Is My Audio Delayed?Find common causes of late sound across devices, apps, and connection paths.
What Is Round-Trip Latency?Understand why recording and monitoring often combine output and input delay.
Input vs Output LatencySeparate playback delay from recording delay and understand the signal path.
Bluetooth Audio LatencyLearn why wireless audio can feel delayed and what affects Bluetooth timing.
Wired vs Wireless Headphone LatencyCompare the timing tradeoffs between wired listening and Bluetooth playback.
Audio Interface LatencyUnderstand interface delay, monitoring paths, buffers, and recording setup factors.
Sample Rate and LatencySee how sample rate and buffer settings can affect real-time audio delay.
OBS Audio LatencyFix stream sync issues involving game audio, microphone, camera, and capture cards.
How to Reduce Audio LatencyUse practical steps to lower delay and retest after each setup change.
About the tool
Author and Editorial Trust Strip
This Sound Latency Test is designed as an educational audio tool for people who want to estimate sound delay, compare device paths, understand latency results, and troubleshoot timing problems. The goal is to make audio latency easier to test, read, and reduce without overstating what a browser-based result can prove.
The page explains latency in milliseconds, result fields, test methods, and practical troubleshooting.
Results are framed around average, minimum, maximum, variation, confidence, and test method.
The content separates click-response, round-trip, device-path, and A/V sync concepts.
The tool is positioned as an estimate, not a lab-grade audio measurement system.
Microphone, storage, and processing explanations should match the final plugin behavior.
The page uses readable structure, clear headings, keyboard-friendly links, and mobile-first layout.