Browser Permissions & WebRTC Diagnostics
How to Allow Webcam Access in Safari for a Specific Website Permanently
Safari's Websites settings tab lets you set a genuinely permanent per-site camera policy — Allow, Deny, or Ask — that persists indefinitely rather than prompting on every single visit. This lives under Safari Preferences (or Settings on newer macOS) → Websites → Camera, separate from the macOS-wide System Settings camera permission covered elsewhere on this site.
Configuring Permanent Website Permissions in macOS Safari
Safari maintains two separate layers of camera permission that are easy to conflate: a macOS-wide System Settings toggle that governs whether Safari can access the camera at all, and Safari's own internal per-website permission list that governs which specific sites, once that broader access is granted, are allowed to actually use it. This guide covers the second, more granular layer.
Unlike a one-time prompt response, this dedicated Websites settings tab shows every site Safari has ever asked about in one place, with an explicit, persistent dropdown for each — genuinely useful when you want to set up trusted sites (a regular video-conferencing platform, for instance) once and never be asked again, without needing to hunt for an individual prompt each time.
Step-by-Step Setup Guide
Step 1: Open Safari → Settings (or Preferences on older macOS versions).
Step 2: Click the "Websites" tab.
Step 3: Select "Camera" from the sidebar list
Of website-specific permission types.
Step 4: Find the specific site in the list
Or visit it once first if it doesn't yet appear, since Safari only lists sites that have already requested camera access at least once.
Step 5: Change its dropdown from "Ask" to "Allow"
For a permanent, no-prompt permission going forward.
Step 6: Optionally set the "When visiting other websites" default
At the bottom of the same panel if you want a different fallback policy for sites without their own specific entry. ↑ Test with the widget above.
This Setting Is Per-Mac, Not Per-Apple-ID
It's worth knowing that Safari's website permission list is tied to the specific Mac and user account you configure it on, not synced automatically via iCloud to your other Apple devices — setting a site to "Allow" on your MacBook doesn't carry that same permanent permission over to an iPad or a different Mac you also use, each of which maintains its own separate list requiring its own one-time setup.
If you regularly use the same handful of trusted sites — a specific video-conferencing platform for work, for instance — across multiple Apple devices, budgeting a few minutes to set up the same permanent permission on each device individually is worth doing once, rather than being surprised by a fresh prompt on a second device you assumed was already configured.
If a site you've set to "Allow" starts prompting again unexpectedly after a macOS update, that's a known, occasional side effect of major system updates resetting certain privacy-adjacent settings back to their defaults — checking the Websites tab again after any significant macOS upgrade is a reasonable, quick habit rather than assuming your permanent setting was somehow specifically reverted.
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.