Microphone Quality, Noise & Latency Tester

How to read your room's noise floor

The noise floor is the level of background sound present in a room when no intentional signal is being produced, and every room has one, caused by HVAC systems, computer fans, traffic, and the thermal noise of the microphone capsule itself. In audio production, a lower noise floor means cleaner recordings with more usable headroom, and a high floor eats into that headroom and forces you to record louder, which in turn captures even more of the background in the final track.

The result is expressed in dBFS (decibels relative to full scale), where full scale, 0 dBFS, represents the maximum digital amplitude.¹ All real-world signals sit below this, so noise floor readings are negative numbers, and the further from zero, the quieter. A reading of −58 dBFS is quieter than −42 dBFS, and because the decibel scale is logarithmic, that gap represents a far larger difference in actual energy than the raw numbers suggest.

A concrete reading makes the workable threshold easier to judge. If your 3-second test reports −58 dBFS, that sits comfortably below the −50 dBFS mark most home setups need for usable voice recording, so background noise should stay well out of the way during normal speech. A reading of −38 dBFS, by contrast, sits above that threshold, and you would expect HVAC hum or fan noise to be audible under quieter passages of the recording.

What is microphone clipping and why it matters

Clipping occurs when an audio signal exceeds the maximum level that a recording system can represent, and in digital audio, that ceiling is 0 dBFS. When the signal hits this limit, the tops and bottoms of the waveform are literally cut flat rather than following their natural curve.² The result is a harsh, buzzing distortion that cannot be removed in post-production.

Common causes of clipping

Common causes of microphone clipping: gain set too high on an audio interface, speaking too close to a condenser capsule, or sudden loud sounds (plosives, table knocks) hitting an unprotected input. Transient peaks are especially easy to miss because a brief overshoot can slam past 0 dBFS even when the average level on your meters looks perfectly safe. The fix is always to reduce gain before the signal reaches the converter, not to apply limiting after the fact.

How the detector flags clipping

The Clipping Detector watches for samples at the absolute maximum or minimum of the digital scale (values of 0 or 255 in the 8-bit display range³). When more than 1% of samples in a single frame hit these limits, the CLIPPING badge appears. The threshold is intentionally conservative because even a handful of clipped samples represent permanent distortion that no post-processing can undo. If you see the badge frequently during normal speech, reduce your input gain.

Reading a frequency response curve

The frequency response display shows how much energy your microphone captures across the audible range (20 Hz–20 kHz)⁴ on a logarithmic scale. The horizontal axis compresses the upper octaves so that each decade (10 Hz→100 Hz, 100 Hz→1 kHz, 1 kHz→10 kHz) takes equal visual space, matching how human hearing perceives pitch.⁵

What the shape tells you about voice capture

A flat-ish response across the speech range (80 Hz–8 kHz)⁶ indicates a well-balanced microphone for voice. Weak energy below 200 Hz produces a thin, telephony-like sound, common in small-capsule USB mics with aggressive high-pass filters. Weak energy above 4 kHz creates a muffled, blanket-over-the-speaker quality, often caused by poor capsule placement or a microphone designed for instrument close-miking rather than voice.

Understanding round-trip audio latency

Round-trip latency is the total delay from a physical sound entering the microphone to the system's response being heard through speakers. In the Clap Latency Test, this path is: clap → mic capsule → OS audio driver → browser → JavaScript → tone synthesis → OS → speaker → room → mic again. Every step in that chain adds delay.

What counts as acceptable latency

Browser audio latency varies by browser, operating system, audio driver, and hardware.⁷ Web Audio exposes baseLatency and outputLatency estimates, and browser-based DAWs have reported best-case round-trip latency around 30 ms with 10 ms as a good target.⁸ Musicians monitoring in real time generally find anything at or below 10 ms comfortable, while standard operating-system drivers without dedicated audio buffers can push the delay up to several hundred milliseconds. This matters for live monitoring (hearing yourself through headphones while recording), real-time collaboration, and any application that needs tight audio synchronisation.

How to get a reliable reading

For best results: use headphones during the Clap Latency Test to prevent the reference tone from feeding back into the microphone through room reverberation. Room reflections and speaker bleed are the main confounders that make a clean single-clap measurement hard to reproduce without that isolation. Sit in a quiet space and clap sharply once, because a crisp transient registers faster than a palm slap. If the test shows "Echo not detected," increase microphone gain or reduce speaker distance.

Test conditions for your actual use case

Microphone requirements differ enough between podcasting, video calls, and music production that a single test in a single environment gives an incomplete picture. Podcasting demands a low noise floor and clean frequency response across the speech range, with recording done in a treated room at close range. Your noise floor test should reflect actual recording conditions: the same room, the same chair position, and the same nearby equipment running during a typical session. A noise floor that looks acceptable in a quiet test environment can sit above the threshold for comfortable listening if your production HVAC system runs during the real thing, and that difference only surfaces when you test under realistic conditions.

Video calls and conferencing platforms

Video calls place different demands on the hardware. Conferencing platforms apply their own noise suppression and automatic gain control, which can mask a weak or noisy microphone at the cost of voice character and intelligibility artefacts. Running the clipping test at the gain level your conferencing software applies, rather than at maximum hardware gain, shows you whether the platform is aggressively compressing your signal. Frequent CLIPPING badges at normal speaking volume with the gain your video call software sets means the input gain is misconfigured for that use case, regardless of how clean the hardware appears at lower gain settings.

Musicians and live monitoring

Round-trip latency matters most for musicians recording with software instruments or monitoring through headphones during a take. Latency above about 10 ms can become noticeable for monitoring, and 25 to 50 ms of software monitoring can start to sound more like double tracking than a clean echo.⁹ Ensemble research also shows that 10, 20, and 40 ms delays change coordination patterns, so the clap latency test gives you a sanity check before committing to a session rather than a promise that every setup can hit a fixed target.¹⁰ Consistently high latency results point to the driver buffer size setting in your audio interface software rather than a problem with the microphone itself.