Why does the mic work in one tab but not another?

Permission state is per-site. If you blocked access earlier, the browser can keep that decision until you reset permissions and reload.

Can a Bluetooth headset be the problem?

Yes. Bluetooth headsets can switch profiles or degrade when battery is low. Charge it, or test with a wired mic/headset to compare.

Do I need to reinstall the browser?

Usually no. Permissions, OS privacy toggles, drivers, and exclusive capture are the common blockers. Reinstall only after a clean profile test.

Why is the mic distorted after a few minutes?

USB power saving and thermal limits can downshift devices mid-call. Try another USB port, avoid unpowered hubs, and keep the laptop plugged in.

Fix Microphone Not Working in Chrome, Edge, or Firefox (Run the WebRTC Test)

Confirm mic input with the WebRTC Test

Open the WebRTC Test and speak. The input meter should move and show Microphone: allowed. If it is blocked or silent, leave the test open, apply each fix below, and rerun to see which change works. Common symptoms: the mic dropdown is empty, people hear silence, or the input meter is flat.

Fix 1: Allow the microphone for the site

If you clicked "Block" before, the browser will not prompt again.

Click the lock icon in the address bar on the call site and set Microphone to Allow.
Chrome/Edge: Settings > Privacy and security > Site settings > Microphone → remove the site from the blocked list.
Reload the page and check the WebRTC Test meter.

Fix 2: Grant OS microphone permission

The OS can mute access even when the browser allows it.

Windows 10/11: Settings > Privacy & security > Microphone. Turn on device-wide access, then allow your browser.
macOS: System Settings > Privacy & Security > Microphone. Enable your browser, then quit and reopen it.
Linux (PulseAudio/PipeWire): open your audio settings and ensure the default input is not muted.

Fix 3: Pick the right input device

Laptops, monitors, and headsets expose multiple inputs.

In the call app, select the intended mic (USB headset, laptop array, XLR interface).
Chrome/Edge: chrome://settings/content/microphone → set the correct default device.
Unplug unused mics and dongles to simplify the list, then rerun the WebRTC Test.

Fix 4: Unmute and raise input gain

Physical mute switches and low gain often look like a broken mic.

Check the hardware mute button or inline cable switch.
In Windows Sound settings > Input > Device properties, raise input volume and disable Input sensitivity auto-mute features from vendor apps.
On macOS, System Settings > Sound > Input → pick the mic and raise Input level.

Fix 5: Close apps that lock the mic

Only one app can hold exclusive control on many drivers.

Quit desktop Zoom/Teams, Discord, game capture tools, DAWs, or virtual cable apps. On Windows, disable Allow applications to take exclusive control of this device under Sound > More sound settings > Recording > Properties > Advanced.
Reopen the browser and test again.

Fix 6: Update audio drivers and firmware

Outdated or generic drivers can block WebRTC capture.

Windows: in Device Manager > Sound, video and game controllers, right-click your audio device → Update driver. For USB mics, install the vendor package if available (e.g., Blue Yeti, Elgato Wave, Shure Motiv).
macOS: apply system updates; audio class drivers ship with macOS.
Linux: keep PipeWire/PulseAudio and ALSA packages current through your package manager.

Fix 7: Remove extensions that modify audio

Noise suppression or privacy extensions can intercept audio.

Disable virtual audio cable extensions, heavy privacy blockers, and user-agent spoofers.
Open the call in an Incognito/InPrivate window to verify. If the mic works there, add the site to the extension's allowlist or leave it disabled during calls.

Fix 8: Clear corrupted site data

Stuck permissions or cached SDP can block renegotiation.

Chrome/Edge: Settings > Privacy and security > Cookies and other site data > See all site data and permissions → remove the call site.
Reload, allow the mic again, and rerun the WebRTC Test.

Fix 9: Reduce background noise processing when it cuts audio

Aggressive noise filters can mute soft voices.

In Meet/Teams, lower the noise suppression level and retest.
On Windows laptops with vendor audio suites (Realtek, Dell Waves MaxxAudio), disable "noise reduction" or "voice clarity" toggles if they mute your voice.

Verify the fix

Run the WebRTC Test again. The mic meter should respond, and the permission line should be green. Join a call and ask a teammate to confirm your audio. If the mic fails only on a managed device, capture the failing test output and ask IT to review any AudioCaptureAllowed policy in chrome://policy.