The short answer
A microphone that is not working may be blocked by browser or operating-system permissions, muted, routed to the wrong input, disconnected or unavailable to the current application. Start by checking whether sound reaches this browser. A moving input meter narrows the problem to a different part of the path; a silent meter does not by itself prove the microphone is broken.
Run the Testpartout Microphone Test, explicitly allow microphone access and speak normally during the short check. It analyses sound locally without recording or uploading audio. The page uses the input selected through the browser and system, not its own microphone picker. If the wrong device opens, change the system input and repeat before troubleshooting a calling app.
Run the Microphone Test first, then compare the checks below. Explore Audio Tests for related checks.
Quick diagnostic checklist
- Connect or pair the intended microphone and select it as the system input.
- Check a headset mute switch, microphone mute key and any USB microphone controls.
- Open the test in a current main browser over HTTPS, not an embedded social-app browser.
- Start the test and allow microphone access for this site and for the browser in OS privacy settings.
- Speak at a comfortable normal volume; check whether the meter responds during the run.
- If sound arrives here, check the device selected by the app where your microphone fails.
- If it stays silent, compare another supported input or connection and change only one setting at a time.
Browser permission and operating-system permission are separate
The website asks for microphone access only when you start the test. If you denied a prompt earlier, the browser can remember that choice and block later attempts without asking again. Open the browser’s site-permission controls for Testpartout, inspect the Microphone setting and allow access if you want to run the check. Reload after changing it. Interface names vary across browsers and versions.
The operating system can independently prevent the browser from using audio input. On Windows, inspect microphone privacy settings and whether desktop applications are permitted. On macOS, inspect Privacy & Security → Microphone for the browser you are using. On a phone, check the browser’s app permissions. An allowed website cannot override a blocked browser application. Managed work or school devices may also enforce policies you cannot change yourself.
A detected microphone can still deliver silence
Opening an audio track confirms that the browser obtained an input stream, not that useful sound crossed the entire path. A hardware mute switch can leave the device connected while suppressing the signal. Some headsets mute when a boom is raised; USB microphones may have their own gain or mute controls. Check the device’s indicator and manual instead of assuming that detection means it is unmuted.
Inspect system input volume and speak toward the intended microphone at a normal distance. Do not solve silence by shouting or immediately maximizing gain. The test observes whether sound crosses a relative digital threshold, so very quiet input can remain below detection even though a tiny signal exists. A “No audio detected” result describes this run and threshold; it is not a definitive statement that no microphone hardware is present.
Wrong input selected: laptop microphone versus headset
A laptop may have a built-in microphone alongside a USB device, webcam microphone and Bluetooth headset. Hearing sound through a headset does not establish that its microphone is selected. Inspect the system input selection, then speak close to that device and look for the meter’s response. The device label shown by the test can help when the browser exposes it, but labels are not always clear or available.
Testpartout currently requests the browser’s selected input rather than offering an input-device selector. Change the input in system or browser controls where available and restart the test. If you disconnect one device, the system may silently fall back to another. Repeat after the connection settles. In a communication application, inspect its separate microphone dropdown too; it may deliberately ignore the system default.
USB microphones and wired headset connections
For a USB microphone, reconnect it and try a supported direct port if available. A hub, dock or adapter adds another connection that can fail or behave differently. Wait for the system to recognize the device before opening the test again. Confirm that the microphone appears among system inputs and inspect any manufacturer control application without installing unrelated drivers from untrusted download sites.
For a wired headset, check that the plug is fully seated and that the socket supports microphone input. A headphone-only socket does not necessarily accept a headset microphone. Separate microphone/headphone connectors and combined headset connectors may need a compatible adapter; similar-looking plugs do not guarantee compatible wiring. Follow the device’s documentation. Do not force connectors, open equipment or make electrical modifications to diagnose silence.
Bluetooth headsets can use different input and output modes
Bluetooth playback and headset microphone operation can use different modes depending on the device and operating system. A headset may play music while its microphone is unavailable or another input remains selected. Confirm pairing, choose the intended microphone and check whether opening a call changes the audio device or playback quality. Those changes can be a routing consequence rather than proof of damaged hardware.
Charge the headset and compare a supported wired connection or built-in microphone if you have one. Avoid treating a mode change as a universal Bluetooth defect: behavior varies with the platform and headset. If another app is already using its microphone, close that app before repeating. Compare the same brief spoken phrase under similar conditions so you can distinguish a connection change from a change in speaking level.
Microphone busy, embedded browsers and secure access
Some systems or applications can hold an audio device exclusively. Close recording or communication applications, end other browser calls and try again. A browser error may only say that the input is unavailable, not which application has it. Reconnecting the device or restarting the browser can help isolate a stale connection, but is not a guaranteed remedy for every unavailable-device error.
Use the main browser rather than a web view inside a messaging or social application. Embedded browsers may restrict media permissions or present different controls. Published microphone access requires a secure HTTPS context; an insecure page cannot request the same access. If there is no permission prompt, inspect browser support, remembered permissions and OS restrictions before deciding that the microphone failed. Restricted enterprise policies may require your administrator’s help.
It works here but not in Discord, Zoom or a game
A responding meter here establishes that this browser received input in this session. It does not guarantee another app selected the same microphone. Check that app’s input device, mute state, push-to-talk binding, input sensitivity and OS permission. A meeting may also have a separate mute control from your hardware. If you use a browser-based call, compare that site’s microphone permission with Testpartout’s permission.
When the meter moves but other people cannot hear you, inspect the communication path after capture: the selected meeting input, application processing, channel settings and transmission state. Noise gates or suppression may remove quiet speech; push-to-talk may not be engaged. Compare the application’s own input indicator before blaming the microphone. Avoid posting private audio or granting remote access merely to prove that sound exists.
What the Testpartout measurement actually means
The current microphone test analyses an audio stream in memory for a ten-second run, unless you finish it earlier. It computes a relative digital input level from audio samples, smooths the visible meter and tracks whether input crosses its detection threshold. The analyser is not connected to the speaker destination, so the test does not play your voice back. Browser requests to disable input processing may not be honored identically by every device.
A relative digital level is not calibrated sound-pressure level in dB SPL. The reading depends on input gain, device processing, distance and browser behavior. It cannot certify microphone frequency response, speech intelligibility or broadcast quality. A working observation is useful evidence that sound arrived; compare recordings only in a separate tool you intentionally choose. Testpartout itself does not provide a recorder or stored audio clip.
Privacy, stopping and sensible next steps
Microphone audio remains local and is neither recorded nor uploaded. The stream and audio context are released when the run finishes, on page hide and when you leave the test. Consent-controlled analytics may describe starting, completing or granting permission, but does not receive microphone levels, audio or the outcome. Browser permission can persist after a stream ends; you can revoke it in site settings if you wish.
If the symptom persists across another supported connection, browser and input selection, collect non-sensitive observations for manufacturer support: the device model, connection type, whether it appears as an input and whether any application receives sound. That comparison makes hardware involvement more plausible without identifying an exact internal fault. Review the audio hub for output checks if your actual symptom is that you cannot hear others rather than that others cannot hear you.
Frequently asked questions
Why is my microphone detected but not picking up sound?
The input can open while muted, set very low, routed to the wrong source or blocked elsewhere in the device path. Check mute, input selection and system level, then repeat a normal spoken phrase.
Why does the microphone work in one app but not another?
Applications can select different inputs and apply separate permissions, mute, push-to-talk or sensitivity settings. A successful browser check does not bypass those controls.
Does this test record my voice?
No. Audio is analysed in memory for the local meter and detection check. Testpartout does not record, save or upload your voice.
Does a silent result prove the microphone is broken?
No. It means no sound above the test threshold was detected in that run. Permissions, routing, mute, gain and connection problems can produce the same observation.
Keep the next step specific
Repeat the Microphone Test after changing one relevant setting. Read our methodology for browser measurement limits and privacy policy for current data handling. If you find a mismatch between this guide and the test, send the non-sensitive details through Contact.