Webcam Test: Check Your Camera Before the Meeting Starts
A camera has three failure modes and all of them are invisible until someone on the other side says something. It can be the wrong device: the laptop lid camera instead of the good USB one. It can be the wrong picture: a window behind you blowing out the exposure, or a lamp that puts a highlight on your forehead. Or it can be no picture at all, because another application grabbed the device first. A webcam test shows the answer in a couple of seconds, while there is still time to move a chair.
This page explains what the test actually measures, what the browser does behind the permission prompt, why the camera list sometimes looks empty, and which defects each kind of picture points at.
What a webcam test shows
The browser exposes a camera as a media input device. When a page asks for it, the browser shows a permission prompt, opens a stream from the device and hands that stream to a video element. Everything the tool does happens inside those three steps. There is no encoder, no frame buffer on a server, and no file: what you see is the current output of the sensor.
That has one practical consequence. The test can only tell you what the camera reports to the browser. If a meeting application applies cropping, a virtual background or a beauty filter, the test will not reproduce it, because those effects live in the meeting application. What the test does show is the raw material those effects start from, and that is where the real problems are: bad light, wrong framing, a dirty lens, a camera pointed at a wall.
The preview keeps the whole frame visible inside a 16 by 9 box, letterboxed rather than cropped. If your camera reports a 4:3 picture, you see it whole with bars on the sides. Meeting applications often crop to fill, so a test that also cropped would hide exactly the part of the frame that the meeting will cut off.
Why the camera list can look empty
This is the single most common question about camera testers, and the answer is a deliberate browser rule. Before a site is allowed to use a camera, the browser hides device identifiers and names: it reports the devices with empty values, or reports nothing at all. The reasoning is privacy. Without that rule, any page could fingerprint a visitor by the exact set and model of cameras attached to the machine, without ever asking for a permission.
The consequence for the interface is simple. A list of cameras cannot be filled before permission exists, so a well-behaved tool asks for the camera first and fills the list afterwards. In practice:
| State | What the picker shows | What the browser knows |
|---|---|---|
| Page just loaded, no permission | Empty, or a placeholder | Device count only, names hidden |
| Prompt answered "allow" | Every camera by its name | Names and stable identifiers |
| Prompt answered "block" | Empty, plus an error on Start | Nothing until the site is unblocked |
| Permission granted earlier | Filled on load | Names available immediately |
If the picker is empty and Start does nothing but show an error, the permission was answered "block" at some point. The fix is in the browser settings for the site, not on the page.
Framing, light and sharpness: what to look at
The preview is not a selfie mirror. Its job is to answer three questions that decide whether a call looks professional.
Framing. Eyes should sit in the upper third of the frame, with a little room above the head and the shoulders visible. A laptop on a desk usually aims slightly upwards, which flatters the jaw but shows a lot of ceiling. A stack of books under the laptop changes the angle more than any software setting.
Light. The face should be lit from the front, not from behind. A window behind the chair is the classic mistake: the camera exposes for the bright window and the face becomes a silhouette. Turning the desk ninety degrees, or closing a blind, fixes it without touching any setting.
Sharpness. A soft picture usually means one of three things: the lens is smudged, the camera focused on the background, or the resolution selected by the browser is low. Wiping the lens with a cloth is worth trying before blaming the device, and the difference is visible immediately in the preview.
A fourth check is colour. Many laptop cameras produce a green or magenta cast under mixed lighting, because automatic white balance picks the stronger source. Holding a sheet of white paper into the frame shows the cast clearly; if the paper looks blue, the meeting will look blue too.
Cameras the picker can show
The list is whatever the operating system reports as a video input, which is more than the built-in camera on most machines. Common entries:
| Device type | Appears as | Worth testing because |
|---|---|---|
| Laptop camera | Integrated camera | Default device, often the worst one |
| USB webcam | Named model | Usually sharper, needs the right USB port |
| Capture card | HDMI capture | Check the signal arrives and is not stretched |
| Virtual camera | Software device | Confirms streaming software is publishing |
| Phone as camera | USB or wireless input | Checks the link holds a stable frame |
| Dummy or test device | Virtual input | Useful in a build or a test environment |
Switching between them takes one selection and one Start. The choice applies to the next stream, so pick the device first and then press Start; a stream that is already running stays on the old device until it is restarted.
Start, stop, and the frozen last frame
Stop ends the video track. The camera is released, the recording indicator in the browser goes out, and another application can take the device without waiting. The picture, however, stays on screen as a still image, because the video element keeps the last frame it received.
That behaviour is worth knowing for two reasons. First, a frozen frame is not a live stream: if the picture does not move when you wave, the camera is off, not broken. Second, it makes the tool usable as a comparison aid. Set the light, press Stop, look at the still, change the lamp, press Start again, and compare.
The camera indicator in the browser is the reliable signal for "is the camera open". It follows the track, not the page, so a preview that is frozen with the indicator off means the device is free.
When the preview stays black
A black preview with no error message is almost always a device conflict, not a page bug. The usual causes, in order of frequency:
- Another application holds the camera: a meeting client, a recorder, or a browser tab left open with an active preview.
- The operating system blocks camera access for the whole browser, which is common on managed laptops and on macOS after an update.
- A physical privacy shutter is closed, or a hardware switch is off on the lid.
- The camera driver crashed after sleep; unplugging a USB camera or rebooting the browser restores it.
The tester cannot distinguish these for you, because the browser only reports success or failure. What it can do is make the failure visible: a refused stream produces a message, so a silent black frame means the device opened but produced no usable picture. That narrows the search to the device side.
Privacy: where the frames go
There is one connection between the camera and the page, and nothing else. The stream is created by the browser, consumed by a video element in the same document, and dropped when the page closes. No frame is encoded, uploaded or written to disk.
Two details follow. First, the page works with the network disconnected once it has loaded, which is a quick way to check for yourself that nothing is being sent: switch off Wi-Fi, start the preview, and the picture keeps coming. Second, opening the same page from a laptop and from a phone sends nothing between them; each stream stays on its own device.
Permission is remembered per site. Answering "allow" once means the next visit opens without a prompt, and revoking it is done in the browser settings, not on the page.
Browsers, phones and secure pages
Camera access requires a secure context, which means an HTTPS page or localhost. A plain HTTP page cannot open a camera at all, in any modern browser. Beyond that rule, support is broad:
| Browser | Camera preview | Device names | Notes |
|---|---|---|---|
| Chrome and Edge | Yes | After permission | Best device coverage on Windows |
| Firefox | Yes | After permission | Remembers the choice per site |
| Safari | Yes | After permission | Asks again after a long pause |
| Chrome on Android | Yes | After permission | Front camera by default |
| iOS browsers | Yes | After permission | Limited to the system camera stack |
On a phone, the preview fills the width and the controls stack vertically, because a camera test on a phone is mostly about checking the front lens before a video call.
Frequently asked questions
Does the tester record anything?
No. The stream goes from the device into the page and is displayed; there is no recorder, no file and no upload. Closing the tab ends the stream as well.
Why do I see two camera entries for one webcam?
Some webcams expose two interfaces, for example a normal view and a cropped or higher frame rate mode. The picker lists what the system reports, so both appear; the preview shows which one you actually selected.
Is it normal that the picture is mirrored?
Some cameras and some drivers mirror the preview for the local user while sending a non-mirrored picture to applications. The tester shows what the browser receives, so a mirrored preview here usually means the device mirrors by itself.
Can I check the microphone too?
Not on this page. Camera and microphone are separate permissions and this tool asks only for the camera; a microphone test with a level meter is a different tool.
Why does the preview take a second to appear?
The browser has to open the device, negotiate a resolution and start the pipeline. On USB cameras the first frame can take up to two seconds; a second Start on an already warm device is much faster.
Does a stopped camera keep running in the background?
No. Stop ends the track, and the browser indicator goes out. If the indicator stays on, another tab or application is using the camera, not this page.
What resolution does the preview use?
Whatever the browser negotiates with the device, usually 640 by 480 or 1280 by 720. The tool does not request a specific resolution, so what you see is close to what a meeting application will negotiate by default.
Does the test work with a phone camera over USB?
Yes, if the operating system exposes it as a video input. It then appears in the picker like any other camera, and the preview behaves the same way.
Summary
A webcam test is a small tool with a narrow job: show the frame the camera sends, name the device, and let you release it. The useful checks are the ones a screenshot cannot fix later: which camera is selected, where the light falls, whether the background steals the exposure, and whether the lens is clean. Two clicks cover all of it, and the camera is free again for the meeting.
Hungary · SO reputation 7991 · Badges: 6🥇53🥈77🥉 · SO member since 2011