Start here
Why do I hear echo on calls?
You say something. Half a second later, a thin copy of your own voice comes back at you. It's distracting, it derails your sentences, and — here's the part almost nobody tells you — it's usually not your fault. This page explains where that second voice comes from, why the person who hears the echo is rarely the person causing it, and how to trace it to the right device without turning the call into an IT session.
The one rule that changes everything: for you to hear your own voice back, it has to be re-transmitted to you — which means it went out of a speaker and into a microphone somewhere else on the call. If you hear the echo, the loop is almost always on another participant's end. If they complain about echo, the loop is probably yours.
How the loop forms
Every call echo is the same five-step circuit, no matter the app:
- Your voice leaves your microphone and travels to the other side.
- It plays out of their speakers — laptop speakers, external speakers, a phone on speakerphone.
- Their microphone picks up what their speakers just played.
- Their device transmits that pickup right back into the call, as if it were their speech.
- It arrives at your ears a network-round-trip later — your own voice, delayed and hollow.
The delay is why echo is so disorienting: your brain expects instant feedback from speaking, and a 300–800 ms late copy collides with your next sentence. (A copy with no delay is a different, much gentler problem — sidetone or mic monitoring — and a copy that snowballs into a screech is feedback. Late copy = echo. Instant copy = sidetone. Rising howl = feedback. This page is about the late copy.)
In theory, step 4 never happens: every calling app runs an acoustic echo canceller (AEC) whose whole job is to recognize "what the mic just heard is what the speaker just played" and subtract it. Echo you can hear means someone's AEC lost that fight — because their speakers were loud, their room reflective, their audio path rerouted, or their hardware weird enough to fall outside the canceller's model. The gory details are in our AEC explainer; you don't need them to fix this.
Diagnose by symptom
1. You hear yourself; others are fine
The loop is on another participant's device. On a two-person call, it's the other person — their speakers are feeding their mic. Say it kindly and concretely: "I'm getting my own voice back, which usually means your mic is picking up your speakers — could you drop your speaker volume a bit or grab earbuds?" Volume down often fixes it on the spot, because AEC that was almost keeping up suddenly can. On a group call, don't guess — use the mute-in-turn method to find the one device doing it.
2. Others hear themselves; you're accused
Mirror image: your speakers are feeding your mic. You won't hear anything wrong yourself, which is why the accusation feels baffling. Believe them anyway. Turn your speaker volume down, move your mic away from your speakers or laptop-speaker grilles, and check that your calling app is using its real AEC — if you've routed audio through a virtual device or mixer, the canceller may never see the loop (full fix list here). If you need speakers at volume, that's the exact case where a dedicated echo cancellation layer earns its keep.
3. Everyone hears everyone, chaos
Almost always two devices on the same call in the same physical room — a laptop and a phone both joined, or two colleagues at adjacent desks, each with live mic and speakers. Sound ping-pongs between them faster than any canceller can model. One of the devices leaves the call, or mutes mic and speaker both. This is also the standard failure when someone joins a meeting from a laptop while dialed in by phone for audio.
4. Echo only started recently
Same setup, new echo? Something changed the audio path — an app update, a new virtual device, a changed default output, a Bluetooth device that reconnected in a different mode. We keep a checklist for exactly this in "Echo suddenly started".
If the loop turns out to be yours
Work through these in order; each step removes a cause:
- Drop output volume. Echo energy scales with how loud your speakers hit your mic. This alone fixes a startling share of cases.
- Increase mic-to-speaker distance. A mic sitting in front of laptop speaker grilles, or beside a desktop speaker, is being force-fed the far side's voice.
- Kill duplicate audio paths. One app in a call at a time; no phone-plus-laptop double joins; browser tab and desktop app not both live.
- Check for rerouting. Virtual mics, mixers, "listen to this device," loopback tools — anything that moves audio around can smuggle output back into input past the AEC.
- Add a cancellation layer if the above isn't enough. If your work genuinely requires open speakers at volume, built-in AEC may be out of its depth — that's the case for dedicated echo cancellation software, and the free tiers mean testing costs nothing.
And yes: headphones on either end break the loop completely, because there's no speaker output for a mic to catch. We're a software site and you don't need new gear — any wired earbuds in a drawer already do the job on the side that wears them. If headphones aren't an option for you, the speakers-only playbook is written for your exact situation, and the no-muting guide covers keeping a whole group audible without the mute hammer.