Webcam permissions, indicators, and privacy — what each browser does differently

Close the tab where you were on a video call. Is the camera still active? The answer depends on which browser you were using, which OS you're running, and whether the laptop you bought has a dedicated camera LED. The first part of that question — granting access — works roughly the same way everywhere. The second part — knowing the camera has actually stopped — is where browsers diverge, sometimes in ways that matter.

This is a tour of the differences. Not which browser is "safest" — they're all safe in the sense that no site can quietly turn on your camera without your knowledge — but the small UX gaps that explain why you can never quite remember which icon means "camera was on" and which means "camera is on right now".

How browsers prompt for camera access

The underlying API — navigator.mediaDevices.getUserMedia({ video: true }) — is identical everywhere. What the user sees is not:

• Chrome (and Edge, Brave, Arc, the rest of the Chromium family). A top-of-tab prompt with Allow / Block buttons. The address-bar icon lights up the moment you click Allow.
• Safari. A system-level dialog the first time any site asks. Subsequent visits to the same site honour whatever you picked. You can audit and change choices in Settings → Websites → Camera.
• Firefox. An in-tab popup with a device picker baked in — you choose which camera before granting access, rather than after. "Remember this decision" is opt-in rather than implicit.
• Edge. Like Chrome, plus extra enterprise controls — if you're on a managed device, your admin can pre-permit or pre-block specific origins via group policy.

None of them grant access until you click. The permission state is per-origin, persisted across tabs but not across browsers — granting Zoom.us access in Chrome doesn't grant it in Safari.

Indicator lights — where each browser shows "in use"

This is where the divergence gets messy. Three layers can independently show an indicator: the OS, the browser tab, and the hardware itself.

OS indicators:

• macOS. A green dot in the top-right of the screen, on top of every window, whenever the camera is active. Inherited from the iPhone's privacy indicators in 2021. Unmissable.
• Windows 11. A small camera icon in the system tray when the camera is in use. Less prominent than macOS — you have to be looking at the tray to notice. Click it to see which app is using the camera.
• Linux. Nothing standard. Some desktop environments (recent GNOME, KDE) show a system-tray indicator; many don't.

Browser indicators:

• Chrome / Edge. A red dot on the tab itself plus a camera icon in the address bar.
• Safari. The address-bar icon goes solid red when active. No tab-level indicator.
• Firefox. A red camera in the address bar; the tab also gets a colored bar at the top.

The browser indicator goes away when the page releases the camera. The OS indicator goes away when every application has released the camera — so if you close one tab but another tab in the same browser still has access, the OS indicator stays on. This catches people out.

The hardware light (LED)

On laptops with a dedicated camera LED, the light is wired to the camera module's power. The OS can't turn it off independently of the camera being active. This is by design — if the camera is on, the LED is on, full stop.

This wasn't always the case. Some early-2010s MacBooks had a software-controlled LED that researchers demonstrated could be bypassed by writing directly to the camera firmware. Apple changed the design after that became public. Modern hardware from every major vendor — Apple, Lenovo, Dell, HP, Framework — wires the LED in hardware. If the LED is dark, the camera is off.

Webcams without an LED — many cheap external USB ones, some older laptop modules — have no such guarantee. The browser and OS indicators are the only signal you have.

Per-site vs default-device permissions

Granting getUserMedia access usually means "default camera". Picker permissions — choosing a specific camera — vary by browser:

• Chrome / Edge. Separate dialog after the initial grant. The address-bar permissions panel exposes a Camera dropdown.
• Firefox. Baked into the initial prompt — you pick which camera at the moment of granting.
• Safari. Not exposed at all in current versions. Whichever camera the OS considers default is what the page gets.

Switching cameras mid-session requires the page to call getUserMedia again. Some apps handle this gracefully; some don't, and ask you to refresh.

What can go wrong: a short list

The common failure modes, ranked by how often they actually happen:

• Indicator still on after closing the page. Almost always another tab in the same browser still has the camera. Check the other open tabs first; the system tray on Windows or the Control Center on macOS shows which app is the current holder.
• Wrong camera shown. The browser picked the OS default, and the OS default isn't the one you wanted. Change the default in OS settings or use the browser's device picker (Chrome / Edge / Firefox).
• Camera light on but no preview. The device is being acquired but no frames are reaching the page. Usually a driver issue or another app holding the device in a partial state. Restart the browser before restarting the machine.
• External webcam not detected. If the OS doesn't see it, the browser won't either. Check the system camera app first; that's a clearer test than the browser.
• Permission stuck on denied. Most browsers won't re-prompt automatically after a denial. Reset via the address-bar permissions panel and reload.

Privacy practices: what to expect from a webcam-using site

Honest sites follow three habits:

1. Ask for permission only when needed, not on page load. Drive-by permission prompts are a red flag.
2. Release the device the moment they don't need it. A Stop button that actually stops the stream.
3. Show their own indicator in the UI on top of the browser's. "Camera is on" is hard to miss when the page itself says so.

The camera test on this site follows all three. Start acquires the camera; Stop releases it; nothing auto-reacquires; the page shows its own "camera active" state next to whatever the browser is doing.

When to use the camera test

The camera test is useful for three things: a pre-call sanity check, diagnosing a driver issue, or just seeing what your camera is showing without joining a meeting first. Click Start, look at yourself for ten seconds, click Stop. No frames leave your device.

Related reading

The microphone test covers the audio side. The browser diagnostic shows the full permissions state in one place. The existing pre-call checklist walks through the full five-minute routine, and the three layers of mic permission applies almost identically to cameras — same layers, same diagnostic flow.