What microphone latency is and why you should measure it

Microphone latency is the delay between the moment sound enters your mic and the moment your computer processes it. If you stream, record, or use video calls, even a small delay can throw off your timing — you'll hear yourself a fraction of a second late, or your audio will drift out of sync with video.

Latency comes from three places: your microphone hardware itself, your audio interface or USB hub, and your operating system's audio drivers. Most people can't feel delays under 20 milliseconds, but anything above 50 milliseconds becomes noticeable. If you're monitoring your own voice while recording or streaming, even 30 milliseconds can feel wrong.

You don't need special software to measure it. The method depends on what equipment you have, but the core idea is the same: send a sound into your mic, measure how long it takes to come back out, and do the math.

Key Takeaways

  • Latency is the delay between sound entering your mic and your computer processing it, measured in milliseconds.
  • The simplest test uses a phone, a quiet room, and a stopwatch to measure the round-trip time of your own voice.
  • For more precise results, use Audacity (free, on Windows and Mac) to record a click, play it back into your mic, and measure the gap.
  • USB microphones typically have 5 to 15 milliseconds of latency; audio interfaces with XLR mics can be lower or higher depending on driver quality.
  • If latency bothers you during recording or streaming, direct monitoring (hearing the mic signal without going through your computer) is the fastest fix.

The phone and stopwatch method

This is the quickest way to get a rough number. You'll need a quiet room, your phone's stopwatch app, and a way to hear your mic output — usually headphones plugged into your computer.

Open your recording software (Audacity, OBS, or even your phone's voice memo app) and put on headphones. Start the stopwatch on your phone, speak a word like "now" into the mic, and stop the timer the instant you hear it come back through the headphones. That's your round-trip latency. Divide by two to get the one-way delay your mic adds.

This method is rough because human reaction time adds error, but it's fast enough to tell you if something is obviously wrong. If you're getting 200 milliseconds round-trip, your latency is around 100 milliseconds one-way — that's a problem worth investigating.

Using Audacity to measure with a click track

Audacity is a free audio editor available for Windows, Mac, and Linux. This method is more precise because it removes human reaction time from the equation.

First, generate a short click or tone in Audacity. Go to Generate > Tone, set it to 1000 Hz, and make it 0.5 seconds long. Export this as a WAV file to your desktop. Now set up Audacity to record from your microphone, put on headphones, and play the tone file through your speakers while Audacity records. The tone will loop back into your mic, and Audacity will capture both the original and the delayed version.

Stop recording and zoom in on the waveform. You'll see two peaks — one from the original tone playing through your speakers, and one from that same tone coming back through your mic. Measure the distance between them in samples. Audacity shows the sample rate at the bottom of the window (usually 44100 or 48000 Hz). Divide the number of samples by your sample rate to get latency in seconds, then multiply by 1000 to convert to milliseconds.

Example: if the peaks are 882 samples apart and your sample rate is 44100 Hz, your latency is (882 ÷ 44100) × 1000 = 20 milliseconds.

Testing with an audio interface or USB hub

If you use an external audio interface (like a Focusrite Scarlett or PreSonus interface) or a USB hub between your mic and computer, latency can hide in the driver or the hub itself. The click track method still works, but you need to isolate which part is causing the delay.

First, test your mic plugged directly into your computer's USB port. Then test it through the hub or interface. If the latency jumps significantly, the hub or interface driver is the culprit. Check the manufacturer's website for driver updates — outdated drivers are a common source of unnecessary latency.

Some audio interfaces have a direct monitoring button or knob. This lets you hear your mic signal without sending it through your computer first, which eliminates latency entirely for monitoring purposes. If your interface has this feature, use it during recording or streaming to avoid hearing yourself delayed.

What to do if latency is too high

If your measurements show latency above 50 milliseconds and it's bothering you, start with the easiest fixes. Update your audio drivers — go to your computer manufacturer's website or the audio interface maker's site and download the latest version. Restart your computer after installing.

If you're using a USB hub, try plugging your mic directly into your computer instead. USB hubs can add latency, especially cheap or unpowered ones. If that's not possible, switch to a powered hub rated for audio devices.

Lower your buffer size in your recording software. In Audacity, go to Transport > Transport Options and look for buffer settings. In OBS, check Settings > Audio. A smaller buffer means your computer processes audio more often, which reduces latency — but it also uses more CPU power. If your computer starts crackling or dropping audio, increase the buffer back up.

If none of that helps and you're streaming or recording, use direct monitoring if your mic or interface supports it. This bypasses your computer's audio processing entirely for the signal you hear, so you'll never hear yourself delayed even if the recorded audio has latency.

Why your measurements might vary

Latency isn't always the same number twice. Your computer's CPU load, what other programs are running, and even the temperature of your equipment can shift latency by a few milliseconds. Take three measurements and average them instead of trusting a single test.

Also, the latency you measure includes both the microphone hardware and your computer's audio system. A USB microphone's latency is mostly fixed by the hardware, but a microphone plugged into an audio interface can vary depending on your driver version and buffer settings. If you change either one, measure again.

Frequently Asked Questions

Is 20 milliseconds of latency bad?

No. Most people can't perceive latency below 20 to 30 milliseconds. If you're streaming or recording and you're not hearing yourself delayed or noticing sync issues with video, your latency is fine. Only measure if you're actually experiencing a problem.

Why does my latency change every time I measure it?

Small variations are normal — your computer's CPU load shifts, background processes wake up, and other factors add a few milliseconds of noise to each measurement. If your latency swings wildly (like 15 milliseconds one time and 80 the next), your USB hub or driver might be unstable. Try a different USB port or update your audio drivers.

Can I reduce latency on a USB microphone?

A little. Update the microphone's firmware if the manufacturer offers it, and lower your buffer size in your recording software. But most USB microphone latency is baked into the hardware. If it's a problem, switching to an audio interface with direct monitoring is the real solution.

What's the difference between latency and delay?

Latency is the hardware and software delay built into your system. Delay is an effect you add intentionally in audio software. They're measured the same way, but latency is something you measure to diagnose problems, while delay is something you use creatively.

Do I need to measure latency if I'm just recording voice memos?

No. Latency only matters if you're monitoring your own signal in real time — hearing yourself while you record or stream. If you just hit record and speak without listening to yourself, latency doesn't affect the final file.