“Good” latency depends on what you’re doing. A mixing engineer working on a finished track can tolerate 50–100ms of latency because they’re not relying on live monitoring feedback. A singer recording a vocal track needs latency under 20ms to feel natural. A live performer or DJ needs it under 50ms to stay in time.
The absolute best-case scenario is latency so low the human ear can’t detect it. For most music production, that threshold is around 10ms roundtrip. For video and live performance, it’s more variable. The key is matching your latency target to your workflow.
What Latency Numbers Mean in Practical Terms
At 5ms latency, the delay is imperceptible. You could never feel it even if you were listening for it. This is the sweet spot for professional tracking and live performance.
At 10–15ms, most people still don’t notice a delay during live monitoring, but sensitive musicians and trained ears may detect a slight timing inconsistency. It’s usually acceptable.
At 20–30ms, many musicians report feeling “off” or dragging the beat. The delay becomes palpable in a feedback loop (playing something and hearing it back immediately). It’s the threshold where compensation starts to kick in—you’ll unconsciously rush or lag to sync with the delayed signal.
At 50ms and beyond, the delay is obvious and distracting. Most live performance work, video sync, and professional tracking requires staying under this number.
Sub-10ms: The Gold Standard
If you achieve latency under 10ms roundtrip, you’ve hit the gold standard. At this range, latency is imperceptible for virtually all real-time audio work. You can track vocals, play virtual instruments, do live performance monitoring, and sync to video without any feeling of lag.
Professional audio interfaces typically spec 2–5ms roundtrip latency. The best USB and Thunderbolt interfaces achieve sub-5ms. If you’re shopping for an interface and latency is a priority, look for specs in the 2–5ms range.
Test your interface’s actual latency with a roundtrip measurement tool to see if it lives up to the manufacturer’s claims. Real-world latency depends on buffer size, sample rate, and driver optimization.
10–20ms: Still Acceptable for Tracking
If you’re between 10–20ms, you’re in acceptable territory for most music production tasks. You can record vocals, guitars, and live instruments with minimal adjustment for timing drift. Most musicians won’t notice a problem, though trained performers may feel slightly off.
This range is achievable on any modern interface paired with a halfway-decent computer and optimized drivers. Set your buffer size to 256 samples at 48 kHz (about 5ms), add another 3–5ms from your interface’s hardware latency, and you’ll land here.
Above 50ms: When Latency Becomes a Problem
Once you exceed 50ms roundtrip, most musicians will feel the delay during live monitoring. Your brain is used to zero latency between your body and the world, so a half-second gap registers as unnatural.
For video sync, above 20–30ms you’ll see visible lip-sync drift. If an actor’s mouth moves a quarter-second before the dialogue reaches the speaker, viewers notice immediately.
For streaming (Zoom, Teams, Discord), latency of 100–300ms is normal and people accept it as part of a real-time call, but it’s still noticeable and prevents truly natural conversation.
Latency Specs for Professional Audio Interfaces
When shopping for an audio interface, latency specs are usually listed as “roundtrip latency” at a specific buffer size and sample rate. A typical spec might read: “3ms @ 48 kHz, 256-sample buffer, ASIO driver on Windows.”
Good interfaces promise 2–5ms. Budget interfaces often spec 5–10ms. Very cheap or outdated interfaces might be 10–20ms or higher, especially over USB 2.0.
Keep in mind that the manufacturer’s spec assumes optimal conditions: latest drivers, 48 kHz or 44.1 kHz sample rate, and mid-range buffer sizes (256–512 samples). Your real-world latency may vary based on your computer’s specs and whether you’re using WASAPI, ASIO, or the standard Windows audio driver.
Compare your current setup’s latency to interface specs you’re considering so you know whether an upgrade will help.
How Plugins and Effects Add to Total Latency
Many audio plugins—especially linear-phase EQ, look-ahead compression, and convolver reverbs—introduce processing latency of their own. A single plugin might add 10–50ms depending on the algorithm.
If you’re tracking through heavy effects, plugin latency stacks on top of your interface and buffer latency. A typical scenario: 4ms interface latency + 5ms buffer latency + 10ms from a linear-phase EQ + 20ms from a convolver reverb = 39ms total.
For live tracking, use minimal or zero-latency plugins. Save heavy processing for the mixing phase. If you must use effects while recording, test your DAW’s latency with a latency measurement tool so you know what you’re working with.
Latency and Wireless Audio Devices
Bluetooth and Wi-Fi audio adds significant latency on top of your interface. Standard Bluetooth headphones add 100–300ms. aptX Low Latency headphones reduce this to about 40–130ms. 2.4 GHz wireless headsets (like those used in stage monitoring) can achieve 5–20ms but require a dedicated transmitter.
If you’re monitoring through any wireless device, expect latency to exceed acceptable ranges for real-time tracking. Use wired headphones for monitoring during recording and reserve wireless for mixing playback or non-critical listening.
Frequently Asked Questions
Is 20ms latency acceptable for recording a vocal?
It depends on the vocalist’s sensitivity. Most singers tolerate 10–20ms without trouble. Some experienced vocalists need it under 10ms to feel natural. Test with your singer and see if they feel drag or timing inconsistency.
Why do some interfaces claim 1–2ms latency but feel slower?
They may be measuring input-to-output latency only, not including driver or buffer overhead. Or they’re measuring at a very high buffer size and sample rate that you’re not actually using. Real-world roundtrip latency is usually 2–3ms higher than the headline spec.
Does latency affect audio quality or fidelity?
No. Latency is a timing delay, not a quality issue. Low-latency settings (small buffer sizes) don’t degrade sound quality; they just demand more CPU power.
What latency should I aim for when recording drums or percussion?
Below 20ms ideally. Drummers and percussionists are very timing-sensitive. Anything above 30ms and your drummer will hear a noticeable lag and struggle to stay in pocket with the track.
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.