When to run this microphone test
Press Start Microphone Capture, allow the browser permission, and the page draws a live waveform from your input. If the waveform moves when you speak, the mic is working. The check runs in your browser using FileReader, canvas, and a blob URL on the client-side path. Free, no installs.
Test Your Microphone for Clear Audio Performance
This online mic test verifies your microphone's input level and browser permission before a call, recording, or gaming session - no software to install, works across laptops, desktops, and smartphones in any modern browser.
What this microphone test measures
The test exercises the four layers a call or a recording depends on: input-device detection, sample-rate negotiation, live level metering, and echo/noise behaviour.
- Input device detection. The browser reports the active microphone (built-in, USB headset, Bluetooth, external interface). If the wrong device is selected at the OS level, the waveform stays flat even when you speak - that is your first diagnostic.
- Sample rate negotiation. Most browsers open the stream at 44.1 kHz or 48 kHz; the canvas waveform reflects that rate. Drop-outs or audible crackle suggest driver re-sampling - close other audio apps and reload.
- Live level metering. The green bars show input gain. Peaks below half-scale at normal volume: raise the OS mic gain. Peaks clipping at full-scale: lower it - clipping distorts call audio and ruins recordings.
- Echo and noise cue. Toggle Play sound from your microphone to hear what the other side hears. Echo, hum, and keyboard clatter are usually acoustic - a headset or physical treatment fixes more than software filters do.
Browser permission troubleshooting
Most "no audio" reports resolve at the browser or OS permission layer, not the microphone itself.
- Chrome. Click the mic icon in the address bar and choose Always allow; if blocked, open
chrome://settings/content/microphoneand remove the block. - Safari. Safari → Settings → Websites → Microphone. Mobile Safari requires a user tap before first mic access.
- Firefox. Click the mic icon in the address bar to clear the block; or open
about:preferences#privacy→ Permissions → Microphone, remove the site, and reload. - Edge. edge://settings/content/microphone; also check Settings → Privacy & security → Microphone at the OS level.
- macOS. System Settings → Privacy & Security → Microphone - toggle the browser on.
- Windows. Settings → Privacy & security → Microphone - enable both app and desktop-app toggles.
If every browser fails with permissions granted, test the mic in Voice Memos (macOS) or Sound Recorder (Windows) to isolate a hardware or driver fault.
Privacy - how the test handles your audio
The microphone stream runs entirely in the browser via the Web Audio API - nothing is uploaded, stored, or transcribed. When you close the tab or click Stop, the browser releases the device and discards the stream. The green level bars are rendered from raw PCM samples; no audio byte reaches any server.
Run this test first when a call drops audio while video stays up, or when a recording captures silence despite the mic being on.
Pairing the mic check with a camera test
For a complete call setup, also run the camera test once the waveform confirms mic input is live - audio and video are independent streams, so a passing mic result says nothing about the camera until you test it separately.
What makes this a reliable pre-call check is the pairing of a live spectrum meter with a browser permission probe: granting microphone access in the browser confirms the page can reach the device, and the waveform that then moves on the canvas as you speak confirms the mic is actually picking up sound. Seeing both - the permission cleared and the meter responding - is the proof you are call-ready, before you join the meeting or start a recording.
The depth behind the waveform - what Start Microphone Capture actually builds
When you click Start Microphone Capture, the page calls navigator.mediaDevices.getUserMedia, and on browsers where that interface is undefined it falls back gracefully rather than throwing, so an older engine reports a clear permission state instead of a blank screen. The granted stream is wired into a Web Audio graph - window.AudioContext (or webkitAudioContext on older WebKit builds) opens at whatever rate your driver negotiates, typically 44.1 kHz or 48 kHz, and every frame the canvas redraws from the live samples, which is why the waveform tracks your voice in real time instead of lagging a second behind. None of those samples are written to a buffer or a blob for download: the client-side path uses FileReader, canvas, and a transient blob URL purely for the in-browser render, so there is genuinely no Record control and nothing to upload. The one real tradeoff lives in the "Play sound from your microphone" checkbox - leaving it on routes the input straight to your speakers for an end-to-end loopback that confirms speakers AND mic together, but on a laptop with open speakers that same loop becomes an audible feedback howl within a second or two, so the safe pattern is to monitor through headphones or to flip the toggle off once the green level bars already prove the mic is picking up sound.
Before a job interview or video meeting, the guide how to check your webcam and microphone before an interview sequences this microphone test, a camera check, and a browser permission verification into a two-minute pre-call routine.
FreetoolOnline Editorial Team
Frequently Asked Questions
Why Use an Online Mic Test?
Online mic tests are fast and easy, allowing you to verify your microphone's functionality from any device with internet access without needing to download or install software.
Can I Test My Laptop's Built-in Microphone?
Yes, this tool works with built-in microphones on laptops, desktops, and mobile devices, as well as with external microphones.
Is My Audio Data Stored or Shared?
No, this tool does not store or share your audio data. It operates entirely within your browser, ensuring your privacy.
Will This Tool Work on Mobile Devices?
Yes, the tool is compatible with most mobile browsers, allowing you to test microphones on smartphones and tablets as well.
Do I Need to Install Any Software?
No installations are required. This tool functions fully within your browser, offering a plug-and-play solution for microphone testing.
The tool asks for permission but shows no level - what next?
Two common causes. First, the browser is using the wrong input device: click the microphone icon in the URL bar (or Site settings → Microphone), select your intended mic from the dropdown, and reload. Second, on macOS Sonoma and Windows 11 the OS-level privacy switch blocks browser access even after Allow - check System Settings → Privacy & Security → Microphone and confirm your browser is toggled on. If the level bar is still flat, the physical mute switch on your headset or laptop may be the culprit.
What level reading should I see on the meter during normal speech?
Speech at a comfortable conversation distance (20-30 cm from the mic) should peak between −18 dB and −6 dB on the level bar, with occasional peaks toward 0 dB on loud syllables. Constant readings near 0 dB mean the mic gain is too high (expect clipping and distortion on calls); readings below −30 dB mean the gain is too low or the wrong input is selected. Adjust input gain in your OS sound settings until normal speech sits in the −18 to −6 dB band.
Is a USB microphone or a built-in laptop mic better for video calls?
A USB mic wins on quality every time - larger diaphragms, better noise rejection, and closer pickup distance. Built-in laptop mics pick up keyboard typing, fan noise, and every reflection in the room because they sit far from the speaker. For frequent calls (interviews, client meetings, podcasts), a USB mic under $50 is the single cheapest quality upgrade you can make. Test both with this tool and compare the baseline noise level between passes.
How do I grant microphone access on iPhone or iPad?
iOS Safari surfaces a tap-triggered permission prompt the first time you open the page. If you missed or denied it, open Settings → Safari → Microphone and set freetoolonline.com to Allow, then reload the page in Safari (a fresh user tap is required after the flip). If the prompt never appears at all, the page is loaded inside an in-app browser (Twitter / Slack / Gmail webview) - iOS blocks mic access in cross-origin webviews; open the URL in standalone Safari instead.
I blocked the mic on Chrome Android once and the prompt will not reappear - how do I reset it?
Chrome Android remembers a denied mic permission and will not re-prompt on its own. Open chrome://settings/content/microphone, locate the freetoolonline.com entry under Blocked, tap it, and switch to Allow - or remove the entry so the next visit re-triggers the prompt. On Android 12 and later also confirm Settings → Privacy → Microphone access is on globally; an OS-level kill switch overrides every app.
Bluetooth headset or built-in phone mic - which should I use for a call?
For a quick check the built-in mic is usually fine - it sits closer to your mouth than a far-field laptop array, and the OS already runs noise suppression on it. Bluetooth headsets win on hands-free use but introduce two failure modes the test surfaces: a 200-300ms input lag (interactive apps feel sluggish), and a degraded SCO/HFP profile when the headset switches into call mode (the audio band drops to 8 kHz and voice sounds tinny). Unpair-and-repair if the test reports either.