Audio Latency Test

Overview

The Audio Latency Test measures the delay between a sound firing and you actually hearing it, two ways: click Measure Now to read your browser's reported output and base latency, or run the Play Sound / I Heard It! tap test to get an estimated total based on your own reaction time. That delay is what causes lip-sync problems in gaming, live streaming, video calls, and music production. Try the free vocal range test online for a quick, no-install way to check this yourself. The volume level discrimination test sharpens your ear with short, repeatable rounds.

Ever wondered exactly how many milliseconds of audio delay sit between the moment a signal is triggered and the instant you actually hear it? This Audio Latency Test gives you a precise, perceptual measurement of your output latency — the kind of number that determines whether your setup is fast enough for live performance, recording, casual play, or just watching video without a distracting lip-sync error. Whether you're a musician troubleshooting your in-ear monitors, a mix engineer dialling in a live stage rig, or a gamer chasing the lowest possible delay, knowing your real delay puts you in control of your setup.

How This Audio Latency Test Works — Understanding the Latency Test Method

What Is Audio Delay and Why Does It Accumulate?

Audio latency is the time gap between a signal trigger — such as a button press, a MIDI note, or a digital cue — and the moment that output reaches your inner ear. It is not a single delay introduced at one point in the signal path; it is the cumulative result of every stage your signal must pass through. The room mode and bass resonance calculator works out the exact figure instantly as you type.

From the moment your playback application generates a signal, it travels through the OS audio stack, is handed off to the DAC (digital-to-analogue converter), passed through speaker or headphone driver electronics, and finally converted into vibrations that travel to your ear. Every link in that chain adds a small cost.

On a cable-connected output with a well-optimised platform, that chain may take only 5–20 ms. Add a wireless connection and the total can balloon to over 250 ms.

The perceptual consequences are real. Below 10 to 15 milliseconds, delay feels instantaneous — equivalent to being 3 to 5 meters from a live source.

Above 40 ms, guitar delay becomes tangible. Singers reporting an echo effect when singing through monitors are typically experiencing delays above 20 ms.

Beyond 80 ms, footage sync breaks down and lip-sync errors become unmistakable. Understanding where your rig sits on that spectrum is exactly what this tool is designed to reveal, and the ability to measure audio delay precisely is its core purpose.

How the Test Measures Your Audio Delay in Milliseconds

The perceptual slider method works by playing a repeating click synchronised to a visual flash delay on a one-second cycle. Because of your system's output delay, the click arrives at your ears slightly later than the flash reaches your eyes.

You drag the delay slider to push the flash forward in time until both the simultaneous flash and the click feel perfectly aligned. The offset reading at that point is your end-to-end delay relative to your display's display baseline. For the most stable reading, use your peripheral vision to watch the flash while listening for the click.

The tap-based method works differently. You tap the button each time you hear a beat and stay on beat with the rhythm.

The tool measures the gap between your signal's play-start time and the moment you tap — which corresponds to when you hear it. Results are computed as a trailing average of the last 10 beats to smooth out reaction time variation.

A countdown and timer prepare you for the starting beat, and the first beat anchors the baseline. The tool also displays a modulo between beats figure — this tries to calculate delay even if you missed a whole beat, because some output devices have a delay that extends beyond a full beat duration. The formula the tool uses internally is:

[current latency] % [ms between beats]

This modulo operation lets the tool handle cases where device delay exceeds the length of a single beat interval, recovering a meaningful current delay reading even when a missed beat would otherwise throw off the result. The detected BPM and current BPM values confirm whether your tapping rhythm is consistent with the playback tempo — if they diverge, your trailing average result may be less reliable.

Critically, this test applies no signal encoding to the output during measurement. The click is delivered as uncompressed output — stereo at your web client's native sample rate (commonly 44.1 kHz, 48 kHz, or up to 96 kHz) — to ensure that encoding-introduced audio delay from the platform does not corrupt the measurement of your physical playback device. The test signal itself is generated at full bit resolution, typically 16-bit or 24-bit, preserving precision throughout.

What Is the Reported Output Latency Shown Here — and What Does It Really Mean?

Modern web clients expose two delay estimates through the Web Audio API: baseLatency and outputLatency. The baseLatency property represents the size of the client's internal processing buffer — the buffers queued before handing audio off to the platform.

The outputLatency property is the client's estimate of the total delay from the Web Audio API's output to the playback device, including OS processing time. Together, they represent the reported latency that appears as a reference figure on this page. This is what we call the reported audio output latency from the API.

However, these values are client-side estimates, not physical measurements. They cannot see inside your wireless earphones, cannot account for encoding delay introduced during wireless processing, and cannot observe converter delay at the device level.

This is why the perceptual slider test consistently reads higher than the output delay reported by the API on cable-free devices. The reported figure is useful as a display baseline — particularly for technical users, support teams, and power users who want a quick platform-level reference — but your perceptual test result reflects actual end-to-end delay as you experience it during real listening and production work. Use this tool to monitor latency across different devices and connection types.

Audio Latency Benchmarks by Connection Type — How Your Setup Compares

Why Is Bluetooth Latency So High? Understanding the Wireless Audio Delay Problem

The audio latency problem with wireless connections is structural. When your device sends output wirelessly, it must first encode the signal using a transmitter codec, break it into data packets, transmit those packets over radio frequency (where radio interference can force retransmission), perform packet buffering at the receiver to reassemble the stream, then decode the signal before it reaches the speaker driver.

Each of these steps adds delay — and the encoding format support available on both your source device and your earphones determines the floor. Both sides must support the same format for you to get the encoding benefit; if either device falls back to older SBC formats, you get the worst-case result.

The SBC format — the baseline standard required of all wireless audio devices — typically delivers 150-300 ms of delay. That range is far above what is considered acceptable for anything other than passive listening.

The AAC format (common in Apple devices and many premium in-ear options) brings this down to around 100–200 ms. The aptX format targets 60–120 ms, while aptX Low Latency achieves approximately 32 ms — close to borderline acceptable for light interactive use. Next-generation formats like aptX Adaptive and LE Audio (part of Bluetooth 5.2+) can reach 40–80 ms, making them viable for clip sync and light play sessions.

On Windows and macOS, the platform output layer adds its own contribution. The audio subsystem, headphone driver, and any post-processing applied by the OS all add to end-to-end delay. On Windows, poorly tuned output buffers or high interrupt execution times will push the total higher — this is where tools capable of in-depth latency tests beyond what a web client can provide become relevant for power users and support teams building or maintaining real-time audio rigs.

Latency Thresholds by Use Case — How Many Milliseconds Is Acceptable?

What counts as acceptable delay depends entirely on what you're doing. Human perception is sensitive to timing in ways that vary significantly by task. The table below shows typical delay ranges by connection type and the use cases each supports.

For live performance — whether you're a vocalist singing through in-ear monitors, a guitarist monitoring through a floor monitor, or a performer relying on wireless in-ear monitors via a wireless monitoring rig — the target is firmly under 20 ms. At 10–15 ms, delay is low enough for live performances and is perceptually transparent: the perceived delay matches the natural offset of standing 3 to 5 meters from a speaker in a room. Beyond 20 ms, performers begin to experience an echo effect or a subtle chorus effect, especially when their voice resonates through bone resonance simultaneously with delayed output in the inner ear.

For casual play, under 60 ms is responsive. For competitive or live interactive use, you want under 20 ms where possible — delays above 80 ms introduce a lag between a trigger event in-game and your auditory response.

For clip playback, lip-sync errors become noticeable around 80 ms; an AV sync test or av sync calibration is the recommended approach for TV delay, soundbar delay, TV latency, or projector delay specifically. For passive listening and streamed content, even high delay may be imperceptible since nothing needs to synchronise with a visual reference.

Worked Examples: Measuring Latency for Different Audio Setups

Seeing how these thresholds apply to real-world playback devices makes them much easier to act on. The three examples below show how the same delay tester produces different results depending on your connection type and encoding format. Each example helps you test latency in a practical scenario.

Example 1 — Wired headphones (3.5mm jack), studio monitoring

1. Run the test with cable output active. A pair of reference headphones connected via 3.5mm jack passes through the output converter directly to the DAC with no wireless encoding step.
2. Observe the offset reading. A typical result is approximately 5 ms of total delay — within the 5–20 ms range considered acceptable for professional work and recording environments.
3. Interpret the result. At 5 ms, this setup is fully suitable for live output tracking, live instrument monitoring, in-ear monitoring, and recording in a DAW. The connection delay is low enough that your perception of the output is effectively instantaneous. This is your reaction baseline and display baseline for comparing cable-free output.

Example 2 — Bluetooth earbuds using SBC codec

1. Switch to wireless earbuds and run the audio latency test again. The earbuds negotiate the SBC format — the default fallback when neither the source nor the earbuds support a higher-quality encoding option.
2. Observe the offset reading. A result in the range of 150–200 ms (within the 150–300 ms SBC range) is typical. That is roughly 10× the wired result.
3. Interpret the result. At 150–200 ms, this setup produces a severe output delay that makes video unwatchable without lip-sync correction and interactive play essentially unresponsive. The encoded output and decoded signal pipeline of the SBC format is the primary culprit. This setup is only suitable for passive listening where no synchronisation is needed. Upgrading to earbuds with aptX or AAC support — and ensuring your source device also supports the same format — is the most effective remedy.

Example 3 — Bluetooth headphones with aptX Low Latency

1. Connect Bluetooth headphones that support aptX Low Latency and run the test. Both the source device and headphones must support this format for it to activate — confirm via your device's wireless settings.
2. Observe the offset reading. A result around 32 ms is typical for aptX Low Latency — well below the 40 ms threshold targeted by aptX Adaptive and LE Audio, and at the borderline of light interactive acceptability.
3. Interpret the result. At 32 ms, this setup is borderline acceptable for casual play and comfortable for clip playback. It falls short of the under 20 ms needed for live instrument work or singing through monitors on a live stage, but represents a dramatic improvement over older SBC output. For passive listening and general media consumption, the quality at this delay level is effectively transparent.

Using This Latency Tester for Windows System-Level Audio Diagnostics

System Factors That Increase Audio Latency Beyond the Connection Type

Even a cable connection can suffer from elevated delay if your Windows platform has underlying output issues. The audio latency problem on Windows stems from the fact that it is not a hard real-time operating system.

Instead, it relies on a soft real-time model in which the task planner dispatches threads on a best effort basis. When interrupt events occur — driven by devices connected to the platform — their interrupt handler executes at elevated IRQL and cannot be interrupted by the thread dispatcher. If a playback process is preempted by a long ISR or DPC, it may miss its buffer deadline, causing output gaps.

Hard pagefaults are another major contributor. When the playback process accesses a memory address that is not resident in physical RAM, the OS triggers an INT 14 (page fault) to retrieve the data from the swap file on disk.

If the data is in the hard disk cache, the penalty is moderate. If it must be physically read from disk sectors, the delay is severe and almost always causes audible output gaps.

Playback software built around large samplers is particularly prone to this. Solutions include locking the working set into fast storage, expanding installed RAM, or tuning the swap file behaviour — though disabling it entirely prevents crash dump creation if a system crash occurs.

Advanced users — including rig builders, core developers, and support teams — can use dedicated Windows analysis tools to track DPC routines, ISR routines, timer events, timer delays, and interrupt to user process latencies. These tools function as a combined ISR tracker, DPC monitor, and pagefault monitor, generating a comprehensible report that identifies which specific kernel modules, firmware components, and processes are responsible for highest delays and buffer underruns.

The report captures all sampled data for in-depth analysis and flags any execution times that exceed recommended thresholds (typically 100 µs). CPU power management settings that reduce processor frequency between buffer cycles — along with SMIs (System Management Interrupts) and processor stalls caused by firmware — can also push interrupt resolution beyond acceptable limits.

This depth of technical testing is relevant not just for audio professionals working in recording environments, but also for OEMs, rig builders, and driver developer teams who need to verify that their devices deliver low delay and stable output. For those users, combining a browser-based delay checker like this one with a full Windows kernel analysis tool (a latency monitor / dpc monitor with execution times reporting) provides the most complete view of output subsystem health.

Wi-Fi and Network-Based Audio Latency — Audio Over WiFi Considerations

For audio over wifi, delay depends heavily on your network setup. A crowded 2.4 GHz band introduces packet collisions and retransmissions that push millisecond delays well above 80 ms.

Switching to a 5GHz band and using a dedicated router (or a recommended router with QoS prioritisation) can bring wifi output into a range competitive with aptX. Digital consoles and cable-free monitoring rigs used on a live stage typically specify a maximum ms delay budget, with a digital mixing console and a mixer connection to a wifi router ideally delivering under 20 ms for individual channels and individual mixes. For personal monitoring and in-ear monitoring via wifi output, setup requirements should specify a free connection on the 5 GHz band for reliable session audio and live output tracking.

iOS, Android, and Cross-Platform Audio Beat Testing

On mobile platforms, iOS and Android have different delay floors. iOS typically achieves lower output delay through its Core Audio framework, while Android's response has historically been higher due to platform fragmentation. Checking delay via a browser-based wireless delay checker or bluetooth latency test tool gives you a quick cross-platform reading without installing dedicated software. Windows and Mac desktop environments generally outperform mobile for real-time audio with a cable-connected output device, and a high-quality analogue console bypasses digital delay entirely for the mixing stage.

Connecting via an audio interface with proper encoding support at 24 bits 96 kHz — delivering full signal resolution and uncompressed output with 16-bit stereo or 24-bit depth — establishes a recording baseline that client-reported delay figures can then be compared against. The crystal clear output and seamless in-ear experience that professional performers and mix engineers expect requires verifying that your complete signal chain stays within acceptable connection delay budgets from source to cable speakers or cable-free earbuds.

Related Hearing and Audio Latency Tools — Explore Your Full Audio Test Setup

Vocal Range Test and Tinnitus Matcher for Complete Hearing Assessment

Your audio setup is only as reliable as your hearing. If you're unsure whether the delay you're perceiving is genuine output lag or a factor of your own hearing sensitivity, these related tools help complete the picture.

The Vocal Range Test identifies your voice type and the pitch extremes your voice can reach — useful for performers and mix engineers calibrating individual channels in a room mix or broadcast mix. The Tinnitus Matcher helps you identify the pitch of ringing in your ears, which is particularly relevant for sound professionals who spend long hours wearing in-ear monitors or headphones. Persistent tinnitus can affect your ability to judge delay and output quality, so understanding your personal hearing baseline is part of responsible engineering.

Additional Online Audio Tests for Novice Users and Audio Professionals

• Hearing Test — Find the upper limits of your hearing across the full audible pitch range. Useful for first-time users checking whether age-related hearing loss affects their ability to detect high-pitch artifacts.
• Hearing Age Test — Estimate how old your ears are compared to population norms. A practical tool for performers, mix engineers, and anyone concerned about long-term hearing health after years of tracking at live events.
• Mosquito Tone — A high-pitch quality test that reveals the upper edge of your hearing. Relevant for checking whether you can hear encoding artifacts in streamed output at various bitrates.
• Subwoofer Test — Verify bass playback down to 1 Hz, useful for recording and home theatre setups where low-frequency synchronisation and alignment are critical for mixing and production.
• Vocal Range Test — Identify your voice type from bass to soprano. Used by performers and recording engineers during practice sessions to calibrate monitor mixes.
• Tinnitus Matcher — Match the pitch and character of ringing in the ears. Valuable for sound professionals tracking hearing health across multiple live performance seasons.

Together, these tools form a complete suite for understanding both your audio hardware output and your personal hearing sensitivity. Whether you're a mix engineer ensuring your digital output rig meets real-time standards, a broadcast engineer verifying voice latency on a production line, or a performer checking drums latency and guitar latency during a practice session, running a full set of online audio tests gives you the connection speed and device factor data you need to make confident decisions about your setup — from encoding settings to format selection to price-quality ratio trade-offs when choosing your next pair of cable-free earbuds or in-ear monitors. The sound latency you measure here is the starting point for every informed decision that follows.