Check if your microphone is working. See live audio waveform, volume level, and record a test clip. No install.
Audio stays in your browser. Nothing is recorded or uploaded to our servers.
We will ask for microphone access so you can see live input activity, volume level, and test a short recording in your browser.
Your browser will ask for microphone permission after you click start.
Audio stays in your browser. Nothing is uploaded.
Microphone level idle
Use a short local recording to confirm your microphone input, browser encoding, and speaker playback all work together.
Ready to record a short microphone sample.
Request microphone access and show live waveform, volume, and input activity feedback.
Record a short clip and play it back to verify your full microphone input chain.
An online microphone test is the fastest way to confirm that your browser can access your mic and that your input signal is reaching the page correctly. Instead of installing software or opening a call app, you allow microphone access in the browser and then check whether your voice creates visible movement in the waveform, spectrum, or volume meter. A useful microphone test does more than show a permission prompt. It should help you answer practical questions: is the browser seeing my mic, is the level too low, is the wrong device selected, and can I record a short clip and hear it back clearly? That is why this tool focuses on both live input feedback and a local record-playback test. It helps separate permission problems, device-selection mistakes, and actual hardware issues before you blame Zoom, Teams, Discord, or your operating system.
When a microphone test fails, the cause is usually one of a few common issues. The browser may be blocking microphone permission. The wrong audio input may be selected, especially if you use a USB mic, Bluetooth headset, webcam mic, or laptop dock. Your operating system may be routing input to a different device than the one you expect. Hardware mute switches can also cause confusion, particularly on headsets and professional microphones. In some cases, the mic works but the level is too low because gain is reduced in system settings or on the physical device. Browser tests are useful because they reveal whether the problem exists before you even open a call app. If the live waveform does not move at all, start with permission, device selection, and mute state before assuming the microphone is broken. If the waveform moves but the recording sounds weak or distorted, the problem is more likely gain, positioning, or mic quality than total failure.
Permission is the biggest UX challenge in any browser microphone test. Modern browsers block microphone access until the user explicitly agrees. If you click allow and the mic becomes active, the test can continue normally. If permission is denied, you usually need to re-enable it from the browser address bar settings, site permissions, or the operating system privacy panel. Chrome, Firefox, and Safari all present microphone access differently, so a good tool should explain the difference clearly instead of showing a vague error. Another complication is that some browsers remember a previous denial and will not show the prompt again until the permission is manually reset. That can make a working microphone look broken when the real issue is only stored browser state. The most helpful recovery path is simple: check the site permission, check the OS privacy setting, retry, then confirm the correct mic is selected once access is restored.
Many users search for a mic test because a work call or voice chat app is not picking up audio correctly. A browser-based test is useful because it tells you whether the microphone problem exists before the app layer. If the microphone works in this test but fails in Zoom, Teams, or Discord, the likely cause is app-specific input selection, mute state, noise suppression, or permissions inside that app. If it fails here too, the issue is more likely browser permission, system routing, hardware mute, or device connection. That makes an online test a strong first checkpoint before deeper troubleshooting. It is especially useful for laptops with built-in mics, USB podcast microphones, Bluetooth headsets, and webcam microphones, because those setups often create device-selection confusion.
The fastest way to get a trustworthy result from a microphone checker is to move in a simple order. First, allow access and confirm that the waveform and volume meter react when you speak. Second, verify that the selected device is the one you actually want to test, especially if you have a webcam mic, USB microphone, Bluetooth headset, or dock attached. Third, record a short sample and play it back. That playback step matters because some users have live input activity but still sound distorted, quiet, or routed through the wrong microphone in real apps. A good online mic test should help catch those problems before a meeting, interview, podcast recording, or stream. The goal is not only to see whether any sound exists, but to confirm that the browser is using the correct audio input test path and that your microphone quality is good enough for the task in front of you.
Click the start button, allow microphone access, and check whether your voice creates live activity in the waveform, spectrum, and level meter.
No. The tool is designed so audio stays in your browser and is not uploaded to our servers.
Common causes include browser permission denial, no hardware connected, wrong input device selected, mute switches, or operating system privacy settings.
Yes. If the browser can access it as an audio input device, you should be able to select it and test it.
Yes, but Bluetooth routing can be tricky. Make sure the headset mic is selected as the active input device in both the OS and the browser.
Microphone access is protected for privacy. Browsers require an explicit user action before they allow audio input to a page.
You usually need to re-enable microphone permission from the browser site settings or system privacy panel, then retry the test.
Yes. The tool is planned to include a short local recording and playback step so you can verify the full input and output chain.
Yes. Built-in laptop mics, webcam mics, USB mics, and many headset microphones can all be tested if the browser can access them.
Low level usually points to input gain, distance from the mic, hardware mute state, or the wrong device being selected.
Yes. It is useful before Zoom, Teams, Meet, Discord, streaming, or recording because it shows whether your browser can access the correct microphone and whether the input level looks healthy.
That usually means the microphone is detected, but the selected input, gain, placement, or audio quality still needs adjustment. The recording step helps catch that case.