Why Your MacBook Camera Shows a Black Screen After Waking from Sleep Mode

macOS runs a background system process to manage which app currently has access to the camera and to hand frames off between apps as needed. Under normal conditions it starts fresh when an app requests the camera and cleanly releases control when that app closes.

Sleep and wake cycles are one of the more common triggers for this handoff to go wrong — the process can come back from sleep still believing it owns an active camera session that no longer really exists, leaving the camera hardware in a locked, unresponsive state until that specific process is restarted. Notably, the indicator light doesn't always reflect this cleanly: some users see the light stay off since the process never actually re-establishes a real capture session, while others see a brief flicker as it half-initializes before failing.

This is a well-known enough behavior that it isn't a sign of anything being damaged — it is a software handoff bug, not a hardware fault, and the fix below resolves it completely without needing any deeper troubleshooting in the overwhelming majority of cases.

Step 1: Open Terminal.

Press Cmd + Space, type "Terminal," and press Enter.

Step 2: Type

sudo killall VDCAssistant and press Enter.

Step 3: Enter your Mac's admin password when prompted

(the password won't be visible as you type — that's normal).

Step 4: Reopen the app that needs your camera.

MacOS automatically relaunches a fresh instance of the process the moment any app requests the camera again. ↑ Or test right here with the widget above.

If the problem returns frequently after every sleep cycle rather than as an occasional one-off, keeping macOS fully updated is worth checking — Apple has refined sleep/wake camera handling across several macOS releases, and older point releases are more prone to this specific bug than current ones.

A couple of habits also reduce how often it happens: fully quitting camera-using apps (not just closing their window) before putting your Mac to sleep gives the handoff process a clean state to resume from, and avoiding closing the lid while a video call is actively connecting — as opposed to already fully connected — sidesteps one of the more common trigger conditions.

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.