How to Fix Audio Echo in OBS Recording

An echo in OBS is never mysterious once you accept the single rule behind it:

The same sound reached your recording through two different paths.

That is the whole problem. Your job is not to hunt for an "echo setting", because there isn't one. Your job is to find the second path and close it.

There are four paths that commonly open by accident, and here is the useful part: they sound different from each other. You can tell which one you have before you open a single menu.

Diagnose it by ear first

Play back your recording and listen to the character of the echo:

That table is most of the work. Now go fix the one you have.

Fix 1: The same microphone is on two sources

This is the most common cause by a wide margin, and it produces the tight doubled voice.

OBS treats every audio input as an independent lane, and it is perfectly happy to let two lanes point at the same physical microphone. When that happens it records your voice twice. The two copies are captured a few milliseconds apart because they travel through different buffers, so they do not cancel out. They double.

There are three places a duplicate can hide, and you have to check all three:

A. The global devices. Open Settings, Audio, Global Audio Devices. Set Mic/Auxiliary Audio 2, 3 and 4 to Disabled. You almost certainly need only one microphone lane. Anything else is a second lane waiting to catch your voice.

B. A duplicate source in the scene. Look at your Sources list for an Audio Input Capture source. If you added one pointing at your Blue Yeti, and your global Mic/Aux is also set to the Blue Yeti, that is your echo. Both are live, both are recording you. Delete one. (Keep the scene source if you want per-scene control, keep the global one if you want it everywhere.)

C. Your webcam's built-in microphone. This is the sneaky one. When you add a Video Capture Device, OBS often enables its audio too, and every webcam has a pinhole mic in it. It picks up your voice at lower quality and slightly later than your real mic. Look at the Audio Mixer: if you see a meter bouncing that is labelled something other than Mic/Aux and Desktop Audio, that is it.

Double-click the Video Capture Device, scroll to the bottom of its properties, and either set Audio Output Mode to Capture audio only and mute it, or better, disable the device's audio entirely. Muting it in the mixer with the speaker icon also works.

The fastest way to find any duplicate: in the Audio Mixer, mute every source, then unmute them one at a time while you talk and watch the meters. Any source that jumps when you speak, other than your actual microphone, is a second path. This binary search takes thirty seconds and it beats reading a checklist.

Fix 2: The feedback loop

If the echo builds on itself into a howl or a squeal, this is not a duplicate source. This is a physical loop:

Your speakers play your voice. Your microphone hears your speakers. OBS sends it back to your speakers. Repeat, louder each time.

Every public-address system in the world has this failure mode, and the fix is the same as it is on a stage.

• Wear headphones. This ends the loop instantly and permanently, because your speakers are no longer in the room your mic is listening to. This is the correct fix and you should just do it.
• If you cannot use headphones, set your microphone's Audio Monitoring to Monitor Off in Advanced Audio Properties. That stops OBS from feeding your own voice back out of the speakers.
• Turn the speaker volume down and move the mic away from them. This raises the threshold, but it does not close the loop, and it will bite you again the moment you speak up.

Fix 3: The monitoring trap (fine live, doubled in the file)

This one is genuinely non-obvious, and it is the reason people swear their audio "sounded perfect while recording."

Here is the mechanism. On Windows, Desktop Audio is captured by loopback, meaning OBS records everything your playback device is playing. If you set your microphone to Monitor and Output, OBS plays your voice out to your monitoring device. Your monitoring device is a playback device. So Desktop Audio loopback captures your voice as part of the desktop mix.

Your voice is now in the file twice: once from the microphone source, and once via Desktop Audio, delayed by the monitoring round trip.

You do not hear it while recording, because you only hear one copy in your ears. It appears on playback.

The fix:

1. Open Advanced Audio Properties from the Audio Mixer's three-dot menu.
2. Find your microphone row, in the Audio Monitoring column.
3. Set it to Monitor Off, or to Monitor Only (mute output) if you genuinely need to hear yourself.

The rule of thumb: Monitor and Output on a microphone, while Desktop Audio is being captured, is an echo waiting to happen. If you need to hear yourself, use Monitor Only, or use your audio interface's hardware direct monitoring instead.

If the opposite is happening and you cannot hear anything at all in your headphones, that is the mirror-image problem, covered in OBS audio monitoring not working.

Fix 4: Sample rate mismatch and clock drift

If your audio is clean at the start and slides into a widening delay or a metallic ring over twenty or forty minutes, nothing is duplicated. Your clocks disagree.

Audio devices run on their own crystal oscillators. If Windows is feeding OBS at 48 kHz while OBS believes it is receiving 44.1 kHz, every second of audio is resampled slightly wrong, and the error accumulates. Long recordings drift apart. Short ones sound fine, which is why this hides so well in testing.

On Windows:

1. Press Windows + R, type mmsys.cpl, press Enter.
2. On the Recording tab, right-click your microphone, Properties, Advanced. Note the Default Format (for example 2 channel, 16 bit, 48000 Hz).
3. Do the same on the Playback tab for your speakers or headphones.
4. Set them both to the same rate. 48000 Hz is the right choice for video work.
5. In OBS, Settings, Audio, set Sample Rate to the same 48 kHz.

On macOS: open Audio MIDI Setup, select each device, and set the Format to 48000 Hz for all of them. Then match OBS.

All three numbers must agree: your input device, your output device, and OBS. One mismatch is enough to cause drift.

If your audio is not echoing but is simply landing ahead of or behind the picture, that is a different problem: OBS audio out of sync.

Fix 5: It might be reverb, not echo

If the sound is hollow and cavernous but your words are not repeating, you do not have a technical fault. You have a room.

Hard walls, bare floors, a desk under a window, and a microphone eighteen inches from your face all add up to audible reverb. No OBS setting removes it, and the noise-suppression filters will not touch it, because reverb is your own voice rather than noise.

What actually works, in order of effect:

• Get closer to the microphone. Six to eight inches. This is by far the biggest lever, because it improves the ratio of your direct voice to the reflected sound, and it costs nothing.
• Put soft things in the room. A rug, curtains, a bookshelf on the wall behind you, even a duvet on a stand off-camera.
• Speak across the mic, not into it, and stop recording in an empty room with a laptop mic.

A cheap microphone six inches away beats an expensive one three feet away, every time.

Verify the fix in sixty seconds

Do not fix four things at once and hope. Change one thing, then record a short take saying "one, two, three" with a clear pause after each number. Play it back.

The pauses are what matter. An echo is obvious in silence and easy to miss under a continuous voice. If the pauses are clean, you are done.

Or record without the mixing desk

Every one of these echoes exists because OBS is a broadcast mixer that trusts you to route your own audio. Two lanes on one mic, a monitor feed looping back through loopback capture, a sample rate you were never told to check: none of these are bugs. They are the cost of a tool that gives you the whole patch bay.

Cubix Capture does not hand you a patch bay. It captures your microphone and your system audio as two clean tracks, in sync, with no monitoring bus to loop back on itself and no global device slots to accidentally fill twice. It also handles the zooms and the cursor smoothing for you, so what you get when you press stop is a finished tutorial rather than an audio problem to debug.

Keep reading: OBS audio monitoring not working · OBS mic crackling and distorted audio · OBS audio out of sync · OBS desktop audio cuts out