To reduce latency recording at home, the two biggest levers are lowering your audio buffer size and using direct (hardware) monitoring so you hear yourself before the signal even reaches your computer. Combine those with good drivers and a tuned-up system and you can monitor with delay so small it feels instant.
Quick answer: Lower the buffer size to 64 or 128 samples while tracking, enable direct monitoring on your interface, use ASIO (Windows) or Core Audio (Mac) drivers, and free up CPU by closing apps and disabling heavy plugins on record-enabled tracks.
Why latency happens
Latency is the short delay between making a sound and hearing it back through your DAW. The signal has to be converted to digital, buffered, processed, buffered again, and converted back to analogue. Each stage adds time. When monitoring through software, this round trip can be large enough that singers and players hear themselves lagging, which ruins timing. For the full background, see what is audio latency.
1. Lower your buffer size
The buffer size is your main control. A smaller buffer processes audio in smaller, more frequent chunks, which cuts delay. While recording, drop to 64 or 128 samples. If you hear clicks or dropouts, step up to 256. Learn how the trade-off works in what is buffer size. Where to set it:
- GarageBand: Settings, then the Audio/MIDI tab, plus your interface’s control panel.
- Audacity: Preferences, then Devices, adjust buffer length.
- FL Studio: Options, then Audio Settings, set the Buffer length slider low for tracking.
2. Use direct monitoring
The single most effective fix is direct monitoring: your audio interface routes the input signal straight to your headphones in hardware, bypassing the computer entirely, so you hear yourself with effectively zero delay. Flip the monitor switch (often a Direct/Input vs Playback control) on your interface and mute the input track’s software monitoring in your DAW so you do not hear it twice. If you are new to the concept, our guide to what direct monitoring is walks through exactly how it works. This lets you keep a high buffer for stable playback while still tracking comfortably. Most modern interfaces support it — see our audio interfaces hub.
3. Use the right drivers
Drivers matter enormously on Windows. Use the manufacturer’s ASIO driver for your interface rather than generic Windows audio, which carries high latency. On macOS, Core Audio is already low-latency and needs no extra driver. Keep your interface’s drivers and firmware up to date, and select the dedicated driver in your DAW’s audio settings rather than the built-in option.
4. Free up your CPU
A struggling CPU forces you into a larger buffer, which raises latency. Lighten the load so you can track at a small buffer without glitches:
- Close web browsers and background apps.
- Bypass or remove heavy plugins (reverbs, convolution, virtual instruments) on record-enabled tracks while you track.
- Freeze or bounce finished tracks so they no longer tax the processor.
- Disable wireless and power-saving features that can cause audio interruptions on laptops.
- Raise the buffer again when you switch from tracking to mixing.
5. Set monitoring up cleanly
Once latency is low, make sure your monitoring chain is tidy. Monitor on closed-back headphones while tracking to avoid bleed, set sensible levels with good gain staging, and confirm your interface is wired correctly using how to set up an audio interface. If you only ever hear a slight delay on plugin-heavy sessions, switch to direct monitoring and the problem disappears.
How to choose the right approach for your session
There is no single buffer setting that suits every moment of a project, so it helps to think in two modes: a tracking mode and a mixing mode. The smart workflow is to switch between them rather than hunt for one compromise value.
While you are tracking, prioritise low delay. Set a small buffer (64 or 128 samples), strip the record-enabled track of anything heavy, and lean on direct monitoring wherever your interface offers it. If you are recording a vocal or an instrument that depends on tight timing, hardware monitoring is almost always the better answer than chasing an ever-smaller buffer, because it removes the round trip entirely instead of just shortening it.
Once recording is finished and you move into editing and mixing, latency stops mattering. Raise the buffer to 512 or 1024 samples so your computer can run every plugin and virtual instrument without dropouts. The larger delay is irrelevant when you are no longer performing in real time, and the extra headroom keeps playback rock solid. Building this two-mode habit means you stop fighting your system and let each stage of the project use the setting that suits it.
Common latency mistakes to avoid
Most home-recording latency problems come down to a handful of avoidable errors. Watch out for these:
- Double monitoring. Leaving software monitoring on while direct monitoring is engaged means you hear two copies of yourself, one delayed. Mute the input track in the DAW so only the hardware path reaches your ears.
- Using the wrong driver on Windows. Sticking with the generic Windows driver instead of the dedicated ASIO driver is the most common cause of stubborn latency. Always select your interface’s own driver in the DAW.
- Tracking with a heavy plugin chain. Loading reverbs, amp sims or convolution on a record-enabled track forces a bigger buffer. Record dry and add those effects later.
- Forgetting to raise the buffer for mixing. A tiny buffer that was perfect for tracking will glitch badly once you stack plugins. Step it back up before you start the mix.
- Running everything else at once. Browsers, video calls and sync clients quietly steal CPU and create the dropouts that tempt you into a larger buffer. Close them before a session.
Quick checklist
- Drop buffer size to 64 or 128 samples for tracking.
- Enable direct monitoring and mute software monitoring on the input track.
- Use ASIO (Windows) or Core Audio (Mac) drivers, kept up to date.
- Close background apps and bypass heavy plugins while recording.
- Raise the buffer back up when you move to mixing.
Frequently asked questions
What is an acceptable latency for recording?
Round-trip latency under roughly 10 milliseconds usually feels instant when monitoring a performance. Above that, performers begin to notice a lag. Direct monitoring removes the issue entirely because you hear yourself in hardware.
Will lowering the buffer size hurt my recording quality?
No. Buffer size only affects latency and CPU load, not the fidelity of the recorded audio. The captured file sounds the same whether you tracked at a low or high buffer.
Why do I still hear delay with direct monitoring on?
You are probably also monitoring through the DAW, so you hear both paths. Mute the software input monitoring on the record-enabled track so only the zero-latency hardware signal reaches your headphones.
Does a faster computer reduce latency?
Indirectly, yes. A faster CPU and quick storage let you run a smaller buffer without clicks and dropouts, so you can monitor with less delay. But no amount of computing power beats direct hardware monitoring, which sidesteps the round trip altogether.
Does using a USB hub or long cables add latency?
Cable length makes no audible difference, but a shared or low-quality USB hub can cause data interruptions that force you into a larger buffer. Where possible, connect your interface directly to a port on the computer rather than through a daisy-chained hub, and if you do need one, pick from the best USB hubs for audio interfaces.
