Audio latency problems usually fall into a few predictable categories. Something in your signal chain is slow. The fix depends on which part: buffer settings, driver quality, wireless interference, OS overhead, or hardware limits. Most people can fix their latency problem in under an hour by following a diagnostic process.
The most common source of high latency is not your hardware—it’s a setting that’s easy to change.
Problem 1: Buffer Size Too Large
This is the #1 culprit. A 512-sample buffer at 44.1 kHz produces 11.6 ms of latency. That’s borderline acceptable for some workflows but terrible for others. If you’re recording an instrument while monitoring yourself and hearing a noticeable delay, your buffer is likely too high.
Quick fix: Lower your buffer size. In your DAW, find the audio settings and reduce buffer from 512 to 256 samples, then test. If that’s better, try 128. If you hear crackling or dropouts at lower buffers, your CPU can’t keep up—raise it until stable, then accept that limitation.
Most home studios find their sweet spot at 128–256 samples. Below that demands a powerful CPU. Above 512 sounds obviously laggy for music work.
Problem 2: Outdated or Generic Audio Drivers
This affects Windows users most. If you’re using onboard audio, your manufacturer’s driver might be old or poorly optimized. If you have an audio interface, an outdated driver can add 5–20 ms of unnecessary latency.
Quick fix on Windows: Go to your audio interface manufacturer’s support page and download the latest driver. If you’re using onboard audio (Realtek, Intel chipset), check Windows Update for driver updates, or download directly from the chipset manufacturer. After installing, restart your DAW and measure latency again.
If drivers are current and latency is still high on onboard audio, try ASIO4ALL (free), a third-party ASIO wrapper that bypasses the Windows audio mixer. This can cut onboard audio latency roughly in half.
On Mac: Audio drivers are more stable, but older interface drivers can still cause problems. Check your interface maker’s support page for the latest macOS-compatible driver, then restart.
Problem 3: Bluetooth Codec Mismatch
Bluetooth adds 40–300 ms of latency depending on codec. Standard Bluetooth (SBC) adds 150–300 ms. aptX adds 50–100 ms. aptX Low Latency reaches 32–40 ms. If you’re using older Bluetooth headphones or earbuds that default to SBC, you’re introducing serious delay.
Quick fix: Switch to wired headphones, a wired USB microphone, or a USB audio interface. Zero latency from wireless.
If you must use Bluetooth, choose devices that explicitly support aptX Low Latency. Check your device specs. If it doesn’t mention a low-latency codec, assume standard Bluetooth latency applies.
Also: Make sure your Bluetooth device is charged and in range. Low battery or interference can increase latency unpredictably.
Problem 4: DPC Latency Spikes (Windows)
DPC (Deferred Procedure Call) latency is the OS’s way of handling driver interrupts. When DPC latency spikes above 300 microseconds, your audio drivers don’t respond in time, causing clicks, pops, and dropouts. This isn’t quite the same as audio latency, but the result is the same: unusable audio.
Quick fix: Download LatencyMon (free, Windows only). Let it run for 1–2 minutes while you’re not doing audio-intensive work. Check if any drivers show high DPC latency.
Common culprits:
Network drivers (especially WiFi)
GPU drivers
USB hub drivers
Poorly optimized background services
If a driver is flagged, update it. If it’s a network driver and you’re on WiFi, switch to Ethernet if possible. If you can’t update the driver or identify the problem, disable the device temporarily and test whether audio improves.
Problem 5: Too Many Background Apps and Plugins
If you’ve optimized buffer size and drivers but latency is still high, your CPU might be overwhelmed. Running 30 tracks with heavy reverb plugins, Discord, Spotify, and Chrome in the background taxes the system.
Quick fix: Close unnecessary apps. Disable plugins you’re not actively using. In your DAW, freeze tracks with heavy plugin chains to bounce the processing to audio. Disable CPU-intensive effects during recording, then re-enable during mixing.
Check your DAW’s CPU meter. If it’s consistently above 70% at your working buffer size, your computer can’t handle that configuration. Either upgrade your computer, use fewer plugins, or accept a larger buffer size.
Problem 6: Sample Rate Mismatch
If your interface is set to 48 kHz but your DAW is running at 44.1 kHz, the OS has to resample audio in real-time. This adds latency and can cause sync issues.
Quick fix: Make sure your interface, your DAW, and your OS audio settings all use the same sample rate. If you don’t have a preference, pick 48 kHz (video standard) or 44.1 kHz (music standard) and lock everything to it.
You can verify this:
On Windows: Right-click speaker icon → Sound settings → Advanced → Check current sample rate
On Mac: System Settings → Sound → Check output format
In your DAW: Audio settings or Preferences → Check session sample rate
If they don’t match, change your DAW to match the interface, or change the interface to match your DAW. One setting change, often the fix.
Problem 7: Hardware Limitations
Some older computers, low-cost USB interfaces, or onboard audio simply can’t achieve sub-10 ms latency. This is a hardware limit, not a configuration problem.
If you’ve optimized buffer, drivers, and removed background apps but still can’t get below 30 ms, your hardware is the bottleneck.
Quick fix: Accept the limitation and work around it. Use direct hardware monitoring (if your interface supports it) so you monitor the input signal before it goes through the computer, eliminating software latency for monitoring. Or upgrade to a newer computer or interface.
Most USB 3.0+ interfaces can achieve 5–10 ms. Older USB 2.0 or cheap interfaces top out at 15–30 ms. If you’re stuck with old hardware, that’s the ceiling.
Problem 8: Network Latency (Video Calls and Streaming)
Zoom, Teams, Discord, and OBS all introduce network buffering. Even if your interface latency is perfect, the platform adds 50–200 ms to account for network jitter. Your audio latency in a video call isn’t your interface’s fault—it’s inherent to how VoIP works.
Quick fix: For video calls, there’s not much you can optimize. The platform controls the buffering. Switch from WiFi to Ethernet to reduce network jitter, which can improve stability but not reduce platform-imposed latency much.
For streaming, check if your streaming software (OBS, vMix) has audio delay settings. Some platforms let you dial in a few milliseconds of compensation.
The Real Diagnostic Process
Test your setup systematically:
- Measure baseline latency with our Sound Latency Test. Note the number.
- Check your DAW’s reported latency at your current buffer and sample rate. Compare against the formula (Buffer ÷ Sample Rate × 1000). If the reported number is 5+ ms higher than calculated, you have driver overhead.
- If latency is higher than expected, run LatencyMon (Windows) or check Activity Monitor (Mac) for CPU spikes or driver problems.
- Lower buffer size by one step. Test again. If it gets worse, raise it back.
- If still high, check your drivers are current.
- If still high, disable background apps one by one until latency improves. That app is the culprit.
- If audio becomes unstable (dropouts, clicks), raise buffer size until stable.
Dalton is an audio testing and latency optimization writer at SoundLatencyTest. He focuses on audio latency analysis, sound delay testing, recording performance, and audio troubleshooting tools for producers, gamers, streamers, musicians, and audio engineers.