Camera Check
"Camera check" is the everyday synonym for "camera test" - the in-browser tool at Camera Test Online that asks your browser for the webcam feed, shows a live preview, and confirms the lens is open and not held by another app.
FreetoolOnline Editorial Team| Property | Value |
|---|---|
| Implementing tool | Camera Test Online |
| Browser API used | MediaDevices.getUserMedia({ video: true }) |
| Upload required | No - the preview is rendered in your browser |
| End-states | 3: allowed, blocked / denied, ignored |
| Time to run | Under 30 seconds for the basic check |
What people mean by "camera check"
What people mean by "camera check" is a short webcam confirmation before a call, after plugging in a USB camera, or after a driver update - open Camera Test Online, allow permission, and confirm a live preview appears.
Run the check
The check itself takes one click. Open Camera Test Online, accept the permission prompt the browser shows in the address bar, and a live preview of your webcam should appear in the page. If the preview activates and you see yourself, the camera is allowed and working. If the preview stays dark or empty, the page hit one of the two failure modes the next section covers. No frame is uploaded, no recording is saved, and stopping the test releases the camera so the indicator light goes off. The page also reports the resolution the camera negotiated - 1280x720 or 1920x1080, for example - so you can confirm before a call whether the feed is HD or standard-definition.
Three end-states you might see
Three end-states you might see on a camera check: Allowed (live preview), Blocked (browser remembered Deny), or black preview with LED on (another app or OS privacy toggle is holding the stream).
Blocked / denied. Either you clicked Block on the prompt earlier, or the per-site setting is set to Block by policy. The browser silently rejects future getUserMedia calls and the preview stays dark. The address-bar icon shows a camera with a slash through it. Camera test permission blocked: how to allow camera access walks the per-browser allow path.
Ignored. The prompt appeared but you closed it or switched tabs without responding. The browser treats this as no-decision and re-prompts on the next page load. Refreshing the camera test page triggers a fresh prompt; click Allow this time.
If something is not working
If something is not working on the camera check: clear the site permission, close Zoom/Teams/Meet that may hold the device, then check the OS camera privacy toggle before assuming hardware failure.
One less-obvious cause: getUserMedia requires a secure HTTPS page. If Camera Test Online loads over a plain HTTP address - for example on a company intranet without HTTPS enabled - the browser silently blocks the camera request regardless of what the permission dialog shows. Switch to the HTTPS version of the URL first.
Privacy posture
Privacy posture for this camera check: the page calls getUserMedia in your browser and never uploads the video frames - when you close the tab the stream stops and nothing is stored on a server.
Checking a second camera
If your machine has more than one camera - for example a built-in webcam and a plugged-in USB camera - the test opens the system default device. To check the second camera, use the Switch Camera button on the Camera Test page; it cycles through every camera the browser can see so you can run the same check on each one.
Related guides
The guides below pick up where the camera check leaves off - phone camera quality testing, pre-call routines, and fixing a blocked permission.
- How to check camera quality on your phone - steps for testing rear and front cameras on iOS and Android, including focus sharpness, low-light performance, and video stabilisation.
- Device test checklist for remote work - a broader weekly sweep that bundles the camera check with microphone, screen, and keyboard checks before important calls.