Microphone Test Shows Volume 0: Diagnose Missing Input

Essential answer

A microphone test that stays at volume 0 means the page is not receiving a usable audio signal from the selected device. On Windows 11 and most browsers, this is usually one of three conditions: the wrong microphone is selected, browser or system microphone access is blocked, or the chosen device is muted, unplugged, or not producing a signal. The same fixed 0 reading can also appear when the browser receives no permission for microphone capture.

Check input selection first

The test only measures audio reaching the input currently selected in the browser. A headset microphone, a webcam microphone, a USB audio interface, and the computer's internal microphone are separate inputs. Selecting the webcam video is not the same as selecting the webcam's microphone.

• Look for the microphone or input selector on the test page and choose each available device in turn.
• If the page allows changing the input without restarting, watch the volume meter after each selection. A 0 reading on one input tells you only that the selected input supplied no signal; it does not prove another microphone is faulty.
• If a new input shows activity, the previous input was wrong, muted, disconnected, or inaccessible.
• If no input shows activity, permission or system routing is more likely.

Check browser permission

A blocked microphone permission can make the test keep a 0 reading because the page never receives capture data. The permission may have been denied in an earlier session and remembered by the browser.

• Reload the test page and approve the microphone prompt if it appears.
• Check the site permissions in the browser and set microphone access to allow for that test page.
• Make sure the correct device is allowed where the browser lists input choices.
• Retest after changing the permission. If the meter responds, access was the cause.

Check Windows 11 input settings

Windows 11 has separate settings for system access, app access, and the selected input. A device may be visible to Windows but denied to the browser, or shown as the default but not producing a signal.

• Confirm the microphone is enabled under Windows sound input settings.
• Confirm desktop apps are allowed to access the microphone; some Windows configurations treat browser capture under app-level microphone permission.
• Select the device you are testing and check its input level. Speak while watching the Windows input indicator. If the indicator moves, the device is producing a signal in Windows.
• If the Windows indicator stays at 0, the selected device is getting no usable signal. Check its mute switch, physical connection, power, or driver status next.

The Windows reading is not proof of what a particular browser or test page receives. It shows whether the device is producing audio within Windows. A moving Windows meter with a still-zero browser test points back to browser permission or browser input selection.

Check physical controls and connections

If Windows also reports a static 0 input, the most reversible checks are physical. These apply mainly to headsets, USB microphones, webcam microphones, and dedicated audio interfaces.

• Check any hardware mute button or swivel mute on the microphone or headset cable.
• Reseat a USB microphone or webcam in the same port and retest.
• Try a direct USB port if the device is currently connected through a hub.
• For wireless headsets or microphones, confirm the device is powered on and connected to the computer.
• Remove the device from Windows input selection temporarily only if you are confident you can select it again; otherwise leave routing unchanged and retest after each connection change.

What to change after a finding

Start with changes that are easy to reverse: allow the browser permission, choose another listed input, unmute the hardware, or reseat a cable. Retest the original symptom after each change by speaking normally and watching both the test page and the Windows input level.

• If changing the browser input fixes the meter, keep that input selected and use it for the intended call or recording.
• If allowing microphone access fixes the meter, permission was the blocker and no driver change is needed.
• If the Windows input meter moves but the browser remains at 0, stay with browser permission and browser input selection before touching drivers.
• If the Windows meter also stays at 0 while another known microphone produces a signal in the same port, the no-signal device is the likely fault.

When volume 0 is not a device failure

A 0 reading may represent capture being unavailable rather than a microphone being electrically dead. A denied permission, the wrong input, a browser that lost capture access, or an app holding the device exclusively can all produce the same symptom while the hardware remains functional.

A microphone test proves whether a signal arrived through the selected capture path. It does not prove that the microphone capsule, cable, or driver is fully working unless that path is confirmed as the only plausible failure.

When to stop and escalate

If you have confirmed the intended input in Windows, allowed browser access, selected the same device in the browser, and verified another microphone works through the same connection while the target still shows 0 in both Windows and the browser test, the remaining likely causes are device-specific failure or a driver problem. At that point, check the device maker's official support guidance for the specific model before reinstalling drivers, updating firmware, or resetting the device, because those actions can change settings and may have their own side effects.