Fix it
How to fix mic echo
Mic echo is almost always a signal path problem, not a broken microphone. Once you know the four things that cause it, each one takes about a minute to fix.
First, figure out which echo you have
People say echo to mean a few different things: a hollow room sound, your own voice repeating back at you, or the person on the call hearing themselves. These have different causes, so the fix depends on who hears the echo and when. Ask yourself two quick questions. Do you hear it, or does the other person? And does it happen only on calls, or also when you record yourself alone?
In almost every case the culprit is one of four things: speakers bleeding into the mic, two audio paths carrying your voice at once, a routing loop that feeds a source back into itself, or a stray Windows listen setting. Work through them in order and you will land on the right one.
Cause 1: your speakers are bleeding into your mic
This is the most common echo of all, and it only happens on calls. Your speakers play the other person's voice, your microphone picks that voice back up out of the air, and the call sends it straight back to them. They hear themselves a fraction of a second late. That is the echo.
The fix is physical, and it is quick:
- Use headphones.The single most reliable fix. If the other person's voice never leaves your ears, your mic cannot pick it up. Ninety percent of call echo disappears the moment someone puts on headphones.
- Turn your speaker volume down if headphones are not an option, and move the mic further from the speakers.
- Enable echo cancellation in your call app if it has it. It helps, but it is a patch over a speaker problem, not a cure.
If you hear echo and you are the one on speakers, it is usually the other end causing it. Politely ask them to switch to headphones too.
Cause 2: your voice is going out on two paths at once
This one produces a doubled or slightly delayed version of your own voice, and it is a wiring problem rather than a room problem. It happens when two things are carrying your microphone at the same time: for example, two apps are both set to use your mic and both are transmitting, or your voice is reaching a call through two different virtual devices. The two copies arrive a hair apart and you get an echoey, doubled sound.
- Close any app you are not actively using that also listens to your mic. A background call app, a second recorder, or a game overlay can all quietly hold the microphone open.
- Make sure each app points at one microphone source, not the raw mic in one place and a processed version of it in another.
- If you use a mixer or voice tool, confirm your voice reaches each destination exactly once. Sending both the clean mic and the mixer output into the same call is a classic way to double yourself.
Cause 3: a routing loop feeds a source back into itself
This is the echo that feels impossible to track down, because nothing is obviously wrong. It happens when a signal path bends back on itself: a source is routed to a destination that, somewhere down the line, returns to that same source. The audio circles, and each pass through the loop adds another delayed repeat. In its worst form it builds into a rising howl of feedback.
Loops come from tangled routing, which is exactly why it helps to understand what audio routing actually is before you start pulling things apart. The fix is to trace the path and find the one connection that closes the circle:
- Pick your microphone and follow where it goes. Note every output and virtual device it feeds.
- For each of those destinations, check whether anything sends it back toward your mic's input. That returning connection is your loop.
- Remove the one route that closes the circle. A source should never feed a destination that comes back to it.
Each trip around the circle adds another delayed repeat. In patchd that returning route is a lit coral line, so you can see the loop and unclick the one connection that closes it.
Cause 4: a stray "listen to this device" setting
Windows has a per-device option called Listen to this device, which plays a microphone straight out of your speakers or headphones. It is useful now and then, but left on by accident it creates a live loop between your mic and your speakers, which is echo cause 1 and cause 3 at the same time.
- Open Sound settings, then the classic Sound control panel.
- Go to the Recording tab, open your microphone, and click the Listen tab.
- Uncheck Listen to this device unless you deliberately turned it on.
Want to confirm the setting stuck? Our mic test lets you check what your microphone is actually sending without opening a call.
How patchd makes echo obvious
Most of the fixes above are detective work because Windows hides the signal path from you. You cannot see which app is holding your mic or which route bends back on itself, so you guess. patchd is a virtual audio mixer, a piece of software that sends sound between your apps and devices, and it draws the whole path on screen. Every input is a strip on the left. Every destination sits on the right: your headphones, your speakers, and virtual outputs (a bus, which is a virtual output other apps see as a microphone). Each destination owns one fixed color. You send a source somewhere by clicking a colored pill on its strip, and an active connection lights up in that color.
That visibility is what kills routing loops. When each connection is a lit line in a fixed color, a source feeding back into itself stops being an invisible mystery and becomes something you can literally look at and unclick. Because you build each destination as its own bus, you also send your voice to a call exactly once, which rules out the doubled-path echo from cause 2. When another app needs your processed voice, you select the patchd bus as your microphone in Discord or OBS, one clean feed, no stray copies. If per-app control is new to you, the walkthrough on how to route audio per app on Windows shows how the strips and buses fit together.
A noise gate for the leftover room echo
Once the wiring is clean, you may still hear a faint hollowness from a reflective room, the soft reflections that a bare wall and hard floor throw back at your mic. That is not a routing bug; it is your space. A noise gate handles it. It mutes your channel the instant you stop talking, so the room tone and its reflections never make it into the mix, then opens again the moment you speak. In patchd the noise gate is a free effect in the effects rack on every channel, and it runs live as you talk. Pair it with the steps in how to reduce background noise on your mic and a boxy, echoey room starts to sound like a clean, close mic.
The short version
- Wear headphones. This alone fixes most call echo.
- Close extra apps that are holding your microphone open.
- Trace your routing and remove any path that loops back to its own source.
- Turn offWindows "Listen to this device" if you did not mean to enable it.
- Add a noise gate for whatever room echo is left.
patchd puts all of this in one place: a visual mixer where loops are easy to spot, a real effects rack with a free noise gate on every channel, and color-coded routing so you always know where your voice is going. It is in development now. Join the waitlist and we will tell you the moment it is ready to install.