Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

Camera access in mobile Chrome is controlled at two levels, and both must allow it. First, the operating system app permission: your phone has to grant the Chrome app access to the camera. Second, the Chrome site permission: Chrome has to allow the specific website to use the camera. If either layer blocks it, the website cannot see your camera, no matter how many times you tap Allow.
Quick steps (Android):
Modern websites such as video-call apps, KYC and ID-verification flows, online webcam tests, and QR or barcode scanners request your camera through a browser API called getUserMedia(), part of the WebRTC stack. When a page calls this API, Chrome does not silently hand over the camera. Instead it forwards the request through two gatekeepers.
The first gatekeeper is the operating system. Android and iOS treat Chrome like any other app: unless you have granted the Chrome app camera access at the OS level, Chrome itself has no camera to offer a website. The second gatekeeper is Chrome's per-site permission. Even when the OS trusts Chrome, Chrome still asks you, per website, whether that specific origin may use the camera. This two-layer model is why a camera can appear "blocked" even after you tapped Allow once.
One more requirement underpins all of this: camera APIs only work in a secure context. The page must be served over HTTPS (or be running on localhost during development). On a plain HTTP page, Chrome will not even surface the permission prompt.
On Android you usually need to confirm both layers. Start with the operating system, then move to Chrome's site setting.
Unblock a specific site you blocked earlier:
On iOS the model is simpler but more restrictive, because Chrome on iPhone and iPad runs on Apple's WebKit engine rather than its own.
Important iOS limitation: the Camera and Microphone toggles only appear in Settings > Chrome after a website has requested camera access at least once. If you do not see them yet, open a webcam-test page in Chrome first to trigger the request, then return to Settings. Also note that Chrome on iOS does not support per-site camera permissions; access is granted at the app level for all sites at once, which is a constraint imposed by iOS WebKit rather than by Chrome.
Because permission has two layers, the OS app permission and Chrome's per-site permission. Allowing one but not the other still blocks the camera. On Android, check both Settings > Apps > Chrome > Permissions > Camera and Chrome > Settings > Site settings > Camera.
Open Chrome > Settings > Site settings > Camera, expand the Blocked list, tap the site, and choose Allow, then reload the page. You can also tap the lock or info icon next to the address bar, open Permissions > Camera, and set it to Allow.
Yes. Android Chrome supports per-site camera permissions, so you can allow a single origin while keeping others blocked. Chrome on iOS does not offer per-site permissions; access is granted app-wide for all sites at once.
Open iOS Settings, scroll to Chrome, toggle Camera on, then open the site in Chrome and tap Allow on the prompt. The Camera toggle only appears in Settings > Chrome after a website has requested camera access at least once.
Likely the OS has not granted Chrome camera access (Settings > Apps > Chrome > Permissions), the page is not served over HTTPS, another app or tab is already using the camera, or a work or school policy blocks it. Check each of these in turn.
Open Site settings for the site in Chrome and tap Reset permissions (or clear the site's data), then reload the page so Chrome prompts you again. On the next visit the in-page Allow prompt reappears.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance