Why Your Browser Mic Level Doesn't Match Windows Sound Settings

Your microphone level meter in Windows Sound Settings shows 40%. You run a browser mic test and it shows 75%. You lower Windows input volume to 30% — and the browser meter barely moves. This is not a bug. It is Chrome's Auto Gain Control (AGC) doing exactly what it was designed to do.

What Chrome Does to Your Microphone Signal

When any website calls getUserMedia() — the browser API that requests microphone access — Chrome does not simply pass through the raw signal from your microphone. It applies a processing chain by default:

• Auto Gain Control (AGC): Automatically adjusts the gain to keep your voice at a consistent level. If Windows drops your input volume, AGC compensates by boosting the signal.
• Noise Suppression: Filters out background hiss and hum.
• Echo Cancellation: Removes echo caused by speaker feedback.

These three are enabled by default on every getUserMedia call unless a website explicitly disables them using audio constraints. Most websites, including most mic test tools, do not disable them.

The technical constraint names are autoGainControl, noiseSuppression, and echoCancellation.

Why Windows Volume and Browser Level Disagree

Here is the actual signal path:

1. Your microphone capsule generates a signal
2. Windows receives it at the OS driver level (this is what Windows Sound Settings shows)
3. The browser receives the OS signal and passes it through WebRTC processing (AGC, noise suppression, echo cancellation)
4. The processed signal is what the browser mic level meter shows

The Windows input volume slider controls step 2. AGC in step 3 partially compensates for changes at step 2.

This is why: lowering Windows input from 100% to 60% might only move the browser level from 75% to 65% — AGC is fighting the reduction.

How to See This in Action

1. Go to miccheckonline.com/mic-test and note your level while speaking
2. Open Windows Sound Settings → Input → Device Properties
3. Lower the input volume from 100% to 50% while the mic test is running
4. Watch the browser level meter — it will drop less than you expect

The gap between what you set and what the meter shows is AGC working.

What This Means Practically

Scenario 1: You lowered Windows mic volume but people still say you're too loud

AGC is compensating. The real fix is to also reduce gain in your conferencing app (Zoom, Teams, Discord) — or disable automatic gain control inside the app.

Scenario 2: You raised Windows mic volume but the browser level didn't change much

AGC is capping the level. You are already at the AGC target. The OS volume change had little effect.

Scenario 3: Your mic test shows a great level but you sound bad in Zoom

Zoom applies its own processing on top of WebRTC. The browser level and Zoom's internal level are not the same signal path.

The Real Control Points

To reliably change your voice level on calls, adjust these in order:

1. Physical mic gain knob (if your mic has one) — comes before all software
2. App-level input control (Zoom Settings → Audio, Teams Settings → Devices) — this is the most reliable
3. Disable automatic gain control in the app — Zoom: uncheck "Automatically adjust microphone volume"; Discord: Settings → Voice & Video → disable Automatic Gain Control
4. Windows input volume — affects the baseline but is partially compensated by AGC

What MicCheck Online's Mic Test Shows

The level meter on miccheckonline.com/mic-test shows the post-processing browser signal — the same signal your browser-based calls (Google Meet, Zoom web client) will use. It is a realistic representation of what Meet and Teams receive when you use them in a browser.

If you use the Zoom or Teams desktop app instead of the browser version, those apps use their own audio stack and may show different levels than the browser test.