Echo in Google Meet: Cut the Loop

AABy the AllHands Audio crew · Published July 29, 2026 · Last updated July 29, 2026

This page contains affiliate links — see our disclosure.

Same physics as every platform: someone's speakers are feeding a live microphone — usually at the desk of the one person who can't hear the echo. Meet's twist is the browser: a second tab joined to the same meeting counts as a second device, and two tabs with live audio loop beautifully. Find the culprit, apply headphones, and allow only one audio-carrying tab per human.

Google Meet, current web & mobile clients — checked against official vendor documentation July 28, 2026.

1. Find whose desk hosts the loop

Watch participant tiles while someone speaks — the tile that lights as if talking, while silent, is re-broadcasting.
Host: mute that participant and ask them to use headphones or drop speaker volume.
No host powers? A polite 'someone's on speakers — could you check?' with the tile name works.

Why this works: the echo's victim hears it; its cause doesn't — their voice never returns to them. The lighting tile is the objective witness.

2. Hunt the duplicate tab

Check your own browser for a second Meet tab of the same meeting — close it or leave the call in one.
Joining from laptop + phone? One carries audio; the other joins muted with volume zero.
Companion-mode users: companion joins are audio-less by design — use them for the second screen.

Why this works: browsers make double-joining effortless and invisible; two live audio endpoints under one roof is the loop's favourite architecture.

If your account tier says no

Echo cut, background noise remains?

No noise-cancellation toggle on your Workspace plan? You don't need the upgrade — Krisp filters before Meet ever hears the audio, on any account tier, and the 7-day full trial needs no card.

Skip the tier upgrade Krisp with Meet & Webex — the full picture →

3. If speakers are your life, starve the loop

Volume to the minimum the room can follow.
Mic physically away from the speakers.
Mute whenever you're not the one talking.

Why this works: echo cancellation absorbs quiet, distant playback and drowns under loud, near playback — you're keeping residue inside the absorbable range.

Still stuck?

Echo only with one participant? Their setup; share this page kindly.
Robotic garble, not echo? Network starvation — a different article's problem.
Meeting-room hardware plus laptops? Room system owns audio; laptops join silent.

Quick answers

Can my headphones fix echo I keep hearing?

No — the loop lives where the speakers are. Your headphones prevent echo you'd cause; the echo you hear needs taming at its source desk.

Why does echo start when someone joins by phone and laptop?

Two connections, both with live audio, in one room: each re-broadcasts the other. One of the two must give up audio entirely.