Chrome not picking up the microphone — Google Meet shows “no microphone found,” voice search doesn’t activate, or the site asks for mic permission but nothing records — runs through four distinct permission layers. All four have to be correct for Chrome to use the microphone. The most common failure is permission being set to “Block” for a specific site, but knowing which layer is the problem saves time. This fits into the wider topic we cover in our Google Chrome Errors.
The four layers, in order from most to least common cause:
- Site-level permission in Chrome (blocked for that specific URL)
- Windows privacy settings for Chrome (microphone access denied to the browser)
- Chrome’s default microphone device selection (wrong device chosen)
- Driver or hardware issue preventing any application from using the mic
Layer 1: Site-level Chrome permission
Click the lock icon (or microphone icon) in Chrome’s address bar → check what it shows for Microphone. “Blocked” means you or Chrome previously denied mic access for this specific site. Change it to “Allow” → reload the page.
For sites where the permission prompt appeared and was dismissed (without clicking Allow or Block): the site may not prompt again automatically. Chrome Settings → Privacy and security → Site settings → Microphone → look under “Not allowed” for the site → click the trash icon → reload and grant permission when it prompts again.
Layer 2: Windows microphone privacy
If Chrome itself is blocked from accessing the microphone at the Windows level: site-level Chrome permissions are irrelevant — Chrome can’t access the mic regardless of what the site permission shows.
Settings → Privacy and security → Microphone → “Let desktop apps access your microphone” → On. This specific toggle covers Chrome and other non-Store applications. Also confirm the top-level “Microphone access” is On and “Let apps access your microphone” is On. All three layers of this Windows toggle need to be enabled.
Layer 3: Default microphone device in Chrome
Chrome has its own microphone device selection separate from Windows’ default. If Chrome is trying to use a microphone device that doesn’t exist or isn’t connected — a previously-used USB headset that’s now unplugged, for example — it fails even though another working microphone is available.
Chrome Settings → Privacy and security → Site settings → Microphone → the dropdown at the top shows the current device. Change it to “Default” or select the correct active microphone. After changing: reload any tabs using the microphone for the change to apply.
Layer 4: Hardware and driver
If the microphone doesn’t work in Chrome or any other application: the issue is at the system level. Right-click the speaker icon → Sound settings → Recording tab → speak into the microphone — the green bar should move. If it does: Chrome has the right mic but permission is blocking it (layers 1-3). If the bar doesn’t move at all: the microphone hardware or driver needs attention (see our full microphone troubleshooting guide for the driver and hardware steps).
Site-specific Chrome microphone prompts not appearing
If a website that needs the microphone doesn’t ask for permission: either permission was already granted (check the lock icon — it should show microphone with a green indicator), or it was previously blocked (lock icon shows blocked), or the site isn’t triggering the permission request correctly (JavaScript issue on the site).
For sites where the prompt should appear but doesn’t: try the site in a private window (permission state is fresh) or manually grant mic access: lock icon → Site settings → Microphone → Allow.
Chrome microphone in corporate environments
Chrome Enterprise policies can restrict microphone access across all sites or for specific domains. chrome://policy shows active policies — look for AudioCaptureAllowed or similar. If policy restricts mic access: IT controls this and local changes won’t persist. Request an exception for specific video calling services if microphone access is needed for work.
Our microphone troubleshooting guide covers the full Windows-level diagnostics including the recording test, driver reinstall, and exclusive mode settings that affect microphone behaviour across all applications. Chrome’s microphone documentation covers the exact permission reset steps for specific sites and the chrome://settings/content/microphone page that shows all current site permissions at a glance.
Microphone works in some Chrome sites but not others
Microphone permissions in Chrome are per-site. A site where you previously clicked “Allow” retains that permission until cleared; a site where you clicked “Block” retains that block. If mic works on Google Meet but not on Zoom Web: Zoom’s site permission may be set to Blocked while Meet’s is Allowed.
Navigate to chrome://settings/content/microphone — this page lists all sites with non-default microphone permissions, divided into “Allowed” and “Not allowed” sections. Review and adjust permissions for any site that shouldn’t be blocked.
Microphone blocked in Incognito
Chrome’s default in Incognito: microphone permission is cleared for all sites (fresh session). The first time a site in Incognito asks for mic access, Chrome prompts. But: microphone access in Incognito is also governed by the Windows privacy settings. If Windows blocks Chrome from accessing the microphone: Incognito also fails, and the Chrome permission prompt either doesn’t appear or immediately returns “blocked.”
If mic works in regular Chrome but not Incognito for the same site: Incognito’s fresh permission state means you need to grant permission again — this is expected. If mic fails in both regular and Incognito: it’s a Windows-level block (Layer 2 above).
Cached permission blocking a new microphone device
Scenario: you replaced a headset with a new one. The new headset’s microphone works in Windows (shows in Recording tab) but Chrome’s voice features don’t use it. Chrome may have cached the old device’s identifier and is still trying to access the unplugged headset.
Fix: Chrome Settings → Site settings → Microphone → change from the old device name to “Default” or the new device name. Also clear Chrome’s media device cache: chrome://settings/clearBrowserData → check “Cookies and other site data” → Clear (this also clears media permissions, so you’ll re-grant them on sites you use).
Google Meet-specific microphone issues
Google Meet is one of the most common places Chrome microphone problems surface. Meet has its own audio device selector in the meeting (three dots → Settings → Audio) separate from Chrome’s default microphone. If the Chrome default is set to a working device but Meet’s internal selector is on a different or disconnected device: the meeting shows “no microphone” even though Chrome itself has the device.
In a Meet meeting: click the three dots → Settings → Audio → Microphone → select the correct device. This per-meeting selection overrides Chrome’s default for the duration of that call.
Web Speech API and Chrome microphone access
Websites using the Web Speech API (voice search, dictation, speech recognition) require microphone access through a slightly different permission path than video calling. Some sites request microphone only through the Web Speech API, which can behave differently from the standard getUserMedia() request that video calling uses.
If voice features on a site don’t work but video calling does: the site may use a different API. Check the lock icon for both microphone and notification permissions — some voice-enabled sites request notification permission alongside microphone access for push-to-talk features.
Extensions interfering with microphone access
Privacy extensions (Privacy Badger, uBlock Origin in aggressive mode, browser VPN extensions) sometimes block getUserMedia() requests that microphone access requires. If microphone access fails in regular Chrome but works in Incognito (where extensions are disabled): an extension is the culprit. Disable extensions one at a time to identify the conflict. The responsible extension usually has settings to whitelist specific domains (like meet.google.com or zoom.us) for microphone access.
Checking Chrome’s actual microphone access in real time
While on a site that needs the microphone: look for a camera/microphone icon in Chrome’s address bar (right side). A red dot or “blocked” indicator means Chrome is actively preventing mic access for this site. Clicking this icon shows the current permission state and lets you change it without navigating through settings. This real-time indicator is the fastest way to confirm what’s happening during an active meeting or voice recording session.
Microphone latency and quality in Chrome
If the microphone works (green bar moves in Windows recordings tab, permission granted in Chrome) but the audio quality in calls is poor: the issue isn’t permission-related — it’s audio processing. Chrome applies echo cancellation and noise suppression by default for web audio. Some microphone types (particularly condenser microphones and some USB mics) work better without Chrome’s processing.
No direct setting to disable Chrome’s audio processing from the browser UI exists for regular users. But: meeting applications (Zoom, Teams web, Google Meet) each have their own audio processing toggles that can suppress Chrome’s processing by using a hardware mode. In Google Meet: Settings → Audio → “Noise cancellation” toggle. Disabling the app-level processing sometimes improves audio quality for microphones that interact poorly with the double-processing (Chrome + Meet both applying noise suppression).
| What you see | Layer failing | Fix |
| Chrome prompts for mic, then shows blocked | Site permission blocked | Address bar lock icon → Microphone → Allow |
| No prompt appears at all | Windows privacy block or already granted | Windows Settings → Privacy → Microphone; check lock icon |
| Works on one site, not another | Per-site permission difference | chrome://settings/content/microphone → adjust site |
| Selected mic but wrong device used | Chrome’s default device stale | Chrome Settings → Site settings → Microphone → correct device |
| Doesn’t work in Chrome or any app | Hardware/driver level | Windows Recording tab test → driver investigation |
Chrome microphone troubleshooting works best when you start from the correct layer. The address bar lock icon and Recording tab test together take 60 seconds and tell you definitively whether the problem is in Chrome’s permission system or lower in the stack. From there, every fix is targeted rather than speculative.
A practical note for remote workers who join many different video call platforms: keeping chrome://settings/content/microphone bookmarked provides a one-click view of all microphone permissions across all sites, making it fast to check and adjust site permissions without navigating through Settings menus. Reviewing this page before an important call takes 30 seconds and catches blocked permissions before they cause a “my mic doesn’t work” moment mid-meeting.
Microphone access after Chrome update
Chrome updates sometimes reset microphone permissions for specific sites or change how the permission prompt behaves. If microphone stopped working on a site immediately after Chrome auto-updated: check the site’s permission in the address bar — the update may have moved it from “allowed” to “ask” or “blocked.” Re-granting permission after a Chrome major version update is occasionally necessary for sites where the permission handling changed.
Troubleshooting with chrome://media-internals
For advanced diagnosis: navigate to chrome://media-internals/ in Chrome → then trigger the microphone access on the failing site → the Media Internals page logs audio device access attempts, showing the device names Chrome tries to use, whether getUserMedia() succeeds, and any errors in the audio pipeline. This is a developer-oriented tool but its output is readable enough to confirm whether Chrome is finding the device, accessing it, and whether any processing errors occur.
For users who regularly switch between multiple microphone devices (a USB headset for calls, a standalone microphone for recording, a built-in laptop mic for casual use): setting Chrome’s default to “Default” rather than a specific device name prevents the “wrong device” problem automatically. When set to “Default,” Chrome uses whichever device Windows has designated as the default recording device at that moment — making device switching seamless without needing to update Chrome’s settings each time.
Understanding that Chrome’s microphone permission system is intentionally multi-layered (Windows privacy, then Chrome’s global setting, then per-site setting, then the specific device) is what makes troubleshooting systematic rather than frustrating. Each layer was added to give users more granular control — but it means there are more places for something to go wrong. The framework of checking from outermost (Windows) to innermost (site-specific) ensures you don’t skip a layer and spend time on site permissions when the Windows-level block is the actual problem.
One more edge case: if Chrome microphone access works in a personal browser profile but not a work profile (or vice versa), the profiles have independent permission states. Chrome profiles maintain completely separate permission databases. The work profile may have the site blocked, the Windows privacy settings may be different for that profile context, or the microphone device selection differs between profiles. Checking all three layers in the specific profile where the mic fails — not the one where it works — is essential for diagnosing profile-specific microphone problems. Our guide on Chrome Autofill Stopped Working covers an adjacent issue.
Lastly: if a meeting or recording session is actively in progress and the microphone suddenly stops working mid-session — rather than failing to start — the cause is usually the device becoming disconnected or Windows switching the default device mid-session. Chrome doesn’t always detect these changes automatically. Refreshing the tab (F5) or toggling the microphone off and on within the meeting application reconnects Chrome to the current default device and restores audio without needing to end the session. See also Chrome Dark Mode Not Working for a related case.
