The pickup problem
Mic picking up speaker sound? Here's how to stop it
The complaint arrives in two flavors. Flavor one: "we can hear ourselves when you're on the call" — your mic is catching the far side's voices out of your speakers and mailing them straight back. Flavor two: "we can hear your video / your music / your whole computer" — your mic is rebroadcasting your desktop audio to the meeting. Same root cause: sound leaving your speakers is arriving at your microphone loud enough to survive the processing that should have removed it. Both are fixable while keeping your speakers.
First, rule out the impostor: internal loopback
Before blaming acoustics, check that the sound is actually traveling through the air. Windows machines can have a recording device commonly labeled "stereo mix" — a driver feature that captures everything the computer plays as if it were a microphone. If a calling app ends up using that (or a virtual "what-you-hear" device installed by audio software) as its input, your desktop audio is being sent to the call electrically, with no speakers involved at all. The tell: people hear your computer audio with perfect clarity even when your speaker volume is nearly zero.
The check takes thirty seconds: open your calling app's mic selector and make sure the chosen input is your actual microphone — not stereo mix, not a mixer output, not anything with "virtual," "loopback," or "cable" in the name (unless you put it there on purpose and know why). If the input was wrong, you're done; no acoustics were involved. If it was right, read on — your problem is airborne.
Why your canceller is losing the airborne fight
Your device knows what it's playing and is supposed to subtract it from what the mic hears — that's acoustic echo cancellation, and it runs by default in every serious calling app. When speaker sound still gets through, one of these is true:
- The mic is being overfed. Speakers loud, mic close to them, or mic gain cranked. Cancellation is subtraction, and subtraction leaves residue in proportion to what goes in.
- The speakers are distorting. Small speakers pushed hard produce sound that was never in the reference signal — mathematically invisible to the canceller. Loud and clean is hard for laptop hardware.
- The canceller lacks the reference. Media players, games, and browsers play audio the calling app never saw, so the app's AEC can't subtract them — many cancellers handle this via system-level references, but routing tools and multi-device setups break that. This is why meetings hear your YouTube tab: to the app's canceller, that audio can be a stranger.
- Something changed recently. New audio software, an update, a different output device — the sudden-echo checklist handles the "it was fine last week" case.
The fix sequence
- Verify the input device (the loopback check above). Cost: 30 seconds.
- Cut speaker volume by a third and retest. Ask the far side directly: "still hearing yourselves?" You're looking for the threshold where the canceller starts winning.
- Move mic and speakers apart. Mic in front of you, speakers angled away from it, never facing each other. On laptops, an external mic even a hand-span closer to your mouth than the chassis improves the voice-to-speaker-bleed ratio dramatically — closer voice means you can lower both gain and volume.
- Lower mic gain / disable mic boost. A hot mic hears everything, including what you wanted subtracted. Set gain so your voice peaks comfortably, not so the room breathes into the call.
- Don't play meeting-irrelevant audio into the loop. Blunt but true: if the call doesn't need your music, mute the media, not the mic. When you must share sound, use the app's built-in share-audio path — it delivers the signal directly instead of round-tripping it through your room.
- Add a system-wide cancellation layer. If speakers-at-volume is non-negotiable and steps 1–5 didn't finish the job, a virtual-mic canceller sits before every app and subtracts speaker bleed with a system-level view of what's playing. Options and honest limits in the software guide.
Special cases worth knowing
- Others hear their own voices, but only when they speak: classic speaker-to-mic loop, this whole page applies — and if you want the diagnostic logic from their side of the call, it's in why do I hear echo.
- A screech or howl instead of a delayed copy: that's a runaway gain loop, not pickup residue — different fix, covered in speaker–mic feedback.
- You hear yourself, instantly, in your own headset: not this page's problem at all — that's sidetone or monitoring.
- The pickup only matters on recordings: if live participants are happy and only your recording carries bleed, record the processed (post-canceller) feed rather than the raw mic — same tools, applied before the recorder.