Microphone Not Working? How to Find Out Whether It's the Browser, Your System or the App
Microphone not working? Run TryYourGear's Microphone Test, then work through browser permission, system privacy, input device, other apps and the app.
When a microphone “doesn't work”, the problem can sit in five different places: the browser's permission for a site, the operating system's privacy switch, the input device that is selected, another app that is holding the microphone, or the settings of the app you actually want to use. Changing settings at random mixes them up.
The TryYourGear Microphone Test can check one thing: whether your browser can get audio from the microphone. Its result tells you which layer to look at next. It can't diagnose drivers or hardware, and it can't see what a particular app is doing.
What this guide can and can't tell you
A working result means the browser layer works in this test. A failing one points you to the layers below, in order. Neither proves that the microphone hardware is fine or faulty.
Run the test and read its state
Open the Microphone Test, press Start microphone test and answer the browser's prompt. Then speak. Match what you see to a row.
| What TryYourGear shows | What it suggests | What it doesn't show |
|---|---|---|
| “Requesting microphone access…” and nothing else happens | The browser is waiting for your answer to the permission prompt, or the prompt isn't visible. Look near the address bar and answer it. | Why no prompt appeared. |
| “Microphone access was denied…” | The browser reported that access wasn't allowed. Start with layer 1 (the site's permission), then layer 2 (the system's privacy switch). Browsers report this same error for several reasons, including you blocking the site or blocking all access globally. | Which of those reasons applies: the test can't tell a blocked site from a blocked system. |
| “Could not access your microphone. It may already be in use by another app.” | Any failure other than a permission denial ends here. The browser can report, for example, that no matching device was found or that the device couldn't be read. Check that the microphone is connected and selected (layer 3) and that no other app has it (layer 4). | Which error it was. “In use by another app” is one possibility, not a diagnosis. |
| The test is active and the level bar moves when you speak | The browser is receiving audio from the microphone selected in the test's list. Layers 1 to 3 work for the browser. If another app still fails, look at layers 4 and 5. | That the app you want to use has access, or how it processes the sound. |
| The test is active but the level bar stays flat | The browser gets no signal, or almost none, from the selected input: the wrong device, a muted or very low input volume, or a physical mute switch. Try the other inputs in the test's device list, then check layer 3. | The cause. The level is relative, not in decibels, so a very quiet microphone can look flat too. |
| The level moves and the 5-second recording plays back your voice | The whole browser path works: permission, device, capture and playback. | How other apps process your voice, or whether the quality suits a call. What you hear is your own judgment. |
Browsers report a permission denial and a device problem as different errors; the test keeps the first apart and groups everything else as “could not access”. MDN's getUserMedia reference lists what each one means.
Layer 1: the browser's permission for the site
Permission is granted per site, and each browser keeps its own list. Change it for the site you're testing, then reload the page and run the test again.
| Browser | Where to change it |
|---|---|
| Chrome | Settings > Privacy and security > Site settings > Microphone. Select the blocked site and change its permission to Allow, as Chrome Help describes. The same page lets you pick the microphone Chrome uses. |
| Edge | Settings > Cookies and site permissions > Microphone, as Microsoft documents for Teams on the web. Other Microsoft pages describe it under Privacy, search, and services > Site permissions > All sites (Microsoft Support), so menu names vary slightly between Edge versions. |
| Firefox | Click the permissions icon in the address bar and clear the Blocked status so Firefox asks again, or go to Settings > Privacy & Security > Permissions > Microphone > Settings, as Firefox Help describes. |
| Safari (Mac) | Safari > Settings > Websites > Microphone, then choose the option for the site (Apple Support). |
The Microphone Test has its own list of inputs, and Chrome also lets you choose the default microphone under Site settings > Microphone. If the level doesn't move, try another input in the test's list first.
Layer 2: the system's privacy switch
- Windows 11: Start > Settings > Privacy & security > Microphone. Make sure Microphone access and Let apps access your microphone are on. Windows lists Microsoft Store apps individually and controls the rest with Let desktop apps access your microphone; Microsoft says an app you can't find in the list is likely a desktop app. Web browsers are normally desktop apps, so that toggle usually applies to them, although Microsoft doesn't list browsers by name.
- Windows 10: Start > Settings > Privacy > Microphone, with Microphone access for this device, Allow apps to access your microphone and Allow desktop apps to access your microphone.
- macOS: Apple menu > System Settings > Privacy & Security > Microphone. Turn access on for each app in the list; if your browser is listed, make sure it is on.
Sources: Microsoft Support and Apple Support. A system-level block affects the browser as a whole, so it can stop the microphone on every site, not just one. Chrome's help also notes that the system's camera and microphone permissions matter.
Layer 3: the right input device
A microphone can be connected and working without being the one the browser or the system is using. The test lists the inputs the browser exposes; the system has its own default.
- Windows 11: Start > Settings > System > Sound, and under Input use Choose a device for speaking or recording. Selecting a microphone shows its properties, with an Input volume slider and a Start test button: speak, choose Stop test, then Play to hear it (Microsoft Support).
- macOS: Apple menu > System Settings > Sound, where you choose the input device and set its volume (Apple Support).
On Windows you can compare the two tests. If the system's test hears you but the TryYourGear level doesn't move, look at layers 1 and 3 in the browser. If neither hears you, the problem is in the system or the device. This narrows down where to look; it doesn't prove a hardware fault.
Layer 4: another app is using the microphone
An app can hold a microphone so that another one can't open it. Close other apps that may have it open (calls, recorders, streaming or voice software) and run the test again; Microsoft's Teams troubleshooting page lists this check too.
In Windows, an app can also open a device in exclusive mode, which gives it exclusive use of it. The setting Allow applications to take exclusive control of this device is in the Sound control panel, under Recording, in the device's Properties > Advanced, and Microsoft's documentation explains that exclusive-mode access is enabled by default and can be turned off per device. The test's error message mentions another app as a possibility, but the test can't confirm it.
Layer 5: the app's own settings
Even when the browser and the system are fine, an app has its own permission and its own device choice. In Microsoft Teams, for example, you pick the microphone in Settings > Devices > Audio settings and can make a test call (Microsoft Support); other apps have their own equivalents. Check the microphone the app has selected, the app's permission in the system (layer 2) and, for a web app, that site's permission in your browser (layer 1).
What to do with your result
It works in TryYourGear but not in an app
The browser layer worked in this test: the browser could get audio from the microphone. That doesn't point to a single cause. Check the app's own device selection (layer 5), the system permission for that app (layer 2) and whether another app has the microphone (layer 4). The permission you gave TryYourGear applies to TryYourGear only, so a web app in the browser needs its own (layer 1).
It doesn't work in TryYourGear
Go through layers 1 to 4 before assuming the microphone is faulty: the site's permission, the system's privacy switch, the selected input and other apps. If the system's own test doesn't hear you either, try the microphone on another computer, or another microphone on this one. TryYourGear can't tell you whether the hardware is faulty; it can tell you that the browser is getting nothing from it.
The same permission layers apply to a camera. If your camera is blocked too, the Webcam Test works the same way: it reports a permission denial separately from other errors.
Summary
- Run the Microphone Test and read its state: permission denied, another error, or active with a level that moves or stays flat.
- Go through the layers in order: the browser's permission for the site, the system's privacy switch, the right input device, other apps using the microphone, and the app's own settings.
- Working in TryYourGear means the browser layer works in this test. It doesn't say what an app is doing.
- Not working in TryYourGear means checking permissions, the input and the system before suspecting the hardware, and even then the test can't confirm a fault.