Google Meet says the microphone is blocked: how to fix that

Google Meet reporting that the microphone is blocked is not a hardware diagnosis. It is a report that something in the chain answered no, and the answer is stored somewhere that can be found and changed. The word blocked is the clue: a broken microphone produces silence, while a blocked one produces a message.

There are only two places that store that answer on a Mac, plus a third thing that looks like a block and is not: a device selected that is no longer sending sound. Clearing the two lists in order, then verifying with a test that actually shows something, takes a few minutes and does not require restarting anything.

Blocked means a stored answer

Browsers keep permission decisions per site, and the decision offered is not binary. Google's page on using the camera and microphone in Chrome describes the prompt as offering Allow while visiting the site, Allow this time, or Never allow.

The third option is the one that produces this message later, because it is remembered. After it has been chosen once, no prompt appears again for that site and the call simply has no voice. Nothing is broken, nothing needs reinstalling, and no amount of unplugging headsets will change it.

The same page documents a rule that explains a stranger symptom. Allowed sites can start to record while the user is on the site, and a site cannot start recording while a different Chrome tab or a different app is in front. A microphone that refuses to come back on while notes are being read in another tab is following that rule rather than failing.

Before either list is opened, Google's own troubleshooting order starts with something simpler, and it is worth thirty seconds because it is free. The first step it names is to make sure nothing is muted: that the mute switch on a headset cord is off, and that the account is not muted on the website or conferencing service itself. Only then does it move on to site permissions, then to system settings and whether the microphone is the default recording device with correct levels, then to restarting the call and the computer. A message about being blocked makes the permission layers likely, but a hardware mute switch produces the same silence for free, and it is the one cause that no settings screen will reveal.

Symptom	Where the answer is stored	Where to go
Microphone is blocked, with an icon in the address bar	The site permission in the browser	Chrome site settings
Prompt never appears at all	A previous Never allow for that site	Delete the exception, then reload
Allowed in the browser, still nothing	The macOS permission for the browser	System Settings, Privacy & Security
Was fine, then went quiet mid call	The selected input device changed	Sound settings and the Meet dropdown

Clearing the answer at the site level

The site level is first because it is the layer that produces the exact wording, and because it is the one that can be fixed without leaving the browser.

Google's instructions are to open Settings, then Privacy and security, then Site settings, then Microphone under Permissions. That screen does three things. It sets the default behaviour for sites. It lists sites that are allowed and sites that are not allowed. And it lets an existing exception be deleted, which is the move that matters here, because deleting the entry brings back the prompt on the next visit.

For a site sitting under the not allowed heading, the permission can be switched directly: select the site's name and change the microphone permission to Allow. Either route works. Deleting and re-prompting has the advantage of confirming that the prompt itself still appears.

The same screen carries a setting worth making deliberately rather than by default. Google documents selecting a default microphone there: under Microphone, use the down arrow to choose which device sites get. Setting this to the built-in microphone, rather than leaving it on whatever was last connected, removes the most common cause of a call that starts silent after a headset has been unplugged.

Reload the meeting page after any change. A page that was refused a device when it loaded does not necessarily ask again on its own.

Then the system level, which is a separate list

Permission inside the browser is not permission from macOS. The operating system keeps its own list, and both have to say yes.

Apple's instructions are to choose Apple menu, then System Settings, then Privacy & Security in the sidebar, then Microphone, and to turn access to the microphone on or off for each app in the list. The entry to look for is the browser being used for the meeting, not Meet, because Meet is a page rather than an installed application.

Apple's page also names the indicator that tells the truth about whether anything is listening. The Recording Indicator light in Control Center shows when the computer's microphone is in use or has been used recently. That is a useful cross check: if the indicator never appears when joining a call, nothing has been granted the microphone, and the site level change did not take effect.

One detail catches people who use more than one browser. A permission granted to one browser says nothing about another, and a browser that has never asked for the microphone may not be listed at all. Installing a second browser for meetings means granting this permission a second time.

Sound has no preview, so verify it on purpose

A camera problem announces itself: the tile is black. A microphone gives no feedback at all, which is why people discover a blocked microphone by being asked to repeat themselves. Meet provides a test, and it takes five seconds.

Google's documentation describes the green room self-check before joining a meeting. The peripheral devices appear at the bottom of the preview tile, and the dropdown arrow next to each one selects a different device. The test for sound is stated plainly: click Microphone and speak, and if the mic bar moves, the microphone works. There is a matching test for the speaker, which plays a test sound.

Inside a meeting the same controls exist next to the microphone icon. Click the arrow beside it, and a pop up shows the audio devices, with the same mic bar as confirmation. Google adds a warning worth remembering when swapping devices in a hurry: mismatched microphone and external speaker devices might cause an echo, which is a different complaint that gets blamed on the microphone.

Testing before the meeting rather than during it changes what the message means. Seeing the mic bar move in the green room, then hearing that nobody can hear anything, points at the meeting rather than the permission.

When the input device changes under you

The third class of problem is not a permission at all. The microphone is allowed, and the Mac is listening to something else.

Apple's page on sound input settings describes the screen: choose Apple menu, then System Settings, then Sound in the sidebar, then Input, and select the device to use from the list of sound input devices. All available input devices are listed, and a display's built in microphone appears as the Mac model followed by Microphone. The input volume slider on the same screen is the other half of this, because a slider left at the bottom produces a device that is selected, permitted, and silent.

Apple documents a specific case where the selection refuses to stick. With a headset plugged into a Mac connected to a display, selecting the display's built in microphone in the Input options may revert to the headset, and the fix is to unplug the headset first and then make the selection. Anyone who works at a dock and switches between a headset and a display microphone will recognise this as the reason a choice does not hold.

An iPhone can be in this list too. Apple describes using an iPhone as a microphone for a Mac by selecting it in the Input list, with the requirement that the iPhone be in landscape orientation and stationary with its screen turned off when the Mac has no built in microphone. Tapping Disconnect on the iPhone removes it as a webcam or microphone option for the Mac, so a device that was working an hour ago can be gone with no change made on the Mac.

While in this area, one adjacent setting solves the complaint that a voice is heard but sounds wrong. Apple's page on Mic Modes describes selecting Voice Isolation to filter out background sounds or Wide Spectrum to include them, from the menu bar in apps that support the feature.

When the setting is not yours to change

There is one case where all of the above is a waste of time, and it is worth recognising early on a work machine.

Google's page states that for Chrome used at work or school, a network administrator can set camera and microphone settings, and that it may not be possible to modify them. The visible symptom is a setting that reverts as soon as it is changed, or a Site settings screen that shows the choice greyed out.

The correct next step there is a message to whoever manages the machine, naming the site and the permission. Repeating the change, clearing browsing data, or reinstalling the browser will not override a policy, and each attempt costs time that the meeting does not have.

Keeping the call out of the tab strip

Two of the behaviours above are made worse by the way most browsers are used, and both are about the call sharing a window with everything else.

The rule that a site cannot start recording while a different tab or app is in front matters far more when the call is one tab among thirty, because switching away to read a document is a reflex. A call in its own window is still switched away from, but it does not compete for the same row of tabs, and it survives a reflexive Cmd+W. Keeping each web app in a window of its own is what a browser designed around separate workspaces does by default, and the Workspaces page describes how that separation works. Which services can be held that way is listed on the Supported apps page.

What to change first

Clear the site level answer before anything else, because it produces this exact message: delete the entry for the meeting site under Chrome's microphone site settings, reload, and answer the prompt when it returns. Then confirm the browser is switched on in System Settings, Privacy & Security, Microphone.

After that, stop leaving the input to chance. Set a default microphone in the browser, pick the device explicitly in Sound settings, and use the green room mic bar before every call that matters. Platform and pricing details for keeping meetings in a window of their own are on the SpaceDeck page.