Operating System & Device-Specific Fixes
How to Allow Browser Camera Access in macOS System Settings
Across macOS Ventura, Sonoma, and Sequoia, browser camera permission lives in the same place: System Settings → Privacy & Security → Camera. Each browser needs its own individual toggle switched on — enabling Safari does not automatically enable Chrome or Firefox, since macOS tracks permission per application.
Managing Camera Privacy in Modern macOS Versions
Apple renamed "System Preferences" to "System Settings" starting with macOS Ventura (13), and reorganized several sections in the process, including privacy controls. The good news is that Ventura, Sonoma (14), and Sequoia (15) all share this same reorganized layout, so the steps below apply identically across all three current-ish versions rather than differing release to release.
The list of apps shown under Privacy & Security → Camera is populated dynamically — macOS adds a browser or app to this list the first time it actually requests camera access, not automatically at install time. If a browser you expect to see is missing entirely, that usually means it has never yet attempted to request the camera, which is worth trying deliberately (visit a site that asks for camera access) before assuming something is broken.
Step-by-Step macOS Camera Permission Guide
Step 1: Open System Settings.
Click the Apple menu → System Settings.
Step 2: Click "Privacy & Security" in the sidebar.
Step 3: Click "Camera."
This shows every app that has ever requested camera access.
Step 4: Turn on the toggle for your specific browser
— Safari, Chrome, Firefox, Edge, or whichever you use. If it's not listed, open that browser and visit any site that requests camera access first, which will add it to this list automatically.
Step 5: Fully quit and reopen the browser
After changing the toggle. ↑ Then test with the widget above — some browsers cache the old permission state until fully restarted, so a simple page refresh alone is often not enough to pick up the change.
Why Every Browser Needs This Done Separately
macOS deliberately does not have a single "allow all browsers" switch — camera access is tracked and granted per individual application as a privacy safeguard, so that granting access to one program never silently extends trust to another you may not have reviewed. This is slightly more setup the first time you configure a new browser, but it also means you always know exactly which specific applications currently have camera access, since the full list is always visible in the same place.
If a Browser Still Can't Access the Camera
A small number of cases persist even after the toggle is confirmed on. Check that no Screen Time or parental-control content restriction is active (Screen Time → Content & Privacy → Apps, if enabled), since that layer can silently override an otherwise-correct Privacy & Security toggle. It's also worth confirming you're editing the toggle for the correct browser if you have multiple versions installed side by side, such as both a regular and a beta or developer channel build — macOS treats these as entirely separate apps with independent permission entries, even though they share a similar name.
A Few More Things to Check on Mac
What are VDCAssistant and AppleCameraAssistant, and why do they matter for camera problems?
These are macOS’s own background processes for managing camera access — VDCAssistant coordinates the camera hardware itself, and AppleCameraAssistant works alongside it. If either one gets stuck, commonly after an app crashes without properly releasing the camera, every app can show the camera as unavailable until both are reset. Opening Terminal and running sudo killall VDCAssistant AppleCameraAssistant forces a clean restart of both, which resolves a large share of stuck-camera and black-screen issues that a simple app restart doesn’t fix.
What is UVCAssistant, and is it different from VDCAssistant?
On some macOS versions, Apple introduced UVCAssistant as an additional process specifically for USB Video Class (UVC) compliant external webcams — the standard most third-party USB cameras follow. If you’re using an external webcam rather than the built-in camera, and killing VDCAssistant alone doesn’t resolve a stuck camera, check Activity Monitor (View → All Processes) for UVCAssistant specifically and force-quit it the same way.
Does Apple Silicon (M1/M2/M3/M4) handle the camera differently than Intel Macs did?
Yes — Apple Silicon Macs route camera video through the chip’s own dedicated image signal processor rather than the path Intel Macs used, and the exact background processes involved can differ across specific Apple Silicon generations. If a fix written for an Intel Mac, or for a different chip generation, doesn’t fully apply on your machine, checking Activity Monitor’s actual running process list — rather than assuming a name from an older guide — is the most reliable way to identify what’s genuinely holding your camera.
Once this is fixed, testing your webcam online is a quick way to confirm the camera is fully working again, not just detected.