videocalling
Before your call

Background Noise & Echo Meter — Test Your Mic Environment Online

Measure ambient noise, spot hum and hiss, and check for echo before a call — runs entirely in your browser.

Loading…

How to use it

  1. 1

    Click Start measuring

    Allow microphone access when your browser prompts. Audio is analyzed locally — nothing is uploaded.

  2. 2

    Read the dB meter

    The big number is the rolling 1-second average. Aim for −50 dB or quieter for clean meetings. Below −40 dB is acceptable for most calls.

  3. 3

    Check the frequency profile

    If the low band dominates, you likely have hum from a fan or AC. If the high band is loud, that's hiss from appliances or a noisy mic.

  4. 4

    Run the echo test

    Press Run echo test. The tool plays a short tone, then measures what bounces back. If echo is detected, soften the room with curtains, rugs, or a headset.

Reading the dB scale

The decibel scale used here is digital full-scale (dBFS): 0 dB is the loudest signal your microphone can capture without clipping, and quieter sounds sit at negative numbers. Casual silence in a typical home office reads around −55 to −45 dB. Normal speech at the mic peaks around −20 to −10 dB. The meter floors at −60 dB so the display doesn't flicker on near-silence.

The big number is a rolling 1-second average — that smooths out the natural ups and downs of speech and gives you a stable read of how quiet your room actually is. The smaller "Current" and "Peak" numbers reflect instantaneous levels and short-term peaks.

Why echo happens (and how to fix it)

Echo isn't a microphone problem. It's a room problem. Hard surfaces — bare walls, floors, monitors, windows — bounce sound back into the mic, and your call partner hears a delayed copy of your voice. Most modern conferencing tools use echo cancellation, but it works better when there's less echo to cancel.

The fixes, in order of effort:

  • Wear headphones. Eliminates the speaker→mic feedback loop entirely. This single change solves echo for almost everyone.
  • Move your mic closer. Closer to your mouth = louder voice relative to room reflections. Even 10 cm makes a difference.
  • Lower your speaker volume. Less direct sound = less reflection.
  • Add soft surfaces. Rugs, curtains, couches, even a stack of books absorbs reflections. You don't need a foam-treated studio — just break up the parallel hard walls.

Hum, hiss, and what they mean

The four-band frequency profile maps roughly to physical causes:

  • Low (≤200 Hz) — fans, AC units, traffic rumble, refrigerator compressors. If this band dominates, look for something humming nearby.
  • Low-mid (200–500 Hz) — voice fundamentals. This band tends to fill out when you're talking; it's not noise per se.
  • Mid (500 Hz – 2 kHz) — voice clarity range. High energy here usually means you're speaking; high energy in silence can mean nearby conversations.
  • High (≥2 kHz) — hiss, sibilance, keyboard clicks, appliance whine. Persistent high-band energy with no speech is the signature of a noisy mic or a buzzy power supply.

When you can't change rooms

Sometimes you can't fix the room — you're traveling, sharing a workspace, or stuck in a noisy coffee shop. Three practical fallbacks:

1. Use a headset mic. Headset and earbud mics are physically close to your mouth, so they pick up far less of the room. 2. Turn on noise suppression. Most modern conferencing tools (Zoom, Meet, Teams, Whereby, Daily, our app) have a noise-suppression toggle. It's usually off-by-default for the speaker side and on-by-default for your outgoing mic. 3. Record key sections in advance. If you're hosting a presentation in a noisy environment, pre-record sensitive segments in a quieter spot and play them during the call.

The goal isn't a silent room. It's a room quiet enough that listeners can focus on what you're saying instead of straining past your environment.

Browser support

BrowserStatusNotes
Chrome 90+ (desktop & Android)Full
Edge 90+Full
Safari 14+ (macOS & iOS)PartialThe echo test is less reliable on iOS because device speakers sit close to the mic and aggressive echo cancellation may suppress the tone.
Firefox 88+Full
Internet ExplorerUnsupported

Frequently asked questions

Is my audio uploaded anywhere?+

No. The meter uses the Web Audio API and reads aggregate numbers from the analyser node. The audio buffer never leaves your browser, and nothing is recorded.

What dB reading is good for a meeting?+

Anything at or below −50 dB is excellent — quiet enough that listeners won't hear your room. −50 to −40 dB is good. Above −30 dB, your background will be audible to others.

Why does my dB number look high even when I'm not talking?+

That's ambient noise: fans, computer hum, traffic, AC, neighbors. The dB readout reflects the room, not just your voice. The frequency profile helps you see *what kind* of noise it is.

How does the echo test work?+

We play a short 1 kHz tone burst from your speakers and measure how much sound your mic picks up immediately after the tone ends. If significantly more energy is reflected back than the baseline noise level, that's an echo. It's an approximate test — the tips below cover the practical fixes.

I see Echo detected — what should I do?+

Echo is almost always a room problem, not a gear problem. Add soft surfaces (rugs, curtains, a couch), move your mic closer to your mouth, lower your speaker volume, or — easiest of all — wear headphones.

Why does the meter need microphone access?+

There's no way to measure room noise without listening to it. We only read aggregate analysis values from your browser's audio engine; we don't record or upload the signal.

Does this work on mobile?+

Modern mobile browsers support `getUserMedia` and the Web Audio API, so the meter works on iOS Safari and Chrome on Android. The echo test is less reliable on mobile because phone speakers are physically close to the mic.

Related tools