Sound Latency Test

Use the free Sound Latency Test to measure the round-trip delay between your audio output and microphone input. The test runs in your browser and reports latency in milliseconds (ms), so you can check how quickly your current audio setup responds.

This is useful when audio feels delayed during recording, monitoring, gaming, streaming, video calls, or other interactive applications.

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.

Ready
Before you start: Test in a quiet room and keep the same device path during each run. A browser test is an estimate, not a lab-grade audio measurement.
Click-response mode plays a beep and measures how quickly you tap after hearing it. This includes human reaction time, so use it mainly for comparison between devices.
0/7 samples

Choose a mode and press Start.

Estimated latency -- ms

Run the test to see your result context.

Average--
Minimum--
Maximum--
Variation--
Confidence--
Method--
LowModerateHighVery high
Click-response mode

Useful for comparing devices, but results include your reaction time. Use multiple samples and compare averages.

Round-trip mode

Uses a microphone to listen for the test pulse. It estimates output plus input path delay when conditions are clean.

A/V sync helper

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.

For the most useful comparison, test the exact setup you normally use — such as wired headphones, speakers, Bluetooth headphones, HDMI audio, USB audio, or an external audio interface.

Important: This browser-based test measures an acoustic round-trip path. It is a practical diagnostic estimate, not a laboratory-grade measurement of one individual hardware component.

What Does a Sound Latency Test Measure?

Sound latency is the delay between an audio signal being produced and that signal being detected again.

The Sound Latency Test measures round-trip audio latency. A short test signal is generated through your selected audio output, captured through your microphone, and analyzed to estimate the time between output and capture.

The measured path can include several parts of your audio system:

  • Browser audio processing
  • Operating-system audio buffering
  • Audio drivers
  • Speaker or headphone output
  • Bluetooth processing and transmission
  • Sound travel through the room
  • Microphone input processing
  • Browser audio scheduling

The result therefore describes the behavior of your complete browser-to-output-to-microphone path, rather than identifying the exact latency of a single component.

For a deeper technical explanation, see How Sound Latency Is Measured.

How to Use the Sound Latency Test

You can run the test directly in your browser without installing dedicated latency-testing software.

1. Connect the device you want to test

Use the headphones, speakers, Bluetooth device, HDMI output, USB audio device, or audio interface whose latency you want to evaluate.

2. Create a quiet test environment

Background noise, room reflections, and other sounds can make acoustic detection less reliable. Reduce unnecessary noise before starting.

3. Allow microphone access

The microphone is needed to detect the test signal after it has passed through the output path.

4. Start the test

Follow the instructions shown by the tool and allow it to complete the measurement.

5. Run multiple measurements

Do not rely on a single reading when comparing setups. Multiple runs help show the average, minimum, maximum, and variation between measurements.

6. Compare the same setup

If you are troubleshooting latency, change one part of the audio path at a time and retest. This makes before-and-after comparisons more useful.

For a detailed testing workflow, see How to Test Audio Latency.

Understanding Your Latency Result

The main result is displayed in milliseconds (ms).

A smaller latency value generally means less delay between the output event and its detected return. However, the number should always be interpreted in the context of the activity and the measurement method.

Average latency

The average is the mean of the successful measurements in the test.

Median latency

The median is the middle value after the measurements are ordered. It can be useful when one unusually high or low reading affects the average.

Minimum and maximum

These show the fastest and slowest successful measurements during the test.

Variation or jitter

Variation shows how consistently the system behaves from one run to another. A setup that produces similar results repeatedly may be more predictable than one with large changes between measurements.

A latency result is most useful when you compare the same device path under the same conditions.

Is Lower Audio Latency Better?

For interactive audio, lower latency is generally more desirable because it reduces the delay between an action and the resulting sound.

The practical importance depends on what you are doing.

  • Music recording and monitoring: Delay can make live performance and monitoring feel disconnected.
  • Gaming: Audio delay can make sound events feel less immediate.
  • Streaming: Latency can contribute to timing problems between sources.
  • Video calls: Audio delay can affect conversational timing.
  • Casual listening: Moderate latency may be much less noticeable because there is no immediate interaction.

There is no single latency number that is automatically “good” for every situation. The useful question is whether the measured delay is appropriate for your particular audio workflow.

For more context, see Audio Latency Perception.

Round-Trip Latency vs Input and Output Latency

Audio latency can occur at different points in the signal path.

Output latency

Output latency is the delay before generated audio reaches your headphones or speakers.

Input latency

Input latency is the delay introduced while sound entering a microphone or audio input becomes available to the software.

Round-trip latency

Round-trip latency combines the outbound and inbound portions of the path.

The Sound Latency Test is designed to estimate round-trip acoustic latency. It should not be interpreted as an isolated measurement of output latency or input latency.

For a detailed comparison, see Input vs Output Latency and What Is Round-Trip Latency.

Why Can Audio Latency Change?

Your latency result can change even when you use the same computer.

Common factors include:

  • Audio buffer size
  • Sample rate
  • Browser behavior
  • Operating-system audio settings
  • Audio drivers
  • CPU and system load
  • Background applications
  • USB audio devices
  • Bluetooth processing
  • Wireless conditions
  • Microphone processing
  • Speaker-to-microphone distance

This is why repeating the measurement is useful.

If you change a setting or device, run the test again and compare the results rather than assuming that a single measurement represents the entire system.

See Sample Rate and Latency for more detail about the relationship between audio configuration and latency.

Wired vs Bluetooth Audio Latency

Bluetooth audio can introduce additional processing and buffering compared with a wired connection. Bluetooth playback may involve encoding, wireless transmission, decoding, buffering, and device-specific processing before the sound reaches you.

As a result, Bluetooth headphones and earbuds can behave differently from wired headphones even when the rest of the computer setup is unchanged.

If you are specifically investigating wireless audio delay, use the Bluetooth Latency Test.

For broader comparisons, see Wired vs Wireless Headphone Latency.

What Can Cause High Audio Latency?

A high latency result does not necessarily mean that one device is defective.

Possible sources include:

  • Large audio buffers
  • Bluetooth codec and buffering overhead
  • Operating-system audio configuration
  • Browser audio scheduling
  • USB or external audio-device configuration
  • Driver behavior
  • Additional processing in an application
  • HDMI or display-device processing
  • Capture-card processing
  • System load

The correct troubleshooting approach is to identify which part of the signal path changed and then retest.

If your result is unexpectedly high or the test behaves inconsistently, use Troubleshooting and Common Audio Latency Problems.

Testing an Audio Interface

An external audio interface can have very different latency behavior from built-in computer audio.

The browser test measures the real-world output-to-microphone path available to the browser, but it cannot isolate every individual stage inside an audio interface or determine hardware-only latency separately.

For professional audio work, a physical loopback measurement can provide a more controlled test of an interface and its software configuration.

The browser-based Sound Latency Test is best used as a convenient way to check and compare the latency of your current setup.

Accuracy and Limitations

The Sound Latency Test is intended as a practical browser-based diagnostic tool.

Its result reflects the complete measurement environment at the time of testing. Browser behavior, operating-system audio processing, hardware, device drivers, microphone behavior, room acoustics, and other factors can affect the result.

The test cannot isolate:

  • Hardware-only latency for an individual component
  • Output-only latency
  • Input-only latency
  • Hardware-level zero-latency monitoring that bypasses the software audio path
  • The exact latency a DAW will produce under a different buffer size or plugin load

For the complete technical explanation of the measurement pipeline and its limitations, see How It Works.

Microphone Permission and Privacy

The microphone is required because the test needs to detect the audio signal after it travels through the output path.

Microphone data used for the measurement is processed in the browser during the test. The site’s technical documentation states that the microphone stream is not recorded, stored, or transmitted.

You can control or revoke microphone permission through your browser settings.

For the site’s complete privacy information, see the Privacy Policy.

When Should You Run a Sound Latency Test?

A latency test can be useful when:

  • Your headphones or speakers feel delayed.
  • A microphone or instrument feels slow while monitoring.
  • Game audio seems noticeably behind the action.
  • Bluetooth audio feels less responsive than wired audio.
  • Audio and video appear out of sync.
  • You changed an audio setting and want to compare the result.
  • You are comparing two audio devices.
  • You want a baseline measurement before troubleshooting.

The most useful comparison is usually before vs. after: measure the current setup, change one relevant setting or device, and measure again.

Related Sound Latency Tools and Guides

Test and diagnostic tools

Audio latency guides

Use-case guides

Frequently Asked Questions

What does a Sound Latency Test measure?

It estimates round-trip audio latency — the elapsed time between an audio signal being output and that signal being detected again through the microphone.

What does ms mean in an audio latency result?

ms means milliseconds. One second contains 1,000 milliseconds, so a smaller number represents a shorter measured delay.

Is lower audio latency better?

For interactive uses such as recording, monitoring, gaming, and live applications, lower latency is generally preferable. The acceptable amount depends on the specific use case.

How do I test audio latency online?

Connect the device you want to test, allow microphone access, start the Sound Latency Test, and run multiple measurements. Keep the same audio path when comparing results.

Why does Bluetooth audio have more latency?

Bluetooth audio can involve encoding, transmission, buffering, decoding, and additional device processing. These stages can add delay compared with a wired audio path.

Can this test measure output latency by itself?

No. The Sound Latency Test measures the round-trip acoustic path. It does not isolate output latency from input latency.

Why do my latency results change between tests?

Browser scheduling, system load, audio buffering, microphone processing, room conditions, and other factors can cause run-to-run variation. Multiple measurements provide a more useful baseline.

Can I use this test for an audio interface?

Yes, the browser test can help you evaluate and compare the real-world latency of an audio interface setup. However, it does not isolate every hardware stage or measure hardware-only latency.

Is the Sound Latency Test a professional laboratory measurement?

No. It is a browser-based diagnostic estimate intended for practical testing and comparison. Professional hardware characterization may require controlled loopback measurement equipment.

About SoundLatencyTest

SoundLatencyTest.com provides browser-based audio latency testing and educational resources about audio timing, browser audio, operating-system audio pipelines, hardware interfaces, Bluetooth latency, and practical troubleshooting.

The site’s content and technical documentation explain both what the measurement can tell you and what it cannot determine. For the site’s editorial and technical standards, see Editorial Guidelines.

If you find a technical error or have a question about the tool, visit the Contact page.

Scroll to Top