Few things kill a good take faster than hearing your voice or guitar a fraction of a second after you actually perform it. That lag is latency, and learning to fix latency when recording is one of the highest-value skills a home recordist can pick up. The delay comes from the time your computer needs to convert incoming audio, process it, and send it back to your headphones. The good news: it is almost always solvable with settings you already have, no new gear required. This guide covers every fix in order of impact.
Why latency happens – and the fastest way to fix latency when recording
Your interface collects incoming audio into a small buffer before passing it to the CPU. A bigger buffer is easier on the processor but adds delay; a smaller buffer reacts faster but works the CPU harder and can cause crackles or dropouts. Buffer size is measured in samples, and it is the single biggest lever you control.
The immediate fix is to lower your buffer size while tracking. In your DAW’s audio settings, set it to 64 or 128 samples. At 44.1 kHz, 128 samples is roughly 3 ms of buffer delay – low enough that most players cannot feel it. Then, when you switch to mixing, raise the buffer back to 512 or 1024 samples so plugin-heavy sessions play back without glitches. This two-mode workflow – small buffer to record, large buffer to mix – solves the problem for the majority of home setups.
- Round-trip latency under about 10 ms feels natural to most performers.
- Above ~20-25 ms it becomes distracting, and singers especially start to fight it.
- Watch for crackling: if lowering the buffer introduces pops, you have gone too low for your CPU – step back up one setting.
Use the right driver
The driver connecting your interface to your DAW hugely affects latency. On Windows, generic drivers add a lot of delay – install your interface manufacturer’s ASIO driver instead, or use ASIO4ALL if the device lacks a dedicated one. Avoid MME/WDM/DirectSound for recording. On macOS, Core Audio is already low-latency and built in, so there is nothing extra to install; just select your interface as the audio device.
Make sure your DAW is pointed at the correct ASIO or Core Audio device, not the computer’s built-in soundcard. Using onboard audio is a common hidden cause of high, unfixable latency.
Direct monitoring: the zero-latency escape hatch
Even a perfectly tuned buffer has some delay because the signal makes a full round trip through the computer. The way to eliminate that entirely is direct (hardware) monitoring. Most interfaces route your input straight to the headphone output in analog, so you hear yourself with effectively zero latency while the DAW still records the signal.
Look for a “Direct Monitor” switch or a monitor-balance knob on your interface, or use its companion software mixer (Focusrite Control, UA Console, Audient’s mixer app). The trade-off: you hear your dry signal without DAW effects like reverb. When tracking through direct monitoring, mute the DAW’s input monitoring for that track – otherwise you hear both the instant hardware signal and the delayed software signal at once, producing a doubled, flangy echo that sounds worse than plain latency.
Deeper fixes when latency persists
If low buffers still feel laggy or your CPU cannot cope, work through these:
- Raise the sample rate carefully. Recording at 96 kHz halves buffer time versus 44.1 kHz for the same sample count, but it also doubles CPU load. 48 kHz is a good balance for most home projects.
- Freeze or disable heavy plugins while tracking. CPU-hungry reverbs and amp sims force you into higher buffers. Bounce or freeze finished tracks so the processor has room for a small buffer on the part you are recording.
- Bypass wireless and Bluetooth. Bluetooth headphones add massive, uneven latency – always monitor through wired headphones plugged into the interface.
- Close background apps and, on Windows, disable power-saving CPU throttling so the processor runs at full clock while recording.
- Compensate on playback, not input. Most DAWs automatically apply plugin delay compensation for mixing, so latency you notice while performing is almost always a monitoring issue, not a recording-accuracy issue – the recorded file lands in time regardless.
A reliable tracking setup
Put it together into a repeatable routine: select your ASIO or Core Audio interface driver, set the buffer to 128 samples, enable direct monitoring on the interface, mute DAW input monitoring, and use wired headphones. With that configuration, the vast majority of home studios record with imperceptible delay. Save mixing for a separate pass with the buffer raised to 512-1024 samples so your effects run cleanly.
Latency is a solved problem once you understand that it is about monitoring, not about the recording itself – your takes land in perfect time even when the headphone feed lags. If you are also chasing clean levels and placement, our guides on recording studio-quality vocals at home and the free calculators in our audio tools hub pair well with this workflow. And if the delay you hear turns out to be room echo rather than digital latency, see how to remove echo when recording.
