An instantaneous level meter only tells you what’s happening right now. The Sound Input Monitor acts as a microphone monitor with memory: it keeps the history, so you can leave it running during a recording, a call, or a practice take and review your recording levels over the last 30, 60 or 120 seconds. Each vertical bar is a short slice of time; its height is the peak level in that slice, and the brighter line traces the RMS (average) level — the gap between them is your signal’s crest factor (how spiky or dynamic the signal is). A wide gap is normal for speech and transient-heavy sources; a narrow gap typically indicates sustained broadband noise or heavy compression.
Alongside the chart, the session stats accumulate from the moment you start (or last cleared): the loudest peak you hit, your average RMS level, and a count of any digital clips. That makes it easy to catch problems an instantaneous meter hides — a single overload on a loud word, a fan that cycles on and off, or your level slowly drifting as you lean away from the mic. For podcasters and voice-over artists, a healthy target is an average RMS around −18 to −20 dBFS with peaks no higher than −6 dBFS; the session stats let you confirm this over a full take rather than just a single moment.
How to use it
- Catch intermittent overloads: if the clip count climbs even once, something briefly hit full scale — scrub the history to see when, and lower your gain.
- Check consistency: a steady RMS line means an even level; a wandering one means you’re moving relative to the mic.
- Spot environmental noise: bumps in the floor between phrases reveal fans, traffic, or handling noise.
- Pass-through monitoring: enable pass-through monitoring via "hear yourself" (headphones only) to listen to your mic feed while you watch the chart.
How this differs from the Gain Level Meter
The Mic Gain Level Meter is for setting your gain right now — peak-hold ballistics and a target zone. This monitor is for watching over time — a scrolling history and cumulative session stats. Use the gain meter to dial in, then leave this running to verify your input stays clean. If you also want to see the frequency content of what your mic is picking up, combine this with the Audio Spectrum Analyzer, which gives a real-time FFT view alongside the level history. And if you need to quantify how quiet your room actually is between takes, the Noise Floor Analyzer measures your octave-band noise floor independently.
What’s the difference between peak and RMS here?
Peak is the loudest instantaneous sample in each time slice — what determines clipping. RMS is the average level over the slice, which tracks perceived loudness. On the chart the bar is the peak and the line is the RMS; a big gap between them means a spiky, dynamic signal (high crest factor).
Why use this instead of a normal level meter?
A normal meter shows only the present moment, so brief problems vanish before you notice. This keeps a rolling history and cumulative stats, so a one-off clip, an intermittent fan, or gradual level drift is visible after the fact. Leave it running through a take and review it.
What do the session stats mean?
Session peak is the loudest single sample since you started or last cleared. Average (RMS) is the overall mean level across the whole session. Clips counts how many distinct times the signal reached digital full scale. Elapsed is how long the current session has been running.
Can I hear myself while monitoring?
Yes — click "Monitor (hear yourself)" to route your mic to your output. It’s off by default. Use headphones: on speakers the mic picks up its own output and you’ll get feedback. Monitoring uses the same in-browser path; nothing is recorded.
What does the history window length change?
It sets how much time the chart shows — 30, 60, or 120 seconds. A shorter window gives finer time detail; a longer one shows more of the session at once. Changing it clears the chart so the time axis stays consistent (session stats keep accumulating).
Why are the levels in dBFS?
dBFS (decibels below digital full scale) is the natural unit for a digital input — 0 dBFS is the maximum before clipping. A browser can’t measure calibrated dB SPL, so these are relative to full scale and depend on your input gain, which is exactly what you want for watching recording levels.
Does it record my audio?
No. The signal is metered in real time to draw the history and stats only; nothing is recorded, saved, or transmitted. The microphone is released when you press Stop or close the tab.
Does it disable auto-gain?
Yes — it requests the raw signal with auto-gain, noise suppression and echo cancellation off, so the history reflects your true input. If your OS forces auto-gain, you may see the level drift on its own; turn off microphone "enhancements" in system settings.
Which browsers support the microphone input level history feature?
Chrome, Edge, Firefox, and Safari (iOS 15.1+ and macOS 14.1+) all support the Web Audio API required for this monitor. Chrome and Edge give the most reliable raw mic access with constraints (auto-gain off) honoured. Firefox may ignore some constraints. On iOS, the page must be loaded over HTTPS and the user must interact before audio starts — both conditions are met here automatically.
What is a good average RMS level to aim for when recording voice or podcast audio?
For speech recording the generally accepted target is an average RMS of −18 to −20 dBFS, with peaks kept below −6 dBFS. This leaves headroom for post-processing while keeping the signal well above the noise floor. The session Average (RMS) stat on this monitor lets you confirm you hit that range over a full take — something a standard peak meter cannot show you.
How do I troubleshoot the "No microphone permission" error?
If the browser shows a permission error: (1) click the lock or microphone icon in the address bar and set microphone access to "Allow"; (2) reload the page and press Start again. On macOS, also check System Settings → Privacy & Security → Microphone and ensure the browser is listed. On Windows 10/11, open Settings → Privacy → Microphone and verify apps are permitted. If no devices appear in the drop-down, check that your interface or headset is connected and recognised by the OS before pressing Start.