← Back to the FAQ

Hardware & System Errors

How to tell if your webcam is physically broken or just disabled

Quick answer: Check whether the operating system lists the camera at all. If it appears in Device Manager or System Report without a warning, the hardware is almost certainly fine and the fault is software. Absence from those listings is the only strong signal of real failure.

Before assuming the worst, run through this — the overwhelming majority of broken webcams are actually just disabled somewhere in software.

There is one decisive question: does the operating system see the device? Everything else follows from the answer, and it takes under a minute to establish.

Try It Yourself

Check whether a camera is detected at all

Enumerates cameras visible to your browser. A device appearing here proves the hardware is present and the driver is loaded.

Run the free online webcam test

Check whether the operating system sees the camera at all

On Windows, open Device Manager and look under Cameras or Imaging devices. On Mac, check About This Mac → System Report → Camera. Listed with no warning icon means the hardware is very likely fine and the problem is software-level.

Decision panel showing hardware present and driver bound both succeeding, with likely software fault highlighted and likely hardware failure offDecision — is the camera listedListed, no warningListed with warningNot listed at allWhat each outcome meansHardware presentDriver boundLikely a software faultLikely hardware failure!A clean listing means permissions, drivers or another app are at fault. Italmost never means broken hardware.
A camera listed cleanly in Device Manager or System Report has working hardware and a bound driver, which rules out physical failure.

If it is listed but not working

A driver conflict, a privacy setting, or another app holding the camera open are all far more likely than hardware failure. Work through permissions and drivers before concluding anything is broken.

Test in a second application as well — a camera that works in the built-in Camera app but not your browser has an application-level problem, not a hardware one.

For a guided pass through every layer between hardware and application, use the Camera Troubleshooter Wizard.

If a built-in camera is not listed at all

This is a stronger signal of a real hardware or firmware issue, but rule out two things first: a physical privacy shutter, and a camera disabled in BIOS or UEFI. Either makes a working camera completely invisible to the operating system.

The BIOS setting in particular is easy to miss, and on some business laptops it can be set by an IT policy without the user knowing.

If an external USB camera is not listed at all

Try a different USB port and a different cable if it is detachable, then test the camera on a second computer if you can.

Failing to appear on any machine through any port is a strong signal of actual hardware failure — and it is the only test that establishes this confidently.

If the camera is detected, the Stream & Device Metadata Inspector confirms what it reports about itself.

Check for a status light with no video

If the LED turns on but you get a black screen or a frozen frame, that is usually a software, driver or permission issue rather than physical damage.

A genuinely dead camera typically will not show its indicator light at all, because the light is driven when the stream opens.

Test with a completely different application

If one app fails but the camera works in another — the built-in Windows Camera app, or Photo Booth on Mac — the hardware is fine and the issue belongs to the failing app's settings or permissions.

Choose a test app that uses a different capture path from the failing one, which is why a browser and a native app make a better pair than two browsers.

To document the fault for a warranty claim or IT desk, generate a Tech Support Report.

Where each operating system lists attached cameras

These listings show detection independently of permission, which is exactly the distinction you need here.

Windows

Device Manager → Cameras, or Imaging devices

Enable View → Show hidden devices to reveal cameras that are present but disabled.

macOS

About This Mac → System Report → Camera

A camera listed here with a model identifier is physically present and recognised, whatever any application reports.

Linux

Terminal: v4l2-ctl --list-devices

An absent device means the UVC module has not bound, which dmesg will usually explain.

BIOS / UEFI

Boot menu → Security or Devices → Integrated camera

This setting sits below the operating system entirely, so a camera disabled here appears broken in every check above.

The table below shows where each operating system lists attached cameras and what control it gives you over them:

Practical ceiling and manual control available per app
AppPractical ceilingManual control
WindowsShows warning icons for driver faultsUpdate, roll back, uninstall
macOSLists detected cameras with model IDsNone — detection only
LinuxKernel-level device enumerationFull module control
BIOS / UEFIHides the camera from every OS when disabledEnable or disable

Troubleshooting checklist: broken or just disabled

One decisive check first, then branch according to what you find.

  1. Open Device Manager or System Report and establish whether the camera is listed at all.
  2. If listed cleanly, treat this as a software problem and stop considering hardware failure.
  3. Test in a second application that uses a different capture path, such as a native camera app.
  4. Check whether the indicator LED lights, which confirms the stream opens even if the picture is black.
  5. Slide open any physical shutter and check the camera function key.
  6. For a built-in camera, check BIOS or UEFI for a disabled integrated camera setting.
  7. For an external camera, try another port, another cable, then another computer.
  8. Only after all of the above, treat non-appearance on every machine as genuine hardware failure.