Echo happens when audio that came out of a speaker gets picked up by a live microphone and sent back to the call. Every fix follows from that one sentence: break the path between a speaker and a microphone, and the echo stops. The hard part is not the fix — it is working out which participant's setup is closing the loop.

Read the Direction First

Before changing a single setting, establish who hears what. It narrows the problem to one machine almost every time.

Symptom Where the loop is
Others hear themselves repeated back Your end — your speakers are feeding your microphone
You hear yourself repeated back Someone else's end, and they probably cannot hear it
Everyone hears everything twice Two devices joined from one room
Echo only when one person speaks That person's device, regardless of who reports it

This is why "everybody mute and unmute one at a time" works so reliably in practice: it is a binary search for the device closing the loop. Zoom's own guidance on managing audio echo in a meeting starts from the same premise.

The Four Causes, in Order of Frequency

Speakers instead of a headset

The classic. Laptop speakers play the other person's voice, the built-in microphone sits a few centimetres away and hears it. Echo cancellation copes at low volume and gives up as you turn it up.

Two devices in one room

A colleague joins from the next desk, or you open the meeting on a laptop and a phone. No software can cancel this: to each device, the other one's output is just room noise.

Windows routing audio somewhere you did not expect

A headset connects but Windows keeps playing through the laptop speakers, or a dock reappears and grabs the default output. You are wearing the headset and still causing an echo.

The meeting open twice

A browser tab still in the call behind the desktop app, or a second window from a failed rejoin. Two live audio streams on one machine echo each other perfectly.

The thirty-second fix, in order: put on a headset and confirm Windows is actually playing through it; close any other window or tab holding the same meeting; if a colleague is in the room with you, one of you turns audio off entirely. That covers the large majority of real cases.

What Echo Cancellation Can and Cannot Do

Teams, Zoom and Meet all run acoustic echo cancellation. It compares what the app just played against what the microphone just heard, and subtracts. Within one device at sensible volume it is genuinely good, which is why laptop speakers often work fine on a quiet one-to-one call.

It breaks in two situations. First, when the loop crosses devices — the algorithm has no reference signal for audio a different laptop played, so there is nothing to subtract. Second, when output is loud enough to distort or arrive with heavy room reflection, because the returning signal no longer resembles the reference closely enough to cancel. Turning the volume down is not a workaround; it is directly attacking the failure condition.

Resist the urge to fix echo by lowering your microphone level. It makes you quiet without closing the loop — you end up with a faint echo and people asking you to speak up. Change the output path instead.

Check the Device Windows Will Actually Use

Almost every echo problem on Windows reduces to one question you can answer before joining: which device will play sound, and which device will listen? Open Windows sound settings and confirm both, then confirm the same pair inside Teams, Zoom or Meet, which keep their own device pickers — Microsoft documents the Teams side under manage your call settings in Microsoft Teams. If Windows itself is behaving oddly with a device, fix sound problems in Windows is the starting point.

The failure people hit is not that they chose wrong. It is that the choice changed since last time — a headset that reconnected as a second entry, a monitor that claimed default output, a dock that came back after sleep. You find out when someone says "there's an echo."

What CallReady Can Check

CallReady is a Windows tray utility for Windows 10 version 2004+ and Windows 11 on x64 and ARM64. One click checks camera, microphone, speakers, face presence, lighting, changed devices, and network latency, jitter and throughput in about 10 seconds, then returns READY, NEEDS ATTENTION or NOT READY.

For echo specifically, the useful part is the device picture. CallReady reports which output and input Windows has selected right now, confirms the microphone is receiving signal, and — the one that matters most here — warns when a device has changed since your last successful check. That is the silent headset-to-speakers switch, caught before the call rather than three minutes into it.

To be clear about the boundary: CallReady does not detect echo, and it cannot, because an echo needs a second participant to exist. It answers the question that precedes it — am I about to join on the speakers instead of the headset? Analysis is local; there is no account, backend or analytics. Network testing contacts Cloudflare. CallReady does not modify Teams, Zoom, Meet or Windows audio settings.

Related articles

For the full pre-call routine, read Test Your Camera and Microphone Before a Video Call. If people say you are hard to hear rather than doubled, see Microphone Too Quiet on Windows 11. When Windows sees a device but the meeting app does not, use Camera or Microphone Works in Windows but Not Teams or Zoom. If audio breaks up rather than repeats, that is usually the network — see Why Video Calls Still Lag on Fast Internet, or measure it in advance with Check Your Internet Before a Video Call. And when the picture is the problem rather than the sound, see Improve Webcam Lighting for Video Calls on Windows.

Frequently Asked Questions

Why do people hear an echo when I talk?
Your speakers are playing their voice loudly enough for your microphone to pick it up and send it back. Switching to a headset removes the path between the two and ends the echo immediately.
I hear the echo but nobody else does. Whose fault is it?
Usually not yours. If you hear your own voice returning, another participant's setup is looping your audio back. The person causing an echo rarely hears it themselves, which is why asking the room who is on speakers finds it faster than changing your own settings.
Does a headset always fix echo?
It fixes the echo you cause, as long as the audio actually routes to it. Windows sometimes keeps playing through laptop speakers after a headset connects, so confirm the selected output device rather than assuming the headset is in use.
Why does echo start when a second person joins from the same room?
Two devices in one room create a loop the software cannot cancel: one laptop's speaker output reaches the other laptop's microphone as ordinary room sound. Only one device in a room should have audio on.
Can echo cancellation handle it automatically?
Teams, Zoom and Meet all cancel echo from a single device's own output, and it works well at moderate volume. It cannot cancel sound that arrives from a different device in the room, and it degrades when external speakers are loud.

Get CallReady

Windows 10 version 2004+ and Windows 11. Start with a 7-day full trial, then continue with a lifetime purchase.

 Get it on Microsoft Store