Microphone Not Working on Google Meet

Microphone Not Working on Google Meet: Browser Permission Fix Guide

In Chrome, Google Meet requires microphone permission granted at the browser level for the specific Google Meet domain. Chrome's microphone permission system operates independently from the OS permission¹. Even if your OS allows microphone access, Chrome can have the permission blocked for meet.google.com specifically. A browser-based microphone test confirms hardware function independently of Meet's permission system.

The browser test here and Google Meet both use Chrome's getUserMedia API to access the microphone. If this tool can access the microphone in the same Chrome window, Google Meet should be able to as well, unless permissions for meet.google.com are specifically blocked. Conversely, if this tool cannot access the microphone in Chrome, the problem is at the Chrome or OS level, not in Meet specifically, and fixing it here will fix it in Meet.

Check the hardware first

Run the Noise Floor Grade. If it returns a result, Chrome has microphone access and the hardware is functioning. If it fails with a permission error, click the camera or microphone icon in the Chrome address bar and check whether capytoolkit.com has microphone blocked. This initial test establishes whether the problem is at the hardware, OS, or browser-permission layer before you spend time adjusting Meet-specific settings that cannot help if the underlying issue is a blocked site permission or a disconnected cable.

Browser permission before Meet device settings

Both this site and meet.google.com need permission granted in Chrome's site settings independently. Chrome treats each website as a separate permission context², which means granting microphone access to one site does not automatically extend to another. If the Noise Floor Grade works here but Google Meet still cannot access the microphone, the issue is almost certainly that meet.google.com has been blocked or has not yet been granted permission in Chrome's site settings.

What the test results mean

Noise Floor Grade returns a reading: hardware and Chrome permission are working at the browser level, which means your Meet problem is in Meet's own device selection or in the per-site permission grant for meet.google.com specifically. In Chrome, go to meet.google.com > click the three-dot menu > Settings > Audio and verify the correct microphone appears in the dropdown with a working input level meter. If the correct device appears but the level meter does not move when you speak, the issue is that Chrome has permission to access the microphone but the specific site permission for meet.google.com has not been granted.

Noise Floor Grade fails: Chrome's microphone permission is blocked at the browser level, and the same block affects Meet because both sites depend on the same underlying Chrome permission. Go to Chrome Settings > Privacy and Security > Site Settings > Microphone to check whether Chrome has OS-level access, and verify that the specific site permission for meet.google.com is also granted.

Chrome grants microphone access on a per-origin basis, meaning capytoolkit.com and meet.google.com are treated as entirely separate permission contexts. This security design prevents a malicious website from accessing your microphone just because you granted permission to a different site, but it also means that a working Noise Floor Grade here provides no guarantee that Meet has its own separate permission grant, and you must check the permission status for meet.google.com specifically in Chrome's site settings to confirm it has been granted.

Platform-specific fix path

Chrome on Windows: Settings > Privacy and Security > Site Settings > Microphone > Sites that can use microphone. Verify meet.google.com is listed. Chrome on macOS: System Settings > Privacy & Security > Microphone. Confirm Google Chrome is listed and enabled. Chrome on Android: long-press the Chrome icon > App info > Permissions > Microphone > Allow. Chrome on ChromeOS: the privacy indicator in the taskbar shows active permissions. Ensure Meet has access.

On macOS, Chrome needs microphone permission at two independent levels: the macOS system level in System Settings > Privacy & Security > Microphone, and the Chrome site level for each individual website. A common failure mode is having Chrome enabled at the macOS level but having meet.google.com blocked at the Chrome site level. If the Noise Floor Grade works in Chrome on macOS but Meet does not, the macOS-level permission is already granted and the problem is specifically the per-site permission for meet.google.com within Chrome's own settings.

Microphone access across multiple Chrome profiles

Chrome manages microphone permissions independently for each user profile. If you use multiple Chrome profiles (personal and work, for example), a microphone permission granted in one profile does not carry over to another. The Noise Floor Grade working in your personal Chrome profile does not guarantee it works in your work profile: each profile requires separate permission grants for each site that needs microphone access, including both this tool and meet.google.com. This multi-profile behavior is a common source of confusion for users who test their microphone successfully in one profile and then open Meet from a different profile where the permission has never been granted.

Permission behavior after clearing Chrome browsing data

Clearing Chrome's browsing data, including site settings, removes all stored microphone permissions for every site in that profile. After clearing, this tool and meet.google.com both require fresh permission grants. Navigate to each site, allow the permission prompt, and verify in Chrome Settings that the permission appears under each site's entry. The Noise Floor Grade provides immediate confirmation that the re-granted permission is active: if the test runs without a permission error, Chrome has successfully recorded the new grant.

Meet audio quality after hardware confirms clean

Google Meet applies its own noise suppression and audio processing to the microphone signal after it leaves the OS audio stack³. If the Noise Floor Grade returns Good or Excellent but participants report poor audio quality in Meet, the issue is in Meet's processing rather than the hardware. Meet's noise suppression, when applied to a signal that is already clean, can introduce artifacts: metallic voice character, speech clipping on quiet consonants, and intermittent dropout on soft syllables. These artifacts are a direct result of the noise suppression algorithm applying aggressive processing to a signal that does not need it⁴, and they are audible to every participant on the call even though your local monitoring sounds clean.

When Meet's noise suppression degrades clean hardware

In Meet's settings, navigate to Audio and set Noise cancellation to Off. If voice quality immediately improves for participants, Meet's suppression was the source. A hardware Noise Floor Grade in the Good range (below −50 dBFS) is clean enough for Meet without suppression assistance. Reserve noise cancellation for environments where the Noise Floor Grade is Noisy or worse, where it provides genuine benefit rather than processing a clean signal that did not need treatment.

Before disabling suppression, confirm the hardware baseline is actually clean by running the Noise Floor Grade in the same Chrome window you use for Meet, because a hidden per-site block or a stale profile permission would otherwise present the same symptoms as over-processing. If the grade is Good or Excellent and participants still hear artifacts, suppression is the cause and turning it off is safe; if the grade is Noisy, rule out a Chrome permission block first and fix the room instead.

When to use this

Use this test before a Google Meet call when the pre-join screen shows no microphone input, or when participants report they cannot hear you despite your microphone appearing active.

Examples

Noise Floor Grade works. Meet permission was never granted for the new Chrome profile — profiles have independent permissions

Granted microphone permission for meet.google.com in new profile settings — Meet works

Noise Floor Grade works. Chrome update reset microphone permissions for meet.google.com

Re-granted permission in Chrome site settings for meet.google.com — resolved