Why Is My Camera Not Working? A Layer-by-Layer Fix

The short answer

Work the layers from physical to software, and stop when the camera starts working. First check there is no shutter slid over the lens and that no keyboard camera key is toggled off. Then confirm your browser can see the camera by running the linked Camera & Mic Test — that single check tells you a lot, because the browser and the call apps ask the operating system the same question.

If the browser test shows your camera working, the hardware and the driver are fine and the problem is a per-app permission or an in-app device selection — go to the app section for the one that is broken. If the browser test shows the camera as black, blocked, or missing, the fix is one layer lower: the operating system's privacy toggle or the driver. If it says no camera was found at all, that is usually the device being disabled, unplugged, or held by another program.

• Physical first: privacy shutter open, any keyboard camera key enabled, indicator light behaviour.
• Then the OS privacy toggle for the camera (Windows Settings, macOS System Settings, iOS/Android Settings).
• Then the app's own permission — a camera that works everywhere except one app is almost always that app's setting.
• Then device ownership: close any other app or browser tab that could already be using the camera.
• Then the in-app device picker — the right camera selected, not a virtual or the wrong one.

How a camera actually gets turned on, and where it breaks

A camera does not simply turn on when you open an app. Between the lens and the video on your screen there is a chain, and every link is owned by something different. At the bottom is the hardware itself — the sensor, its switch or shutter, and the driver that lets the operating system talk to it. Above that sits the operating system's privacy gate, a master toggle and a per-app allowance that the platform enforces before any program is allowed to see a frame. Above that is the application's own permission state, which on phones and browsers is set once and remembered. Next is ownership: on most systems only one program can capture from a webcam at a time, so whoever grabbed it first wins and everyone else gets a black screen or an error. At the top is the app's device selection — which of your several cameras it points at.

This chain is why the symptom tells you the cause. A blank black box inside one app while other apps are fine means a permission at the OS or app layer was denied. A “camera not found” message means the device is disabled, unplugged, or missing a driver. An “in use” or “device not readable” error means another program already owns it. A frozen or wrong view means the app is selecting a different camera than you expect.

Once you can name the layer, the fix is mechanical. The rest of this guide is organised by layer, then by platform, then by app, so you can jump straight to the one that matches your symptom.

Step one: find out which layer is broken

The fastest diagnosis is to ask the browser to open the camera, because a browser requests it through the same operating-system layer that Teams, Zoom and Meet use. Open the linked Camera & Mic Test and press Enable camera. The page uses the browser's own camera API, asks for a video stream, and shows it back to you live along with the resolution and frame rate the camera is actually delivering.

What you see is the verdict. If the preview appears and moves, your hardware and driver are healthy and the fault is further up the chain — a permission or device choice inside a specific app. If a permission prompt appears and you allow it but nothing shows, or it reports access was denied, that is the OS or browser privacy gate blocking the camera. If it says no matching device was found, the camera is disabled, unplugged, or being held by another program. If it reports the camera is already in use or not readable, another app has exclusive ownership right now.

Two honest limits of this test, stated by the tool itself: some call apps hold the camera exclusively, so if Zoom has it open the browser may not be able to grab it even though everything is healthy — close the other app first. And a few rare camera drivers expose only lower resolutions to browsers, which can make a working camera look poor here without being broken.

The physical switches people forget

Before any settings, rule out the two hardware things that look exactly like a software failure. Many laptops have a sliding privacy shutter over the lens; if it is closed the camera returns a uniform black image no matter what the software does. Slide it open and make sure nothing — a sticker, a screen protector, a folded laptop sleeve — is covering the lens.

A lot of laptops also switch the camera off with a keyboard shortcut, often a function key printed with a camera icon, sometimes combined with the Fn key. Check your keyboard for that icon. If you suspect the shortcut is the culprit, the linked Keyboard Tester can show whether that keypress reaches the operating system at all — press it and watch for a key event. Be careful reading the result: many function and media keys are handled by the keyboard's own firmware and produce no event a browser can see, so a silent key there does not prove the toggle is broken. A good physical tell on almost every machine is the camera indicator light: if it never turns on when an app tries to use the camera, the device is off at the hardware or operating-system layer rather than misconfigured in the app.

On a Windows laptop

Windows is the platform most likely to block a healthy camera with a privacy setting, and the fix is a couple of toggles. Open Settings and go to the Camera privacy page — on Windows 11 that is under Privacy & security, on Windows 10 it is simply under Privacy. There you will find a master switch for camera access across the whole device, an option to let apps access the camera, a per-app list, and a separate allowance for desktop apps.

That last one trips people up: webcams used from Chrome, Edge, Firefox, and full desktop programs like the Zoom and Teams installable apps fall under the “desktop apps can access your camera” switch, not the app list. Make sure the master toggle is on, the desktop-app allowance is on, and the specific app you are using is switched on in its own row. Then restart the app.

If the camera is missing rather than blocked: the driver

When the browser test reports no camera found, open Device Manager (right-click the Start button and choose it) and look for your camera under Cameras, Imaging devices, or sometimes Sound, video and game controllers — the grouping has moved across Windows versions. If the entry has a down-arrow icon it is disabled: right-click and Enable. If it has a warning triangle, the driver is the problem.

For a warning state, right-click and try Update driver first; if that does not help, Uninstall device and then restart, which makes Windows reinstall the camera on boot. If the camera does not appear in Device Manager at all, this is more likely a hardware or firmware switch (the keyboard key above) than a driver. After any of this, re-run the browser test to confirm.

Third-party software that intercepts the camera

Some antivirus suites and webcam-privacy utilities add their own camera-protection layer that blocks programs the operating system already allowed. If the browser test fails on Windows but the Settings toggles are all correct, check whether such software is installed and whether its camera or “webcam protection” feature is denying access. Turning that guard off for the app you are using, or temporarily disabling it to test, isolates it as the cause.

On a Mac

macOS gates the camera behind an explicit permission and makes it obvious when a camera is live: a green light next to the lens turns on whenever anything is actually capturing. If that light never comes on, the camera is blocked at the permission or hardware layer; if it does come on but the app is black, the problem is higher up, in the app's own selection.

The permission lives in System Settings under Privacy & Security, then Camera. You will see a list of apps with a switch each, and granting a newly requested app often requires quitting and reopening it to take effect. On an older macOS this same list is under System Preferences → Security & Privacy → Privacy → Camera. If the app you need is not listed or its switch is off, that is your whole problem — turn it on and relaunch the app.

When the camera is greyed out or restricted

If a camera works in no app at all, Screen Time's content and privacy restrictions can disable camera access system-wide, and a management profile from a school or employer can do the same. Check under Screen Time's content-restriction settings, and under Privacy & Security for any configuration profile that governs the camera.

For an external or USB webcam, also try a different port and cable, and unplug it and plug it back so macOS re-enumerates it. A restart resolves a surprising number of stuck camera states because it releases any process that had quietly kept the device open.

On iPhone and iPad

On iOS the camera problem is almost always a per-app permission, because the system asks you once and remembers the answer — and if you ever tapped Don't Allow, the app stays blind forever without an obvious error. Open Settings and go to Privacy & Security, then Camera: you get a list of apps with a switch each. Turn on the app that is failing. If you cannot find it there, scroll to the bottom of Settings to the app's own entry and look for its Camera permission directly.

If apps are fine but the Camera app itself has vanished or refuses to open, Screen Time may be hiding it: Settings → Screen Time → Content & Privacy Restrictions → Allowed Apps, where Camera must be switched on. If everything is allowed but the preview is black inside one app, the likely cause is ownership — another app (a FaceTime call, a recorder, a background video app) still holds the camera; close it, or just restart the device to force every app to release it.

On Android

Android wording shifts between manufacturers, so treat the exact labels as approximate: the camera permission is somewhere under Settings → Apps, then pick the app, then Permissions → Camera, and set it to allow. Pixel-style settings also expose a Privacy hub with a Permission manager that lists every app allowed to use the camera, which is the quickest way to check them at once.

Two Android-specific causes are common. First, ownership: a phone's camera belongs to one app at a time, so if your camera is black because another app opened it first — a video call, the system camera, a scanner — you must fully close that app, not just leave it in the background. Second, enterprise or parental controls: a work profile or a device-admin policy can disable the camera entirely for security reasons, and if that is the case the option is greyed out and no app-level permission will fix it.

Fix it inside the app

Once the platform-level tests pass, the remaining faults are app-specific: the app was never granted the camera, or it is pointed at the wrong device. The general recipe is the same everywhere — first make sure the operating system has allowed this particular app to use the camera, then open the app's own video or device settings and confirm it has selected the physical webcam rather than a virtual camera, a second lens, or a device another program is holding.

Below are the accurate paths for each app people reach for, grouped by where the setting actually lives. Where a menu moves between versions or between the desktop and mobile builds, the description stays general and says so rather than promising an exact click count that may not match your screen.

Microsoft Teams

Teams — the installable app and the browser version both rely on the operating system having granted the camera. On Windows that means the desktop-app camera allowance is on for Teams; on a Mac it means Teams is switched on under Privacy & Security → Camera. In the app itself, open the device settings — under the profile or three-dot menu, look for Devices or Settings and then the Cameras section — pick your webcam from the list, and check the built-in preview.

If the preview is black in Teams but works elsewhere, either Teams is selecting the wrong camera in that picker or another program owns the device; close other call apps and re-select. In browser Teams, the browser also needs its own camera permission for the site, which you grant from the prompt or the permission icon in the address bar.

Zoom

Zoom is a frequent source of false alarms because it can show a black preview even on a healthy camera. The desktop app reads the operating-system permission first — on Windows the desktop-app camera switch must be on for Zoom, on macOS Zoom must be enabled under Privacy & Security → Camera. Then in Zoom, open Settings and go to Video: your camera is a dropdown at the top, and the preview sits beside it; choose the correct device there.

If a device is held by another app, Zoom often says so — stop the other program. On phones, grant Zoom the camera in the system settings for the app. If the preview stays black after all that, sign out and back in, and restart the app so it reopens the device cleanly.

Google Meet

Meet runs in the browser, so the two gates are the browser's permission for meet.google.com and the operating system's permission for the browser itself. On the pre-meeting screen Meet shows a self-view and lets you check the camera before you join; if it is blocked, click the camera or lock icon at the left of the address bar, set Camera to allow for the site, and reload.

If the site is allowed but Meet still cannot see a camera, the browser as a whole is blocked at the OS level — the Windows desktop-app camera switch, or macOS's per-app list that includes your browser. Close any other tab or app that might already hold the webcam, then refresh Meet.

FaceTime

FaceTime uses the system camera, so a camera that works in the normal camera app usually works in FaceTime too — when it does not, the gap is a permission or an ownership conflict. On an iPhone, make sure FaceTime is allowed the camera under Settings → Privacy & Security → Camera, and that the Camera app itself is not restricted under Screen Time's allowed apps. On a Mac, FaceTime is one of the apps listed under Privacy & Security → Camera.

Because a phone's camera belongs to one app at a time, an already-running recorder or another call will make FaceTime show black — close those first. Also confirm the lens is not covered and the front camera is what you expect; a restart clears any app that quietly refused to let go of the device.

TikTok

TikTok records through the camera, so a black record screen is a permission or ownership problem, not a feed bug. On both iOS and Android, TikTok must be granted the camera in the system settings — on iOS the app appears under Privacy & Security → Camera; on Android it is under the app's permission screen. If you declined the original prompt, granting it here fixes it, and you may need to restart TikTok to pick it up.

If the permission is granted but the preview stays blank, another app is holding the camera or the privacy shutter is closed. Close background apps and reopen TikTok; on a laptop, use the browser's camera permission for tiktok.com.

Snapchat

Snapchat is built around the camera and behaves badly when it is denied — the classic symptom is an all-black camera screen the moment the app opens. The cure is the same permission: on iOS go to Settings → Snapchat and enable Camera, or find it under Privacy & Security → Camera; on Android grant Camera under the app's permissions. Snapchat also shows its own request on first launch, and revoking it later reproduces the black screen.

After granting the permission, force-close and reopen Snapchat rather than just backgrounding it, so it reopens the camera cleanly. If it still will not show video, close any other app that owns the camera and make sure no physical shutter covers the lens.

Common problems and what they actually mean

The camera works everywhere except one app. That is the app's own permission or its in-app device selection, full stop — the platform test passing is proof the hardware is fine. Grant that app the camera in system settings and re-select the device in the app.

Every app shows black, but the indicator light never turns on. That is the hardware or firmware layer: a closed privacy shutter, a keyboard camera toggle, a disabled device, or a missing driver. This is why checking the physical switches first is not paranoia.

An “in use” or “device busy” error. A webcam is normally a single-occupancy device; something else has it. Close other call apps and extra browser tabs, and if you cannot find the culprit a restart forces every process to release the camera.

A black screen with a permission prompt you already accepted. On a Mac, newly granted camera permissions often do not take effect until the app is quit and reopened. The same relaunch trick fixes a surprising number of Windows and mobile cases, because it makes the app re-request the device.

The right camera is listed but the wrong one is used. If you have several cameras or a virtual one, the app is selecting a different device — open its camera dropdown and pick the physical webcam you mean.

Frequently asked questions