Browser Permissions & WebRTC Diagnostics
How to Test Webcam on Brave Browser Without Disabling Fingerprint Protection
Brave lets you grant a camera-specific exception for one trusted site while keeping strict fingerprinting protection active everywhere else you browse. The fix is scoping the change narrowly through the per-site Shields panel, rather than lowering your overall Brave privacy settings globally just to make one specific site work.
Balancing Brave Privacy Features with WebRTC Functionality
A common, reasonable instinct when a privacy feature blocks something you need is to simply turn the whole feature off — but Brave's Shields are specifically designed to be adjusted per-site rather than as a single global switch, meaning you don't have to make that trade-off across your entire browsing experience just to fix one site.
This distinction matters in practice: a work video-conferencing platform you trust and use daily is a reasonable candidate for a permanent, site-specific exception, while your general browsing on unfamiliar sites benefits from keeping Brave's default strict protection fully intact. Brave's per-site model supports exactly this kind of selective, deliberate trust.
How to Grant Specific Media Exceptions in Brave
Step 1: Visit the specific site that needs camera access.
Step 2: Click the Brave lion icon in the address bar.
Step 3: Open the detailed Shields settings for this site
(usually an expandable section within the same panel).
Step 4: Adjust "Fingerprinting blocking" specifically
From Strict to Standard, leaving other protections like ad and tracker blocking untouched.
Step 5: Reload and test.
↑ Confirm with the widget above. If Standard alone doesn't resolve it, the camera-specific permission (padlock icon, separate from Shields) is worth checking too, since both systems need to agree before access works.
This per-site setting persists across future visits automatically, so this is genuinely a one-time setup per trusted site rather than something to repeat on every visit.
Why This Balance Matters
Fingerprinting protection exists because your specific combination of camera model, screen resolution, installed fonts, and dozens of other subtle technical details can uniquely identify you across websites even without cookies — a genuinely powerful tracking technique that most users have no visibility into at all. Brave's approach of making this adjustable per-site, rather than forcing an all-or-nothing choice, is what allows you to keep this protection meaningfully intact while still using the specific sites that need full camera functionality.
If you find yourself creating exceptions for many different sites over time, periodically reviewing your list of per-site Shields adjustments (accessible through Brave's Settings → Shields) is a reasonable habit, since a site you no longer use doesn't need to retain a standing exception indefinitely.
Brave releases regular updates that occasionally refine exactly how Shields interacts with WebRTC and media device access, so if a specific site's behavior changes unexpectedly after a Brave update, checking that site's Shields settings again is worth doing before assuming something you configured has broken on its own.
It's also worth comparing your experience against Brave's own built-in Brave Talk video calling feature, which is naturally exempt from Shields interference since it's a first-party Brave product rather than a third-party site subject to the same fingerprinting protections — if you specifically need reliable video calling in Brave without any per-site configuration at all, that's a genuinely simpler default option worth considering.
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.
For a full check of resolution, frame rate, and audio together, not just this one issue, the free webcam test covers all of it in one place.