Microphone Test Permission Blocked: How to Allow Mic Access in Your Browser

Last reviewed 2026-05-06. Targeted at the moment a browser microphone test page loads, the level meter stays flat while you speak, and either a permission prompt is sitting in the address bar that you ignored, or one already-denied prompt has hidden itself. Routes the actual test action to Microphone Test Online (in-browser via the MediaDevices.getUserMedia() Web API; no upload, no install).

Permission blocked vs no prompt at all

A browser microphone test asks the operating system for live audio frames from a capture device. Before the page can read any sample, the user agent (your browser) must run a permission check. Three end states are possible, and they look different on the page:

• Allowed. The permission prompt either appears once and you click Allow, or the browser remembers an earlier Allow from this site and skips the prompt entirely. In both cases, the level meter starts responding to your voice within a second or two of the page finishing its initial paint.
• Blocked (denied). You answered the prompt with Block at some point - on this page or on another page from the same origin - and the browser remembered the choice. There is no new prompt; the page asks for microphone access, the browser silently rejects the request, and the level meter stays flat or shows a "permission denied" notice. A small microphone-with-a-slash icon is usually visible in the address bar.
• Ignored (no decision). The prompt did appear, but you clicked elsewhere, switched tabs, or the prompt scrolled into a part of the screen you did not look at. The browser keeps the request pending without committing to either state. The level meter stays flat, but unlike the blocked case, the browser is not yet remembering "no" - the next page reload will surface the prompt again.

Knowing which of these three states you are in saves time. If a small icon appears in the address bar, you are in case (a) or (b); if there is no icon and the page says nothing, you are in case (c) and a single reload often fixes it. If the icon shows the microphone-with-a-slash, you are in case (b) and the steps below switch the per-site permission back to Allow.

Chrome (desktop)

Chrome stores microphone permission per origin in the user profile. To grant or re-grant access:

1. Look at the very left of the address bar. If the microphone icon shows a red slash through it, click that icon.
2. In the small popup, set Microphone to Allow (sometimes labelled "Always allow on this site"). Close the popup.
3. Reload the page (Ctrl/Cmd + R). Speak into your microphone; the level meter should jump within a second.

If you do not see the microphone icon, the permission may already be set to "Block" and Chrome may be hiding the icon when no recent request has fired. Open chrome://settings/content/microphone directly, scroll to the Not allowed to use your microphone list, find https://freetoolonline.com, click the trash icon next to it to clear the rule, then reload the microphone test page; Chrome will surface a fresh permission prompt the next time the page calls getUserMedia. On managed devices (school or workplace policy), microphone access can be policy-blocked at the OS or admin-console level - in that case Chrome shows "Managed by your organisation" and the per-site toggle is greyed out.

Firefox (desktop)

Firefox shows the active permission as a small microphone icon to the left of the URL when a page has requested or been granted access. Steps:

1. Click the microphone icon to the left of the URL. A panel labelled Permissions opens.
2. Find the Use the Microphone row. If it shows Blocked Temporarily, click the x next to the entry to clear it, then reload the page; Firefox will re-prompt. If it shows Blocked with no x, the choice was made permanent - open about:preferences#privacy, scroll to Permissions → Microphone → Settings, find the freetoolonline.com entry in the list, change it to Allow or remove it, then save and reload.
3. When the prompt re-appears, click Allow (and optionally tick Remember this decision so Firefox does not ask again).

Firefox separates "blocked temporarily" (one-page-load decision) from "blocked permanently" (origin-level decision). Most users hit the temporary case on a first visit and do not realise that a single page reload would have re-prompted. The permanent case requires the about:preferences route above.

Safari (macOS)

Safari ties microphone permission to the per-website settings for the active Safari profile, not to a single page session. To allow:

1. With the microphone test page open, choose Safari → Settings for freetoolonline.com from the menu bar (or Safari → Settings → Websites → Microphone).
2. Set the microphone dropdown for freetoolonline.com to Allow.
3. Close the settings panel and reload the page (Cmd + R).

If "Allow" is not in the dropdown, macOS itself may be blocking Safari's access to the microphone at the OS level - open System Settings → Privacy & Security → Microphone, ensure Safari is toggled on, then return to Safari and retry. macOS surfaces a one-time prompt the first time Safari tries to use the microphone on any page; once that is allowed, per-site Safari preferences take over.

Edge (desktop)

Edge follows the Chromium permission model with the same UI flow as Chrome. Click the microphone icon at the left of the address bar, choose Allow, reload. If the icon is hidden, open edge://settings/content/microphone and clear or change the per-site rule for freetoolonline.com. Edge on managed Windows installations also respects Group Policy - if the toggle is greyed out, the IT admin has policy-locked the setting and a per-user override is not possible from the browser UI.

iOS Safari and Android Chrome (mobile)

Mobile browsers add an OS-level layer in front of the per-site permission, so a "blocked" microphone test on mobile can have two distinct fixes - one in the browser, one in the OS settings.

iOS Safari. Open Settings → Apps → Safari → Microphone. Set the default for "Microphone" to Allow (or Ask). Then, with the microphone test page open, tap the small aA button in the address bar and choose Website Settings → Microphone → Allow. Close and re-open the tab. iOS also requires that Safari itself has Microphone access in Settings → Privacy & Security → Microphone → Safari - on a fresh device or after a privacy reset this can be turned off.

Android Chrome. Tap the lock or info icon to the left of the URL, then Permissions → Microphone → Allow. If the toggle is missing, open Settings → Site settings → Microphone, find the freetoolonline.com entry under "Blocked", clear it, then reload the page so Chrome re-prompts. The Android OS has its own layer too - Settings → Apps → Chrome → Permissions → Microphone must be set to Allow only while using the app (the default) for any site to use the microphone.

When you keep denying by accident: clean revoke and re-grant

If you have clicked through several "Block" decisions in different browsers and want a clean reset, the most reliable path is to clear the per-site permission entirely so the browser asks fresh on the next page load. Each browser has a slightly different setting URL:

• Chrome / Edge: chrome://settings/content/microphone or edge://settings/content/microphone → remove the freetoolonline.com entry under "Not allowed to use your microphone".
• Firefox: about:preferences#privacy → Permissions → Microphone → Settings → remove the entry.
• Safari (macOS): Safari → Settings → Websites → Microphone → select the entry and click Remove.

After clearing, reload the microphone test page; the browser treats the next getUserMedia call as a first-time request and surfaces a fresh prompt. This is also the right route when shared computer accounts have left a stale Block decision from a previous user.

If permission is allowed but the meter is still flat, the cause is downstream of the browser. Three downstream causes account for almost all "permission OK but no sound" reports: (1) the OS-level master toggle is off (macOS: System Settings → Privacy & Security → Microphone; Windows: Settings → Privacy & security → Microphone with both app-access toggles on), (2) another app holds the device (Zoom, Teams, Google Meet, Discord, OBS Studio, or a virtual-mic driver like Krisp / NVIDIA Broadcast / VoiceMeeter / Loopback - quit the offending app), or (3) hardware mute / wrong input device (USB-headset cable mute switch, laptop function-key mute, or a Bluetooth-headset auto-pair to the wrong device - confirm the active input in System Settings → Sound → Input). The dedicated four-cause walkthrough is at Microphone Test No Sound: 4 Fixes That Work - it covers each downstream cause in detail.

Privacy and what the microphone test actually does

The browser microphone test on this site reads the live audio stream entirely in your browser. The page calls navigator.mediaDevices.getUserMedia({ audio: true }) to ask for an audio stream, attaches the stream to a Web Audio analyser node, and renders the level meter from the analyser's frequency-domain output - all on your device. No sample is uploaded, no recording is saved, and stopping the test releases the stream and the microphone indicator goes off. If the indicator stays on after you leave the page, that is almost always another tab or another application holding the device, not this page; closing the offending tab releases the microphone within a second.

Granting permission to freetoolonline.com only authorises this origin's pages to call getUserMedia while you are on a tab from this origin. Permission does not persist across origins, does not extend to sub-pages of other domains, and the browser will revoke it automatically if you change the per-site setting back to "Ask" or "Block". The Privacy Policy documents this in plain language.

Related reading

• Microphone Test Online - the actual test action: a live level meter that confirms the selected microphone is delivering audio frames to the browser.
• Microphone Test No Sound: 4 Fixes That Work - what to check when permission is granted but the meter is still flat (OS toggle, app holding, hardware mute).
• Microphone Test Levels: What Quiet, Normal, and Peak Mean - reading the meter once permission is allowed.
• Microphone Test Online: What It Actually Checks - what a browser microphone test can (and cannot) tell you about your setup.
• Camera Test Permission Blocked: How to Allow Camera Access in Your Browser - the symmetric guide for camera permission, useful when both video and mic are blocked before a call.
• How to Check Webcam and Microphone Before an Interview - sequencing the camera and mic tests for a high-stakes call.
• Before a Video Call - Which Tools to Run - a five-minute pre-call checklist.