Conclusion: First determine whether the audio reaches the browser
Check the microphone connection and physical mute, then verify input level, waveform, and the device in use in DevelopTools before opening the meeting page. If normal, check input selection, in-app mute, permissions, and network settings in the meeting application.
| order | What to Check | Points of judgment |
|---|---|---|
| 1 | connection | The headset or USB microphone to use is recognized |
| 2 | Permissions | Allow it in DevelopTools and begin input |
| 3 | selection | The active device is the microphone used for meetings |
| 4 | Volume | Meter and waveform respond to your normal voice |
| 5 | Meeting app | Select the same input device and unmute it |
Narrow down the areas to check based on symptoms
Microphone “recognition,” “voice input,” and “passing to the app” are separate steps. We do not conclude that the microphone itself is malfunctioning just because there is no sound, but record the extent to which it was successful.
| Symptoms observed | Main points to check | Next action |
|---|---|---|
| No authority request/failure to obtain authority | Site permissions, OS permissions, HTTPS, management policies | Check address bar permissions and OS privacy settings |
| Mic starts but meter doesn't move | Physical mute, input volume, separate device, connection | Re-select the device and compare it to the OS input meter |
| DevelopTools is responsive | Devices, muting, permissions, and audio processing on the conference app side | Proceed to input settings within the target app |
| Only certain browsers do not respond | Site permissions, supported APIs, audio restrictions, browser implementation | Compare with another browser using the same device and microphone |
| Only the volume is unstable | Distance, input gain, AGC, driver, app processing | Compare the level and recording before and after settings under the same conditions |
Even if the test works, we do not guarantee that it will work with Zoom, Google Meet, Microsoft Teams, Discord, etc. Each service has its own device selection, muting, audio handling, and permissions.
Priority cause for this symptom
- Physical mute is already enabled before opening the meeting application
- The built-in microphone and headset selections are mixed up.
- Browser site permissions differ from meeting service permissions
- Confusing headphone selection for output with microphone selection for input
- The meeting application's own noise suppression or automatic gain affects the audio
If input can be confirmed in DevelopTools, that indicates that audio from the selected microphone is at least reaching the current browser. However, it cannot confirm that the meeting app works correctly, playback for the other party, or network quality.
If the browser used for the meeting differs from the browser where DevelopTools is open, check site permissions and OS permissions for each. Desktop meeting applications have separate app-specific permissions and input settings.
The name and order of the settings screen will change depending on OS/browser updates and organization management policies. If it doesn't exactly match the text in the article, look for items like Microphone, Microphone, Site settings, Privacy & Security, etc.
Range and limitations that can be confirmed with microphone test
| Item | What you can check with current tools | something that cannot be determined |
|---|---|---|
| Input confirmation | Displays input level, time waveform, and frequency spectrum | The response is a clue that the audio has reached the browser, and is not an automatic determination of a malfunction. |
| Level display | Estimated dB and meter with RMS converted for display | It is not the dB SPL of a calibrated sound level meter and cannot be used for absolute comparisons between devices. |
| device | Select from default or list to display track label and sample rate in use | Before permissions, labels and non-default devices may be restricted. |
| audio processing | Require echoCancellation, noiseSuppression, autoGainControl to be false | A simple boolean is a desired value, and the actual applied value is not checked on the screen. |
| Record | Create a WebM of up to 5 minutes in the browser when MediaRecorder is supported, and confirm saving after stopping. | There is no in-page recording and playback function, and it cannot be used if the browser does not support WebM recording. |
| Termination processing | Stop MediaStreamTrack and close AudioContext on stop and page exit | It does not control the use of microphones maintained by the OS or other applications. |
Estimated dB is a guideline for comparing before and after changes in distance and input volume using the same device and same microphone. Display values alone do not guarantee sound pressure, device sensitivity, or call quality. Frequency display is also an analysis clue and is not a substitute for a calibrated measuring instrument.
The record button is enabled after the microphone starts and displays a confirmation before recording starts and after stopping and before downloading. Recordings can be up to 5 minutes using WebM. There is no in-page playback, so check the saved file in a local compatible player.
Proceed with confirmation and correction in order
- 1. Connect the microphone used for the meeting and disable physical mute.
- 2. Select the target device in DevelopTools and speak in your normal voice.
- 3. Check the input level, waveform, and device in use.
- 4. If needed, record several seconds of audio, save WebM locally, and check how it sounds.
- 5. Select the same device in the meeting app and disable in-app mute.
If you change multiple settings at the same time, you will not be able to determine the cause. Please change one item at a time and retest at the same distance and voice volume each time.
Check the current specifications with official information
Permission UI, OS setting names, and API support will be updated. Based on the following primary information, we do not apply old screen procedures or unofficial browser fixed values as they are.
| Confirmation destination | URL | What you will see in this article |
|---|---|---|
| Google Chrome Help「Use your camera and microphone in Chrome」 | https://support.google.com/chrome/answer/2693767 | Current guidance on site permissions, default microphone, mute, and restart |
| Mozilla Support「How to manage your camera and microphone permissions with Firefox」 | https://support.mozilla.org/kb/how-manage-your-camera-and-microphone-permissions | Resetting microphone permissions by site in Firefox |
| Microsoft Support「Windows camera, microphone, and privacy」 | https://support.microsoft.com/windows/privacy/windows-camera-microphone-and-privacy | Edge site permission and Windows microphone permission |
| Microsoft Support「How to set up and test microphones in Windows」 | https://support.microsoft.com/windows/hardware/drivers/how-to-set-up-and-test-microphones-in-windows | Windows input devices, input volume, and test procedures |
| Microsoft Support「Turn on app permissions for your microphone in Windows」 | https://support.microsoft.com/windows/privacy/turn-on-app-permissions-for-your-microphone-in-windows | Microphone access and desktop app permissions in Windows 11 |
| Apple Support「Control access to the microphone on Mac」 | https://support.apple.com/guide/mac-help/mchla1b1e1fe/mac | Microphone permission in macOS Privacy & Security |
| Apple Support「Change the sound input settings on Mac」 | https://support.apple.com/guide/mac-help/mchlp2567/mac | Sound Input, input device, input volume |
Check again under the same conditions after making corrections
Reload the page after changing settings, and if necessary, stop and restart your microphone. Compare the device name, sample rate, input level, waveform, frequency, and short WebM recording under the same conditions.
| Reconfirmation items | Clues to normalcy | Next division if remaining |
|---|---|---|
| Permissions | Changes from waiting for permission to inputting | Check OS permissions, HTTPS, and management policies |
| device | The intended microphone name is displayed on the device in use. | Reconnect and check OS defaults and browser selection |
| Input | Level and waveform change according to voice | Compare with physical mute, gain, different ports, and different devices |
| Target app | The app's input meter also responds | Check input selection, mute, permissions, and restart on the app side |
After confirming, press "Stop Microphone". The tool stops the retrieved MediaStreamTrack and closes the AudioContext. Also make sure that the browser's microphone usage display disappears.
Example: Check a USB headset before a meeting
After connecting a USB headset, select the device name from the DevelopTools list. If the input level and waveform move when you speak, you can verify the input path to the browser.
Next, open the conferencing app and select the same headset as the input device. Do not conclude that the conferencing app is working correctly based only on DevelopTools results.
- Connect a USB headset.
- Start the microphone and check the device in use.
- Speak at a normal volume for about 10 seconds.
- Check the meeting application's input settings and mute state.
Obtain consent when recording another person's voice. Stop the microphone after checking.
Frequently asked questions
- If it responds in DevelopTools, does that mean it will also work correctly in Zoom or Teams?
- It can indicate that audio reaches the browser, but separately check input selection, permissions, mute, and network settings in the meeting app.
- Is recorded audio sent to a server?
- Microphone Tester recordings create WebM in the browser and download it to the device if you choose to save. Audio is not sent to a server.
Try It in Your Browser
Your input is processed entirely in your browser. Keep the original data, review the output, and only then save or share it.
Open microphone test