Camera Test Permission Blocked: How to Allow Camera Access in Your Browser

Last reviewed 2026-05-06. Targeted at the moment a browser camera test page loads, the live preview area is dark or empty, 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 Camera Test Online (in-browser via the MediaDevices.getUserMedia() Web API; no upload, no install).

Free Tool Online Editorial Team

Why the camera preview stays dark: three permission states explained

A browser-side camera test asks the operating system for live video frames through the MediaDevices.getUserMedia() Web API. Before the page can paint a single frame in the preview area, the user agent (your browser) consults its per-origin permission store and decides whether to honor the request. Three end states are possible, each producing a different on-page result for the reader holding a dark preview:

• 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 live preview area renders frames 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 camera access, the browser silently rejects the request, and the live preview stays dark or shows a "permission denied" notice. A small camera-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 live preview stays dark, 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 camera-with-a-slash, you are in case (b) and the steps below switch the per-site permission back to Allow.

Chrome (desktop)

Chrome stores camera 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 camera icon shows a red slash through it, click that icon.
2. In the small popup, set Camera to Allow (sometimes labelled "Always allow on this site"). Close the popup.
3. Reload the page (Ctrl/Cmd + R). The live preview should activate within a second.

If you do not see the camera 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/camera directly, scroll to the Not allowed to use your camera list, find https://freetoolonline.com, click the trash icon next to it to clear the rule, then reload the camera test page; Chrome will surface a fresh permission prompt the next time the page calls getUserMedia. On managed devices (school or workplace policy), camera 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 camera icon to the left of the URL when a page has requested or been granted access. Steps:

1. Click the camera icon to the left of the URL. A panel labelled Permissions opens.
2. Find the Use the Camera 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 → Camera → 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 keeps two camera-permission states distinct: a temporary Blocked Temporarily that clears with one page reload, and a permanent Blocked that survives reloads until you edit it under about:preferences#privacy → Permissions → Camera → Settings. Most readers landing on this camera-test guide hit the temporary state on a first visit and assume the webcam is permanently disabled; Firefox's small camera-with-slash icon in the URL bar is the diagnostic that tells the two states apart before you change any per-site rule.

Safari (macOS)

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

1. With the camera test page open, choose Safari → Settings for freetoolonline.com from the menu bar (or Safari → Settings → Websites → Camera).
2. Set the camera 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 camera at the OS level - open System Settings → Privacy & Security → Camera, 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 camera 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 camera icon at the left of the address bar, choose Allow, reload. If the icon is hidden, open edge://settings/content/camera 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.

Mobile camera permission - iOS Safari and Android Chrome

Mobile cameras sit behind two permission gates on phones - one the browser owns (per-origin Camera = Allow / Block) and a second the operating system owns above it (Settings → Privacy & Security → Camera lets Safari or Chrome touch the lens at all). A dark preview on the camera test page after you tap Allow in the browser prompt is the classic sign that the OS-level toggle is the blocker, not the per-site rule. iOS adds a third wrinkle: front-camera vs rear-camera selection inside the browser is governed by the same Camera permission, but the page's facingMode hint can land on a lens whose privacy LED you cannot see, so reload-once-after-allow is the recommended verification step.

iOS Safari. Open Settings → Apps → Safari → Camera. Set the default for "Camera" to Allow (or Ask). Then, with the camera test page open, tap the small aA button in the address bar and choose Website Settings → Camera → Allow. Close and re-open the tab. iOS also requires that Safari itself has Camera access in Settings → Privacy & Security → Camera → 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 → Camera → Allow. If the toggle is missing, open Settings → Site settings → Camera, 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 → Camera must be set to Allow only while using the app (the default) for any site to use the camera.

Reset a stuck camera-blocked state when the slash icon will not clear

The single most reliable diagnostic for "I keep getting denied" is the small camera-with-a-slash icon in the address bar - it means the browser is remembering an earlier Block decision against the freetoolonline.com origin and silently rejecting future getUserMedia calls without surfacing a fresh prompt. Closing the tab, reloading the page, or even quitting the browser will not clear this decision because per-site camera rules are stored against the origin, not against the tab or session. The fix is to delete the remembered per-site entry so the next visit triggers a brand-new permission prompt, after which the camera icon switches back to plain (allowed) and the live preview activates without restarting the browser. Each desktop browser exposes the per-site camera entry in a slightly different place:

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

After clearing, reload the camera 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.

Privacy and what the camera test actually does

The browser camera test on this site renders the live preview entirely in your browser. The page calls navigator.mediaDevices.getUserMedia({ video: true }) to ask for a video stream, attaches the stream to a hidden <video> element, and reads frames into a <canvas> for display - all on your device. No frame is uploaded, no recording is saved, and stopping the test releases the stream and the camera light goes off. If the camera light 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 camera within a second.

Permission you grant from the camera-with-slash icon in the address bar only authorises pages on freetoolonline.com to call getUserMedia({ video: true }) while a tab from this origin is active. The grant does not carry across origins, does not extend to sub-pages of other domains, and the browser revokes it automatically the moment you flip the per-site setting back to "Ask" or "Block". Closing the tab also releases the live preview - the camera indicator light turns off as soon as the stream stops, so leftover access is bounded by tab lifetime rather than session length. The Privacy Policy documents the no-upload, no-recording contract for the camera-test surface in plain language.

Related reading

• Camera Test Online - the actual test action: a live preview that confirms the selected camera is delivering frames to the browser.
• Camera Test Black Screen: 4 Fixes That Work - what to check when permission is granted but the preview is still dark (cable, in-use elsewhere, lens cover, driver).
• Webcam Mirror vs Flip Explained - what the mirror toggle does and why your reflection looks different to your meeting partner.
• Before a Video Call - Which Tools to Run - a five-minute pre-call checklist.
• How to Check Webcam and Microphone Before an Interview - sequencing the camera and mic tests for a high-stakes call.