macOS 27 Drops Intel: What It Means for Your Mac's Camera and Mic
macOS Tahoe is the final version of macOS that supports Intel Macs. Its successor, macOS 27, was announced at WWDC 2026 and is Apple Silicon only. If your Mac has an Intel processor, the camera and microphone permission model you have today is the one you will keep for the life of the machine.
What the cutoff actually means
This is a clean break rather than a gradual deprecation. Intel Macs stay on Tahoe; Apple Silicon Macs move to macOS 27. For hardware troubleshooting that is unusually good news for Intel owners: the permission layout, the prompts and the Privacy and Security panel stop changing, so any guide written against Tahoe remains accurate indefinitely.
It also means a specific class of advice stops applying to you. Instructions that begin "in the latest macOS" will increasingly describe a system you are not running. Check which macOS a set of steps was written for before following it.
How camera and mic permission works on both
The model is the same on Tahoe and macOS 27, and it is worth understanding because it explains most confusing failures. Camera and microphone access is granted per app, not system-wide. An app that has never asked will not appear in System Settings, Privacy and Security, Camera at all.
Enforcement runs through the Hardened Runtime, which every notarised Mac app is required to use. An app must declare a camera or microphone entitlement before it can even request access. So an app that never produces a permission prompt is usually an app that was not built to ask — that is a build problem, not a setting you can toggle.
macOS also lets only one app hold the camera at a time. That single rule explains most reports of a camera working in FaceTime but not in a browser or a meeting app.
Check the hardware independently
Before you spend time in Settings, establish whether the hardware works at all. Open the webcam test and the microphone test and grant permission when the browser asks. Both run entirely in the browser, so a pass tells you the camera and microphone are physically fine and the driver stack underneath is working.
That result splits the problem cleanly. If the browser test passes and one specific app fails, it is that app's permission or device selection. If the browser test also fails, the problem is below the app layer and worth escalating to a restart or a hardware check.
Where to go next
For a camera that will not start in any app, our guide on fixing a camera on macOS covers the permission grant, the one-app-at-a-time rule and the reset sequence in order.
If the problem is app-specific — working in one place and not another — webcam not working in Teams or Zoom deals with per-app camera selection, which is the usual culprit when the hardware is provably fine.
Sources: MDN — MediaDevices.getUserMedia() · Microsoft — Camera, microphone and privacy
Frequently asked questions
What does the Intel cutoff mean for my Mac?
It is a clean break rather than a gradual deprecation. Intel Macs stay on Tahoe and Apple Silicon Macs move to macOS 27, so for Intel owners the permission layout and the Privacy and Security panel stop changing.
Why does an app never ask for camera permission?
An app must declare a camera or microphone entitlement through the Hardened Runtime before it can even request access. An app that never produces a prompt is usually one that was not built to ask — a build problem, not a setting you can toggle.
Why does my camera work in FaceTime but not in a browser?
macOS lets only one app hold the camera at a time. That single rule explains most reports of a camera working in one place and not another.
How do I tell whether the hardware or the app is at fault?
Run a browser-based webcam and microphone test and grant permission when asked. A pass means the camera and microphone are physically fine, so an app that still fails has a permission or device-selection problem of its own.