AllHands Audio

Echo in Google Meet: Same-Room Laptops, Adaptive Audio, and the Other Loops

AABy the AllHands Audio crew · Published July 29, 2026
A loudspeaker at a back-row desk sends your voice round again: the dashed copies. Right of the aisle there is no loop.

Google Meet echoes when the meeting's sound comes out of a speaker and goes back into a live microphone. One of the most common ways it happens now is several laptops joined from the same room, each one playing everyone else and picking it up again. Meet has a built-in fix for exactly that, adaptive audio, which merges the laptops' mics and speakers into one system. It only exists on certain paid Workspace plans, though. Everyone else fixes echo the classic way: find the desk with open speakers, put headphones on it, and allow one audio connection per room.

If you're the one whose voice returns a moment later, your own setup is almost never the cause. Your echo is made at someone else's desk, so the first job is finding which one.

Google Meet, current web client — checked against Google's Meet and Workspace help.

The same-room problem and adaptive audio

Picture three colleagues in a meeting room, each on their own laptop. Every laptop plays the meeting through its speakers. Every laptop's microphone hears the other two laptops' speakers. Each voice now enters the meeting three times, slightly apart, and the people dialed in from home hear the room repeat itself. Turn the volume up and it can tip into howling.

Two diagrams of three laptops in one room. Without adaptive audio, sound loops between each laptop's speaker and the others' mics. With adaptive audio, the laptops act as one microphone and speaker system and the loop is gone.
Why same-room laptops echo, and what adaptive audio changes. Based on Google Meet help.

Adaptive audio is Google's answer. When Meet detects two or more laptops in the same room, it switches into adaptive audio mode and combines their microphones and speakers. Google says you'll see a pop-up reading "To avoid feedback, your audio is merged with other devices nearby." If Meet asks you to confirm instead, click Merge mic & speakers. People with merged audio are grouped together in their video tiles, and the group lights up when any of them speaks.

Two details change how you behave in the room. You don't need to mute when you're not speaking, because Meet picks the microphone closest to whoever is talking. And because Meet uses every microphone in the room, you can still be heard with your own mic muted; only when every mic in the room is muted does the room go silent.

Who has adaptive audio, and where the toggle is

This is the part most echo guides leave out. Adaptive audio isn't available to everyone. Google's help page says it requires an eligible Google Workspace subscription, and Google's Workspace feature list names Business Standard, Business Plus, Enterprise Standard, Enterprise Plus and Frontline Plus. Business Starter and Enterprise Starter aren't on the list, and neither are personal Google accounts. Google also says adaptive audio can't be used with Meet hardware devices.

Grid of Google account types against two Meet features, adaptive audio and cloud noise cancellation. Personal accounts have neither, except that Meet cancels noise on the device itself on most Android phones; Business Starter has no adaptive audio and isn't on the noise cancellation list; Business Standard, Business Plus, Enterprise Standard and Enterprise Plus have both; Google One 2 TB and up has noise cancellation only.
Which accounts get Meet's two room-audio features. Google Meet and Workspace help.

If your plan includes it, there's no switch to turn on: it's on by default and triggers automatically. The settings you'll actually touch are the off switches. To stop merging for one meeting, open People, then the menu next to your name, and choose Stop merging your audio. To turn it off for good, go to More > Settings > Audio and switch off Adaptive audio at the bottom. Google's warning is blunt: turning off adaptive audio may cause echo or a howling noise.

If Meet doesn't detect the other laptops, Google lists three checks: the computers' speakers mustn't be fully muted, microphones mustn't be muted outside Meet (including physical switches), and Voice Isolation on macOS or Noise Suppression on ChromeOS must be off. Meet's own noise cancellation is fine to leave on; Google says it works alongside adaptive audio.

Echo causeThe fixWho can use it
Several laptops in one roomAdaptive audio merges their mics and speakersBusiness Standard/Plus, Enterprise Standard/Plus, Frontline Plus
Several laptops in one room, no adaptive audioOne laptop keeps audio; the rest join in Companion modeEveryone
One person on open speakersHeadphones at that desk, or lower volumeEveryone
Same person joined twice (two tabs, or laptop + phone)Leave on one; the second joins muted with sound offEveryone
Speaker too loud or too close to the micLower volume, more distance, mute when silentEveryone
Excessive mic gain on room equipmentTurn gain downEveryone (usually an admin for room kit)

Sources: Google Meet help articles 14263133 (adaptive audio), 11295507 (Companion mode) and 10620583 (quality), plus Google Workspace's admin troubleshooting guide.

No adaptive audio on your plan?

Krisp includes echo cancellation and runs on your own Mac or Windows laptop, whatever your Workspace plan. 7-day trial, no card needed.

Try Krisp free for 7 days Krisp with Meet & Webex — the full picture →

1. Find whose desk hosts the loop

If the echo isn't a same-room problem, it's one person's speakers feeding their own mic. The person causing it rarely notices, since the loop doesn't return their voice to their own ears. Everyone else hears it. So the hunt happens from the outside:

  1. Watch the participant tiles while someone else is speaking. A tile that lights up as if talking while its owner is silent is replaying the meeting into the mic.
  2. Ask the suspected person to put on headphones, or to turn their speaker volume down.
  3. No host controls? A quick message in chat naming the tile is enough. Most people are glad to be told.

Meet also helps. When it detects echo, a red dot appears on the More options button; open More options > Troubleshooting & help, and under "Audio & video devices" you'll find echo instructions. Google says Meet automatically tries to fix the echo, and suggests headphones, lower speaker volume and muting when you're not speaking.

2. Hunt the duplicate tab

Browsers make it easy to join a meeting twice without noticing. A second Meet tab of the same meeting is a second device, with its own mic and speaker, in exactly the same spot as the first. It's a perfect loop.

  1. Check your browser for a second tab of the same meeting, and close one.
  2. Joined on laptop and phone? Only one carries audio. Mute the other and turn its volume to zero.
  3. Want a second screen for slides or chat? Join it in Companion mode instead (next section).

Companion mode for hybrid rooms

Companion mode is Google's built-in way to join a meeting on a second screen without adding a second microphone and speaker. Google says that in Companion mode your mic and video are turned off to avoid audio feedback. You join from the meeting invite under Other joining options > Use Companion mode, or by going to g.co/companion.

For a meeting room without adaptive audio, Companion mode is the practical setup. One laptop, or the room's own conferencing system, carries the audio for everyone. Everybody else joins in Companion mode, so each person still has the meeting on their own screen without adding a single extra mic to the room. The flip side: Google warns that in Companion mode the microphone and speaker are unavailable, so if someone in Companion mode wants to talk from their own laptop, they need to leave and rejoin normally.

Loop gone. The room still hums?

A virtual mic Meet accepts on any account. Seven trial days free; Krisp Core is priced at $8 a month paid yearly, or $16 paid monthly (checked 9 Oct 2026).

Try Krisp free for 7 days Krisp with Meet & Webex — the full picture →

3. If speakers are your life, starve the loop

Some setups can't use headphones: a shared desk, a hearing need, an all-day call. Echo cancellation can still keep up if you keep the playback quiet and far from the mic.

  1. Turn the speakers down to the lowest level you can follow comfortably.
  2. Move the microphone away from the speakers, or turn it so it faces away from them.
  3. Mute when you're not the one talking.
Why this works: echo cancellation removes sound it can predict from its own playback, and quiet, distant playback is easy to predict. Loud playback right next to the mic swamps it. Google's Workspace admin guide adds one more cause from room equipment: too much microphone gain or sensitivity can cause echo or audio stuttering.

Edge cases

A room with Meet hardware

If the room has a Google Meet hardware kit, adaptive audio is off the table: Google says it can't be used with Meet hardware devices. The room kit is the one microphone and speaker system, so laptops brought into that room should join in Companion mode. Two systems in one room, a kit and an open laptop, is the same loop as two laptops.

Your audio carries other tabs or apps

Sometimes the "echo" people complain about is a video or notification sound from your own computer. Google's audio troubleshooting page notes that, depending on your operating system and audio devices, sounds from other tabs or applications can be audible to other participants, and its fix is headphones. If you mean to play a clip, share the tab with its audio instead of playing it through your speakers into the mic.

Echo that comes and goes with adaptive audio

Google says adaptive-audio problems usually disappear after a few seconds as Meet settles the merged devices. If they persist, leave and rejoin. If they keep coming back, Google's fallback is one computer for the room, which brings you back to Companion mode for everyone else.

Still stuck?

  • Echo only when one person speaks? Their setup. Share this page with them.
  • A meeting-room system plus laptops? The room system owns the audio. Laptops join in Companion mode.
  • Robotic or choppy rather than doubled? That's a network or processing problem, not echo. Open More options > Troubleshooting & help and read the network stability graph first. Our note on Google Meet audio cutting out has the full fix order.

Quick answers

Why is my Google Meet echoing?

Because a speaker is feeding meeting audio back into a live microphone. A frequent culprit is two or more laptops joined from the same room. Otherwise it's one participant on open speakers, or someone joined twice. Headphones at the right desk fix most cases.

What is adaptive audio in Google Meet?

It's a Meet feature that detects several laptops in the same room and merges their mics and speakers, so they work as one system and don't echo. It needs an eligible Workspace plan, such as Business Standard or Enterprise Plus, and can't be used with Meet hardware.

Why can I hear myself echo in Google Meet?

Your voice is coming out of someone else's speakers and into their microphone. Your own headphones won't stop it, because the loop is at their desk. Watch the tiles for one that lights up while its owner is silent, and ask that person to use headphones.

How do I turn off adaptive audio?

For one meeting, open People, then the menu next to your name, and choose Stop merging your audio. To turn it off permanently, go to More > Settings > Audio and switch off Adaptive audio. Google warns this may cause echo or howling if others are in the room.

Can two laptops be in the same Google Meet room?

Yes. With adaptive audio, Meet merges them automatically. Without it, let one laptop carry the audio and have the other join in Companion mode, which turns off its mic and video to avoid feedback.

Sources