Quick answer
What this guide helps you determine
Improve distance, input gain, connection and application settings while avoiding excessive clipping.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
A quiet microphone is often improved by distance, direction and correct input selection before software gain. Excessive gain can amplify room noise and clip sudden sounds, so change one stage at a time from the physical source toward the application.
Step-by-step method
- Confirm the intended microphone is selected and that its capsule faces the source correctly. Move to the manufacturer’s normal speaking distance and check plugs, adapters and interface input type.
- Watch the meter while speaking normally. Increase operating-system or interface input gain in small steps, retesting quiet and loud phrases. Keep peaks below persistent maximum and listen to a short local playback.
- Disable conflicting automatic-gain or noise-processing settings for one comparison, then test the actual meeting or recording app. If one channel or connector remains weak across devices, inspect cable and interface compatibility.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Move closer before adding gain
- Watch peak level for clipping
- Check plug and adapter compatibility
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Level improves greatly when closer | Distance and microphone sensitivity were major factors. | Use consistent placement rather than extreme gain. |
| More gain adds hiss but little voice | Wrong input, connection type or a noisy stage may be involved. | Verify device, cable and interface mode. |
| Browser level is healthy but one app is quiet | That app’s selected input or processing differs. | Review its gain and automatic-level controls. |
Common mistakes to avoid
- Do not connect incompatible powered inputs without documentation.
- Do not set every gain stage to maximum.
- Do not use the browser meter as a calibrated dB SPL value.
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “Level improves greatly when closer”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Should I use microphone boost?
Use only as much as needed after placement and input selection; boost can raise noise and clipping.
Why is a headset mic quiet through an adapter?
TRRS wiring standards, splitter direction and input type may not match. Use a documented compatible adapter.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.