Meet runs in a browser, so your voice passes three gates before anyone hears it: the operating system decides whether any app may use the microphone, the browser decides whether this site may, and Meet decides which device to listen to. A Google Meet microphone not working means exactly one of those gates is closed, and Meet usually tells you which one in the wording of its own error. Muted by system points at the first gate. Not found points at the third. Anything else, and you are looking at the browser in the middle. The whole diagnosis takes about two minutes once you know which message maps to which layer, which is more than you can say for the ten minutes you have already spent clicking the mic icon.
Three gates, in the order your voice meets them
The order matters, because a closed gate low down makes the two above it irrelevant. If Windows or macOS is withholding microphone access from your browser, no site permission will help and no device picker will show anything useful. Check from the bottom up and you never chase a symptom created one layer below. The quick version of this is on our short page for a Meet mic that will not work; the gates model here is for when the quick version did not land.
- Gate one, the OS: microphone access for your browser, granted per application.
- Gate two, the browser: site permission for meet.google.com, granted per site.
- Gate three, Meet: the input device chosen in the call's own settings.
- Above the gates: whether the far end can hear what does arrive.
Two habits make this harder than it needs to be. The first is that browsers remember a decision made months ago on a different network, so a permission you have no memory of setting is still in force. The second is that a laptop accumulates audio devices, and Meet's picker lists all of them, including a dock, a monitor and a headset that is currently in a drawer. Choosing by name once, in the call, is worth more than any amount of restarting. Neither habit is a fault in Meet, and neither shows up as an error until you are already in the meeting.
The two messages, and what each one names
Meet's error text is more specific than it looks. Read it before you change anything, because these two messages point at opposite ends of the chain.
Microphone muted by system
This is gate one. Your operating system, not Meet, is refusing access, and Meet is reporting what it was told. On Windows, open the privacy settings, find the microphone section, and check both the device-wide toggle and the entry for your browser in the list below it. On macOS, open the privacy section of system settings, tick your browser under Microphone, then quit the browser fully and reopen it, because the grant applies from the next launch. A hardware mute switch on a headset or a function key on the keyboard produces the same message on some machines.
Microphone not found
This is gate three, and it usually means the device Meet had selected has disappeared: a headset that went to sleep, a dock unplugged, a Bluetooth pair that dropped. Open the call's audio settings and pick a device by name from the list. If the list is empty, the fault is below, back at gate one. If the list is full and none of them work, the room is not the problem and the meeting still sounds like a call from a car park.
Working through the gates
Almost every case of a Google Meet microphone not working ends at one of these three steps. Start at the operating system, confirm the browser has microphone access, and relaunch the browser after any change. Then the site permission: the padlock or tune icon in the address bar shows what meet.google.com is allowed to do, and microphone should be set to allow rather than ask. Then Meet itself, where the device is chosen by name. Our page on turning on noise cancellation shows where the audio panel lives, and the pre-join mic test lets you settle all three gates before you join anything.
- Grant OS access, then quit and reopen the browser completely.
- Set the site permission to allow, then reload the Meet tab.
- Choose the input device by name, not by leaving it on default.
- Close other apps holding the mic, then rejoin the call.
If all three gates are open and the far side still hears nothing, the fault moved above them. That is a different page: audio not working for others walks the case where your setup looks correct and the call disagrees. If people hear you but the call sounds hollow or doubled, fix echo is the closer match, and Webex users with the same symptom should start at webex audio not working instead, because the client handles devices differently.
Cases the three gates do not cover
Another app is holding the microphone
A recording tool, a second meeting client or a browser tab you forgot can claim the input exclusively, and Meet then finds a device it cannot open. Close the other app rather than reconfiguring Meet. If you cannot find it, a restart clears every claim at once and takes less time than the search.
It works in one browser and not another
Site permissions and OS grants are stored per browser, so a working setup in one and a dead mic in the other is normal rather than mysterious. Grant access to the browser you actually use for calls, and make that the one you open for meetings. Two half-configured browsers cause more confusion than one.
Phones and tablets have a different picker
In the mobile app the permission belongs to the Meet app itself in the phone's settings, and there is no browser gate at all. There is also no device list to correct, so the fix is the app permission, the headset connection, and nothing in between. Check both before you assume the phone's mic has failed.
Google Meet microphone not working: common questions
What does microphone muted by system mean in Meet?
It means the operating system is blocking microphone access for your browser, not that Meet has muted you. Open the privacy settings, enable the microphone for that browser specifically, then quit and reopen the browser so the grant registers. Check for a hardware mute switch on the headset too, since that produces the same message on several laptops.
Why does Meet say my microphone is not found?
The device Meet had selected is no longer available, usually a sleeping headset, an unplugged dock or a dropped Bluetooth connection. Open the audio settings inside the call and choose a device by name. An empty device list means the block is lower down, at the operating system, so fix that gate before returning to the picker.
How do I give Chrome microphone permission for Meet?
Two places, both needed. The operating system grants the browser access to the microphone at all, and the browser grants meet.google.com access to it in turn. Use the icon at the left of the address bar to set the site permission to allow, then reload the tab. If the option is missing entirely, the OS gate is still shut.
Why does my mic work on Zoom but not on Google Meet?
Because a desktop app skips the browser gate. Zoom asks the operating system directly, while Meet needs the OS to trust your browser and the browser to trust the site. A working desktop app therefore proves your hardware and your OS permission are fine, and narrows the fault to the browser layer or Meet's device choice.
Does restarting the browser actually help?
Yes, after a permission change, and rarely otherwise. Both Windows and macOS apply a new microphone grant when the application next launches, so a browser left open keeps the old answer. Quit it completely rather than closing the window. If nothing changed in the permissions, a restart is just a delay with extra steps.