Trusted by creators at startups, agencies, and Fortune 500 teams.
Free forever — no signup, no watermark.
How do I test my microphone online?
Open this page, click Allow when the browser asks for microphone access, and speak at your normal call volume. If the level meter moves, your microphone is reaching the browser and should work in Zoom, Google Meet, Microsoft Teams, Slack Huddles, Discord, and other WebRTC apps. If you also need a live camera preview, run the combined webcam and mic test.
Is my mic working if the bar moves?
Yes. A moving bar means the selected input device is sending audio into the browser. Use the sample recorder to check how it actually sounds: low input gain, Bluetooth compression, plosives, echo cancellation, clipping, or room noise can all be audible even when the meter proves the mic is technically working.
Granting microphone permission, per OS
On Windows 11 and 10, browser-level permission is not enough — the OS also has a global toggle at Settings → Privacy & security → Microphone. Confirm "Microphone access" is on, "Let apps access your microphone" is on, and your browser is listed and enabled below. On macOS Sonoma, Ventura, and Sequoia, the equivalent lives at System Settings → Privacy & Security → Microphone; your browser must be checked. On Ubuntu with PipeWire or PulseAudio, permissions are app-level only — the browser handles them, so the in-page Allow click is normally sufficient. If the in-browser bar still does not move, the test you need is the speaker test — if speakers work but the mic does not, the failure is in the input path, not the audio stack as a whole.
Want to record once your mic is confirmed?
With the mic confirmed, capture a screen recording with narration using Clipy: free, no watermark, instant shareable link. If you just need a voice-only recording, the voice recorder records straight to MP3 in the browser. To verify both audio and video together before a meeting, use the webcam and mic test for a combined camera + audio check, or jump to the webcam test for camera-only, or one of the platform-specific testers above.
Why test before calls, podcasts, and recordings
The single most common reason a call starts with five awkward seconds of "can you hear me?" is the OS routing audio to the wrong input — a Bluetooth headset that was paired yesterday, the laptop's built-in mic instead of the USB one, a webcam mic instead of your headset. Sixty seconds of testing here eliminates that whole category of problem before your team sees it happen.
The same applies to podcast takes and screen recordings: by the time you have noticed the wrong mic was picked up, the take is unusable. The pre-call check costs nothing and saves the recording.
How the test actually works
When you click Allow, the browser opens a MediaStream from your selected input. The stream is piped into a Web Audio AnalyserNode, which samples the time-domain buffer 60 times per second and converts the peak amplitude to a 0–100 scale. The bar-graph meter is a real representation of the audio signal — not an animation, not a placeholder. If it does not move, no audio is reaching the browser, which narrows the root cause to permissions, device selection, or an OS-level mute.
When you record sample A or sample B, the browser's MediaRecorder captures that same local MediaStream into an in-memory blob so you can play it back or download it. No sample is sent to Clipy's servers. The page also reads browser-reported track settings such as sample rate, channel count, latency, echo cancellation, noise suppression, and auto gain when the browser exposes them.
What a "good" microphone level looks like
At a comfortable speaking volume from 20–40 cm away, the meter should sit in roughly the 40–70% range, with peaks pushing toward 80% on louder syllables. Constantly hitting 100% means the input is clipping and your voice will sound distorted — turn down the input volume in Windows Sound settings or macOS System Settings. Sitting under 20% even when you speak loudly means the input volume is too low — raise the input slider, move closer to the mic, or check the gain knob on a USB or XLR mic. A bar that barely moves but is not at zero usually means the wrong input device is selected.
