If you think your audio latency is the problem, you need to measure it first. Guessing leads to hours of wasted optimization. A good latency tester tells you exactly what’s happening in milliseconds and points you toward the actual culprit.
The challenge is that no single tool does everything. Browser-based tests work anywhere but skip some technical detail. Desktop software goes deep but only works on Windows. DAW buffer readouts are accurate but don’t account for operating system overhead. The best approach is to test with multiple tools, cross-reference the results, and triangulate the truth.
Browser-Based Latency Tests: Quick, Universal, Good for Diagnosis
Our Sound Latency Test (https://soundlatencytest.com/sound-latency-test/)
What it does: Measures browser-reported latency (base and output delay in milliseconds) and runs a tap-sync test where you tap a button when you hear a click. The tool subtracts human reaction time and estimates your audio output latency.
Pros: Works on any OS without download. Runs offline after loading. Saves results as CSV. No microphone permission required for the base latency readout.
Cons: Browser-reported latency is an estimate, not ground truth. The tap test requires you to estimate your own reaction time. Results vary based on browser, OS, and device.
Best for: Quick diagnosis of “is my audio setup okay?” and comparing latency across browsers. Repeat the test a few times to get an average.
Superpowered Web Latency Test (https://superpowered.com/webbrowserlatency)
What it does: An acoustic loopback test in the browser—it plays a beep and listens for it on the microphone, then times the round-trip delay.
Pros: True round-trip measurement, not an estimate. Accounts for all delays in the chain (interface, OS, browser, device). The most honest browser-based number.
Cons: Requires microphone permission. Takes longer to run (multiple iterations). Less convenient than browser-reported tests.
Best for: Accurate baseline measurement when you want to compare against professional testing equipment.
Mouse Testing Audio Latency Test (https://mousetesting.com/en/tools/audio-latency-test)
What it does: Shows browser base and output latency separately, then runs a tap-sync test. Explains human auditory reaction time (200–250 ms) so you understand what portion of your measured delay is actually your ears and brain versus the system.
Pros: Educational framing. Helps beginners understand the gap between system latency and human latency.
Cons: Same limitations as tap-sync tests (reaction time variability makes it less precise than acoustic loopback).
Best for: Learning how to interpret latency numbers and understanding your own reaction time.
Desktop Latency Tools: Deep Diagnosis, Windows Only
LatencyMon (Resplendence Software) — Windows only
What it does: Monitors DPC (Deferred Procedure Call) latency, which identifies driver conflicts and hardware interrupts that prevent low-latency audio. It’s not measuring audio latency directly; it’s diagnosing why your audio has dropouts, clicks, or pops.
Pros: Pinpoints the exact driver or device causing problems. Essential troubleshooting tool. Free.
Cons: Windows only. Doesn’t measure audio latency itself, only DPC latency spikes. Requires some technical knowledge to interpret results.
Best for: Troubleshooting audio glitches, dropouts, and clicks when DPC latency is high. Run it for 1–2 minutes and check if any drivers spike above 300 microseconds.
DAWbench (Windows only)
What it does: Runs comprehensive latency benchmarks across multiple buffer sizes and measures round-trip latency with various audio interface and driver combinations. It’s a testing framework rather than a simple tool.
Pros: Compares latency across interfaces and drivers. Professional-grade precision. Used by audio engineers to benchmark equipment.
Cons: Windows only. Requires some setup and technical knowledge. Time-intensive testing process.
Best for: Serious gear comparison and benchmarking if you’re choosing an audio interface.
DAW-Native Latency Readouts
All major DAWs (Ableton Live, Logic Pro, Reaper, FL Studio, Pro Tools) display latency figures in their audio settings or plugins. These are usually buffer latency plus reported interface latency, but they don’t include OS overhead or wireless latency.
Pros: Accurate within your DAW’s measurement system. No external tool needed.
Cons: Only shows part of the picture. Doesn’t account for operating system buffering, network latency, or Bluetooth overhead.
Best for: Relative comparison. If your DAW says 10 ms and you upgrade your interface driver, run the same test again to see if it improved.
Manual Acoustic Loopback (The Gold Standard)
If you want absolute, verifiable latency, do this:
- Play a short, sharp click through your output device
- Position a microphone near the speaker (or use a USB loopback cable if testing an interface)
- Record the click back through your input while noting the exact trigger time
- Open Audacity (free, all platforms) and place both tracks side-by-side
- Measure the time difference between the trigger and the recorded onset
This is how professional audio engineers measure equipment. It captures everything: the interface, the OS, the driver, the DAC, the speaker, the room, the microphone, and the ADC. It’s the real round-trip latency.
Pros: Honest measurement. No estimates or assumptions.
Cons: Time-consuming. Requires a microphone and careful setup. Affected by room acoustics.
Best for: Baseline verification before and after optimization. Benchmarking your own gear.
Which Tool Should You Actually Use?
For casual testing: Use our Sound Latency Test or Superpowered. Takes 30 seconds. Good enough to know if you’re in the ballpark.
For troubleshooting audio problems on Windows: Run LatencyMon first. High DPC latency spikes are usually the culprit behind clicks and dropouts.
For music production: Check your DAW’s reported latency at your actual buffer size and sample rate. If it matches the calculated value from the formula (Buffer ÷ Sample Rate × 1000), your system is clean. If it’s significantly higher, driver overhead is eating into performance.
For professional work: Run an acoustic loopback test in Audacity to verify your true round-trip latency. This is your ground truth.
For comparing interfaces: Use DAWbench or test each interface with the same DAW, buffer, and sample rate, then compare the reported latency figures.
The Interpretation Chart: What Latency Numbers Mean
Under 10 ms: Excellent. Professional-grade. Good for live recording, music production, competitive gaming.
10–20 ms: Good. Noticeable if you’re paying attention, but doesn’t disrupt most work. Acceptable for gaming and casual streaming.
20–50 ms: Fair. Noticeable in music production; you’ll feel it during recording. Acceptable for video and passive streaming.
50–100 ms: High. Problematic for music or timing-critical work. Acceptable only for streaming or video.
Over 100 ms: Very high. Only acceptable for passive listening, video playback, or if you’re using wireless (Bluetooth adds this much inherently).
Remember: Browser tests show browser-only latency. Add Bluetooth (40–300 ms), wireless systems (20–100 ms), or network streaming (50–200 ms) to the reported number for true total latency.
Testing Your Specific Setup
Start with our Sound Latency Test and get a baseline. If you get a surprising result, run it again in different browsers (Chrome, Firefox, Safari, Edge) to see if the issue is browser-specific or system-wide. Then run LatencyMon on Windows if you get high numbers.
For music production, compare the browser result against your DAW’s reported latency at your actual working buffer and sample rate. The two numbers should be in the same ballpark (within 5 ms). If your DAW reports 20 ms but the browser test shows 40 ms, you have system overhead eating into performance—update drivers, check for background services, or lower your buffer.
If you’re still confused after testing, check our complete guide to reducing audio latency, which covers platform-specific fixes for Windows, Mac, and Linux, plus DAW-specific optimization.
Dalton is an audio testing and latency optimization writer at SoundLatencyTest. He focuses on audio latency analysis, sound delay testing, recording performance, and audio troubleshooting tools for producers, gamers, streamers, musicians, and audio engineers.