When Google Meet cannot hear you, the microphone itself is rarely broken. Meet runs inside a web browser, and a web page is not allowed to listen to anything until a chain of gatekeepers has said yes: the operating system, the browser, the individual site, and finally the device selection inside Meet. A “no” at any link in that chain produces the same symptom, which is silence. Working through the chain in order finds the block fastest.
Why browsers guard the microphone
A browser loads code from whatever site you visit. If any page could switch on your microphone without asking, every site would be a potential listening device. So browsers treat the microphone and camera as protected resources. A site has to request access, you see a prompt, and your answer is remembered for that site alone.
The remembering is what catches people out. If you clicked “Block” once in a hurry, the browser does not ask again. It quietly refuses every future request from Meet, and Meet can only report that it has no microphone.
Layer one: the operating system
Above the browser sits the operating system’s own privacy control. Both macOS and Windows have a microphone section in their privacy settings that lists which applications may use the microphone at all. If your browser is switched off in that list, or if microphone access is disabled globally, nothing you change inside the browser will make any difference.
This layer is commonly tripped after installing a new browser or after a major system update. Open the system’s privacy settings, find the microphone section, and confirm that your browser is allowed. On macOS you will generally need to quit and reopen the browser for the change to apply.
Layer two: the site permission
Next is the browser’s per-site permission for Meet. In Chrome, Edge, Firefox and Safari alike, you can inspect it from the address bar while on the Meet page: click the icon at the left of the address, which opens the site’s permissions, and look at the microphone entry. It should read “Allow”. If it reads “Block”, change it and reload the page, since the running page will not notice the change until it reloads.
Some browsers also show a small camera or microphone icon in the address bar when a request has been blocked, which is a useful hint that this layer is the problem. If the address bar route is not obvious in your browser version, the full walkthrough for a Google Meet microphone not working covers where each browser keeps the setting.
Extensions and managed profiles
Two less obvious things can interfere at this layer. Privacy or security extensions sometimes block media access, so try a private window with extensions disabled, or a different browser, as a quick test. And on a managed work or school profile, an administrator policy may fix the microphone permission so that you cannot change it; the settings page normally says so, and the help desk is your route.
Layer three: the device Meet is listening to
Permission granted does not mean the right microphone is in use. Computers accumulate audio inputs: the built-in microphone, a webcam, a headset, a dock, sometimes a virtual device installed by other software. Meet picks one, and it may be one that is not near your mouth, or one that is muted.
Open Meet’s audio settings from the menu in the call or the preview screen and check which microphone is selected. Speak and watch the level indicator. If it does not move, pick another device from the list. Bluetooth headsets deserve particular suspicion, since they may be connected to your phone rather than the computer, or may appear twice under slightly different names.
While you are there, rule out the simple things. Many headsets have a physical mute switch on the cable or the boom. Meet’s own mute button may be on, and hosts can mute participants. Close other calling apps too, since one that has claimed the microphone can keep the browser from using it.
A quick order of operations
If you want the short version, check in this sequence and stop when the level indicator starts to move.
- Hardware: mute switch off, headset connected to the computer, not the phone.
- Meet: not muted, correct microphone chosen in audio settings.
- Site permission: microphone set to “Allow” for Meet, then reload.
- Operating system: browser permitted in the microphone privacy settings, then restart the browser.
- Still silent: try another browser or a private window to expose extension or profile problems.
One silence, several locks
The reason this problem feels so baffling is that every layer fails in the same way, without an error that says which one refused. Once you picture it as a series of locks between the microphone and the meeting, each with its own key, the fix becomes a checklist rather than a mystery. Run through it once on a quiet afternoon, before the meeting where you need to be heard.
