Fix it

Why people can hear themselves through your mic

When everyone on the call complains their own voices are coming back, the echo is being manufactured at your desk: your speakers play their voices into the room, and your open microphone sends the room right back. Headphones fix it in ten seconds. Here is why, plus the rarer software loops to check when headphones alone do not do it.

First, make sure this is the echo you have

This complaint always arrives secondhand. You sound normal to yourself, nothing on your screen looks wrong, and then someone in the Discord call says "we can hear ourselves through your mic." Everyone agrees except you, because you are the one person the loop skips: the echo rides your outgoing audio, so everyone hears their own words come back except the person causing it.

If it is the other way around, you hearing your own voice repeat while everyone else sounds fine, that is the mirror image of this problem, and the walkthrough on how to fix mic echo covers it. This page is for the version where they hear themselves and the finger points at your setup.

Your speakers are in their ears

The mechanism is embarrassingly physical. Discord plays your teammates' voices out of your speakers, into the air of your room. Your microphone does not know the difference between your voice and that air: it picks up everything in front of it, including the speakers. So a fraction of a second after your friend says something, your mic captures the speaker playback of it and Discord dutifully transmits it, and your friend hears their own sentence again, slightly late and slightly muffled. Multiply by everyone on the call.

Your mic sends their words back. The top row is a teammate's phrase coming out of your speakers; the bottom row is what your microphone transmits a moment later, the same words re-captured out of the air at bleed level, while you said nothing at all.

Two properties of this loop make it easy to confirm. It scales with your speaker volume, so if the complaints get worse when you turn the game up, this is your cause. And it happens only while your mic is transmitting, which is why voice-activity users get blamed more often than push-to-talk users: an always-open mic re-broadcasts the room full time.

The fix: put their voices in your ears, not your room

Wear headphones. Any headphones. The moment your teammates' voices play into your ears instead of into the room, there is no sound in the air for your microphone to re-capture, and the echo does not get quieter, it ceases to exist. This is the whole reason gamers wear headsets, and it is why every other fix on this page is second best. Ten-dollar wired earbuds end the problem as completely as a studio headset does.

If you have to stay on speakers

Sometimes headphones are genuinely not an option. You can shrink the loop until it is hard to hear, in this order:

Turn on echo cancellation. In Discord, open Settings, then Voice & Video, and enable Echo Cancellation. It estimates what your speakers are playing and subtracts it from your mic feed. It helps a lot, but it is a patch over a speaker problem, not a cure, and it degrades as volume goes up.
Lower the volume and move the mic. Bleed falls off fast with distance and level. Speakers quieter, microphone further from them and pointed away.
Switch to push-to-talk. Your mic only transmits while you hold the key, so the room is off the air the rest of the time. They may still catch a trace of themselves under your words, but the constant echo is gone.
Make sure Windows is not amplifying the loop. The per-device Listen to this device option plays your mic straight back out of your speakers, which re-feeds everything the mic catches into the room and can climb into a howl. Open the classic Sound control panel, go to the Recording tab, open your microphone's Listen tab, and uncheck it. The full dialog is pictured in the mic echo guide.

Echo with headphones on means a software loop

If they still hear themselves while your room is silent, the copy is not being made in the air. It is being made inside your PC: something is mixing the call's incoming audio into the signal Discord uses as your microphone. This happens to people who route audio through virtual devices, usually while setting up a music listen-along or a stream: desktop sound gets routed into the virtual mic, and the call itself lives inside desktop sound, so the call eats its own tail. A quick way to confirm it: open our mic test, stay silent, and play any sound on your PC. If the meter moves while your room is quiet, playback is leaking into your mic path in software.

Playback

HW 2

HW 3

BUS

Bus 1

Bus 2

Bus 3

3 hardware outs

3 buses

Ears only. The strip carrying the call's incoming voices routes to Playback, lit green, and every bus pill below it is dark, so their voices have no path into anything Discord could read as your microphone.

patchd is a virtual audio mixer, a piece of software that sends sound between your apps and devices, and it makes this loop something you can see instead of guess at. Every source is a strip, and every strip has a colored pill per destination: your hardware outputs and your buses (a bus is a virtual output other apps see as a microphone). Discord's incoming voices land on the fixed Communications strip. Your mic strip feeds Bus 1, and Discord selects Patchd Bus 1 as its input device.

The rule that makes this echo impossible is one unlit pill: the Communications strip routes to your headphones and never to the bus a call is using as its microphone. Audio that is never routed somewhere is never sent there, so the call cannot eat its own tail no matter what else you change. And if you want music in the call for a listen-along, you route the music strip to Bus 1 and leave Communications out of it, which is exactly the separation the stream-hearing-Discord fix uses in the other direction. If strips and buses are new to you, what is audio routing builds the mental model in five minutes.

The short version

They hear themselves because your mic hears your speakers. The loop is made of air, at your desk.
Headphones end it completely. No sound in the room, nothing to re-capture.
Stuck on speakers? Echo cancellation, lower volume, push-to-talk, and uncheck Windows's Listen to this device.
Echo despite headphones is a software loop. Find the route mixing the call's incoming audio into your mic feed and remove it.
In patchd the guarantee is visible. The Communications strip feeds your ears, its bus pills stay unlit, and the call can never re-capture itself.

patchd draws the whole signal path on screen, so "is the call feeding back into itself?" stops being a mystery and becomes a pill you can see is not lit. It is in development now. Join the waitlist and we will tell you the moment it is ready to install.