Echo on calls, solved properly
Every echo has a source.
We break the loop.
Echo is never a ghost — it's always a speaker feeding a microphone somewhere on the call. Echobreak exists to find that somewhere, tell you whose device it is, and shut it down with software and settings. No gear shopping lists, no vague "check your connection" advice.
The one fact that solves most echo
When you hear your own voice bounce back a half-second late, your setup is usually innocent. Your voice left your mic, played out of someone else's speakers, went back into their mic, and returned to you. The person who hears the echo is almost never the person causing it. Once you internalize that, echo stops being spooky and starts being a checklist: whose speakers, whose mic, and what's supposed to be cancelling the loop between them.
Hears the echousually innocent
Causes the echospeaker feeding mic
That cancelling job belongs to a piece of software called an acoustic echo canceller — AEC. Every serious calling app ships one and turns it on by default. When echo gets through anyway, it's because the AEC was overwhelmed, misconfigured, bypassed by a virtual device, or fed a signal it couldn't model. All four of those are fixable, and none of them require buying anything.
We wrote a plain-language tour of the machinery in Acoustic echo cancellation, explained — worth ten minutes if you'd rather understand the loop than memorize fixes.
Start with your symptom
I hear my own voice back
The classic. Work out whose device is looping before you touch a single setting — it's probably not yours.
A group call is echoing
Eight people, one culprit. The mute-in-turn method finds them in under two minutes, in any app.
There's a screech or howl
That's not echo, that's feedback — a runaway loop, usually two devices in one room. Different beast, faster fix.
Others hear my speakers
Your mic is rebroadcasting your desktop audio. Stop the pickup without giving up your speakers.
I hear myself constantly
Instant, not delayed? That's sidetone or mic monitoring — a setting, not an echo. Two-minute fix.
I can't wear headphones
Speakers-only calling that doesn't echo. It's doable — it just needs the loop managed deliberately.
When settings aren't enough: dedicated echo cancellation software
Built-in AEC handles the average case — one laptop, one voice, moderate volume. It struggles with the setups modern work actually produces: external speakers turned up loud, echoey home offices, mics that hear everything, virtual audio devices that quietly bypass the app's processing. That's when a dedicated layer between your mic and your call app earns its keep.
Our echo cancellation software guide covers the whole field honestly: the AEC you already own (free, first thing to try), Krisp — the tool we point to most, with its free tier and its limits stated plainly — and NVIDIA Broadcast for RTX owners, which costs nothing and pays us nothing. Where a fix is free, the guide says so; where a link earns us a commission, it's marked right where it appears.
What Echobreak is — and isn't
This site does one thing: echo on live calls, across every app. We don't review headphones or microphones, we don't do room-makeover advice, and we don't pretend to have run lab tests we haven't run. Claims about what a tool does come from that vendor's own documentation, and anywhere we state a price or a limit, we print the date we checked it. Our method, our bylines, and how we make money are all laid out on the about page — and the blog, Slapback, is where we chase the odder questions: echo versus reverb, why cancellers clip your words, echo that appears out of nowhere.
If you take one thing from this page: don't mute your way through another meeting. Muting hides echo; it doesn't fix it. The loop is findable, and breaking it is usually a five-minute job — here's the playbook.