Microphone Not Working on a Chromebook: How to Fix It

A microphone not working on a Chromebook is never a driver problem, because ChromeOS has no traditional audio drivers to break. The block is always a permission, and ChromeOS stacks several of them. The system chooses the input device and sets its gain. Chrome then allows or denies each website on its own. Android apps hold a third permission, separate from the first two. A managed school or work Chromebook adds a fourth gate that an administrator can lock by policy. Any one of them, when closed, silences your voice with no error. This guide works through the stack from the outside in. Begin with our microphone test and pick your input in Quick Settings. Then check the Chrome site permission, the Android-app permission, and finally the managed-device policies behind most classroom Chromebook failures.

Chromebook Microphone Not Working: Quick Fix Checklist

✓	Test with our microphone test and pick the input in Quick Settings.
✓	Allow the site in Chrome (padlock › Microphone or chrome://settings/content/microphone).
✓	For Android apps, allow Settings › Apps › [app] › Permissions › Microphone.
✓	On a school or work Chromebook, check that an administrator has not blocked the mic.
✓	Restart the Chromebook.

Test your Chromebook's microphone in under a minute

Confirm that the microphone captures sound before you change any setting. The fix for "no signal" differs completely from the fix for "signal, but nobody can hear me." A live input meter gives the fastest honest answer. It reacts to your voice in real time. A record-then-play-back loop hides latency and device-selection mistakes, so avoid it here. Open our online microphone test and allow access when Chrome asks. Now speak normally. If the level indicator moves as you talk, the microphone hardware is fine. The problem then sits in a permission or in one specific app. If the meter stays flat, the signal is blocked or the wrong input is selected. The sections below show you exactly where to look.

Test Your Microphone →

ChromeOS governs the input device in one main place. Click the status area, the clock at the bottom-right corner of the screen. Quick Settings opens. Click the arrow next to the volume slider to reveal the audio panel. That panel lists every input and output the Chromebook can see. Choose your microphone under Input, then drag the input-gain slider up. Speak, and watch the level indicator beside the slider react. A moving indicator here proves ChromeOS receives a signal from that device. Suppose the indicator moves but a website still hears nothing. You have then proven the fault sits in Chrome or in one app, not in the device. The table maps every place a Chromebook governs the microphone. It also states what each place controls.

Layer	Where to set it	What it controls
ChromeOS input	Status area › arrow beside the volume slider › Input	Which device ChromeOS listens to, and its gain
Chrome site permission	Padlock or tune icon in the address bar › Microphone › Allow	Whether one website may use the microphone
Chrome default behaviour	chrome://settings/content/microphone	The site-wide default, the allow and block lists, and the default input
Android app permission	Settings › Apps › [app] › Permissions › Microphone	Whether an installed Android app may record

Why a working microphone still goes silent on a Chromebook

Chrome's per-site permission is the number-one culprit

Most microphone use on a Chromebook happens inside Chrome. Google Meet, the web version of Zoom, and our own tester all run as websites. Each site must be granted the microphone separately. This per-site consent causes more "broken" Chromebook microphones than every hardware fault combined. The trap is that a denied site simply receives silence. A single accidental click on Block sets it, and no error follows. The tell-tale sign sits in the address bar. A padlock or a small tune icon appears at the left of the web address. Click it, find Microphone, and set it to Allow. Chrome reloads the page, and the site may ask again. The broader controls live at chrome://settings/content/microphone. That page holds the site-wide default, the full allow and block lists, and the default input device Chrome hands to websites. A site stranded on the block list will never work until you remove it there. Our Chrome microphone guide covers these controls in full. The Google Meet and Zoom guides show where each service adds its own in-call mute on top of the browser permission.

The "wrong device" trap with USB and Bluetooth

A Chromebook switches inputs when you connect new hardware. That helpfulness is a frequent source of confusion. Plug in a USB microphone or a headset, and ChromeOS may promote it to the default input at once. You then speak into the built-in microphone while the system listens to the USB device. A Bluetooth headset makes this subtler. It can capture in a low-quality call mode, or drop its microphone while still playing audio. Suspect device selection first whenever the microphone works only "sometimes." Open the audio panel from the status area and confirm which input carries the tick. Choose the device you actually intend to use. Then speak and watch the level indicator to confirm the choice. An external USB microphone must be selected here even after it is plugged in. ChromeOS will not always switch to it on its own.

Android apps ask for the microphone separately

Many Chromebooks run Android apps from the Play Store. An Android app does not inherit the Chrome or ChromeOS permission. It carries a permission of its own, exactly as it would on a phone. The Android version of Zoom can therefore be muted while the website version works perfectly. You grant this access at Settings › Apps › [app name] › Permissions › Microphone. Set the app to Allow, then relaunch it. Our Android microphone guide explains the same permission model in detail. When an app and its website behave differently on the same Chromebook, this separate Android layer is usually the reason.

Fixing it, from the most common cause down

Work through these fixes in order. Do not jump to the dramatic ones. The sequence is deliberate. It resolves the most cases first, with the least disruption. Site permissions and device selection together account for most Chromebook microphone failures. Only then does the sequence escalate to restarting or resetting the device. After each change, return to the microphone test or the ChromeOS level indicator. Re-check for a signal before moving on. That way you always know which step made the difference. The matrix below pairs each common symptom with its likely cause and its fix.

Symptom	Likely cause	Fix
One website hears nothing	The site is blocked in Chrome	Padlock icon › Microphone › Allow, or clear it at chrome://settings/content/microphone
Tester works, one app does not	The app points at the wrong input	Select the correct microphone inside that app's own audio settings
An Android app stays muted	The app's own permission is denied	Settings › Apps › [app] › Permissions › Microphone › Allow
Level indicator never moves anywhere	The wrong input is selected, or the gain is at zero	Status area › arrow beside volume › pick the input and raise the gain
Microphone dead in every app and site	A school or work policy has disabled it	Contact the administrator; the block cannot be overridden locally
No microphone in Guest mode	Guest sessions restrict some hardware	Sign in with a normal account to test the device

Allow the site, then check Chrome's defaults

Start where most failures live, inside Chrome. Click the padlock or tune icon in the address bar for the site that cannot hear you. Set Microphone to Allow and reload the page. If the icon offers no microphone entry, the site has not requested access yet. Open chrome://settings/content/microphone to see the wider picture. Confirm the default is set to ask, not block. Scan the block list for the site and remove it if present. Check the default input device named at the top of that page. Chrome hands that device to every website, so an outdated choice here mutes them all at once. This single page resolves the majority of Chromebook microphone complaints.

Select the right input and raise the gain

Return to the audio panel from the status area with permissions confirmed. Click the arrow beside the volume slider. Select the microphone you intend to use under Input. Do not trust whatever ChromeOS chose. Speak, and watch the level indicator. If it barely moves, drag the input-gain slider up. Disconnect any input you are not using. An idle Bluetooth headset will hold the default slot and leave you talking into nothing. Many apps also keep their own input selector. It overrides the ChromeOS choice entirely. So if the level indicator reacts but the app does not, open that app's audio settings and point it explicitly at the right device.

When a managed Chromebook blocks the microphone

School and work Chromebooks answer to an administrator. A device policy can disable the microphone or the camera outright. This is a very common cause on student devices, and it is deliberate. No local setting will override it. The signs are consistent. The microphone fails in every website and every app at once. The ChromeOS input panel may show no usable device, or the level indicator stays dead everywhere. A managed device usually displays a note that an organisation manages it, often on the sign-in screen or in Settings. If you see that note and the microphone is dead system-wide, suspect policy first. The only fix is to ask the administrator to relax the restriction. Time spent on permissions and resets will not help while the policy stands.

Restart, sign out, then Powerwash as a last resort

Suppose permissions are granted, the right device is selected, and the input still will not respond. A simple restart clears most stuck audio states on ChromeOS. Sign out and back in next, which reloads your session cleanly. Test the microphone in Guest mode as a diagnostic. A device that works in Guest mode but not in your account points to a per-account setting or a browser extension. A Powerwash is the final option. It resets the Chromebook to factory condition and signs every account out. Reserve it for a genuine software fault that nothing else resolves.

Warning: A Powerwash erases all local data and accounts on the Chromebook and returns it to factory settings. Files saved only on the device are lost, though anything synced to your Google account remains safe. Back up local downloads first. On a managed school or work device the option may be blocked, and it will not remove an administrator's policy. Use it only as a last resort.

Keeping your Chromebook's microphone reliable

A few habits keep the microphone working once it is back. Review the site list at chrome://settings/content/microphone from time to time. Remove sites that have no reason to listen. This tightens both reliability and privacy. Keep ChromeOS current, because Google ships regular audio and Bluetooth fixes through automatic updates. When you rely on a USB microphone, select it in the audio panel and confirm the level indicator moves. ChromeOS will not always switch to it for you. When the same microphone must work in a website, an Android app, and a call, test it in each place. A microphone that is flawless in our tester can still be blocked one layer up, in a single site or a muted Android app. On a school or work device, remember that the administrator's policy sits above every setting you control.

Frequently Asked Questions

Where do I select the microphone on a Chromebook?

Click the status area, the clock at the bottom-right of the screen. Click the arrow next to the volume slider to open the audio panel. Choose your device under Input and raise the gain. The level indicator beside the slider confirms that ChromeOS hears you.

Why does my school Chromebook microphone not work?

A managed Chromebook follows an administrator's policy. That policy can disable the microphone across every app and website. You cannot override it with any local setting. Ask your school or work IT administrator to relax the restriction.

Why does a website on my Chromebook say the microphone is blocked?

Chrome grants microphone access to each site separately. Click the padlock or tune icon in the address bar, then set Microphone to Allow. You can also clear a blocked site at chrome://settings/content/microphone. Our Chrome guide covers these controls in full.

Why does my Android app on the Chromebook stay muted?

Android apps keep their own microphone permission, separate from Chrome. Open Settings › Apps › the app › Permissions › Microphone and set it to Allow. Relaunch the app afterwards. The website version of the same service uses a different permission entirely.

How do I test my Chromebook microphone without recording anything?

Use a live meter rather than a recording. Our online microphone test shows your input level in real time in Chrome. The ChromeOS audio panel shows the same level beside the input slider. Both confirm the microphone captures sound without saving a file.