What Latency Is and How to Reduce It When Recording in 2026?

If you have ever plugged in a microphone, started recording, and heard your own voice echo back a split second late, you have met latency. It is one of the most frustrating problems in home recording, and nearly every musician, podcaster, and producer runs into it eventually. That tiny delay between when you sing or play a note and when you hear it through your headphones can throw off your timing, ruin a take, and make recording feel impossible.

The good news is that latency is not some mysterious curse on your setup. It has specific causes, and you can fix almost every case with the right settings adjustments. Understanding latency recording fundamentals means you can diagnose the problem in minutes instead of spending hours randomly tweaking buttons in your DAW.

In this guide, I will walk you through what latency actually is, why it happens, what numbers you should aim for, and the exact steps to reduce it. Whether you are recording vocals in a bedroom studio, tracking guitar through an audio interface, or hosting a podcast, these solutions work across all major DAWs including Ableton Live, FL Studio, Logic Pro, Pro Tools, and Reaper. By the end, you will have a clear troubleshooting workflow you can use anytime latency rears its head.

What Is Latency in Recording?

Latency in recording is the delay between when an audio signal enters your system and when you hear it back through your headphones or speakers. It is measured in milliseconds (ms), and it happens because your computer needs time to convert, process, and play back audio. Even a few milliseconds of delay can be noticeable when you are trying to play or sing in real time.

Here is what happens in the signal chain. When you sing into a microphone or plug in a guitar, your audio interface receives an analog signal. The interface converts that analog signal into digital data through a process called analog-to-digital (A/D) conversion. That digital data travels through your USB, Thunderbolt, or FireWire cable into your computer, where your DAW buffers and processes it. Then the processed audio travels back to your interface, which converts it back to analog through digital-to-analog (D/A) conversion so your headphones can play it.

Each step in that chain takes a small amount of time. A/D conversion takes time. Buffering takes time. D/A conversion takes time. When you add all those tiny delays together, you get your total roundtrip latency. The term roundtrip latency refers to the complete journey: from your input, through the computer, and back out to your ears.

Think of it like a conversation with someone on a video call with a bad connection. You speak, and a moment later they hear you. That gap is latency. In audio recording, the same thing happens with your instrument or voice. You play a note, and a fraction of a second later you hear it in your headphones. For tracking and overdubbing, where precision timing matters, even 15 to 20ms of delay can make you feel like you are playing slightly behind the beat.

This is different from the latency you might experience in gaming or video streaming. Audio latency recording specifically deals with the real-time monitoring path through your DAW and audio interface. The recorded audio itself does not have latency issues once it is captured, which is why your tracks often sound perfectly in time on playback even though monitoring felt delayed during the performance.

What Is Acceptable Latency for Recording?

For most recording situations, latency under 10 milliseconds is the target. At 10ms or below, the delay is short enough that your brain does not perceive it as a separate event, and you can perform naturally without adjusting your timing. Once you cross the 10 to 15ms threshold, most musicians start to notice the delay and compensate by playing earlier, which throws off the performance.

Here is a breakdown of what different latency levels feel like in practice:

Under 5ms: Effectively imperceptible. You will not notice any delay, and monitoring feels natural. This is the gold standard for real-time recording.

5 to 10ms: Barely noticeable. Most musicians can record comfortably at this level. You might feel a tiny amount of detachment, but it will not affect your performance.

10 to 20ms: Noticeable but manageable for some tasks. Recording vocals or acoustic instruments at this level can feel slightly off. Guitarists tracking with amp simulation plugins often struggle here.

20 to 40ms: Clearly audible delay. Recording becomes difficult, especially when playing along with a backing track or metronome. You will instinctively play ahead of the beat to compensate, which usually results in sloppy timing.

40ms and above: Severe latency. Recording in real time is nearly impossible. You hear yourself with a noticeable echo, making it extremely hard to stay in time or deliver a natural performance.

200ms and above: Extreme latency. This level of delay makes any real-time recording completely unworkable. You would essentially be performing blind, hearing yourself a fifth of a second after you sing or play.

The right threshold also depends on what you are recording. Vocals and acoustic instruments are the most sensitive to latency because performers rely on hearing themselves naturally. MIDI recording with virtual instruments is more forgiving since the DAW can compensate internally. Podcast recording falls somewhere in the middle. A solo podcaster speaking into a microphone can tolerate slightly more latency than a vocalist trying to hit precise harmonies, but anything above 15ms will start to feel unnatural and distracting.

One common point of confusion: monitoring latency and recording latency are not the same thing. The delay you hear while monitoring your input is what causes problems during performance. The actual recorded audio is typically fine because your DAW applies latency compensation to align recorded tracks with the project timeline. This is why people often say “the recording sounds fine but monitoring is delayed.” Understanding this distinction helps you focus your troubleshooting on the monitoring path rather than worrying about whether your recorded audio is corrupted.

What Causes Audio Latency When Recording?

Latency does not come from one single source. It builds up from several points in your signal chain, and understanding each cause helps you figure out where to make adjustments. Here are the main culprits behind high latency recording.

Buffer Size Set Too High

Your audio buffer is a small chunk of memory that your computer uses to temporarily store audio data while processing it. A larger buffer gives your CPU more time to handle the audio, which prevents clicks, pops, and dropouts. But a larger buffer also means more latency because the computer waits longer to fill the buffer before sending the audio through. This is the number one cause of noticeable delay in home recording setups, and it is also the easiest to fix.

Using the Wrong Audio Driver

On Windows, your choice of audio driver dramatically affects latency. The default Windows drivers (MME, WDM, and WASAPI in shared mode) add significant delay because they route audio through the Windows audio mixer. ASIO drivers bypass the Windows audio layer and communicate directly with your audio interface, cutting latency dramatically. On Mac, Core Audio is the built-in driver and it is already well-optimized, so Mac users generally do not face driver-related latency issues the way Windows users do.

Plugins on Your Input Chain

If you have effects plugins loaded on the channel you are recording through, each plugin adds processing delay. Reverb, EQ, compression, and especially lookahead limiters can add several milliseconds each. Some plugins introduce what is called latency reportingly, meaning they tell the DAW exactly how much delay they add so the DAW can compensate. But during real-time monitoring, that compensation does not help because you are hearing the live signal before any time adjustment happens.

Sample Rate Mismatch

If your project sample rate does not match your audio interface sample rate, your system may perform real-time sample rate conversion, which adds latency. Always make sure your DAW project, audio interface settings, and operating system audio settings all use the same sample rate. The most common rates are 44.1kHz and 48kHz.

Connection Type and Interface Quality

The physical connection between your interface and computer matters. USB 2.0 interfaces are the most common and generally perform well, but Thunderbolt interfaces can offer lower latency due to faster data transfer. The quality of your interface’s internal converters also plays a role. A budget interface with slow A/D and D/A converters will inherently add more latency than a professional-grade interface with high-quality converters.

Computer CPU and RAM Limitations

If your computer is struggling to process audio in real time, you will be forced to use a larger buffer to avoid audio dropouts. This is common on older machines, computers with many background applications running, or projects with heavy plugin loads. Insufficient RAM can cause the system to use disk swapping, which introduces unpredictable latency spikes during recording.

How to Reduce Latency When Recording?: Step-by-Step

Reducing latency comes down to making smart adjustments at each point in your signal chain. I have organized these steps from the most impactful and easiest changes to more advanced optimizations. Work through them in order, testing your latency after each change.

Step 1: Lower Your Buffer Size

This is the single most effective change you can make. Open your DAW’s audio settings and find the buffer size (sometimes called I/O buffer size or ASIO buffer size). Reduce it to 128 samples for recording. If you experience clicks, pops, or dropouts, increase to 256 samples. For reference, at a sample rate of 44.1kHz, a buffer of 128 samples produces about 2.9ms of buffer latency one way. At 48kHz, that same 128-sample buffer drops to about 2.7ms.

The trade-off is simple: lower buffer means less latency but more strain on your CPU. If your computer cannot handle a low buffer during recording, close other applications and reduce the number of active plugins. When you switch to mixing, you can raise the buffer to 512 or 1024 samples since latency does not matter when you are not recording in real time.

Step 2: Install and Use ASIO Drivers (Windows)

If you are on Windows, make sure you are using an ASIO driver, not the default Windows audio driver. Most audio interfaces come with a dedicated ASIO driver from the manufacturer. Download and install it from the manufacturer’s website. Then go into your DAW’s audio settings and select the ASIO driver for your interface.

If your interface does not have a dedicated ASIO driver, download ASIO4ALL. It is a free universal ASIO driver that works with almost any audio interface. While it is not as efficient as a manufacturer-specific driver, it is far better than using Windows default drivers and will cut your latency significantly.

On Mac, you are already using Core Audio, which is excellent. No driver changes are needed.

Step 3: Increase Your Sample Rate

Raising your sample rate from 44.1kHz to 48kHz or even 96kHz reduces latency because the computer processes audio samples faster. At 96kHz, each sample takes half the time to process compared to 48kHz, which means the same buffer size produces half the latency.

However, higher sample rates also increase CPU load since your computer is processing twice as many samples per second. If you jump to 96kHz and start getting dropouts, lower your buffer size or reduce your sample rate back to 48kHz. Most home recording setups work well at 48kHz, which is also the standard for video and film audio.

Step 4: Enable Direct Monitoring on Your Audio Interface

Many audio interfaces have a direct monitoring feature that routes your input signal directly to your headphones before it ever reaches the computer. This means you hear yourself with essentially zero latency because the signal skips the computer processing entirely.

Look for a direct monitor switch or knob on your interface. Some interfaces have a simple on/off button, while others have a mix knob that lets you blend the direct signal with the DAW playback. Set the mix so you hear more of the direct input and less of the DAW-processed signal while recording.

The downside of direct monitoring is that you hear a dry signal without any effects or processing from your DAW. For vocalists who want to hear reverb while singing, this can feel unnatural. Some higher-end interfaces solve this with built-in DSP effects that apply reverb and EQ to the direct monitor signal without adding latency.

Step 5: Remove Plugins from Input Channels

Before you start recording, bypass or remove all plugins from the track you are recording into. This includes EQ, compression, reverb, and any amp simulation. Each active plugin on your input chain adds processing delay that contributes to your total monitoring latency.

If you absolutely need to hear effects while recording, use low-latency alternatives. Many DAWs have stock plugins that are optimized for low latency. Avoid third-party plugins with lookahead features during tracking, as these can add 10ms or more of delay on their own.

Step 6: Close Background Applications

Every application running on your computer competes for CPU time. Web browsers with dozens of tabs, streaming services, cloud sync tools, and even antivirus software can cause audio processing hiccups that force you to use a higher buffer size. Before recording, close everything except your DAW.

On Windows, you can also adjust your power plan to High Performance mode to prevent the CPU from throttling during recording sessions. On Mac, make sure your computer is plugged into power and not in low-power mode.

Step 7: Optimize Your Operating System for Audio

Both Windows and Mac have settings that can help reduce audio latency. On Windows 10 and 11, disable audio enhancements in your sound control panel, as these add processing overhead. You can also adjust your processor scheduling to prioritize background services, which can improve audio performance.

On Mac, make sure your energy saver settings allow maximum performance. If you are using Logic Pro, enable Low Latency Mode, which automatically bypasses plugins that introduce latency above a threshold you define. This is one of the most powerful features in Logic for managing latency during recording.

On any system, keeping your audio interface drivers and DAW software up to date ensures you have the latest latency optimizations from manufacturers. Updates often include performance improvements that can shave milliseconds off your roundtrip latency.

Buffer Size Quick Reference by Scenario

Here is a quick guide to help you pick the right buffer size for different recording situations:

Recording vocals: 64 to 128 samples. Vocals are highly sensitive to latency. Keep the buffer as low as your CPU allows.

Recording guitar (DI or with plugins): 64 to 128 samples. Guitarists using amp simulation plugins need extremely low latency for natural feel.

Recording acoustic instruments: 128 samples. Slightly less critical than vocals but still important for timing accuracy.

MIDI recording with virtual instruments: 128 to 256 samples. Software instruments generate audio inside the DAW, so monitoring latency is generally lower.

Podcast recording: 128 to 256 samples. Podcasters can tolerate slightly more latency than musicians but should still keep it low for natural conversation flow.

Overdubbing: 64 to 128 samples. When layering takes over existing tracks, precise timing is critical, so minimize latency.

Mixing (not recording): 512 to 1024 samples. Latency does not matter during mixing, so use a large buffer to give your CPU maximum headroom for plugins.

Buffer Size and Sample Rate: The Latency Formula

The relationship between buffer size, sample rate, and latency follows a simple mathematical formula. Once you understand this formula, you can calculate exactly how much latency your settings produce and make informed decisions about what to change.

The formula is: Latency (in ms) = Buffer Size / Sample Rate x 1000

This gives you the one-way latency from your input through the buffer. Remember that roundtrip latency includes both input and output, plus the fixed latency from your interface’s A/D and D/A converters. But the buffer-related portion is what you can control, and the formula tells you exactly how much it contributes.

Let me run through some real-world examples so you can see how this works:

128 samples at 44.1kHz: 128 / 44100 x 1000 = 2.9ms (one way). Your roundtrip buffer latency would be approximately 5.8ms, which is excellent for recording.

256 samples at 44.1kHz: 256 / 44100 x 1000 = 5.8ms (one way). Roundtrip buffer latency is approximately 11.6ms, which is borderline for recording vocals.

512 samples at 44.1kHz: 512 / 44100 x 1000 = 11.6ms (one way). Roundtrip buffer latency is approximately 23.2ms, which is too high for comfortable recording.

128 samples at 48kHz: 128 / 48000 x 1000 = 2.7ms (one way). Raising the sample rate from 44.1kHz to 48kHz gives you slightly less latency at the same buffer size.

128 samples at 96kHz: 128 / 96000 x 1000 = 1.3ms (one way). Doubling the sample rate halves your buffer latency. However, your CPU now processes twice as many samples, so you may need to increase the buffer if you get dropouts.

64 samples at 48kHz: 64 / 48000 x 1000 = 1.3ms (one way). This is about as low as most setups can go while remaining stable. Only use this during tracking with minimal plugins.

The key takeaway from the formula is that buffer size and sample rate work together. You can reduce latency by lowering the buffer size, raising the sample rate, or both. But both changes increase CPU load, so you need to find the balance that your computer can handle without producing audio artifacts.

For tracking, aim for a total roundtrip latency of 10ms or less. Based on the formula, a buffer of 128 samples at 48kHz gets you close to that target before accounting for converter latency. For mixing, switch to a buffer of 512 or higher and do not worry about the latency since you are not recording in real time.

Direct Monitoring: The Zero-Latency Solution

Direct monitoring is the most effective way to eliminate monitoring latency entirely. It routes your input signal directly to your headphones before the audio ever reaches your computer, so you hear yourself with virtually zero delay. For performers who are highly sensitive to latency, this is often the best solution.

There are two types of monitoring in recording setups: hardware monitoring and software monitoring. Hardware monitoring (also called direct monitoring) happens inside your audio interface. The interface takes your input signal and sends a copy straight to your headphone output, bypassing the computer completely. Software monitoring routes your input through the DAW, where it gets processed and sent back to the interface for playback. Software monitoring is what introduces latency.

Most modern audio interfaces support direct monitoring in some form. The Focusrite Scarlett series, for example, has a direct monitor switch on the front panel. The Universal Audio Apollo interfaces go further with built-in DSP that lets you apply effects to the direct monitor path without latency. Even budget interfaces from PreSonus, MOTU, and Behringer typically include a direct monitoring option.

Pros of direct monitoring:

Zero latency. You hear yourself instantly with no delay whatsoever. This is especially important for vocalists who need to hear their pitch accurately and guitarists tracking with amp simulation.

Reduced CPU load. Since the signal does not go through the DAW for monitoring, you can keep your buffer size higher without affecting your monitoring experience.

Simpler setup. You do not need to worry about plugin latency, buffer size, or driver optimization for the monitoring path.

Cons of direct monitoring:

Dry signal. You hear your performance without any effects, which some performers find uninspiring. A vocalist who is used to singing with reverb may feel exposed hearing a completely dry voice.

No DAW-based mixing of the monitor signal. You cannot easily apply DAW plugins to what you hear while recording, since those effects only apply to the software-monitored path.

stereo routing limitations. On some interfaces, direct monitoring sums everything to mono or does not respect your DAW’s panning, which can be disorienting if you are recording alongside a backing track.

The best approach for many recording situations is a hybrid setup. Use direct monitoring for the performer’s input signal (so they hear themselves without delay) and let the DAW handle playback of existing tracks (which do not have latency issues since they are already recorded). Many interfaces have a mix knob that lets you blend the direct input with DAW playback, giving you the best of both worlds.

If you need effects while recording and your interface does not have built-in DSP, consider using a plugin with latency compensation disabled just for monitoring purposes. Some DAWs, like Logic Pro with Low Latency Mode and Pro Tools with Low Latency Monitoring, have features specifically designed to manage this workflow.

Latency Troubleshooting Checklist

When latency strikes and you cannot figure out why, work through this checklist in order. Each step addresses a common cause, and most issues can be resolved within the first few steps.

1. Check your buffer size. Is it set above 256 for recording? Lower it to 128. This fixes the majority of latency complaints.

2. Verify your audio driver. On Windows, confirm you are using ASIO, not MME or WDM. On Mac, confirm you are using Core Audio with the correct device selected.

3. Check for plugins on the input channel. Bypass everything on the track you are recording into. Reverb, compression, and especially lookahead limiters add delay.

4. Confirm your sample rate matches everywhere. Your DAW project, audio interface control panel, and operating system sound settings should all show the same sample rate.

5. Try direct monitoring. If your interface supports it, enable direct monitoring and see if the delay disappears. If it does, the problem is in your software monitoring path.

6. Close background applications. Browsers, streaming apps, cloud sync tools, and antivirus software can all cause CPU spikes that force higher buffer sizes.

7. Update your drivers and DAW. Check the manufacturer’s website for your audio interface driver updates. Also update your DAW to the latest version.

8. Test with a different USB port or cable. Faulty cables or USB hubs can cause latency issues. Connect your interface directly to the computer, not through a hub.

9. Check your computer’s power settings. On Windows, switch to High Performance power plan. On Mac, make sure the computer is plugged in and not in low-power mode.

10. Measure your actual roundtrip latency. Many DAWs have a built-in latency measurement tool. Run it to get your exact roundtrip number so you know what you are dealing with. If your roundtrip is above 15ms after all the above steps, you may need to consider a hardware upgrade.

If you have gone through all ten steps and still have unacceptable latency, the issue may be hardware-related. Older interfaces with slow converters, computers with insufficient RAM or outdated CPUs, and damaged cables can all contribute to persistent latency problems. In that case, upgrading your audio interface to a modern USB or Thunderbolt model will likely produce a noticeable improvement. Forum users consistently report roundtrip latency of 4 to 8ms on properly configured modern USB interfaces, which is well within the acceptable range for any type of recording.

FAQs

Wrapping Up: Take Control of Your Recording Latency

Latency recording does not have to be a constant source of frustration. Once you understand what causes it and how to reduce it when recording, you can take control of your monitoring path and perform naturally without fighting against delay. The key steps are lowering your buffer size, using the right drivers, enabling direct monitoring, and keeping plugins off your input chain during tracking.

Start with the simplest fix first: drop your buffer to 128 samples and check your driver settings. That alone resolves most latency issues. If you still experience delay, work through the troubleshooting checklist to identify the remaining causes. Your next step is to measure your roundtrip latency using your DAW’s built-in tools so you have a concrete number to work with and improve upon.