If you’ve ever talked into a microphone and heard your voice echo back through your headphones a half-second later, you’ve experienced audio latency. It’s one of the most common frustrations for podcasters, musicians, streamers, and video creators, and it’s almost always fixable. This guide explains what audio latency is, why it happens, how to measure it, and the practical steps you can take to reduce or eliminate it.
The Simple Definition of Audio Latency
Audio latency is the measurable time delay between a sound being produced at an input and being heard at the output.
Here’s a scenario to understand it. You sing a note into a microphone. That signal travels through your audio interface, into your computer’s software, gets processed, and then gets sent back out to your headphones. Every step in that chain takes a small amount of time. When those steps add up, you hear your voice a fraction of a second after you actually made the sound, and that fraction of a second is latency.
Latency is measured in milliseconds (ms). One millisecond is one-thousandth of a second. That sounds negligible, but in music and audio production, delays of even 10ms, 20ms, or 30ms are enough to throw off a vocal performance, cause lip-sync drift in video, or make a wireless mic feel noticeably “off.” Understanding the unit matters because the rest of this article uses ms benchmarks to help you judge whether your current latency is a problem worth solving.
Why Audio Latency Matters
Audio latency is more than a small annoyance. It can make recording, monitoring, and matching sound much harder. Even a 15-20 ms delay can feel distracting. Singers may lose their natural rhythm while recording in a DAW. They often expect to hear their voice right away. Skilled musicians notice these delays even more because their ears are trained for instant feedback.
For video creators, latency causes lip-sync drift, where a speaker’s mouth movements and the recorded audio fall out of alignment. A delay as small as 40ms can be visible to viewers. For live streamers, high latency between the audio source and the broadcast feed makes real-time audience interaction difficult to manage smoothly. This is why it helps to understand latency before you start recording.
The Main Types of Audio Latency
Not all audio latency comes from the same source. Knowing which type you’re dealing with points you directly toward the right fix.
Monitoring Latency
Monitoring latency is the delay you hear through your headphones while recording, and it’s the most common complaint among new producers, podcasters, and musicians. When you speak or sing into a microphone, the signal travels into your audio interface, then into your DAW, where it’s processed and routed back out to your headphone output. Every step in the software adds a little more delay. The result is a slight echo in your headphones that can range from a few milliseconds to well over 30ms, depending on your system settings and hardware.
Wireless Transmission Latency
Wireless microphones also add some delay before the sound reaches your device. The signal must be processed, sent wirelessly, and processed again. Low-quality wireless systems, which are usually inexpensive, may add 20 to 30 milliseconds or more. Consequences? Lip-sync problems and frustration during live monitoring.
Professional-grade systems are engineered to keep transmission delay well under 5ms. The Hollyland LARK MAX 2, for example, is built for low-latency wireless transmission and pairs with OWS (open-wearable stereo) earphones that support low-latency monitoring. This gives presenters and on-camera speakers the real-time audio feedback they need without the disorienting echo common to cheaper wireless systems.
Plugin and Processing Latency
Some plugins need extra time before they can output sound. Reverbs, convolution effects, and lookahead compressors are common examples. They must process enough audio samples before finishing their calculations. This extra processing time adds more audio latency. The more complex the plugin, the longer the processing window it requires. Most modern DAWs include Plugin Delay Compensation (PDC), which automatically detects and corrects for per-plugin delay by offsetting tracks to maintain time alignment. PDC works well during mixing, but during live monitoring, it can still contribute to the overall latency you hear in your headphones.
Streaming and Playback Latency
Streaming latency is different from recording latency. When broadcasting live, your audio goes through an encoding step, gets broken into chunks by your streaming software, passes through CDN infrastructure, and is decoded again on the viewer’s end. The total delay a remote viewer experiences can range from a few seconds to 30 seconds or more, depending on the streaming protocol. This type of latency is not something you fix in your DAW. It is managed through encoder settings, streaming service configuration, and delivery protocol choices.
What Causes Audio Latency?
Understanding the main reasons gives you direct control over how to reduce latency in your own setup.
Buffer Size
Buffer size is the single biggest lever in managing recording latency. When your computer processes audio, it works in small chunks called buffers. Choosing a bigger buffer can stop unwanted audio problems. You may hear fewer clicks, pops, or dropouts during recording. But there is a downside! The sound takes longer to reach your ears. A smaller buffer means lower latency, but if your computer cannot process audio fast enough to keep up, you will hear artifacts.
For tracking, most engineers set buffers to 64 or 128 samples for low-latency monitoring. For mixing, where real-time monitoring is not critical, buffers of 512 or 1024 samples are common because they allow headroom for plugin-heavy sessions.
Driver Quality and Audio Interface Hardware
The driver connecting your audio device and DAW can change latency. Basic system drivers usually focus more on stability than speed. Because of that, they often create more delay. Audio drivers like ASIO for Windows and Core Audio for macOS are made for recording. They can make the delay much shorter. Using your audio interface with its official driver is also a smart first step. It can improve latency without replacing your current hardware.
Processing Load
Even with ideal buffer settings and the right drivers, a CPU under heavy load will struggle to process audio in real time. Projects with many virtual instruments and heavy audio effects need more processing power. This puts extra pressure on your computer while recording. As a result, the system may add more latency to avoid audio glitches. Unnecessary background applications running during a session can make this problem even worse. Therefore, reducing active plugins during tracking and closing CPU-heavy background tasks frees up headroom for stable, low-latency performance.
What Latency Numbers Actually Mean
If you’re not sure whether your current latency is a problem, this framework gives you a practical reference for evaluating it.
|
Latency Range |
Experience |
Typical Use Case |
|---|---|---|
|
Under 5 ms |
Imperceptible |
Real-time monitoring, live performance |
|
5–20 ms |
Acceptable |
Recording, most studio work |
|
20–40 ms |
Noticeable |
Tolerable for non-critical tasks |
|
Over 40 ms |
Disruptive |
Causes timing errors, sync drift |
Most audio interfaces can keep latency below 10 ms. This is common with ASIO or Core Audio drivers. A buffer size of 128 samples or less also helps. If the delay stays above 10 or 12ms, check your buffer settings first. Try a smaller buffer, or turn on direct monitoring. These changes are worth trying before buying new hardware.
How to Reduce Audio Latency
Most latency problems respond well to settings adjustments before any new gear is needed. Work through these steps in order.
-
Lower your buffer size: Open your DAW’s audio settings and reduce the buffer size to 128 or 64 samples when recording. This is the fastest, most direct way to cut monitoring latency. Raise it back up during the mix stage when real-time monitoring is no longer required.
-
Enable direct monitoring on your audio interface: Direct monitoring routes your microphone signal straight to your headphone output in hardware, bypassing the DAW’s software path entirely. The result is near-zero monitoring latency, typically under 1ms. Most audio interfaces include a mix knob or direct monitor button that blends your live input signal with DAW playback so you can hear both simultaneously.
-
Switch to ASIO or Core Audio drivers: Install the official driver from your audio interface manufacturer first. If you use Windows without a dedicated audio interface, ASIO4ALL is a free option. It usually creates less delay than standard Windows audio drivers. If you use macOS, Core Audio comes built into the system. It is already set up to keep audio latency low.
-
Choose low-latency wireless gear: If you work with wireless microphones, check the manufacturer’s published end-to-end transmission latency spec before purchasing. Prioritize systems rated under 5ms. The Hollyland LARK MAX 2 is made for low-latency wireless audio. It also supports real-time monitoring with OWS earphones. This helps on-camera presenters hear themselves without a noticeable delay.
-
Reduce plugin load during tracking: Disable or bypass CPU-heavy plugins such as convolution reverb and compressors with lookahead while recording. Monitor through a lighter signal chain and reserve heavy processing for the mix pass, when real-time latency is no longer a concern.
FAQs
What is acceptable latency for recording audio?
Under 20ms is generally acceptable for most recording situations, and under 10ms is ideal for real-time monitoring during performance. Once latency exceeds 30–40ms, most performers notice a disruptive echo that interferes with timing. Latency matters less during mixing and editing than during live recording. Your DAW should still use delay compensation to keep tracks aligned. This also helps prevent phase problems and timing errors.
What causes high latency in a DAW?
Large buffer settings often cause higher audio latency. Basic system audio drivers can also add more delay. Too many plugins or unsupported audio hardware may make things worse. In most cases, changing the buffer size and using the right driver fixes the problem. And guess what? You can often do this without spending on any new equipment.
Is audio latency the same as audio lag?
People usually use latency and lag to mean the same thing. They actually describe different types of audio delay. Latency is the time an audio signal needs to pass through a system. Lag usually means a delay that is easy to notice. You might see it as lip-sync problems or delayed game audio. Both are measured in milliseconds.
Does wireless audio always have more latency than wired?
Wireless mics add a small amount of transmission delay. Most professional systems keep that delay under 5 milliseconds. In real recording sessions, that feels almost the same as using a wired microphone. Lower-priced wireless systems can add more than 20 to 30 milliseconds. This may cause noticeable lip-sync problems in videos.
Conclusion
Audio latency is the short delay between sound going in and coming out. It is measured in milliseconds. Buffer settings, audio drivers, and hardware are the most common causes. In many cases, a smaller buffer and direct monitoring fix the issue without expensive and additional gear. If your wireless microphone causes the delay, look for a system with under 5 milliseconds of transmission latency before buying it.
