Microphone Test
A live meter that proves the microphone is picking up sound.
Checking a microphone before a call
A microphone test answers two questions: is the browser receiving audio, and how loud is it. The meter shows level, not quality. A microphone can be perfectly loud and still sound hollow if it is picking up the room rather than your voice.
Speak at the volume you will use on the call and watch the meter. If it peaks at the top of the scale, move back or lower the input gain; clipping cannot be undone in the recording.
Test with the app you will actually use. Browsers apply their own processing, and a microphone that sounds clean in one meeting tool can sound thin in another because of a noise-suppression default.
Try a short recording rather than only watching the meter. Level tells you it is connected; a recording tells you whether it sounds like you, and the difference matters more than any number.
Good to know
The meter shows level, not quality: a loud signal can still be clipping. If the bar is pinned at the top, lower the input gain rather than moving closer.
How Microphone Test works
See a live level meter from your microphone and confirm the right input device is selected. The method behind Microphone Test is the single-purpose logic inside wave41.js, and this page shows the result with its assumptions in the open.
- Open Microphone Test and provide mic test — the page accepts it in the field it shows.
- For Microphone Test, browser APIs and, where stated, one public endpoint do the work.
- The Microphone Test output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.
A worked example for Microphone Test
A typical run of Microphone Test starts with mic test and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.
Repeat the check on a second network: a result that changes with the network is a routing fact, not a fault in your device. That check applies directly to Microphone Test with mic test.
When to use Microphone Test — and when not to
Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Microphone Test is deliberately narrow: it does one job and states its assumptions instead of hiding them.
Diagnostic apps and terminal tools go deeper but need installs or shell access. For a quick lookup or a device test, a page is the lower-friction path. The honest ceiling for Microphone Test: for Microphone Test, results reflect your network and device.
- Best case for Microphone Test: Diagnosing a connection
- Also fine with Microphone Test: Checking DNS or registration data
- Not what Microphone Test is for: for Microphone Test, results reflect your network and device.
Reading the Microphone Test result
The output of Microphone Test is a function of the inputs alone — no hidden state and no server.
Accuracy and limits of Microphone Test
The method is the single-purpose logic inside wave41.js. Microphone Test prints results at the precision its inputs justify, and the limits below are the honest ones:
- Microphone Test: For Microphone Test, results reflect your network and device.
- For Microphone Test, pages that call an endpoint say so and call it only on your click.
Privacy and speed on the Microphone Test page
The Microphone Test page is a static file plus wave41.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.
Speed follows the build: Microphone Test loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.
What you get from Microphone Test
The output of Microphone Test appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the web work finishes the moment the numbers are in.
Because Microphone Test is built from wave41.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.
Questions
Is my audio recorded?
No. It is analysed in the tab and discarded — nothing is stored or sent.
Nothing moves — what now?
Check the browser permission, then the system input device. A muted or wrong device shows a flat meter.
How accurate is Microphone Test?
The method is the single-purpose logic inside wave41.js. For Microphone Test, results reflect your network and device.
What are the limits of Microphone Test?
For Microphone Test, pages that call an endpoint say so and call it only on your click.
Is anything uploaded when I use Microphone Test?
No. Microphone Test runs entirely in the browser tab; nothing is uploaded, stored or logged.
Can I use Microphone Test offline?
Yes — Microphone Test keeps working offline once the page has loaded; the whole tool is a local script.
Device tests
Keep going
More web tools
Voice Recorder
Record audio from your microphone with a live level meter and download the file. Nothing is uploaded or stored.
Open toolKeyboard Test
Press keys and see them light up on a full layout, with the key code and location. Find a key that is not registering.
Open toolClick Test
Measure clicks per second over a five-second window, keep your best score, and see the total in the window.
Open toolMouse Test
Check left, right and middle buttons, count wheel ticks, and see a rough movement rate. Catches a double-clicking switch.
Open toolSpeaker Test
Play a tone on the left, the right or both, check individual frequencies, and run a sweep to hear rattles or a dead cone.
Open toolGamepad Tester
See every button press, both sticks and the axes of a connected controller, with the mapping the browser reports.
Open tool