Mic Test: Check Input and Short Playback

How to test your microphone

Select Start microphone and allow microphone access when your browser asks. In Input device, choose the microphone you intend to use—for example, your USB headset instead of the laptop microphone. Changing the input starts another capture attempt; wait until the status says Receiving input before testing.

Say, “This is my microphone check. One, two, three,” then pause. Use your normal speaking volume and working position. Compare activity during speech with activity during the pause. Record what you observe without treating a moving meter as proof of clear speech.

For a repeat test, write down your phrase, input device, distance, and settings. Note the first result, change one condition, and repeat. For example, increase system input volume while keeping your position unchanged. Test a closer microphone position in a separate run. When comparing different microphones, describe speech clarity and noise rather than ranking devices by meter height.

An optional short recording adds a listening check after starting microphone input. Listen for understandable words, missing syllables, unwanted noise, and distortion. Begin at a low playback volume and use headphones if available. If you cannot make or play a clip, record those stages as untested; the signal observation is still useful.

Recording checks WebM/Opus, MP4, and Ogg/Opus support. A timer requests a stop after 10 seconds. If no supported format is available, input observation remains available.

Select Start microphone, then Record up to 10 seconds. Finish recording ends the clip early while input observation continues. Stop activity also ends capture. Use the audio player to play the clip; playback stops microphone capture. Delete this recording pauses and removes that clip and revokes its playback URL, while retaining saved comparisons. Clear & end session removes all clips and comparisons and stops activity.

Microphone not working: check access, then input

If your microphone is not working, first check whether the page obtained access or opened an input that stays quiet. Browser microphone access requires user permission. For a public website, use HTTPS; browser media access requires a secure context. [MediaDevices: getUserMedia() method - Web APIs | MDN] [MediaDevices: getUserMedia() method - Web APIs | MDN]

A permission request can remain pending if you do not answer it. If the status says Waiting for permission, look for the browser prompt near the address bar. Allow access to continue or decline the request to withhold access. Waiting alone does not identify a microphone fault. [MediaDevices: getUserMedia() method - Web APIs | MDN]

For Permission denied, review the browser’s microphone permission for this site and the operating system’s microphone permission for your browser. Then retry. For No matching input device found, reconnect the microphone and check the system’s input-device list. Try System default or another available input if the previous selection is no longer present.

If the status says Receiving input but there is no visible response to speech, check the microphone’s physical mute switch, selected input, connection, and system input volume. Change one item and repeat the phrase. If the page reports that the signal meter is unsupported, treat the missing meter as an unavailable check rather than evidence of silence.

For quiet input, try a modest increase in system input volume without changing your position. In another run, try moving closer if the microphone’s placement allows it. Include a listening comparison when available; a larger meter response alone is not a reason to keep the change.

If startup still fails, close other calling or recording apps and retry. Compare with your system’s microphone check or another browser. Write down where access or input succeeds and fails. That gives you a concrete next step without assuming the microphone is damaged.

Why the meter moves but playback sounds wrong

Check three stages separately: does signal activity follow your speech, does a recording become available, and can you hear understandable speech from that recording? Use notes such as “signal responds; recording unavailable; listening untested.” Avoid recording a complete pass after checking only the meter.

For silent playback, first check output volume, browser-tab mute, and the output device selected in your system. Play a familiar audio clip through the same output. If that is silent too, start with output troubleshooting. If familiar audio plays, retry the test recording after starting microphone input.

For quiet or distorted speech, replay the same clip at a different, comfortable output volume first. Then make a separate recording with a small input-volume adjustment. This keeps a playback-volume change separate from a change to the recorded sound.

If the recording sounds distant or captures an unexpected source, reselect the intended input and repeat the phrase. Check the listening result rather than relying on the device label alone.

For an echo, compare a new recording made with headphones and without other audio playing. For unwanted background sound, try a quieter setting while keeping input settings and microphone position unchanged. These are troubleshooting comparisons, not diagnoses of the cause.

Write a specific result: “all words audible, fan noticeable during pauses” or “last word missing in both attempts.” If no clip can be played, mark playback as untested and use the system recorder or the intended meeting app for a listening comparison.

Will the result match my meeting app?

A successful browser test does not guarantee the same result in a meeting. Treat it as evidence about the input and listening checks you completed in this browser at this time.

Meeting apps can apply their own input routing, gain, echo cancellation, and noise suppression. Before a call, select the intended microphone in the meeting app, check its mute state, and repeat your phrase using its mic check or a test call. [在线麦克风测试 — 免费话筒检测与录音]

Keep your microphone position and speaking volume consistent with the browser test. If you compare audio-processing settings in the meeting app, change one at a time and note whether words remain clear and complete.

If browser playback is clear but the meeting app is silent, begin with the app’s input selection, permissions, mute state, and input level. If both checks sound wrong, continue comparing the connection, system input settings, and microphone position. Neither pattern alone proves a hardware fault.

For a support request, use a concrete note such as: “USB headset selected; browser signal responds; browser recording is clear; meeting app records silence.” Include the browser and app names and the setting you changed. A browser recording does not establish what another participant receives over a live call.