Browser Permissions & WebRTC Diagnostics
How to Check WebRTC Camera Permissions in Firefox `about:config`
Three about:config preferences govern WebRTC camera access in Firefox: media.navigator.enabled must be true for the getUserMedia API to exist at all, media.peerconnection.enabled controls WebRTC connections generally, and permissions.default.camera sets the fallback policy applied to any site without its own saved exception already in place.
Essential WebRTC Config Preferences in Firefox
about:config exposes Firefox's full internal preference system — far more settings than the regular Settings UI shows, intended for advanced troubleshooting and testing rather than everyday use. A small number of these preferences relate directly to camera and WebRTC functionality, and checking them can reveal a cause that isn't visible anywhere in the normal Settings pages.
media.navigator.enabled controls whether the underlying getUserMedia API exists in the browser at all — if somehow set to false, camera access would be completely unavailable to every site with no error explaining why, since the API itself wouldn't exist to call.
media.peerconnection.enabled governs WebRTC peer connections broadly, the underlying technology video calls are built on. This is distinct from simple camera preview access and specifically relevant if calls fail to connect even though a local camera preview works fine on its own.
permissions.default.camera sets the numeric default policy (0 for ask, 1 for allow, 2 for block) applied to any site that doesn't already have its own specific saved exception — this is the fallback behavior, not an override of individual site decisions you've already made.
Steps to Verify and Enable Camera Flags
Step 1: Type
about:config in the address bar and accept the warning prompt.
Step 2: Search "media.navigator.enabled"
And confirm its value is true.
Step 3: Search "media.peerconnection.enabled"
And confirm it's also true.
Step 4: Search "permissions.default.camera"
And confirm it's set to 0 (ask) rather than 2 (block) if you want normal per-site prompting behavior.
Step 5: If any value has been changed from its default, right-click it and select "Reset"
Rather than guessing at the correct default manually. ↑ Test with the widget above.
These preferences are rarely changed by normal use — if you've never manually edited about:config before, finding one of these already altered from its default is itself a useful clue that something else (an extension, an enterprise policy, or a previous troubleshooting attempt) modified it.
A Word of Caution With about:config
Firefox shows a warning before entering about:config for good reason — these are genuinely internal settings not meant for casual browsing, and changing unrelated preferences can affect browser behavior in ways that are hard to trace back to the actual cause later. Stick to searching for and checking only the three specific preferences named above rather than browsing broadly through the full list, and use the "Reset" option (rather than manually typing in a guessed default value) whenever you want to undo a change.
If you've never opened about:config before on this particular Firefox installation, finding all three preferences already at their standard defaults is actually the expected, healthy result — it means this specific layer isn't the cause of whatever camera problem you're troubleshooting, and it's worth moving on to checking standard site permissions and hardware acceleration settings instead.
A Few More Things to Check on Windows
How do I reset the Windows Camera app itself?
Go to Settings → Apps → Installed apps, find Camera, open its three-dot menu, and choose Advanced options → Reset. This clears the built-in Camera app’s own cache and settings without uninstalling it, which can fix a stuck, frozen, or permanently black preview even when the underlying device and driver are both working correctly. It only resets that one app — not your camera driver, and not other applications that use the camera.
Could my antivirus be silently blocking my camera?
Many third-party security suites — Bitdefender, Kaspersky, Norton, and ESET among others — include their own webcam-protection feature that runs independently of Windows’ own privacy settings. That means Windows can show camera access as fully permitted while the antivirus software blocks it anyway, at a layer Windows has no visibility into. Check the antivirus program’s own settings, usually under a Privacy, Webcam Protection, or similarly named section, and confirm your browser or conferencing app is on its allow-list.
How do I re-enable my camera in Device Manager if it's disabled?
Right-click the Start button → Device Manager, expand Cameras or Imaging devices, and look for a greyed-out icon or a small down-arrow badge. Right-click that entry and choose Enable device. This is a different action from updating a driver — a disabled device won’t respond to any other fix until it’s explicitly re-enabled here first, so it’s worth checking before assuming the problem is a driver or a permission.
Is Windows' own camera privacy toggle blocking access, separately from anything else?
Windows keeps a system-level camera permission at Settings → Privacy & security → Camera, completely separate from Device Manager, the Camera app, and any antivirus software. This one screen has a master Camera access switch plus a per-app list beneath it — both need to be on. It’s worth checking directly, since a camera can show as fully enabled and working in Device Manager while this toggle silently blocks every app from reaching it.
Once this is fixed, testing your webcam online is a quick way to confirm the camera is fully working again, not just detected.