macOS Tahoe 26 Moved Camera and Mic Permissions — Here's Where They Live Now
Quick answer: In macOS Tahoe 26, camera and microphone permissions live under System Settings, Privacy & Security, now grouped by category, with a new Privacy Dashboard that shows which apps recently used your camera or mic. If an app can't access them, grant access there — and if the app never appears in the list, a permissions-database reset usually fixes it. Confirm the hardware works first with the webcam test.
The reorganized permissions
Tahoe refined how macOS handles app permissions. The Privacy & Security section is now organized into clear categories — Camera, Microphone, Files and Folders, Screen Recording and more — so you toggle access per app in one predictable place. The new Privacy Dashboard summarizes recent access to sensitive resources, letting you review and revoke anything unexpected at a glance.
When an app can't see the camera or mic
The most common Tahoe issue is an app that simply never appears in the Camera or Microphone list, so there is nothing to toggle. This usually means the permissions database didn't register the request. Restarting the Mac and re-launching the app to trigger a fresh prompt fixes many cases. For stubborn ones, resetting the relevant permission via Terminal (the tccutil reset approach) forces macOS to re-detect apps and prompt again.
Video-call niceties in Tahoe
Tahoe also added an Edge Light effect that uses the Mac's display to illuminate your face like a virtual ring light on video calls in low light — handy if your webcam footage looks dim. It is separate from permissions but worth knowing if you are troubleshooting how you look on camera rather than whether the camera works.
Prove the hardware is fine
Before digging through settings, open the webcam test and the microphone test in your browser. They run locally and confirm the camera and mic themselves are healthy, so you know whether you are chasing a permissions problem or a hardware one.
Sources: MDN — MediaDevices.getUserMedia() · Microsoft — Camera, microphone and privacy
Frequently asked questions
Where are camera and microphone permissions in macOS Tahoe?
Under Privacy & Security, organised into clear categories including Camera and Microphone, where you toggle access per app in one predictable place. A Privacy Dashboard also summarises recent access to sensitive resources.
Why doesn't my app appear in the Camera list at all?
The list only shows apps that have actually requested access. Quit the app, reopen it and take an action that needs the camera — if it still never appears, the app build is the problem rather than macOS.
How do I force macOS to prompt again?
Restarting the Mac and re-launching the app triggers a fresh prompt in many cases. For stubborn ones, resetting the relevant permission with the tccutil reset approach forces macOS to re-detect apps and prompt again.
Will these permission settings change on my Intel Mac?
No. Tahoe is the last version of macOS that runs on Intel Macs, so the layout described here is the one you keep.
Tahoe is the end of the line for Intel Macs
macOS Tahoe is the last version of macOS that runs on Intel Macs. Its successor, macOS 27, was announced at WWDC 2026 and is Apple Silicon only. If you are on an Intel Mac, Tahoe is where your permission model stops changing — the layout described on this page is the one you will keep.
That also sets a floor under this article for Apple Silicon owners. The permission prompts described here are enforced through the Hardened Runtime, which every notarised Mac app must use. An app has to declare a camera or microphone entitlement to request access at all, so an app that never triggers a prompt is usually an app that was not built to ask — not a broken permission.
Practical consequence: if an app is missing entirely from System Settings, Privacy and Security, Camera, do not keep toggling settings. The list only shows apps that have actually requested access. Quit the app, reopen it, and take an action that needs the camera. If it still never appears, the app build is the problem, not macOS.