Microphone Input Not Working: Check Detection and Permissions

Essential answer

A microphone input usually stops working for one of a few reasons: the microphone is not detected by the system, it is detected but not chosen as the active input, or the operating system or browser is blocking access. The first step is to decide which of these layers is involved, because each one has a different fix. If the microphone does not appear at all in the system or application input list, treat it first as a detection problem. If it appears but cannot be selected, treat it as an input-selection or device-state problem. If it appears and is selected but an application still receives silence or gives a permission error, treat it as a permissions or application-behavior problem.

Start with physical links and hardware state

Before changing software settings, confirm the microphone has power and a usable physical connection. For a USB microphone, disconnect it and reconnect it to a different USB port if one is available, preferably a port directly on the computer rather than a hub. For a microphone with a 3.5 mm plug, check that it is in the microphone or line-in socket and not the headphone socket. A headset microphone also depends on the headset cable and connector being fully seated.

The result of this check is limited: a solid physical connection does not prove the microphone works, and a missing or loose connection is not the only possible cause of failure. It only removes or confirms the physical layer as a likely issue.

Check that the system detects the device

Next, open the operating system's audio input settings. On Windows, this is the Sound settings input section or the classic Recording tab in the Sound control panel. On macOS, this is the Input tab in Sound settings. On many Linux desktop environments, open the sound settings and look for an input device list.

If the expected microphone is missing from the device list, the operating system has not made it available to applications. That supports a device, driver, port, or connection problem rather than a browser-permission problem. Try another port or cable where possible, and check the device manufacturer's instructions for whether a driver is required. If the device appears, detection is working at the operating-system level, and the next likely cause is active input selection.

Confirm the active input selection

A detected microphone is not necessarily the one an application records from. In the same system input settings, make sure the intended microphone is set as the default or selected input. If more than one candidate is listed, such as an internal microphone, a webcam microphone, and a USB microphone, the wrong choice can make the correct device appear unresponsive.

While an input-level meter is available, speak into the microphone and watch whether it moves. A moving meter shows that the selected input is receiving a signal and narrows the remaining problem to the application. A flat meter does not identify whether the fault is in the microphone, its connection, or the selected device; it only shows that no usable signal is reaching that meter.

Check application-level input selection

Some applications and browser-based tools keep their own microphone choice. Open the application's audio settings and confirm that the same microphone selected at the system level is also selected there. The system default is a fallback, not a guarantee, because an application may remember a previous or different input.

Check operating-system microphone permission

If the device is detected and selected but an application receives no audio or reports blocked access, check the privacy or security settings. On macOS, the microphone permission is in System Settings under Privacy and Security. On Windows, microphone access can be controlled in Privacy and security settings, including a switch that affects whether desktop apps may use the microphone.

A disabled system-level permission can block access even when the device appears in the input list. The exact label and location differ by operating system version, so use the setting names shown in the current version you are using.

Check browser microphone permission and site access

For a web-based microphone test, the browser must also be allowed to use the microphone, and the current site may need explicit permission. If the site shows a permission prompt, choose the intended microphone and allow access. If the prompt has been dismissed or denied before, the site may be blocked without asking again.

In the browser's site settings, check whether the microphone is set to allow, ask, or block for that site. A blocked entry prevents the page from receiving audio even if the operating system has granted permission. After changing the setting, reload the page so the test tool can request access again.

Separate webcam video from microphone audio

A webcam with a built-in microphone can make diagnosis confusing. The camera may appear in a video list while its microphone appears separately in an audio input list, possibly under a different name. Confirming that the camera can send video does not confirm that its microphone is available or selected. Treat the audio path as a separate check even when the camera and microphone are in the same device.

When an application still receives no audio

If the microphone is detected by the operating system, selected as the input, allowed at the system level, and allowed in the application, but no signal is received, the remaining likely causes are a defective microphone or cable, a device-level mute, or an application-specific setting such as input volume or a recording-device override.

A successful test in one application does not prove that another application will behave the same way, because applications can have independent input selections or permission states. Use the results from each layer only for what that layer actually tests.