Webcam Test
Test camera access with a local live preview, browser-negotiated video settings, decoded frame size, observed preview cadence where supported, capability ranges, and an unmirrored local snapshot.
- Browser capability-dependent
- Camera only after Start
- No test result history
- No account or upload
Important
- Track settings and capability ranges are browser-reported evidence for the current capture path, not factory sensor specifications or hardware certification.
- Observed preview FPS uses delivered video-frame callbacks where supported and can reflect lighting, browser scheduling, power saving, and main-thread load.
- Preview, observations, and snapshots stay in this browser session; the tool does not request a microphone, record video, or upload media.
This check opens video only after Start. It does not request a microphone, record video, upload frames, or certify camera hardware.
Mirror, Fit, Fill, and Freeze change only this preview presentation. Snapshots use the camera-output orientation and are not flipped by Mirror.
Current webcam check
- Status
- Checking support
- Requested camera
- Not started
- Actual camera
- Not reported
- Duration
- —
- Track width
- Not reported
- Track height
- Not reported
- Track frame rate
- Not reported
- Track aspect ratio
- Not reported
- Facing mode
- Not reported
- Resize mode
- Not reported
- Decoded preview frame
- Not reported
- Observed preview FPS
- Not reported
Track values are browser-negotiated settings for this run. Decoded frame size comes from the rendered preview. Observed FPS uses delivered video-frame callbacks over a rolling two-second window where supported; no animation-frame estimate is substituted.
Browser-reported capability ranges
Capabilities not reported by this browser.
Capability ranges are browser-exposed constraint information, not a factory specification, sensor maximum, or guarantee that every combination can be applied together.
Current visual observation
These are your observations under the current camera, lighting, browser, and system conditions—not an automatic diagnosis.
How to use
- Confirm that this browser context reports camera support; checking support does not request permission.
- Choose the preferred camera for the next Start. Before permission, Browser default camera remains valid and device labels may be hidden.
- Select Start and deliberately allow camera access. This page requests video only, never microphone access.
- Confirm the actual browser-selected camera and wait for a nonzero decoded preview frame.
- Inspect the current track width, height, frame rate, aspect ratio, facing mode, and resize mode where the browser reports them.
- Compare the decoded preview size and browser-observed preview cadence with the track settings; capability ranges appear only where the track API exposes them.
- Use Mirror preview, Fit, Fill, or Freeze/Resume only as presentation aids; they do not change the source camera.
- Optionally take and download a local snapshot. The saved frame uses camera-output orientation even when the preview is mirrored.
- Record one bounded visual observation for the current run, then Stop to release the camera and freeze the last check.
- If troubleshooting, change one variable—camera, permission, lighting, browser, connection, system setting, privacy shutter, or competing app—then start a fresh check.
What the result means
- A live preview means the browser obtained and rendered video frames from the selected capture path; it is not hardware certification.
- Unexpected track dimensions can come from browser negotiation, constraints, the OS or driver, a virtual camera, or source configuration. They do not prove the sensor maximum.
- Low observed preview FPS can involve camera delivery, exposure and lighting, browser or display scheduling, power saving, or main-thread load—not automatically a hardware fault.
- Blur can involve focus, the lens, motion, lighting, or processing. Dark or bright video can involve lighting, auto exposure, or camera, OS, and app processing.
- Flicker can involve lighting and exposure interaction. A black preview can involve a privacy shutter, covered lens, wrong source, virtual camera, another app, privacy settings, driver, or device issue.
- Change one condition and repeat before drawing a diagnosis.
Limitations
- Track settings and capability ranges are browser-reported evidence for the current capture path, not factory sensor specifications or hardware certification.
- Observed preview FPS uses delivered video-frame callbacks where supported and can reflect lighting, browser scheduling, power saving, and main-thread load.
- Preview, observations, and snapshots stay in this browser session; the tool does not request a microphone, record video, or upload media.
Troubleshooting
- Permission is denied or no prompt appears
- Check the camera permission for devicemetrik.com in browser and OS privacy settings, then start a fresh check. Support detection alone never opens the camera.
- No camera is found or the selected camera cannot start
- Reconnect or enable the camera, open any privacy shutter, close competing camera apps, verify the preferred source, and retry. A generic start error is not the same as permission denial.
- The wrong camera opens
- Stop the current check, choose a different Preferred camera for next Start, then start a new check. An idle selection does not open a stream.
- The preview is black, blurry, dark, bright, flickering, or uneven
- Confirm the intended source and privacy shutter, then change one variable such as lighting, lens cleanliness, camera connection, browser, system setting, or competing app before retesting.
- Resolution or preview FPS differs from an advertised value
- Treat the page values as evidence from this browser-negotiated run. Compare another browser, port, lighting condition, or source configuration; the page does not read or certify the sensor maximum.
Related tools
FAQ
Does Webcam Test record or upload video?
No. It shows a live local preview and can create one local snapshot only when you select the snapshot control. It does not use MediaRecorder, store a result history, or upload media.
Does it request microphone access?
No. Webcam Test requests video only. Use Microphone Test separately when you need to inspect a browser microphone input.
Why are camera names missing before Start?
Browsers may withhold full device labels until camera permission is granted. Browser default camera remains a valid first-run choice; missing labels are not a camera fault.
Are track width, height, and frame rate the camera specifications?
No. They are settings negotiated for the active browser track. They are not the sensor maximum, factory specification, or a laboratory frame-rate measurement.
How is observed preview FPS measured?
Where supported, the page counts delivered video-frame callbacks over a rolling two-second window. If that browser API is unavailable, the page reports N/A instead of substituting requestAnimationFrame.
What do the capability ranges prove?
They show constraint ranges and modes exposed by the active browser track. They do not guarantee every combination works together or reveal the camera's complete hardware specification.
Does Mirror preview flip the downloaded snapshot?
No. Mirror changes only the on-page preview. The snapshot is drawn in camera-output orientation so the saved frame is not silently mirrored.
Does a clear live preview prove the webcam is healthy?
It proves that this browser obtained and rendered frames from the selected capture path under the current conditions. It does not certify hardware health, focus accuracy, image quality, latency, or behavior in another app.