MicProbe / Microphone guides
By MicProbe · Updated
Why does my mic sound good in a browser but bad in calls?
A clear browser recording shows that your device captured usable sound in that test. A call adds the app’s microphone selection, sound processing, transmission and the other person’s playback. A problem anywhere along that path can change what the listener hears.
Start by finding where the difference appears. Changing every audio setting at once makes it harder to tell what helped.
1. Make sure both apps use the same microphone
Check the microphone selected in your browser test and in the calling app. A headset, webcam and laptop can each provide an input. An app set to the system default may use a different one after a device connects.
Use the same device and similar microphone distance before comparing recordings. If your voice is missing rather than poor in quality, check mute, microphone permission and the app’s input mode first.
2. Listen to the app’s own microphone check
If the calling app provides a microphone check or recording feature, listen there too. If the browser sample is clear but the app’s check sounds wrong, look at that app’s input and audio settings before assuming the microphone is broken.
For Discord, start with its Voice & Video settings and confirm the input device, input mode and input volume. Discord’s troubleshooting guide covers its current controls.
3. Check sound processing one setting at a time
A calling app may handle background noise, echo and automatic level differently from a browser test. Check its own audio settings and compare one change at a time. Keep a note of the original value so you can restore it.
Removing processing is not always an improvement. For example, echo control matters when speakers feed sound back into a microphone. Listen for the particular problem you are trying to resolve rather than treating every processing option as something to turn off.
4. Separate headset playback from your recorded voice
If you use Bluetooth, sound playing through the headset may change while its microphone is active. That can affect your judgment when you listen back. Compare the same saved recording through another output if available. Read why Bluetooth microphone and playback quality can change.
5. If local checks sound good, check the actual call
Ask whether the problem affects one listener or everyone. If only one person hears it, their playback setup or connection is also worth checking. If everyone hears interruptions, use the calling app’s connection diagnostics or support guidance; a clean local recording cannot rule out a transmission problem.
The app’s own microphone check may not travel through the same path as a real call either. Treat each check as evidence about the part it actually exercises.
Where does MicProbe fit?
Use MicProbe to record, listen and check your side with a local approximation of the selected app’s microphone settings. It does not connect to the app, inspect the live call, test the internet connection or measure the listener’s sound.
A result without warnings only covers the checks that could run on that recording. It does not certify the complete call. Read how MicProbe tests your microphone.
Open the local test for Discord
Using a different app? Open MicProbe to continue your last test or change the selected app.