Microphone Test No Sound: 4 Fixes That Actually Work

Last reviewed 2026-05-03. If your browser microphone test opens but the level meter stays flat while you speak, the mic is rarely broken - one of four causes below is far more likely. Walk the list top-down; each fix takes under a minute.

Fix 1 - Browser permission was denied or stale

The browser is the closest layer to the test page, so its permission state is the most common cause of a flat waveform. The browser may show that the page is "allowed" while still holding a stale permission record from a different network or after a profile sync.

Chrome / Edge: click the lock icon (or "Site information") in the address bar → Microphone → pick Allow, then reload the page. If the dropdown shows Microphone: Block, switch to Allow and reload.

Safari (macOS): Safari menu → Settings for This Website → Microphone: Allow. Safari does not surface the request through the address bar, so changing it through the menu is the only path.

Firefox: click the lock icon → Connection secure → More information → Permissions → clear "Use the Microphone". Reload the page so Firefox re-asks fresh.

If the address-bar icon shows the mic is allowed and the meter is still flat, the browser permission is fine; move to Fix 2.

Fix 2 - Operating-system muted the microphone

Modern OSes maintain a master toggle that overrides every browser permission. macOS introduced this in Mojave; Windows 10 added it in 1903. A flat meter with the browser permission already set to "Allow" almost always means the OS toggle is off.

macOS: System Settings → Privacy & Security → Microphone. Your browser must be toggled on. If it is not in the list, open the microphone test once and macOS will add the entry. Also check the menu-bar Control Center for an orange microphone dot - the OS shows it whenever an app is holding the device.

Windows 11 / 10: Settings → Privacy & security → Microphone. Enable both Let apps access your microphone and Let desktop apps access your microphone. Both flags must be on - the second one covers Chrome, Edge, and Firefox on Windows. Confirm Microphone access at the top of the page is also On.

iOS / iPadOS: Settings → Safari → Microphone → pick Ask or Allow. iOS keeps the mic permission per-site; clearing site data resets it. Also check the small orange dot at the top of the screen - if it is missing while the test runs, iOS has not granted the mic to the page.

Android (Chrome): Settings → Apps → Chrome → Permissions → Microphone → Allow only while using the app. The Android setting overrides the in-browser Allow when the app-level toggle is off.

Fix 3 - Another app is holding the microphone

Microphones expose a single capture stream on most consumer drivers. The first process that opens it gets exclusive access; every later request gets silence because the device is "busy" but not "blocked". Meeting clients and virtual-mic drivers are the most common culprits.

Quit / kill the holder: close Zoom, Teams, Google Meet, Webex, Discord, OBS Studio, Krisp, NVIDIA Broadcast, VoiceMeeter, Loopback, and any DAW (Audacity, GarageBand, Logic, Reaper) that may have left a background stream. On macOS, a Force Quit of the app releases the mic within two seconds; on Windows, ending the process in Task Manager does the same.

Confirm release: macOS shows an orange dot at the top of the screen and an entry in Control Center while any app is holding the mic. Windows 11 shows a microphone icon in the system tray. iOS / iPadOS show the orange privacy dot. If the indicator stays on after every meeting client is closed, a virtual-mic driver is still loaded - reboot to fully clear it.

Re-test: reload https://freetoolonline.com/microphone-test.html. The meter should respond within one second of the page granting permission and you speaking.

Fix 4 - Hardware mute, function key, or Bluetooth-headset auto-pair

The last layer is hardware. Many USB headsets and webcams ship with a physical mute switch on the cable or earpiece; some laptops route the same toggle through a Function-key. Bluetooth headsets add a fourth failure mode: the OS may auto-pair to a different device than the one you intended to test.

USB-headset mute: look for a small switch or button near the inline mic on the cable. It is usually labelled with a microphone icon and a slash. Toggle it off and re-test. The level meter should jump immediately. Some headsets also mute on a long-press of the volume button - check the manual.

Laptop function key: Lenovo, Dell, and HP laptops have an Fn + F-key shortcut (Fn + F4 on most ThinkPads, Fn + F1 on some Dells) that toggles the integrated mic at the firmware level. Press it and re-test. The mic LED on the keyboard usually lights when the mic is muted at the firmware level.

Bluetooth-headset auto-pair conflict: when two Bluetooth headsets are paired, macOS and Windows may auto-select the one that was paired most recently, even if it is not the one in your ear. Open System Settings → Sound → Input (macOS) or Settings → System → Sound → Input (Windows) and confirm the active mic is the one you expected. Switch input device if needed; the test will pick up the change immediately.

USB-hub power issue: some USB-C hubs under-power their downstream ports under load, dropping the mic intermittently. Plug the headset directly into the laptop and re-test - if the mic comes back, the hub is the cause.

Still no sound after all four? - the diagnostic flow

1. Try a second site. Open mictests.com in the same browser session. If that site also shows a flat meter, the cause is still upstream of the page (browser / OS / app / hardware).
2. Try a second browser. If Chrome is flat but Safari shows the meter respond, the cause is browser-level (extension, profile, or a stale permission). Reset Chrome site settings or use a guest profile.
3. Try a second user account. Switch to a freshly-created OS user and open the microphone test. If it works there, the cause is in your user profile (a permission entry, a browser extension, or a virtual-mic driver registered for your user).
4. Try a second machine. If a phone or tablet shows the mic test working immediately, the failing machine has a hardware or driver issue. Open Device Manager (Windows) or System Information → Hardware → Audio (macOS) and look for the microphone under Input.

The four steps narrow the cause from the test page outward to the hardware in under five minutes.

What about camera-test "black screen" issues?

The same four-layer model applies to the camera test: browser permission, OS-level Privacy & Security toggle, another app holding the device, hardware shutter or BIOS toggle. If a video call is failing entirely, run both the camera test and the microphone test in the same browser session - if both come back working, the call client itself is the cause; if only one fails, the test that came back broken pinpoints the layer. The dedicated walkthrough is at Camera test black screen: 4 fixes that actually work.

FAQ

The OS shows the orange privacy dot while the meter is flat - what does that mean?
The dot means the OS has granted mic access to the active page; the silence is downstream of the OS layer. That points to Fix 3 (another app holds the actual stream) or Fix 4 (hardware mute or wrong input device).

Why does the meter respond to keyboard typing but not to my voice?
The mic is working but is too far from your mouth or pointed away. Move the mic within 15 cm and re-test. If you are using a laptop's built-in mic, it is on the screen bezel - speak toward the screen, not toward the keyboard.

Bluetooth headset connected but the meter is flat - is the headset broken?
Almost never. Bluetooth devices have a separate SCO profile for two-way audio and an A2DP profile for one-way listening. If the OS has picked A2DP, the mic is unreachable even though playback works. Switch to "Headset" mode in the OS sound settings or call settings inside the browser to force SCO.

The test works but the recording on the call still has no audio - same fix?
No - that is meeting-app routing, not test failure. Inside the call client (Zoom / Teams / Meet) open audio settings and pick the same mic the browser test uses. The test confirms the mic and OS layers; the call client picks its own device.

Want a complete pre-call checklist instead of debugging?
Read How to check your webcam and microphone before an interview for the 5-minute pre-call run-through, or Device test checklist for remote work for the weekly cadence that catches a failing mic before a call rather than during one. To understand what the test itself confirms (and what it cannot), read Microphone test online: what it actually checks.