Mac Camera Not Working? 8 Things to Check
The green light, the permission list, the app already holding the camera, and five more checks, in the order that finds the fault soonest.
The call where your face is a grey rectangle
The call started ten minutes ago and nobody can see you. The camera worked yesterday. Nothing was installed, nothing was dropped, and the little dot in the menu bar isn't lit.
That silence narrows the search faster than any settings hunt, because a Mac fails at the camera in three separate ways. It doesn't see the hardware. It sees the hardware and refuses to let the app use it. Or it's already handing the camera to something else. Each fault lives somewhere different, and the checks below are ordered to find the right one soonest.
Start with the light
Open Control Center and read the camera row. The indicator names whichever app touched the camera in the last few minutes. A green dot beside an app means the hardware works and somebody is holding it. No dot at all, while an app insists no camera exists, points away from permissions and toward the hardware or the process behind it.
That one glance decides whether the rest of this list takes two minutes or twenty.
1. Quit the app that already has it
On most Macs one process holds the camera at a time. The culprit is rarely the app you're staring at. A browser tab left open on a Meet page keeps the stream alive, and so does a call you joined in Slack and never closed. Zoom's window can be shut while its helper keeps running.
Check the dot, quit the likely holders, then reopen the app you actually want.
2. Read the permission list
System Settings, Privacy and Security, Camera. The list holds every app that has ever asked, with a switch beside each one. Two failures hide here.
The first is a switch that is off, usually because a dialogue appeared mid-meeting and got clicked away. The second is quieter. An app that was denied once doesn't ask again, so it fails silently from then on and nothing inside the app explains why. Flip the switch and most apps start working without a restart.
3. Reset the permission for one app, or all of them
When the switch is on and the app still reports no camera, the stored permission has gone stale. That happens after an app update re-signs its bundle. Terminal clears it in one line:
tccutil reset Camera
That drops the camera entries for everything, so each app asks fresh the next time it wants the lens. If you know which app is broken, name its bundle identifier and leave the others alone:
tccutil reset Camera com.tinyspeck.slackmacgap
Some apps close themselves the moment their permission is revoked. Open them again and answer the prompt that appears.
4. Ask the Mac what it can see
FaceTime and Photo Booth ship with every Mac and ask for nothing unusual, which makes them the neutral test. A working picture in Photo Booth means the hardware is fine and the fault belongs to the app that failed. A crossed-out camera icon in Photo Booth too means the problem sits below the app layer.
Terminal answers the same question with more detail:
system_profiler SPCameraDataType
A camera listed with a resolution and a model identifier means macOS sees the hardware. An empty result is a hardware or service fault, and permission fiddling won't bring it back.
5. Restart the process that serves the camera
The lens is handed out by a background assistant, and that assistant is the piece that hangs when a call crashes mid-stream. Restarting it fixes the "camera unavailable" state more often than any settings change:
sudo killall VDCAssistant
It launches again on demand the next time an app asks. If Terminal isn't your idea of a good time, logging out and back in does the same job and loses nothing.
6. Take the hub out of the path
An external webcam on a busy hub produces the same symptoms as a software fault. Video needs a steady slice of USB bandwidth that a hub shared with a display, an SSD and a card reader cannot always give, so the camera enumerates and then drops when the stream opens.
Plug it into a port on the Mac itself. A picture that returns there means the hub was the fault, and the fix is a powered hub or fewer devices on that branch. A USB camera that fails on one Mac and works on another points at the port rather than the camera.
7. Check the phone pretending to be a camera
Continuity Camera lets an iPhone stand in for the built-in lens, and it brings its own failure mode. The phone needs the same Apple ID, two-factor authentication on the account, Bluetooth and Wi-Fi on for both devices, and a phone that is awake and nearby.
When the phone is asleep in another room, some apps fall back to the internal camera and others report that no camera is available at all. If the camera menu in a call lists your iPhone, deselect it and the built-in lens comes back. Desk View and Center Stage sit in the same Control Center panel, and both vanish when the phone leaves the room.
8. Safe Mode, and what loads before you do
Safe Mode starts macOS with third-party login items and kernel extensions switched off. On Apple silicon, shut the Mac down, hold the power button until the startup options appear, choose the disk, then hold Shift while clicking Continue in Safe Mode. On an Intel Mac, hold Shift the moment the machine starts.
A camera that works in Safe Mode means a login item is holding it. Virtual camera drivers are the usual suspects, because a conferencing plugin or a streaming setup installs one and keeps it loaded whether or not its app is open. Remove the virtual camera from the app that installed it, then restart.
A work Mac under a management profile can have the camera disabled outright. In that case System Settings carries no Camera entry at all, and the fix belongs with whoever runs the fleet.
When it's the app, and not the Mac
Zoom, Teams, Slack and every browser keep their own camera choice on top of the system one. A camera that works in Photo Booth and nowhere else is a per-app setting, not a system fault, and each app hides that menu in a different place.
Browsers add a second layer, because a web page asks through the browser rather than for itself. Safari keeps per-site answers under Settings, Websites, Camera. Chrome keeps them in the site settings behind the padlock in the address bar. A block recorded there survives every permission reset in System Settings, which is how a Meet call keeps failing while the switch upstairs is on.
Where a native app earns its place
Nothing above needs software. The other problem is the camera that works and still produces a bad picture, and that one's worth an app.
CamCascara records webcam video with the measurements on screen while you shoot. Focus peaking paints the sharpest edges green, so you can watch the lens hunt instead of discovering it in the edit. Stripes cover any highlight that has blown out, which is how you find out that the window behind you is the reason your face is dark. Backgrounds are replaced or blurred inside the app, thirteen filters switch while the recording runs rather than being baked into a preset, and a landscape webcam is composed into a 1080 by 1920 vertical frame with that framing written into the file. The microphone opens when recording starts and closes when it ends. It runs on macOS and Windows, sells for $29.99 on its own, and comes with the membership.
CreamRec X covers the case where the camera is only half the recording: screen and face in one take, with the microphone and system audio on separate sources, a pause that drops the paused span, and a GIF export small enough for a chat window. MokaStudio takes the result when the takes need trimming, titles or a second track.
The honest limit: CamCascara records your camera. It can't repair one that macOS refuses to see, so run checks one to eight before installing anything.
The order to work in
Read the Control Center dot. Quit whatever is holding the camera. Check the permission switch. Reset the permission if the switch is already on. Test in Photo Booth, then in system_profiler. Restart the camera assistant. Take the hub out of the path. Try Safe Mode if the fault survives a reboot. Five of those steps take less than a minute, and the last two are the only ones that need a restart.
Most cameras come back at step one or step two. If yours does not, the answer usually arrives at step four, and it is a straight answer: the Mac can't see the hardware and no setting will change that.
Related guides
If the machine is misbehaving in more than one way, the fan guide and the Wi-Fi guide follow the same setup-first order for their own symptoms, and the screenshot guide covers the capture side once the picture is finally working.
One menu, one subscription
getapps.cafe carries 128 native apps for macOS and Windows, and 105 of them have a Windows build. Solo Cup is $3.99 a month, or $1.99 a month billed yearly at $23.88. Family Roast is $7.99 a month, or $3.99 a month billed yearly at $47.88, for up to five computers. Both plans unlock the whole menu. The 7-day trial adds a card when it starts and charges nothing until it ends. Start here.