Skip to content

The playbook

How to fix echo without muting anyone

By the Echobreak team Updated 2026-09-20

"Everyone mute unless you're speaking" is the duct tape of call audio. It stops the echo, sure — the way unplugging a smoke alarm stops the beeping. The conversation turns into a walkie-talkie session, spontaneity dies waiting for the unmute key, and the actual loop causing the echo is still there, ready for the next meeting. Muting treats a group as the problem when the problem is always one device. This page is the alternative: kill the echo, keep everyone's mic live.

Why muting "works": echo needs a circuit — far voice → speaker → mic → back to far side. Muting everyone-but-the-speaker breaks the circuit by amputating every return path at once. Effective, and massively overkill: only one of those paths was looping. Find it and you can leave the other seven mics alone.

Step one: stop treating echo as weather

Echo isn't ambient misfortune that descends on meetings; it's a specific device re-transmitting sound, every time. The whole no-muting strategy rests on that fact, because a problem with an address can be fixed at the address. Two minutes of the mute-in-turn method — briefly muting participants one at a time until the echo dies — gives you the address. (Note the irony budget: you mute people once, for seconds, diagnostically, so nobody has to live muted for the next hour.)

If you're on a two-person call, skip the hunt: whoever hears the echo isn't causing it, so the loop is on the other end — here's that logic in full.

Step two: fix the device you found

In descending order of frequency, the culprit device needs one of these:

  1. Speaker volume down. The echo canceller on that device was probably almost coping. Echo strength scales with how hard the speakers hit the mic; a one-third volume cut is often the whole fix. Loud speakers also distort, which breaks cancellation in a deeper way — explained here.
  2. Mic moved away from the speakers. A webcam mic aimed over speaker grilles, a desk mic parked beside a speaker — small repositioning, large effect. Distance is free attenuation.
  3. Duplicate device evicted. Two joined devices in one room (laptop + phone, or two colleagues side by side) is the unfixable-by-settings case: one device leaves the call or goes fully deaf-and-dumb (mic and speaker off). No canceller models a loop through a second machine's call session.
  4. Audio path un-rerouted. If the culprit recently installed a mixer, virtual device, or loopback tool, the app's canceller may be subtracting against a signal that no longer matches reality. Bypass the routing for calls, or see echo that suddenly started.
  5. Headphones, if they're willing. Any earbuds end that device's loop outright. We're software people, but we don't gatekeep the one fix that needs no software. If they can't or won't, the next step exists.

Step three: reinforce the canceller where life demands speakers

Some setups legitimately need open speakers at volume — shared viewing, accessibility needs, people who can't wear headphones all day. That's not user error; it's just a harder job than built-in cancellation was tuned for. The fix is a dedicated cancellation layer on the speaker-heavy device: a virtual-mic tool that models and subtracts the loop system-wide, before any app is involved. Our software guide compares the field honestly (including the free options); the short version is that Krisp's acoustic echo cancellation is built for exactly this, and NVIDIA Broadcast covers the room-ring half free if that machine has an RTX GPU. For a speakers-only life more broadly — placement, volume discipline, what order to try things — the no-headphones playbook goes deeper.

Keeping it fixed

  • Make "who's echoing" a normal sentence. Teams that can say "we've got an echo — quick round of mutes?" fix in minutes what mute-everyone cultures endure for quarters.
  • Watch for regressions after changes. New audio gear, new routing software, OS updates — echo that returns after a change is nearly always the change.
  • Don't confuse the three sounds. Delayed copy = echo (this page). Instant self-hearing = sidetone. Rising squeal = feedback — that one you fix by separating devices, not by cancellation.
  • Accept the one honest mute. Someone at an airport gate is a noise problem, not an echo problem — muting them while they're not speaking is fine. The point was never "muting is evil"; it's that muting is a last resort, not a policy.