Chromebook Microphone Blocked? Check These Permission Layers

10 min read

Help Desk Geek is reader-supported. We may earn a commission when you buy through links on our site. Learn more.

Your Chromebook microphone is blocked, and a call or recording app cannot hear you. Check access in order: a physical switch if your model has one, ChromeOS microphone access, the affected app or website’s permission, and the selected microphone.

Quick Diagnosis

Fix #1: Check the physical microphone switch

Problem: The microphone fails in every app and website.

Symptoms: Calls cannot pick up your voice, even in apps that previously worked.

Why it happens: Some Chromebooks have a physical microphone switch. When it is off, changing a website’s permission will not make the microphone available. Not every Chromebook has this switch.

  • Look for a microphone switch on your Chromebook. If your model has one, set it to the position that enables the microphone.
  • Try the affected call or recording again.

Verify: If the app now picks up your voice, stop here. If your Chromebook has no switch, continue to the ChromeOS control.

Choose the Permission Layer for Your App

For a website or installed web app, check ChromeOS access and then Chrome’s site permission. For an Android app installed from Google Play, check that app’s Android permission. Linux apps use a separate Linux microphone control; see the note below. If your school or workplace locks a control, ask the administrator.

Fix #2: Turn on Chromebook-wide microphone access

Problem: The microphone is unavailable across apps and websites, or Chrome says a site is allowed but it still cannot use the microphone.

Symptoms: More than one service cannot hear you. A site’s Allow setting appears correct, yet access remains blocked.

Why it happens: ChromeOS has a Microphone access control above individual app and website permissions. Turning it off blocks microphone access for all services, regardless of a lower-level permission. Turning it on lets those permissions take effect; it does not grant every app access. See Google’s Chromebook privacy controls documentation.

  • Select the time at the bottom right of your Chromebook screen.
  • Open Settings > Privacy and security > Privacy controls.
ChromeOS Settings at Privacy and security > Privacy controls, with the Microphone access section visible
  • Turn on Microphone access if you want the affected service to use the microphone.
  • Return to the affected app or website and try its microphone feature.

Verify: If it works, no other permission needs changing. If only one app or site still fails, check that app or site next.

Common Issues and Solutions

Fix #3: Allow the affected app in ChromeOS

Problem: One app cannot use the microphone while other apps work.

Symptoms: The app reports that it cannot access the microphone, but Chromebook-wide Microphone access is on.

Why it happens: An individual app can be denied access even when the ChromeOS-wide control is on. Review the affected app rather than allowing every app on the Chromebook.

  • Open Settings > Privacy and security > Privacy controls.
  • In the microphone permission area, find the affected app and review its permission. The controls shown can depend on the app type.
ChromeOS Privacy controls showing Microphone access and app microphone permissions
  • If the app is one you trust and intend to use, change its microphone permission to allow access.
  • Reopen or retry the app’s microphone feature.

Verify: The app should be able to request or use the microphone. If it still cannot, check whether it is an Android app and follow Fix #4.

Fix #4: Review an Android app’s microphone permission

Problem: An Android app installed on your Chromebook cannot use the microphone.

Symptoms: Chrome websites work, but the Android app does not, or the app’s own permission prompt was denied.

Why it happens: An Android app has a microphone permission to review. Chrome’s website permission screen is not that app’s permission screen. ChromeOS privacy controls can direct you to the Android app permissions; the exact labels you see may vary with the app and ChromeOS version.

  • Open Settings > Privacy and security > Privacy controls.
  • Follow the Android app permission link shown there to the Android Preference Centre.
ChromeOS Privacy controls with Android app permission navigation
  • Find the affected Android app and open its permissions.
  • Review its microphone permission and allow access if you trust the app and need its microphone feature.
The affected Android app's permission screen on ChromeOS with its microphone control visible
  • Return to the app and try again.

Verify: Check whether that app can now hear you. If Chrome websites also fail, check the ChromeOS-wide control in Fix #2 before changing website permissions.

Fix #5: Change a website’s previous microphone denial

Problem: A website was denied microphone access and no longer asks.

Symptoms: The site says its microphone is blocked, or Chrome shows the site among those not allowed to use the microphone.

Why it happens: Chrome remembers a site-specific decision. Block prevents the site from using the microphone; Ask means the site can request permission when it needs access. A website set to Allow may still fail if Chromebook-wide access is off. Google explains Chrome’s microphone controls and site permissions.

  • In Chrome, open More > Settings > Privacy and security > Site settings > Microphone.
Chrome Site settings > Microphone on a Chromebook, showing the default microphone selector and site permission sections
  • Find the affected website in the section for sites not allowed to use the microphone.
  • Open that website’s entry and find its Microphone control.
Chrome site settings for Google Meet with the Microphone permission control
  • In that saved site entry, set its Microphone permission to Allow if you trust the site and want it to use the microphone. If you prefer to decide when it asks, remove the existing site exception so it can request permission again.
  • Refresh the website and try its microphone feature.

Verify: The site should be able to use the microphone if the physical switch, ChromeOS-wide access, and its Chrome permission all permit it.

If the page still reports a block after a change, try refreshing the page first; if that doesn’t help, restarting Chrome may also help before trying the site again.

Fix #6: Choose permission that lasts as long as you need

Problem: A website asks to use the microphone again after you already allowed it.

Symptoms: You approved the site during a previous visit, but another permission prompt appears.

Why it happens: Allow this time grants access for the current visit. Allow while visiting the site is the choice for a trusted site you want to use on future visits. Never allow denies its requests. An Ask setting is a prompt policy, not the same as Block.

  • Open the trusted website and start the feature that needs your microphone.
  • When Chrome displays the permission prompt, choose Allow while visiting the site if you want continuing access. Choose Allow this time if you want to decide again on a later visit.
  • Try the site’s microphone feature.

Verify: With continuing permission, the site should not need a new approval on each visit. If it does, review its entry under More > Settings > Privacy and security > Site settings > Microphone to see what Chrome has saved.

Fix #7: Select the intended microphone in Chrome

Problem: A website has microphone permission but hears the wrong device or no useful sound.

Symptoms: The problem began after connecting a USB headset, an external USB microphone, or a USB-C docking station, or the website shows the wrong microphone in its own audio controls.

Why it happens: Permission allows a site to use a microphone; Chrome’s default microphone setting determines which device it selects by default.

A calling website may have its own input selector and use a different microphone from Chrome’s default. Check the site’s device menu as well; changing Chrome’s default alone may not change the microphone already selected by that site.

  • In Chrome, open More > Settings > Privacy and security > Site settings > Microphone.
  • Use the default microphone selector to choose the device you intend to speak into.
Chrome Site settings > Microphone with the default microphone selector and site permission sections visible
  • Return to the website. If it has an audio or device menu, check its microphone selection there too.
  • Try speaking again.

Verify: The website should respond to the microphone you selected. If it does not, test that microphone in another trusted app or site before assuming the permission is the cause.

Linux apps: Check the separate microphone permission

If you use an app inside an existing Linux development environment, Google documents a separate Allow Linux to access your microphone control. Open Settings > About ChromeOS > Developers > Linux development environment, then review that control. You do not need to enable or install Linux to fix a website or Android app.

Only enable this access if you trust the Linux apps you use: Google notes that permissions shared with Linux are available to all Linux apps in its shared environment. If the control is managed, contact your administrator. See Google’s Linux microphone instructions.

Microphone Messages and Settings at a Glance

What you seeWhat it meansCheck next
Microphone access is off in ChromeOSApps and services cannot use the microphoneTurn it on in Settings > Privacy and security > Privacy controls
A site is set to Block or appears among sites not allowedChrome has a site-specific denialOpen the site’s entry under Site settings > Microphone
A site is set to AskChrome may prompt when that site requests the microphoneRespond to the prompt for a site you trust
Allow this time appears in a promptAccess applies to the current visitChoose Allow while visiting the site if you want continuing access
A site is Allow but still reports a microphone blockAnother permission layer may be stopping itCheck the physical switch, ChromeOS-wide access, and the affected app permission
Access works but the wrong mic is usedChrome or the website may have selected another inputCheck Chrome’s default microphone and the website’s device menu

A website’s own warning may use different words. Use the setting or prompt you can see in Chrome to decide which permission to check.

When a School or Work Chromebook Controls the Setting

If a microphone setting is restricted on a managed Chromebook, contact your school or workplace administrator. Tell them which app or website needs access and which control you cannot change. A local site permission cannot override a ChromeOS-wide restriction.

If the Permissions Are Allowed but the Microphone Still Fails

Stop changing permissions once the relevant switch and controls are enabled. If the microphone still fails, its cause has not been established as a permission issue.

As a general troubleshooting step, trying a different trusted app or a known working USB headset may help you see whether the problem seems to follow one service or one microphone, though this isn’t a guaranteed diagnosis. If the issue follows the built-in microphone across services, ask the Chromebook maker or your administrator for help with a possible device fault.

Keep Microphone Access Under Control

Allow the app or site you actually use, and leave untrusted sites blocked or set to ask. If you only need a website’s microphone once, choose Allow this time. When a trusted site stops working, check the Chromebook-wide control before changing its saved Chrome permission.

Wrapping Up

Fix #2 is the best place to look when every app says the Chromebook microphone is blocked; Fix #5 is more useful when only one website fails. If all relevant permissions are allowed and the microphone still does not work, treat that as a separate device or app problem rather than another permission to uncover.