Microphone Not Working in Google Meet: How to Fix It

Google Meet installs nothing, so a microphone not working in Google Meet nearly always comes down to a browser permission. Meet is a website. It cannot touch the microphone until the browser grants meet.google.com access, and the browser asks only once, the first time you join a call. Dismiss or block that prompt and Meet falls silent for every later call, with no error to explain it. Two more gates sit behind that one: the operating system must let the browser listen, and Meet must point at the right input device. Any of the three, when closed, flattens your level meter. This guide checks all three in order. Start in Meet's own green room, or our microphone test, to confirm capture. Then fix the browser site permission, the operating-system gate, and device selection. The final section covers the mobile app, which follows entirely different rules.

Google Meet Microphone Not Working: Quick Fix Checklist

✓	Test in the green room ("Check your audio and video").
✓	Allow the site in your browser (the Chrome padlock or tune icon).
✓	Pick the mic in More options (⋮) › Settings › Audio.
✓	Grant the operating-system permission for the browser.
✓	Close other apps or tabs using the microphone, then reload.

Test your microphone before a Google Meet call

Confirm that the microphone captures sound before you change any setting. The fix for "no signal at all" differs completely from the fix for "signal, but nobody can hear me." A live input meter gives the fastest honest answer. It reacts to your voice in real time. Open our online microphone test and allow access when the browser asks. Speak normally. If the level indicator moves as you talk, the microphone hardware and its driver are fine. The fault then sits higher up, in a permission or inside Meet itself. If the meter stays flat, the signal is blocked or the wrong input is selected.

Google Meet previews the microphone before you join. The pre-join screen, often called the green room, carries a Check your audio and video control. It shows the selected camera and microphone and lets you switch either one. Use it as your second test. Speak and watch whether Meet registers the input. Inside an active call, the same controls live under the three-dot menu. Open More options (⋮) › Settings › Audio and read the Microphone dropdown. That dropdown is the single most important control in this guide.

Test Your Microphone →

Meet's microphone can be blocked in three distinct places. Knowing which layer holds the block saves the most time. The browser decides whether the meet.google.com site may use the microphone at all. The operating system decides whether the browser itself may use it. Meet decides which physical device the browser then hands over. A failure at any layer looks identical from your seat. The table maps the three gates. It states where each one lives and what confirming it proves.

Layer	Where to check	What it confirms
Browser site permission	Padlock or tune icon in the address bar › Microphone	That meet.google.com itself is allowed to use the mic
OS microphone permission	Windows, macOS or Chromebook privacy settings › the browser	That the browser may reach the microphone at all
Device selected in Meet	⋮ › Settings › Audio › Microphone	That Meet is listening to the input you speak into

Why Google Meet cannot hear you

Meet is a website, so browser permission comes first

Because Meet runs in the browser, the browser's site permission is the number-one factor. A desktop app such as Zoom or Microsoft Teams asks the operating system directly. Meet cannot. It asks the browser, and the browser asks you, once, with a small prompt the first time you join a call. If you dismissed that prompt or clicked Block, Meet falls silent with no further warning. The decision is remembered for every later call on that site. No error inside Meet names the true cause. You simply cannot be heard. In Chrome, the control sits behind the tune or padlock icon at the left of the address bar. Click it, find Microphone, and set it to Allow. The full page lives at chrome://settings/content/microphone. There, meet.google.com should appear under the allowed list, not the blocked list. If Meet sits on the blocked list, remove it, reload the tab, and let the prompt appear again. Our Chrome guide covers this permission in full. Edge, Firefox and Safari place the same control in a similar spot, and their guides walk through each one.

Another application is holding the microphone

Only one application can usually claim the microphone at a time on a desktop. When a second program already holds it, Meet shows Another application is using your microphone. A different browser tab running a web call, a desktop conferencing client left open, or a voice recorder are the usual offenders. The device is busy, so Meet receives nothing. Close the other program or end its call. A background browser tab is easy to miss. It keeps the microphone even while hidden behind other windows. Check every open tab and every conferencing app before you assume a deeper fault. Then reload the Meet tab so it can claim the freed device.

The operating system can still block the browser

Granting the site permission is not always enough. The browser itself needs the operating system's blessing to reach the microphone. This second gate lives outside the browser entirely. On Windows, the switch is Settings › Privacy & security › Microphone. There, "Let desktop apps access your microphone" must be on, and your browser must be allowed. Our Windows 11 and Windows 10 guides show the exact toggles. On a Mac, the list is System Settings › Privacy & Security › Microphone, and the browser must be ticked there, as our Mac guide explains. A Chromebook keeps its own site and system controls, and our Chromebook guide covers both. If this gate is closed, no website, Meet included, can capture a thing.

Fixing Meet's microphone, from the most common cause down

Work through these fixes in order. The sequence resolves the most cases first, with the least effort. Browser permission and device selection together account for nearly every Meet microphone failure. Only then does the sequence escalate to the tab itself. After each change, return to the microphone test or Meet's green room and re-check for a signal. That way you always know which step made the difference.

Grant, then reset, the site permission

Open the browser's site permission for meet.google.com and set the microphone to Allow. Suppose it is already allowed and Meet still hears nothing. The stored decision is then likely stale or corrupt. The clean fix is to reset it. Remove the saved microphone permission for the site, reload the tab, and click Allow when the prompt returns. The browser now treats Meet as a fresh visitor and asks again. Keep our tester open in a second tab throughout. It confirms whether the browser can hear you at all, which isolates a site-specific block from a browser-wide one.

Choose the right input in Meet's Audio settings

With the site allowed, open ⋮ › Settings › Audio and read the Microphone dropdown. Do not trust whatever Meet chose. The browser and Meet both default to a device that may not be the one you speak into. Select your headset or microphone by name. Speak, and watch the input indicator beside it react. A wireless headset that has gone to sleep, or a monitor's built-in microphone chosen by accident, will leave you talking into nothing. Suppose the correct device is missing from the dropdown entirely. The operating system is then not exposing it to the browser, so return to the OS permission gate above. Meet remembers this choice per browser. Set it once on the machine you use, and it holds for future calls.

When the meeting tab itself is stuck

Suppose the site is allowed, the operating system permits the browser, and the right device is selected, yet the meter stays flat. The tab has probably wedged. Reload it first. A single refresh reconnects the microphone in most cases. If that fails, join the call from a different browser to isolate the fault. A microphone that works in a second browser proves the first browser's settings are the problem. Keep the browser current, because Meet tracks recent releases and older builds mishandle audio devices. A full restart of the browser clears whatever remains. The table below matches each common symptom to its likely cause and its fix.

Symptom	Likely cause	Fix
"Another application is using your microphone"	A second tab or app already holds the device	Close the other call or recorder, then reload the Meet tab
No microphone prompt ever appears	The site permission was blocked earlier	Reset meet.google.com's mic permission and reload the tab
Correct microphone missing from Meet's dropdown	The OS blocks the browser, or the device is asleep	Allow the browser in OS privacy settings, then wake the device
Meter moves in the tester but not in Meet	The wrong input is chosen in Meet	Set ⋮ › Settings › Audio › Microphone to the right device
Fine on desktop, silent in the phone app	The Meet app lacks the phone's microphone permission	Grant mic access to the Meet app in your phone's settings

The Meet mobile app follows the app's own rules

Google Meet on a phone or tablet is a native app, not a website. The browser permission no longer applies. The app asks the operating system for the microphone directly, exactly as Zoom does. If you denied that request, or never saw it, the app is muted at the system level. On Android, grant the microphone under the app's permission screen, as our Android guide shows. On an iPhone or iPad, the switch is Settings › Meet › Microphone, covered in our iPhone guide. A phone that joins Meet through a mobile browser instead of the app is back to the website rules, and the browser permission governs again. Test the phone the same way you test the desktop. Speak in the green room and watch the input register before the call begins.

A few habits keep Meet reliable once the microphone is back. Confirm the site permission and the input device once on each machine and browser you use for calls. Meet stores both per browser, so a laptop and a desktop hold separate settings. Keep the browser and, on mobile, the Meet app updated. Both ship audio fixes often. When the same microphone must work in a browser, a desktop app, and a phone, test it in each place. A microphone that is flawless in our tester can still be blocked one layer up, inside Meet or the operating system. Our Zoom and Microsoft Teams guides handle the same checks for those apps.

Frequently Asked Questions

Why can Google Meet not hear my microphone in the browser?

Meet is a website, so it needs the browser's permission for meet.google.com. If that permission was blocked, Meet stays silent with no error. Click the padlock or tune icon in the address bar, set Microphone to Allow, then reload the tab.

Where do I change the microphone inside a Google Meet call?

Open the three-dot More options menu, choose Settings, then Audio. The Microphone dropdown lists every available input. Select your device by name and watch the indicator respond as you speak.

What does "Another application is using your microphone" mean in Meet?

Another program or browser tab has already claimed the device. A second web call, a desktop conferencing app, or a recorder is the usual cause. Close it, then reload the Meet tab so Meet can take the microphone.

Why does my microphone work on desktop but not in the Meet phone app?

The mobile app is native, not a website, so it needs its own system permission. Grant microphone access to Meet in your phone's settings. Our Android and iPhone guides show the exact screens for each system.

How do I test my Meet microphone before joining a call?

Use the green room, the "Check your audio and video" screen shown before you join. It previews the selected microphone and lets you switch it. Our online microphone test gives a second, independent live meter.