Guide · 4 min read
Blocked camera or mic: 7 symptoms and what each one means
A denied permission almost never announces itself. It turns up as a black square, a one-sided silence, or a prompt that never comes back. Here are the seven ways it actually appears.
Why the browser never says "blocked"
Browsers keep this deliberately quiet. When you deny access — or simply dismiss the prompt — the page is handed nothing and is never told why, which is how a two-tap setting ends up feeling like a broken website. Girls Video checks the permission before it starts a call, so a hard no gets you a panel saying the camera or microphone is unavailable and a "How Can I Provide Permission?" button that walks through your particular browser step by step. The confusing cases are the ones in between, where something is half-granted and nothing warns you at all — which is what the seven symptoms below are for.
1. The call connects but your own tile is black
The connection is fine; the page simply has no video track to send. A real network problem takes both directions down and announces itself with stuttering audio first, so a black tile alongside clean incoming sound is nearly always a permission you never granted. You will meet this version on sites that never check — here the app tests the permission first, so the usual outcome is that the call does not start at all and the guidance panel appears instead.
2. The camera indicator light never comes on
Laptops and phones light up whenever the sensor is genuinely in use, and on most devices that light is wired to the sensor itself rather than to software, so a page in the browser cannot switch it off. No light usually means nothing ever opened the camera, which rules out half the things you were about to try. It is the fastest check on this list and it takes one glance. On recent phones the equivalent is the small dot that appears at the top of the screen while the camera is live.
3. She can hear you but cannot see you (or the reverse)
Camera and microphone are two separate permissions and can be answered independently. Approving one and dismissing the other is an easy way to end up half-connected without realising it. Check both in the site settings, not only the one that looks broken — the half that works will happily convince you the site is fine. The reverse case, sound with no picture, has exactly the same cause with the answers swapped.
4. The prompt never appears again
Most browsers ask once per site. Tap outside the box, press escape, or say no in a hurry, and that answer is remembered silently for every later visit. Reloading will not bring the prompt back — you have to clear the stored answer first, which is why the page seems to have quietly given up on you. It is one of the likeliest causes on this list, because the prompt tends to appear at the exact moment you are looking somewhere else.
5. A crossed-out camera icon sits in the address bar
On a computer this is the clearest signal there is, and it stays there once you have said no. Click the lock, open site settings, set camera and microphone to allow, then reload — the new permission only takes effect on a fresh load, which is the step people most often skip before deciding the fix did not work. If you added the site to your home screen there is no address bar at all: open the same site in the browser you installed it from, reset the permission there, then come back to the home-screen app.
6. It works in one browser and fails in another
Permissions are stored per browser and per site — the permission panel here says as much, warning that access is requested separately for every browser and computer you use. So a working camera in one and a black square in another is entirely normal, and it is proof the hardware itself is fine. Use it as a two-minute test: if the camera works elsewhere, stop debugging the device and go straight to site settings in the browser that failed.
7. The site is allowed but the browser is not
Phones add a second layer: the operating system decides whether that browser may touch the camera at all. If the site shows as allowed and it still fails, the block is one level up, filed under the browser's own name rather than the site — on an iPhone that is Settings, then Safari, then the per-website camera and microphone entries, or Settings then Chrome if that is what you use. This is the one that catches people out after a new phone or a system update, because everything else was migrated except this.
The reset that fixes most of them
The shape of the fix is nearly always the same: open the site's permission settings, reset what is stored there, reload the page, then answer the prompt when it comes back. On a phone, check the system-level toggle under the browser's name as well. If you would rather not go hunting, the panel that appears when access is refused has a walkthrough written for the exact browser you are on. And while you sort it out you do not have to sit the conversation out — a text chat needs no camera at all, and a voice call only needs the microphone.
The girls are online now.
Browse who is online, pick someone you like, and start a private 1-on-1 — video, voice or text. Free to start.
See who is online