A Google Meet microphone can remain unavailable even when the site’s permission is allowed. The operating system may separately prevent the browser from accessing audio input. Check that layer only after confirming the intended microphone and Meet’s own site permission, so the investigation stays focused.
Identify the affected browser
Confirm whether the meeting runs in Chrome, Edge, Firefox, Safari, or the Meet web app. Use your operating system’s privacy settings to inspect microphone access for that application. The exact controls differ by platform and version, so follow the relevant operating-system help linked from Google’s audio guidance rather than copying instructions for another device.
Allow the required application
Enable the appropriate browser access when your organization permits it. Some systems distinguish application permissions from broader device microphone access. Check the actual setting labels and any management notice. Do not disable endpoint protection or modify unrelated privacy controls to make an unavailable switch editable.
Repeat the Meet test
Return to the meeting’s audio settings, select the intended input, and speak while watching its meter. If the operating system requests an application restart, save work and warn participants before following that instruction. A microphone working in a separate recording application does not prove that the meeting browser has the same access. Conversely, allowing the browser does not unmute a hardware switch or a host-controlled meeting restriction. Record which permission changed and whether the input meter now moves. If policy blocks the required access, ask the administrator for an approved meeting alternative rather than repeatedly changing settings that do not govern the browser.
References
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.