Google Meet Mic Not Working: Where the Fault Sits

Google names three separate permissions a microphone has to pass before Meet hears it. Its own help page puts them in a list: access for Google Meet, access for your browser, and access for your device. Three gates, and a refusal at any one of them looks identical from the meeting's side. Chrome then adds a fourth that isn't in Google's list, because on a work or school browser the administrator sets camera and microphone policy, and Chrome says plainly that you may not be able to change it. That's the case a troubleshooting article usually skips, though it's exactly the machine most meetings happen on.

The microphone the meeting picked may not have one

Of the 67 headphone listings gathered here, 30 answer the built-in microphone field with No. Wear one of those in a meeting and the microphone Meet finds is the laptop's, sitting under the keyboard, several feet from your mouth and pointed at the fan. The 33 that do carry a microphone don't carry it in the same place, though. Fourteen put it on the earpiece, 4 on an adjustable boom, two on the cable, and nine say only Yes without saying where. Four listings have no such row at all.

Where it sits changes what a meeting hears. A boom reaches toward the mouth, whereas an earpiece capsule doesn't, so the same person on the same call sounds nearer or further depending on hardware nobody mentioned in the invitation.

Three permissions, and the order they fail in

Google's list runs Meet, browser, device, and each is held somewhere different. Meet's own permission lives in the meeting; the browser's lives in site settings; the device's lives in the operating system's privacy panel. A user who grants one and stops has granted nothing useful. Chrome then offers three answers when a site asks, not two: "Allow while visiting the site" persists, "Allow this time" doesn't, and "Never allow" is remembered until somebody goes and removes it. So a meeting that worked yesterday but fails today may simply have been granted the middle option. A desktop application skips the browser link entirely, which is why the same microphone can work in one program and not the other, and it's the single clearest difference between diagnosing a browser meeting and a native one.

There's one more restriction Chrome states and Meet's page doesn't: a site can start recording only while you're on it. Switch to another tab or another application and it can't begin. That's a privacy feature behaving exactly as designed, yet it reads as a fault when a meeting is running in a background tab.

The switch neither the browser nor the meeting can see

A hardware mute interrupts the signal before anything digital sees it. The operating system still lists the device, the browser still holds its permission, and Meet still shows the microphone as selected. Everything reports fine, but nothing arrives. Some headsets put that switch on an inline pod with a lamp, though others put it in the boom itself, where lifting the arm mutes. The mute a headset carries in hardware is the failure that survives every software check, which is why HP puts a lamp on it instead, because no software check can reach it.

What the blue indicator tells you that nothing else does

Meet marks a speaking participant with a blue indicator at the top of their tile, and Google explains how to read it as a diagnostic. If it doesn't light for other people, the fault is their microphone or your speaker. But if it doesn't light for your own tile, the fault is your microphone or their speaker. That single test splits the problem in half before any setting is touched. Since a meeting has two independent chains, and each participant owns half of one, the indicator is the only thing on screen that says which half is broken.

Google also names a mode that removes the question entirely. In Companion mode the microphone and speaker are unavailable by design, and the fix is to leave the meeting and rejoin, because no setting inside it will help.

Muted by somebody else

Other participants can mute you, yet Google states the limit plainly: they can't unmute you. For meetings organised with a personal Google account only the host can mute others at all. So a microphone that stops mid-meeting isn't necessarily broken. It may have been switched off by a person, and the only person who can switch it back is the one wearing it. Nothing about that appears in a device panel.

Before joining, Meet offers a check that settles most of this in advance. The preview tile carries dropdowns for microphone, speaker and camera, and speaking into it moves a bar. If the bar moves the microphone works, and the question moves to which device the meeting picked, which is a different problem with a different fix.

What Google's pages answer about Meet and microphones

Why is my mic not working in Google Meet?

Because one of three permissions is missing. Google's list is Meet itself, your browser, and your device, and each is granted in a different place.

Does my headset microphone work automatically?

Only if the headset has one. Of the 67 headphone listings here, 30 answer No to the built-in microphone field.

Why does the mic work in one app but not in Meet?

A native application asks the operating system directly, whereas a browser meeting needs the browser's site permission as well.

Can someone else mute me in a meeting?

Yes, but they can't unmute you afterwards. On personal Google accounts only the host can mute others.

How do I check my mic before joining?

Meet's preview tile has a microphone dropdown and a level bar. If the bar moves when you speak, the microphone is working.

Where the fault usually is

In the permission chain rather than the hardware. Three gates, each granted somewhere else, and a fourth that an administrator may hold, produce more ways to be silent than any microphone has ways to fail. What's left after that is the hardware nobody can query: an inline mute, a lifted boom, or a headset that never had a microphone. Those three account for the cases where every panel says the device is fine. Everything else the documents cover is device selection, but Meet's own preview answers it in a second, and that single observation separates a wiring problem from a permissions one.

Sources

1. Google's help page on fixing audio issues in Meet: the list of three permissions the microphone must pass, the Companion mode note, the blue speaking indicator and how to read it, and the statement that other participants can mute you but cannot unmute you.
2. Google's help page on connecting your video and audio: the pre-meeting self-check, the microphone dropdown and level bar, and the note that mismatched microphone and speaker devices can cause an echo.
3. Chrome's help page on using your camera and microphone: the three permission answers, the restriction that a site can only start recording while you are on it, and the note that a work or school administrator may set the policy beyond your reach.
4. Apple's guide to privacy and security settings on macOS: where the operating system holds the third permission in Google's list.
5. Microphone counts across the headphone class come from listings of 200 audio products collected the same way. How those are read and compared.

Google's and Chrome's pages were read on 27 August 2026.

What we did not do

No meeting was instrumented for this page. Every instruction above is Google's, Chrome's or Apple's, and what we add is the count: how many headphones in this collection have a microphone at all, and where they put it.