Google Meet (web)
Fix Microphone Not Working in Google Meet
Fix Google Meet mic issues by confirming the mic signal, selecting the right input, and resetting browser/OS permissions so people can hear you.
Use the DevicePrep Mic Test to confirm the mic works before changing Meet settings.
If Google Meet says your mic is muted/off, missing, or sounds robotic/static, the cause is usually a stored permission block or the wrong input device selected. Start by proving the mic signal exists (Mic Test), then lock Meet to the correct microphone and remove the blocks that stop audio.
What this guide covers
- Google Meet says your microphone is muted or no microphone is found
- Your mic works in other apps but Meet can't hear you
- Meet uses the wrong input device (headset vs laptop mic)
Quick wins (2 minutes)
- In Meet, open Settings -> Audio (three dots -> Settings) and pick your microphone by name (not Default if you see it).
- Click the padlock icon in the browser address bar and set Microphone to Allow for meet.google.com.
- If Meet says “microphone is off” or “muted by system”, check your keyboard mic-mute key or headset mute switch first.
- Close Zoom, Teams, Discord, OBS, and any screen recorder that could be holding the mic.
- Unplug and replug USB mics/headsets, then reload Meet so the device list refreshes.
- If you use Bluetooth earbuds, disconnect/reconnect so the “Hands‑Free” mic profile resets.
- Restart the browser after permission changes so Meet re-requests access cleanly.
Step-by-step fix
- Run Device Check to confirm the microphone is detected, then open the DevicePrep Mic Test and speak at call volume.
- In Meet, open Settings -> Audio and select your intended Microphone, then speak and watch the input meter.
- Browser permission: click the padlock icon -> Site settings -> set Microphone to Allow for meet.google.com, then reload.
- Chrome-only: open
chrome://settings/content/microphoneand confirm the correct mic is selected and Meet is not blocked. - Windows: Settings -> Privacy & security -> Microphone -> turn on access and allow your browser/Meet.
- macOS: System Settings -> Privacy & Security -> Microphone -> enable your browser (Chrome/Edge/Firefox) and reload Meet.
- Disable “exclusive control” for the mic on Windows and close other apps so Meet can access the device.
- Retest in the Mic Test, then rejoin Meet and do a short test call to confirm others can hear you.
Deep fixes
Decision tree: what to do based on what works
If Device Check doesn’t list your mic, troubleshoot hardware/USB first. If Mic Test is silent, Meet isn’t the problem yet — fix browser permissions or OS privacy blocks. If Mic Test works but Meet is silent, Meet is listening to a different input device (or another tab/app is holding the mic). This guide is designed so you only change one variable at a time and can verify progress immediately.
Confirm the mic works outside Meet
Open the DevicePrep Mic Test and talk at normal meeting volume. If the meter never moves, Meet is not the problem yet; the OS cannot hear the mic or the mic is muted at the hardware level. Check headset mute buttons, keyboard mic-mute keys, and USB connections. If the meter moves cleanly, your mic and browser pipeline are working, and the remaining issue is almost always Meet settings, permissions, or another app grabbing the device.
Pick the right microphone in Meet (not “Default”)
In Meet, open Settings -> Audio and choose the microphone by its actual name (for example, “USB Audio Device” or your headset model). “Default” can switch when you plug in a device, connect Bluetooth, or dock/undock a laptop. After choosing the mic, speak and watch Meet’s input meter. If it shows activity but audio is choppy, turn off Bluetooth temporarily and test a wired headset or USB mic to rule out a flaky wireless profile.
Fix browser permissions for meet.google.com
Meet cannot use the mic if the browser is blocked. In Chrome or Edge, click the padlock icon in the address bar, open Site settings, and set Microphone to Allow for meet.google.com. In Firefox, click the permission icon near the address bar and allow the microphone for the site. Reload the tab after changing permissions so Meet can prompt again. If you previously clicked Block, removing the saved block is usually faster than trying to “fight” Meet settings.
Check OS privacy settings (Windows and macOS)
On Windows, go to Settings -> Privacy & security -> Microphone and enable both the main toggle and app access. Then confirm your browser is allowed and that “Let desktop apps access your microphone” is on. On macOS, go to System Settings -> Privacy & Security -> Microphone and enable your browser, then fully quit and reopen the browser to apply it. These OS-level blocks override Meet every time, even if Meet is configured correctly.
Remove conflicts and fix robotic/static audio
If another app is already using the mic, Meet may show “no microphone” or record broken audio. Fully quit Zoom, Teams, Discord, OBS, and screen recorders. On Windows, disable exclusive mode: Sound -> More sound settings -> Recording -> your mic -> Properties -> Advanced -> clear both exclusive control boxes. For robotic audio, switch the mic sample rate to 48 kHz (or back to 44.1 kHz) and retest; mismatched rates and Bluetooth “Hands-Free” mode often cause artifacts. When the Mic Test stays stable for 30 seconds, rejoin Meet and verify with a quick test meeting.
Quick checklist
- Mic Test meter moves when you talk
- Meet uses the same mic you tested
- Browser permission set to Allow for meet.google.com
- OS microphone privacy settings allow the browser
- No other app is holding the microphone
- Audio is clear (not robotic/static) for 30+ seconds
FAQs
Why does my mic work in other apps but not in Google Meet?
Meet is usually blocked by a browser permission, or it is listening to a different input than the one your other app uses. Set meet.google.com to Allow and pick the mic by name in Meet settings.
Why can I see the mic meter move but nobody hears me?
That often happens when Meet is using a different mic than your OS, or when the mic is heavily noise-suppressed. Re-pick the mic in Meet, disable aggressive noise suppression, and retest.
Can headphones or speakers cause “echo” warnings?
Yes. If your speakers are loud, your mic can pick them up and Meet may lower or mute audio. Use headphones while troubleshooting and run both the Mic Test and Speaker Test.
Is an online mic test safe?
A browser mic test only reads audio levels after you click Allow. It cannot “turn on” your mic without permission, and you can revoke access anytime in your browser settings.
Sources
Documentation referenced while maintaining this guide.
Wrap up
Use the Mic Test first to prove the microphone works, then fix Meet’s device selection and permissions. Once your levels look stable, run the Pre-Call Checklist so your camera and speakers are ready before your next meeting.