Microphone Test Windows 11: Permissions, Levels and a Browser Check That Shows the Real Signal
A microphone test on Windows 11 fails for reasons that have almost nothing to do with the microphone. The device is usually fine. What breaks is one of the layers between the capsule and the application: the Windows privacy switch, the input selected as default, the driver's gain stage, or an exclusive-mode lock held by another program. This guide walks those layers in the order Windows applies them, then uses a browser test to confirm that the signal actually arrives. Everything runs locally, no driver is installed, and the level you see is the same stream a call app would receive.
Windows 11 checks two things before your browser gets a sample
Windows 11 treats microphone access as a permission, not a device property. The gate sits in Settings, then Privacy and security, then Microphone, and it has two independent levels. The first is global: "Microphone access" must be on, and Windows also exposes separate toggles for the system and for apps in some builds under the same page. The second is per application. A list of every program that ever requested the microphone appears below the master switch, and each entry has its own on or off state. Chrome, Edge, Firefox and Opera each appear as separate entries, because Windows does not treat "the browser" as one thing.
That structure explains the most confusing symptom of all: a working microphone that produces silence in one program while another hears it perfectly. If you denied the microphone once, the per-app toggle stays off until someone turns it back on, and the browser has no way to override the decision. The page asks for a stream, Windows refuses at the operating system level, and the request either fails outright or resolves to a stream of digital zeros depending on the browser version.
There is a second gate after that one, inside the browser itself. The site permission lives behind the padlock or the site-settings icon in the address bar, and it survives page reloads and browser restarts. A site that was blocked months ago stays blocked until you change it there. The order matters during troubleshooting: an operating system denial and a browser denial produce the same flat meter, so check the OS switch first, the site permission second, and only then start looking at hardware.
One detail that surprises people: the device names in the browser dropdown stay generic until permission is granted once. A list reading "Microphone 1" and "Microphone 2" is not a driver problem. It is Windows hiding labels from an application that has not been authorised yet.
The three places Windows 11 keeps microphone settings
Microsoft's support documentation points at one path for testing: Settings, System, Sound, Input, then the arrow next to the device to open its properties page, where the Start test button records a short sample that you can play back. That is the official flow and it does prove the hardware works, but it is only the first of three panels you will need.
The second is the classic Sound Control Panel, still reachable through "More sound settings" in Windows 11. Its Recording tab holds the parts the modern Settings app never exposed: the Levels tab with the input slider and, on many drivers, a Microphone Boost control that adds up to 30 dB of gain; the Listen tab with "Listen to this device", which routes your input to the speakers and gives you immediate confirmation that sound is moving; and the Advanced tab, which holds the default sample rate and two exclusive-mode checkboxes that cause a surprising share of quiet failures.
The third is Device Manager, useful when a device is not listed anywhere in Settings at all. A disabled microphone does not appear as an option in the browser dropdown, so the list looks short rather than broken. Enabling the device, or choosing "Show disabled devices" in the Recording tab, brings it back without a reboot in most cases.
| Where you look | What it controls | Typical symptom when wrong |
|---|---|---|
| Settings, Privacy and security, Microphone | Master switch and per-app access | Silence everywhere, or silence in one browser only |
| Browser site settings (padlock icon) | Permission for this site | Meter stays flat after an earlier block |
| Settings, System, Sound, Input | Default device, volume, official test | Wrong device selected, quiet recording |
| Sound Control Panel, Levels | Input level, Microphone Boost | Bar twitches at normal speaking volume |
| Sound Control Panel, Advanced | Sample rate, bit depth, exclusive mode | Stream fails to open or arrives silent |
| Device Manager | Enabled state, driver stack | Device missing from the browser list |
Running the browser test itself
The browser check answers a question the Windows test cannot: whether the signal survives the full path into an application. Windows records a sample and plays it back, which proves the microphone works. It does not tell you what a calling application receives after its own gain, format negotiation and echo cancellation are applied.
- Open the mic test page in the browser you actually use for calls.
- Press Start preview. If this is the first visit, allow the microphone at the prompt. If no prompt appears and the meter stays dead, you have a permission denial from an earlier session, and the padlock icon is where it gets fixed.
- Choose your microphone from the dropdown. On a laptop with a webcam, a headset and a dock you may see four or five entries, including a stereo mix and a virtual loopback. Pick each candidate and speak; only one moves.
- Talk at your normal distance and volume. The bar shows the smoothed RMS level, the percentage maps it onto a 0 to 100 scale, and the decibel figure beside it is the digital level in dBFS.
- Watch for two failure shapes rather than one number. A bar that pegs at 100 percent means clipping, and a bar that jitters near 10 percent means the gain stage is too low for the distance you work at.
- Press Stop. The stream closes, the analyser disconnects and the device is released, so the next application can open it.
Aim for peaks between -12 and -6 dBFS with ordinary speech. That leaves headroom for emphasis and keeps you well above the room's noise floor. If you cannot reach that range without shouting, the answer is almost always the input slider or the boost, not a new microphone.
Why the meter stays at zero on Windows 11
A flat meter on Windows 11 has a short list of causes, and most of them take under a minute to rule out. The useful habit is to work from the outside in: permission, then device, then gain, then contention.
The global privacy switch is off. Rare outside fresh installs and managed machines, but it happens after a Windows reset, and it kills capture for every program at once.
The per-app toggle is off for this browser. This is the most common single cause, and it appears after an accidental denial. The page will not even show a permission prompt, because Windows answers before the browser asks.
The wrong device is the default. Windows picks whatever arrived last, and a dock or a webcam microphone can take that slot silently. The dropdown in the test page lists every input, so a different device moving while the expected one does not is a quick confirmation.
The input level is at zero, or the device is muted in software. Both live in the Sound Control Panel. A hardware mute button on a headset produces exactly the same reading, and so does a keyboard mute key.
Another application holds the device in exclusive mode. Call clients, recorders, virtual cable drivers and some conferencing tools keep the endpoint open. The browser then receives a stream that carries nothing, or fails to open one. Closing the other program is the entire fix.
The selected format does not match. When the Advanced tab lists a sample rate the application cannot negotiate, the stream either opens silent or dies. Setting 16 bit, 48000 Hz is the safest common denominator for voice work.
Sample rate, exclusive mode and driver stacks
Windows 11 lets an application take exclusive control of an audio endpoint, and the two checkboxes on the Advanced tab decide whether that is allowed and whether such an application gets priority over shared access. The feature exists for low latency recording, and it behaves exactly as documented: while one program holds the endpoint, others either fail or get silence. If a microphone works in one app and not in another, exclusive mode is the first thing to inspect.
Format negotiation sits next to it. A 24 bit, 96000 Hz default on a USB interface looks impressive and works fine for the vendor's own console, while a browser asking for a 48 kHz stream may end up resampled, or refused depending on the driver. Setting the default format to 16 bit, 48000 Hz on the endpoint is the boring configuration that behaves consistently, and for speech there is nothing to gain above it.
The driver stack is the third moving part, and it is where vendor software matters. Realtek, Intel Smart Sound, Waves and Nahimic all insert their own processing between the capture device and the rest of the system. Their effects panels can apply noise suppression, gain normalisation or "voice clarity" that changes what every application receives, including a level meter. When a meter reading contradicts what you hear in headphones, check the vendor console before blaming either the browser or the hardware.
Finally, almost every laptop exposes an array rather than a single capsule. The array entry is the one to test if you use the built-in microphone, while a headset appears as a separate endpoint that only exists while it is connected. Testing the array and then joining a call with the headset plugged in tests two different devices, which is a common source of "it worked yesterday" reports.
Testing before Teams, Zoom and Discord
The value of a quick test is that it happens before the meeting, not during it. The sequence that catches nearly everything is three steps long: confirm the right endpoint is default in Windows, confirm the browser has permission and shows a moving level, then open the call app and speak once.
For Teams and Zoom the endpoint choice lives in the app, not in Windows, so a correct Windows default helps but does not guarantee anything. Discord makes the same choice in its own voice settings and adds automatic gain control and noise suppression on top, which is why the company's own microphone test can sound different from the browser reading. The usual advice applies: test with the processing off to see the raw signal, then turn it back on and accept that the app will shape your voice.
Bluetooth headsets deserve their own mention. In a call the headset leaves high quality stereo playback and switches to the hands-free profile, which carries narrow band audio in both directions. Sound quality drops as soon as an application opens the microphone, and the level meter in a browser can jump at the same moment. That is a profile switch, not a fault.
One habit makes all of this cheap. Two minutes with a browser test before an important call, on the device you plan to use, catches permission resets after updates, a dock that renumbered its inputs and a gain slider that a driver update moved. The test does not record anything and changes no system setting, which is why it is safe to run often.
Frequently Asked Questions
01Why does the browser see no microphone at all on Windows 11?
Either the global microphone switch in Privacy and security is off, or the device is disabled. The dropdown lists only what Windows exposes, so an empty list points at the operating system rather than the page.
02Where do I unblock a browser that I denied once?
Open the site settings from the padlock icon in the address bar and set the microphone entry to Allow, then reload. If that entry is missing, check the per-app list in Windows privacy settings as well.
03Should I use 16 bit or 24 bit for a microphone?
For voice calls 16 bit, 48000 Hz is the safest setting because every application and driver combination supports it. Higher settings help recording work, not speech, and they occasionally break format negotiation.
04Why is the level low even at maximum input volume?
Distance is the usual answer. At arm's length a typical laptop array produces a weak signal, and boosting gain mostly raises the noise floor. Speak closer before raising anything.
05Does an exclusive mode setting affect a browser test?
Yes. If another program holds the endpoint exclusively, the browser cannot open a usable stream. Closing that program or unticking the exclusive mode boxes solves it immediately.
06Why does my Bluetooth headset get quiet when the mic turns on?
The headset switches to the hands-free profile as soon as an application opens the microphone, and that profile carries narrow band audio. Using a different microphone for input keeps the headset in high quality mode.
07Can a browser test tell me whether my microphone is good?
It confirms the device works, shows the level in dBFS and reveals the noise floor of the room. Judging tone and detail needs listening, so a short recording played back through headphones is the honest last step.
08Does testing change my Windows audio settings?
No. The page opens a stream, reads it frame by frame and discards it. Nothing is written to disk, nothing is uploaded, and every system setting stays exactly where it was.
United Kingdom · SO reputation 7987 · Badges: 2🥇59🥈92🥉 · SO member since 2010