LOCAL INPUT CHECK
Check whether your browser can receive a signal from the microphone you choose. This free microphone test runs in the browser, asks for permission only after a click, and gives you a readable result instead of a mystery meter.
START WITH AN INPUT CHECK
Before you start: choose the intended input in your system settings, keep the browser tab open, and use a comfortable speaking level.
A SIMPLE MICROPHONE TEST
The useful question is usually simple: can the browser receive input from the microphone you expect to use? Follow the short flow below, then use the result as a troubleshooting clue for calls, recordings, games, and browser meetings.
Connect the headset, USB microphone, webcam microphone, laptop microphone, or audio interface you want to check. Select it in your operating system first. If you change devices later, stop and restart this page's test so the result describes the new input path.
Click Start Microphone Test and respond to the browser permission prompt. The speaker test on the main page does not need this permission, but an input check cannot work until the browser is allowed to read a microphone stream for this page.
Speak a few words, tap near the microphone, or clap once at a comfortable distance. Watch the live level and the text state. A moving level means input activity reached the browser; it is not a promise that a remote call will sound perfect.
Stop the test when you have enough information. The page closes the media tracks and clears the live meter. If no signal appeared, check the selected device, mute switch, browser permission, and another application before replacing hardware.
UNDERSTAND THE OUTPUT
A browser microphone checker should report narrow, useful facts. It can show whether permission was granted, whether an input stream is available, and whether the signal changes. It cannot hear the room the way a person does or certify the quality of a recording.
The result distinguishes a permission request, a granted stream, a denial, and a browser that cannot provide microphone input. This makes the next action clearer than a meter that stays at zero without explanation.
The local analyser watches the time-domain signal and turns it into a relative percentage. When the number moves after you speak or tap, the browser is receiving activity from the active input path.
After permission, supported browsers can expose input device labels. Select the device you actually want to use, especially when a laptop has a built-in mic and a headset or webcam is connected at the same time.
The page uses the microphone stream to drive a local analyser. It does not need a recording, a file upload, a server-side job, or a login. The stream is stopped when you stop the test or leave the page.
A moving meter is evidence of browser-level input activity, not a calibrated decibel measurement. Treat it as a quick connection check and use a real recording or call to judge the final listening experience.
WHEN THE MICROPHONE DOES NOT RESPOND
Most failed microphone checks come from routing, permission, mute controls, or another application using the device. Change one thing at a time, restart the test, and compare the result with a known voice recorder or meeting app.
Choose Allow in the browser prompt. If you previously blocked the site, open the browser's site permissions and enable microphone access for this domain, then reload or press Start again. The page cannot override a denial.
Reconnect the USB cable, wake the Bluetooth headset, or check that the webcam is visible to the operating system. A browser can only list devices that the system exposes. Retry after the device appears in system audio settings.
Check the input mute switch, system input volume, selected device, and the distance between your voice and the capsule. Speak for several seconds rather than watching for a single instant. If another app also receives silence, fix the system route first.
Video calls, recording software, game chat, and browser tabs can hold an input device or change its level. Stop those sessions temporarily, close duplicate tabs, and restart the microphone test. A NotReadableError often points to a busy or unavailable device.
Move away from speakers, fans, and hard reflective surfaces. Lower the input gain, check the cable, and test without aggressive noise suppression if your system offers that choice. This page can show activity, but a real recording is better for judging noise and clarity.
PRIVACY AND LIMITS
Microphone access is sensitive, so the default flow is intentionally explicit and narrow. Nothing here requires an account or a server-side audio pipeline. You decide when the browser may open the input and when the stream should stop.
Loading this page does not call getUserMedia. The permission request starts only after you press Start Microphone Test. That keeps the main speaker test and the explanatory content available even when you do not want to share input access.
The analyser reads short signal samples in the current browser session to update a relative meter. The page does not upload, save, or publish a recording. Stop the test when finished, especially on a shared computer.
Granted means the browser opened an input stream. Signal detected means the local samples changed above a small threshold. Neither label proves speech intelligibility, hearing ability, studio quality, background-noise performance, or long-term hardware reliability.
COMMON QUESTIONS
These answers cover the practical questions behind an online microphone test, including browser permission, device selection, zero input, privacy, and the difference between a connection check and a recording-quality review.
Choose the microphone you want to use, click Start Microphone Test, allow access, and speak or tap near the device. The meter and result summary show whether the browser receives local input activity. Stop the test when you are done.
No. The page uses the live stream to calculate a local activity level and does not need to record or upload an audio file. The browser still shows its microphone permission indicator while the test is active, so stop the stream when you finish.
Web browsers protect microphone input behind an explicit permission decision. This page waits until you click Start before calling the browser input API. If you deny access, the page can explain the problem but cannot read a signal until permission is changed.
Confirm that the correct input is selected, the hardware mute switch is off, system input volume is raised, and another app is not holding the microphone. Speak for a few seconds, reconnect the device, and retry. If all apps hear silence, troubleshoot the operating system route.
Yes. The browser can test any input device that the operating system exposes to it, including a laptop microphone, headset, webcam, USB microphone, Bluetooth headset, or audio interface. Select the intended device before starting and repeat the test after switching hardware.
No. The meter is a relative signal-activity display. It is useful for checking whether input reaches the browser, but it is not a calibrated dB meter and does not grade frequency response, background noise, speech clarity, latency, or the quality of a final recording.
A microphone test checks audio input from a device. A sound test usually checks audio output from speakers or headphones. They use different browser permissions and routes, so a microphone can work while speakers fail, or speakers can work while the microphone remains muted or unavailable.
READY TO CHECK INPUT
Start with the intended device, keep the first test short, and read the permission and signal states together. That combination gives you a useful next step without overstating what a browser microphone test can prove.
