Camera Test Shows Black Screen: 4 Fixes That Actually Work
If your browser camera test opens but the preview is a black rectangle, the camera is rarely broken - one of four causes below is far more likely. Walk the list top-down; each fix takes under a minute.
Free Tool Online Editorial Team| Cause | LED state | Typical fix time |
|---|---|---|
| Permission denied | Off or slash icon in address bar | Under 1 minute |
| OS-level camera blocked | Off; browser says allowed | 2-3 minutes |
| Another app holds the device | On; preview still black | Under 1 minute |
| Privacy shutter / BIOS toggle | Never lights | Under 30 seconds |
One quick clue before you start: watch the camera-indicator LED (or the physical shutter). If the preview is black and the LED never lights, you're likely dealing with a shutter or firmware toggle (Fix 4). If the LED is on but the preview stays black, a different process is usually holding the stream (Fix 3). This single observation helps you pick the fastest branch first.
Fix 1 - Stale or denied camera permission in the browser
The browser is the closest layer to the camera-test page, and its per-origin camera permission is the most common cause of a black preview. The address-bar lock may show the page as "allowed" while the browser is still honouring a stale permission record from a different network, a profile sync, or a prior incognito session - the camera stream never opens and the preview canvas stays empty. This stale-grant pattern is specific to webcam permission; a microphone-test page would surface the same root cause as a flat waveform on the mic-input meter rather than a black video tile.
Chrome / Edge: click the lock icon (or "Site information") in the address bar → Camera → pick Allow, then reload the page. If the dropdown shows Camera: Block, switch to Allow and reload.
Safari (macOS): Safari menu → Settings for This Website → Camera: Allow. Safari does not surface the request through the address bar, so changing it through the menu is the only path.
Firefox: click the lock icon → Connection secure → More information → Permissions → clear "Use the Camera". Reload the page so Firefox re-asks fresh.
If the address-bar icon shows the camera is allowed and the preview is still black, the camera permission is fine; move to Fix 2.
Fix 2 - Operating-system blocked the camera
Fix 2 - Operating-system blocked the camera: open macOS Privacy & Security -> Camera or Windows Settings -> Privacy -> Camera and allow your browser - an OS master toggle overrides every site permission and leaves Camera Test with a black frame.
macOS: System Settings → Privacy & Security → Camera. Your browser must be toggled on. If it is not in the list, open the camera test once and macOS will add the entry.
Windows 11 / 10: Settings → Privacy & security → Camera. Enable both Let apps access your camera and Let desktop apps access your camera. Both flags must be on - the second one covers Chrome, Edge, and Firefox on Windows.
iOS / iPadOS: Settings → Safari → Camera → pick Ask or Allow. iOS keeps the camera permission per-site; clearing site data resets it.
Android (Chrome): Settings → Apps → Chrome → Permissions → Camera → Allow only while using the app. The Android setting overrides the in-browser Allow when the app-level toggle is off.
Mobile tap requirement: on some phones and tablets the browser requires an active screen tap before it will attempt to acquire the camera sensor on first load. If the preview stays black after granting permission, tap anywhere on the page and reload - the extra interaction unblocks the API on these devices.
Fix 3 - Another app is holding the camera
Fix 3 - Another app is holding the camera: quit Zoom, Teams, Meet, FaceTime, or any capture tool that opened the webcam first - most devices hand exclusive access to one process, so Camera Test gets a black preview until that holder exits.
Quit / kill the holder: close OBS Studio, Snap Camera, ManyCam, NVIDIA Broadcast, Loopback, and any meeting app (Zoom, Teams, Google Meet, Webex) that may have left a background stream. On macOS, a Force Quit of the app releases the stream within two seconds; on Windows, ending the process in Task Manager does the same.
Confirm release: the camera-indicator LED on most laptops turns off the moment the holding process releases the device. If the LED stays on after every meeting client is closed, a virtual-camera driver is still loaded - reboot to fully clear it.
Re-test: reload https://freetoolonline.com/device-test-tools/camera-test.html. The preview should appear within one second of the page granting permission.
Fix 4 - Privacy shutter or BIOS toggle
Fix 4 - Privacy shutter or BIOS toggle: slide open the physical lens cover and check vendor BIOS/firmware camera enables - if the LED stays dark after browser and OS allow, the hardware path is still closed.
Privacy shutter: look for a small slider on the lens bezel above the screen. The closed position covers the lens with a coloured cover; sliding it left or right reveals the lens. A black preview with no LED activity is the symptom of a closed shutter.
BIOS / firmware toggle: on Lenovo and Dell business laptops, the camera can be disabled in BIOS. Reboot, enter setup (F1, F2, or F12 on most models), look for Devices → Webcam or Security → I/O Port Access → Webcam, and confirm it is set to Enabled.
Hardware switch: some older laptops (HP EliteBook 840 G5 / G6, Lenovo X1 Carbon Gen 6) have a function-key shortcut (Fn + F9 or similar) that toggles the webcam at the firmware level. Press it and re-test.
Still black after all four? - the diagnostic flow
- Try a second site. Open webcamtests.com in the same browser session. If that site also shows black, the cause is still upstream of the page (browser / OS / app / hardware).
- Try a second browser. If Chrome shows black but Safari shows the preview, the cause is browser-level (extension, profile, or a stale permission). Reset Chrome site settings or use a guest profile.
- Try a second user account. Switch to a freshly-created OS user and open the camera test. If it works there, the cause is in your user profile (a permission entry, a browser extension, or a virtual-camera driver registered for your user).
- Try a second machine. If a phone or tablet shows the camera test working immediately, the failing machine has a hardware or driver issue. Open Device Manager (Windows) or System Information (macOS) and look for the camera under Imaging Devices.
Still black after all four? Escalate in this order: try a second site (webcamtests.com), a second browser, a second user account, and finally a second machine. That failure pattern is the fastest way to tell whether the cause is browser-level (extension/profile), profile-level (OS user settings), or hardware-level (driver/webcam).
For a black camera preview specifically, the four steps work outward from the browser permission layer to the hardware shutter - most cases resolve in steps 1 or 3 because stale browser permissions and virtual-camera holders (OBS, Snap, Zoom background drivers) account for the bulk of black-preview reports. If steps 1-4 all return clean and the camera-indicator LED still does not light when the test page loads, the lens has gone faulty rather than blocked and a USB-webcam swap-test or a warranty ticket is the next move.
What about microphone-test black-equivalent issues?
What about microphone-test black-equivalent issues is the same four-layer model as a black camera preview: browser mic permission, OS privacy mute, another app capturing audio, then a hardware mute key - reopen Microphone Test after each layer change.
FAQ
Why does the camera-indicator LED stay off when the preview is black?
The LED is wired to the camera's power line, not its data stream. If the LED is dark, the camera is not powered - that means a hardware shutter or BIOS toggle (Fix 4), not a permission or app issue.
Does a VPN cause a black camera test?
No. VPNs route IP packets, not camera streams. A black preview while a VPN is on is a coincidence; check Fix 1 / Fix 3 instead.
Why does the camera work in Zoom but not in the browser test?
Zoom is the holder. Close Zoom (Fix 3) and re-test. The browser cannot acquire the device while Zoom has the exclusive stream open - even if Zoom is in the background, the device is busy.
I see a green camera-indicator LED but the preview is still black.
The camera is powered and a process has opened the stream, but the preview canvas is not painting. Reload the page (Cmd+R / Ctrl+R) to force a fresh stream attach. If the LED is green and the preview still does not paint, a browser extension is most likely intercepting the canvas - try a guest browser profile.
When this guide does not apply
The four-step fix procedure does not apply to Linux desktop browsers - the OS camera-privacy toggle in Fix 2 does not exist in the same form on Linux, and permission paths vary by distribution and browser. The steps also do not cover a camera attached via USB pass-through to a virtual machine (VMware, VirtualBox, or Hyper-V), where the host-to-guest device assignment adds its own layer the four steps here do not reach.
Related
- Camera test - the tool itself; run it after each fix.
- Microphone test - the same four-layer model applied to audio input.
- How to check your webcam and microphone before an interview - the 5-minute pre-call checklist.
- Device test checklist for remote work - the weekly cadence that catches new failures before a call.
- Device test tools hub - LCD, keyboard, mic, camera, and more - all in one place.
- Screen test vs camera test - pick the right tool - when to run each test and what each checks.
- Camera test permission blocked - how to allow it - per-browser steps to re-grant the camera permission.
Why trust these tools
- Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
- No install, no sign-up. Open a tool and get a working output in seconds - nothing to download and no account to create. Tools that need heavy processing run it on our service, so even a low-powered machine gets the job done.
- Analytics stops at the page view. We measure which pages get visited, not what you type or upload inside a tool. There is nothing to sign in to and no profile is attached to your input.
- Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
- Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.