MicTest

Made MicTest to sanity-check my own mic before calls — live meter + waveform + a recording that stays in the browser. Free forever.

With so many casual web utilities moving toward mandatory sign-ups and cloud telemetry, seeing a fully local, browser-based hardware testing suite is a breath of fresh air. The fact that the Web Audio API handles the meter and live waveform rendering locally without uploading a single byte of audio stream to an external server is huge for privacy. It’s incredibly fast, zero-friction, and does exactly what it promises. Upvoted!

With so many casual web utilities moving toward mandatory sign-ups and cloud telemetry, seeing a fully local, browser-based hardware testing suite is a breath of fresh air. The fact that the Web Audio API handles the meter and live waveform rendering locally without uploading a single byte of audio stream to an external server is huge for privacy. It’s incredibly fast, zero-friction, and does exactly what it promises. Upvoted!

A free mic test with meter, waveform, and channel checks is exactly what streamers and remote teammates need before a call. The no-install approach should cut a lot of ?can you hear me? loops.

The failure-mode diagnostics are the most useful bit here: most mic testers just show a flat meter when the browser has blocked access, so telling users whether it is denied, unplugged, busy or muted saves a lot of guessing. Does the device picker remember the last chosen mic between visits, or does it start from the default each time?

The explicit failure-mode diagnostics (denied permission, device busy, muted, unplugged) solve the biggest headache with Web Audio debugging where users just see silence and assume the app is broken. Having an oscilloscope waveform right alongside the level meter makes it effortless to detect background hum or clipping. Do you plan to add a quick frequency spectrum or FFT analysis view as well?

The failure-mode list is the most useful part. Denied, busy and muted all look the same from inside a call app, and people usually just restart everything. Does the busy case tell you which app is holding the mic, or does the browser not expose that?

The channel check is a nice touch, half of my "my mic is broken" moments were a stereo interface sending audio on the left channel only. Would be great to see a short recording playback with the detected sample rate, so people can also hear echo or noise suppression from the browser before a call

The failure-mode diagnostics are the most useful part here — most mic testers just show a flat meter with no clue whether the mic is denied, busy, muted or unplugged, and those all look identical. The stereo/mono channel check is also a smart inclusion, since a mis-mapped interface is a common cause of "my mic is broken" reports. Does the recording test also report the sample rate and bit depth the browser actually negotiated with the device? That would help when a USB interface falls back to a lower rate than expected.

The one thing I'd want a mic test to catch is clipping. Does the level meter flag peaks close to 0 dBFS, or does it show average level only? For anyone recording a podcast, knowing the input is clipping before pressing record is worth more than the meter alone.

Failure mode was a smart and good feature to add!

Made MicTest to sanity-check my own mic before calls — live meter + waveform + a recording that stays in the browser. Free forever.

Showing the negotiated echo cancellation / noise suppression / auto-gain flags is the detail most mic testers skip, and it explains a lot of "my mic sounds different in the test than on the call" confusion. Would you consider a toggle that reopens the stream with all three turned off? Being able to A/B the raw input against the processed one would make it obvious when auto-gain is covering for a mic that's set too quiet at the OS level. The separate panels for denied / busy / unplugged are a really nice touch too.