Start with the live signal, not a recording app
Open the microphone test and speak at a normal distance. A responsive level meter confirms that the browser received an audio stream during that session. It does not judge studio quality, but it separates a completely missing signal from a quiet or distorted one.
Grant permission only after checking the address bar and page name. If the browser offers several inputs, choose the device you intend to use. Headsets, laptop arrays, monitor microphones, virtual audio cables and docking stations can all appear as separate choices.
- Unmute the physical switch and raise the hardware gain to a moderate level.
- Start the microphone test and allow access for this site.
- Speak normally and watch for movement rather than chasing maximum volume.
If permission was blocked
A previous denial is usually remembered. Use the permission icon beside the address, change Microphone to Allow and reload the page. If no site control appears, review the browser's privacy settings and remove the saved block for this domain.
The operating system has a separate privacy layer. Windows, macOS, Android and iOS can allow a browser to run while denying it microphone access. Enable access for the browser itself, then close and reopen it. On a managed work or school device, an administrator policy may control the setting.
Confirm the input and connection
Open system sound settings and observe the input meter there. Select the intended microphone as the current input. For a USB device, connect directly instead of through an unpowered hub. For a 3.5 mm headset, verify that the plug and port support the same combined or separate microphone wiring.
Bluetooth headsets commonly expose a high-quality playback profile and a separate call profile with microphone support. Disconnect and pair again if the input profile is absent. Recharge wireless hardware and check that another nearby device has not taken the connection.
Close conflicts and check the sound quality
Meeting, streaming and voice-processing apps can hold or reroute an input. Close them fully, reload the test and compare again. Virtual mixers and noise-removal utilities should be bypassed temporarily so you can test the physical device first.
If the meter moves but stays very low, move closer and raise input gain gradually. If it remains near maximum or sounds harsh, lower gain and disable automatic enhancement for comparison. Room echo, fan noise and clipping are quality problems, not proof that the signal path has failed.
When hardware becomes the likely cause
Test the microphone in another browser and one native recording application. Then, when practical, try it on another port or device. Failure across independent apps and computers after the correct input and permissions are confirmed makes a cable, connector, mute control or microphone fault more likely.
Avoid sharing recordings that contain personal conversation merely to prove the microphone works. A live local meter is enough for the first diagnosis. If the device is under warranty, document the tested connections and consistent failure before opening or repairing it.