BROWSER PERMISSIONS GUIDE
How to Enable Microphone Access in Your Browser
If a site says your browser cannot access the microphone, start with the site permission first, then check whether the browser itself is allowed to use the microphone in your operating system. This guide shows the quickest path for Chrome, Safari, Edge, and Firefox, then lets you verify the fix with a live Microphone Test on the same page.
Allow microphone?
Use the selected microphone on this site.
Best for: microphone blocked, permission denied, no browser prompt, or a site cannot hear you.
Fast path: pick your browser, change the site permission, refresh, then test the microphone below.
If the live meter moves after the change, browser capture is working and the remaining issue is probably app-specific.
Permission changed? Test it here.
Use the live tool below after changing a browser or system permission. If the meter and waveform move when you speak, the browser permission part is fixed.
REAL-TIME MICROPHONE TEST
Microphone Test: Input Meter & Waveform
Device names may appear after you allow microphone permission.
Diagnostics & Tips
- 1) Click Start and allow microphone permission.
- 2) Speak and watch the volume meter and waveform.
- 3) If input is missing, select a different microphone device.
OPTIONAL SETTINGS
Advanced Options & Recording
Tune getUserMedia constraints for this Microphone Test and (optionally) control recording time limits and playback.
Advanced OptionsApplied as getUserMedia constraints (may vary by browser/OS).
+
Applied as getUserMedia constraints (may vary by browser/OS).
Tip: If you change these while listening, restart the test to apply them.
Recording (Optional)Auto-record starts when you click Start. Download exports the current clip (even while recording).
+
Auto-record starts when you click Start. Download exports the current clip (even while recording).
Live mic path
Permission to meter to playback
Meter
Moving
Loopback
Headphones
Clip
Playback
Input
Select the right microphone
Browser permission, device labels, and system input all have to point to the same source.
Signal
Watch level and waveform
A live meter confirms that speech reaches the browser before you troubleshoot apps.
Quality
Use playback or loopback
Listen for clipping, delay, echo, Bluetooth quality drops, and wrong-device routing.
STEP BY STEP
How to allow microphone access in each browser
Use these browser-specific steps if the live test does not trigger a prompt or the site still says microphone access is blocked.
Google Chrome
Chrome usually needs the site permission changed first. If you clicked Block earlier, Chrome can keep the site blocked without showing a new prompt.
- Click the lock or tune icon in the address bar and set Microphone to Allow.
- If the site is in Chrome’s blocked list, remove the block and refresh the page.
- If the prompt still does not appear, check that Chrome is allowed to use the microphone in your device privacy settings.
Microsoft Edge
Edge has both site-level permission and Windows privacy checks. A site can be allowed in Edge but still fail if Windows blocks microphone access.
- Click the lock icon in the address bar and allow Microphone for the current site.
- Open Edge site permissions if no prompt appears, then remove this site from the blocked list.
- On Windows, confirm Microphone access and desktop app access are enabled for Edge.
Mozilla Firefox
Firefox often needs the previous denial cleared before it will ask again. Reload after changing the permission.
- Click the lock icon and clear the blocked microphone permission for this site.
- Reload the page so Firefox can show a fresh permission prompt.
- If you use a headset, make sure Firefox is not still pointing to the built-in microphone.
Safari on macOS or iPhone
Safari often needs two checks: the website permission in Safari and the app permission in Apple privacy settings.
- In Safari website settings, set Microphone for this site to Ask or Allow.
- On Mac, open System Settings > Privacy & Security > Microphone and allow Safari.
- On iPhone or iPad, check the browser permission in Settings if the website never shows a prompt.
COMMON BLOCKERS
What to do when the permission prompt never appears
A missing prompt is a strong signal that the browser thinks it already knows your choice, or the environment is not eligible to request the microphone in the first place.
Step 1
Reload the page after clearing the site-level block. Many browsers do not re-prompt until refresh.
Step 2
Make sure you are on HTTPS. Browser microphone access is limited on insecure origins, except localhost.
Step 3
Close Zoom, Teams, Discord, Meet, OBS, or any tab that may already be using the microphone.
Step 4
If you opened the page inside an app browser, switch to full Safari or Chrome.
Step 5
On Mac or Windows, confirm the browser itself still has microphone access at the operating-system level.
Google Meet Help specifically calls out browser site permissions, browser-level microphone settings, and system-level access as separate checkpoints, which matches real-world failure patterns for general microphone tools too.
VERIFY THE FIX
How to confirm the browser permission is actually fixed
Do not stop after the browser says Allow. The reliable test is whether live input is detected on the same setup you plan to use later.
Use a live meter
Speak at normal volume and watch the input meter and waveform. A moving waveform confirms the browser can capture sound from the selected microphone.
Check device labels
If the device list shows real microphone names after you allow access, that is another good sign. Browsers often hide labels until permission is granted.
Use playback if available
If your browser supports local recording, download or play back a short clip. This confirms that access works and that your voice sounds normal, not just that the meter moves.
WHY ACCESS FAILS
Why browser microphone access gets blocked
Modern browsers do not let websites record audio automatically. The first time a page requests the microphone, the browser asks you to allow or block access. If you clicked Block before, or if your browser or operating system later removed access, the site can no longer read the microphone until you reverse that decision.
The site was blocked before
This is why users often see no permission prompt on later visits. The browser remembers the old choice and keeps the site blocked until you clear or change it.
The browser is blocked by the system
The site may be allowed in Chrome, Safari, Edge, or Firefox, but Windows, macOS, iOS, or Android can still deny the browser access to hardware input.
The page is inside the wrong environment
In-app browsers, old browser versions, insecure pages, or another app already using the microphone can make a browser permission issue look harder than it is.
The reliable order is site permission first, system privacy second, then device selection and app conflicts.
Browser Microphone Permission FAQ
Why does my browser say microphone blocked even after I clicked Allow before? +
Browsers and operating systems can change permissions after updates, privacy resets, profile changes, or if the browser was denied at the OS level. Re-check both the site permission and the operating-system microphone permission for that browser.
Why do I not see any microphone prompt now? +
The site was often blocked before, so the browser suppresses a new prompt. Clear the old block, refresh the page, and make sure you are using HTTPS or localhost.
How do I reset microphone permission for one website? +
Open the site settings from the address bar lock or permissions icon, find Microphone, and remove the old block or change it to Allow. Then refresh the page so the browser can request microphone access again.
Why are microphone device names hidden in the browser? +
Browsers often hide real microphone names until a site has microphone permission. Start the test, allow access, then reopen the input device list to see labels such as headset, USB mic, webcam mic, or built-in microphone.
Does enabling microphone access mean the site can record me in the background? +
Browsers still show microphone-in-use indicators and only let sites capture audio while the page is active and permission is granted. For your site specifically, the tool runs locally in the browser and does not upload audio.
What if microphone access works in one browser but not another? +
That usually means the issue is browser-specific settings, not the microphone itself. Test the same device in both browsers, then compare site permission, default input selection, and OS access.
Why does the microphone work here but not in Zoom, Meet, Discord, or Teams? +
If the live browser test detects input, your browser can capture the microphone. The meeting or chat app may still be using a different input device, muted settings, its own permission layer, or noise processing that blocks voice input.
Should I fix browser permissions or operating-system permissions first? +
If the browser prompt appears, check the site setting first. If no prompt appears or every site fails, check the operating system permission for the browser as well.
Related microphone guides
Windows 11 Mic Fix
Fix microphone not working on Windows 11 with a practical checklist for privacy settings, input selection, volume, headset jacks, USB mics, and drivers.
Discord Mic Test
Use a Discord mic test workflow to fix no input, wrong device selection, silent playback, and mic quality problems before you join voice chat.
iPhone Mic Test
Run an iPhone microphone test online in Safari or Chrome, check live input and playback, and fix common problems like blocked permissions, muffled sound, and Bluetooth routing.