How to read the meter
The meter shows input level in decibels relative to full scale, which is the same scale every audio application uses. Zero is the loudest signal the system can carry without distorting, so all normal audio sits below it as a negative number.
| Reading | What it means | What to do |
|---|---|---|
| Flat, no movement | No signal reaching the browser | Check the mute switch and selected input; the full fix guide covers the rest |
| Barely moving | Input gain too low | Raise the input level in your system sound settings, or move closer to the mic |
| Green into amber on speech | Healthy | Nothing. This is what you want. |
| Constantly red | Clipping | Lower the input gain. Clipped audio cannot be repaired later. |
| Steady reading in silence | High noise floor | Move the mic away from fans and USB hubs, or enable noise suppression in your call app |
What the readout fields mean
Sample rate is how many times per second the audio is measured. 48000 Hz is standard for video calls, and 44100 Hz is the audio CD rate. Either is fine for speech.
Channels will normally be 1 for a microphone. Speech does not benefit from stereo, and mono uses less bandwidth on a call.
Echo cancellation shows whether the browser is running its own echo suppression. This is on by default and is what stops your speakers feeding back into your microphone when you are not wearing headphones. If you are testing a microphone for music recording rather than calls, this processing will colour the sound.
A note on what browsers do to your voice. Plug in the headset you plan to use first, then check the pair together with the camera and microphone test. By default browsers apply echo cancellation, noise suppression and automatic gain control before the audio reaches this page. That is the right choice for calls but means the level you see is processed, not raw. Music and podcast recording software bypasses all of it.
If the meter does not move
- Look for a hardware mute. Many headsets mute when the boom arm is rotated up. USB microphones often have a mute button that gives no visible feedback.
- Check the right input is selected. Laptops with a headset plugged in have at least two microphones. The input source list on this page shows every input your browser can see.
- Check operating system permission. On Windows this is under Privacy & security, then Microphone. On macOS it is System Settings, Privacy & Security, Microphone. Your browser must be enabled there.
- Check the input volume. Windows lets you set microphone level to zero without indicating anything is wrong. Open Sound settings and confirm the level is above zero.
- Reseat the connection. For a 3.5 mm headset, make sure the plug is fully in. A partially inserted plug often gives audio out but no audio in. If you can hear nothing either, see no sound in the browser.
Other checks
Common questions
Is my voice recorded?
No. Audio is analysed in real time by your browser to draw the level meter and is then discarded. Nothing is written to disk or sent anywhere.
The meter moves but people cannot hear me on calls.
This confirms the microphone and driver work, so the fault is in the calling app. Check which input device that app has selected, and check that you are not muted inside the app or on a hardware mute switch.
What level should I aim for?
Normal speech should push the meter into the middle to upper third, roughly -18 to -6 dB, with the red section reached only on your loudest moments. Constant red means you are clipping and will sound distorted.
Why does the meter never reach zero?
The meter shows decibels relative to full scale, so 0 dB is the absolute ceiling before distortion. Healthy audio sits below it. A meter that pegs at maximum is a problem, not a good result.
Why is there background hiss?
A constant low reading with no one speaking is the noise floor. Cheap microphones, long unshielded cables and USB power interference all raise it. Moving the microphone away from the computer often helps.