You hit record, play a note, and hear it back a fraction of a second later. That tiny delay is enough to wreck a vocal take, throw off a drummer, or make MIDI performance feel disconnected. If you want to know how to fix audio latency, the good news is that most cases come down to a short list of settings, driver choices, and monitoring decisions you can correct quickly.
Latency is simply the time it takes for audio to travel through your system. In a home studio, that path usually includes your interface, your computer, your DAW, and any plugins sitting on the track or master bus. Some latency is normal. The problem starts when the delay becomes noticeable enough to affect timing, performance, or confidence.
The first thing to understand is that not all latency is the same. There is input latency, which affects what happens when you sing or play into the system. There is output latency, which affects what you hear coming back. Then there is plugin delay compensation, which can make playback line up correctly while still making live recording feel slow. If you treat all three like the same issue, you can waste a lot of time changing the wrong setting.
How to fix audio latency at the source
Start with your audio driver. On Windows, the right answer for serious recording is usually ASIO. If you are using MME, DirectSound, or WASAPI inside a pro DAW, that alone may be the reason your system feels sluggish. On Mac, Core Audio is the standard, but you still need to make sure your interface is selected correctly and not running through an aggregate setup that adds complications.
Next, check your buffer size. This is the most common place to fix audio latency fast. A large buffer gives your computer more time to process audio, which helps stability during mixing, but it also increases delay while recording. A smaller buffer reduces latency, but it asks more of your CPU.
For tracking vocals, guitar, or MIDI instruments, a buffer of 32, 64, or 128 samples is usually where you want to start. If your session clicks, pops, or drops out at those settings, move up gradually. If you are mixing and not recording in real time, 256, 512, or higher may be perfectly fine. This is where context matters. The best buffer for recording is often not the best buffer for mixing.
Sample rate also affects latency, though not as dramatically as people sometimes expect. Running at 96 kHz can reduce round-trip latency compared to 44.1 kHz at the same buffer size, but it also increases CPU load. That trade-off is real. If your computer is already struggling, a higher sample rate may make the whole session less stable, not more playable.
Check your monitoring path before anything else
A lot of users think they have a driver problem when they actually have a monitoring problem. If you are hearing both the direct signal from your interface and the delayed return from the DAW at the same time, it will sound like latency even if your settings are decent.
Many interfaces offer direct monitoring. That means you hear your input before it travels through the DAW. For vocals and live instruments, this can be the fastest practical solution. The downside is that you may not hear software-based effects the way you want while performing. If the singer needs reverb from the DAW or the guitarist is playing through an amp sim, direct monitoring alone may not solve the whole problem.
In that case, decide which monitoring path you want and commit to it. Either monitor through the interface with near-zero delay, or monitor through the DAW with a low buffer and a light plugin load. Using both usually creates confusion.
Plugins are often the real problem
This is where many sessions go sideways. You can have a solid interface, the correct driver, and a reasonable buffer, then drop a linear phase EQ, lookahead limiter, oversampling processor, or heavy mastering chain on the master bus and suddenly recording feels terrible.
Some plugins introduce significant latency because of how they process audio. Mastering plugins are frequent offenders. So are noise reduction tools, convolution reverbs, and certain tape or analog emulations running in high-quality modes. Delay compensation keeps playback aligned, but it cannot make live input feel instant when the system is waiting on a plugin that needs extra processing time.
If your session only feels delayed after you start mixing, disable high-latency plugins while tracking. Bypass the mastering chain. Turn off oversampling where possible. Freeze or print instrument tracks that are eating CPU. Most DAWs also offer low-latency monitoring modes that temporarily bypass delay-inducing plugins on record-enabled tracks or throughout the session.
DAW settings that matter more than people think
Every major DAW handles low-latency recording a little differently. In Pro Tools, Studio One, Logic Pro, Cubase, and Ableton Live, there are monitoring and compensation settings that can help or hurt depending on how the session is configured.
Look for options related to low-latency monitoring, input monitoring, plugin delay compensation, dropout protection, or live mode. These are not magic buttons, but they can make a measurable difference. The catch is that one helpful setting can interfere with another. For example, a protection mode that improves playback stability may add enough buffering to make live playing feel disconnected.
This is why generic advice only gets you so far. Two users can have the same DAW and completely different latency behavior because one is monitoring through the interface, the other is monitoring through the DAW, and both are running different plugins and hardware drivers.
Hardware and system issues that cause hidden latency
If your settings look right and latency is still bad, step back and look at the full system. USB hubs are a common problem. Many audio interfaces work best when connected directly to the computer instead of through a shared hub. Power-saving settings can also interfere with real-time audio performance, especially on laptops.
On Windows, check that your computer is set to a high-performance power plan and that USB power-saving features are not throttling devices. On Mac, make sure background system tasks are not pushing the machine harder than necessary during a session. Wireless services, cloud syncing, browser tabs, and video apps may not seem related to audio latency, but they absolutely affect real-time performance.
Your interface driver and firmware also matter. An outdated driver can cause poor low-buffer performance even on a fast machine. And not all interfaces perform equally. Some are simply better at delivering low round-trip latency than others. That does not always mean you need new hardware, but it does mean the interface itself may be part of the limit.
How to fix audio latency when recording MIDI
MIDI adds another layer because you are often dealing with both performance timing and virtual instrument response. If a MIDI keyboard feels late, the issue may still be audio buffer size, because the actual delay is happening in the instrument output, not in the MIDI message itself.
Start by lowering the buffer and testing with a simple instrument patch. Then compare that to a heavier preset with multiple layers or effects. Some virtual instruments respond instantly, while others take more processing time. If one piano patch feels tight and another feels slow, the plugin is telling you something.
Also check whether your DAW has track delay, external instrument compensation, or MIDI offset settings engaged. These can be useful for correction, but they can also create confusion if they were changed for a previous setup and forgotten.
A practical workflow that keeps latency under control
The fastest way to stay productive is to treat recording and mixing as different phases. During tracking, run the session lean. Keep the buffer low, disable unnecessary plugins, and use direct monitoring or low-latency DAW monitoring. During mixing, raise the buffer and bring the heavy processing back online.
That may sound obvious, but a lot of frustration comes from trying to record through a full mix session loaded with CPU-heavy plugins and then wondering why the vocal feels late. Your DAW can do many things at once, but real-time performance always has limits.
If you are moving between sessions often, save templates for tracking and mixing separately. That one change can eliminate a lot of repeated troubleshooting.
When the problem is not your settings
Sometimes the real issue is that the setup is too complicated for a quick guess. Maybe you are running an interface with external DSP, a hybrid monitoring path, multiple cue mixes, and a DAW template that was built months ago. Maybe the latency only appears in one session, with one artist, using one plugin chain. That is exactly where people lose hours chasing forum advice that does not match their rig.
If you are serious about getting results, this is the point where direct one-on-one help beats another night of trial and error. A real engineer can look at your session, your interface, your routing, and your DAW settings in real time and tell you what is actually causing the delay.
Audio latency is frustrating because it breaks the connection between performance and playback. But it is usually fixable. When you approach it methodically – driver first, buffer second, monitoring path third, plugins fourth – the problem gets smaller fast, and the session starts feeling musical again.