Camera Lab // Video Input Diagnostics

WEBCAM RESOLUTION & FRAME RATE TEST

Open a local webcam preview and inspect the resolution and frame-rate settings your browser receives from the active camera. Nothing is uploaded or recorded by GearCheck Lab.

PRIVATE BY DESIGNThe video stream stays in this page and stops when you press Stop Camera or leave the page.

Live diagnostic

Camera preview and reported settings

CAMERA PERMISSION REQUIRED

Camera is off.
Press Start Camera and allow browser permission to begin the local preview.

How to run a reliable webcam check

Close video-call, streaming and recording apps that might already use the camera.
Choose a camera. If names are hidden, start once and allow permission so the browser can reveal its visible inputs.
Press Start Camera and approve camera access for this site.
Confirm the preview is live by moving a hand through the frame; a still image can hide a frozen stream.
Read the selected label, active resolution, reported frame rate and observed callback rate.
Check focus and exposure in normal room light, then compare brighter light if motion looks smeared.
Press Stop Camera when finished so the active media track is released.

What each webcam reading means

Resolution is the width and height of the active browser stream. Reported frame rate is the negotiated track setting. Observed callback rate counts recent video-frame callbacks delivered to this page where the browser supports that API.

Camera label confirms which browser-visible input opened. Facing mode can identify a front or rear mobile camera when the browser supplies that setting.

These readings describe the active browser stream and do not certify the webcam sensor's maximum resolution, raw hardware frame rate or image quality.

How to interpret the webcam result

Observation	What it establishes	Useful next step
Live preview, intended label and stable motion	The selected camera is supplying video to this browser under the current conditions.	Check the same camera selection inside the calling or recording app.
Permission denied	The browser or operating system blocked capture before the hardware could be evaluated.	Allow camera access in site and OS privacy settings, reload and retry.
No camera found	No browser-visible video input was available.	Connect or enable the camera, inspect a privacy shutter, then compare the OS camera app.
Camera busy or unavailable	Another app, driver state, cable, hub or device fault may be preventing startup.	Close capture apps, reconnect USB hardware and try a direct port.
Preview works but resolution is lower than expected	The active stream negotiated a lower mode; it does not by itself prove false hardware specifications.	Improve lighting, close competing apps and compare another browser, port or camera setting.
Reported and observed rates differ	The track setting and frames presented to the page are not the same measurement.	Keep the tab visible, reduce system load and repeat before diagnosing hardware.
Preview freezes or the device disconnects	The active capture path was interrupted.	Reconnect the device, close competing software and compare a known-good cable or port.

Use PASS, WARNING and FAIL honestly

PASS — capture worksThe intended camera opens, the preview moves and the active stream settings appear. This qualifies browser capture now; it is not a lifetime hardware guarantee.

WARNING — retestVideo works but is soft, dark, choppy, lower-resolution than expected or missing callback telemetry. Compare lighting, load, browser and USB path.

FAIL — no usable captureAfter permission and basic conflict checks, the camera repeatedly cannot open, disconnects or never produces a live preview.

Resolution and frame rate have limits

A camera advertised as 1080p or 4K can deliver a lower active browser stream when the requested mode, USB bandwidth, exposure time, driver, operating system or another application constrains capture. Resolution alone also says nothing about focus accuracy, lens quality, dynamic range or compression.

The observed callback value is browser-visible playback timing, not a certified sensor frame-rate measurement. Background tabs, main-thread load and power-saving behavior can change it. Use it for repeatable comparisons on the same setup.

When the webcam works here but not in a call

Confirm the conferencing app selected the same camera label.
Check app-specific permission and virtual-camera settings.
Close this page before retesting if the app requires exclusive access.
Compare the app's HD, background-effect and bandwidth settings.
Remember that network upload and call compression are outside this local camera test.

Before replacing a webcam

Open a physical privacy shutter and check a hardware camera switch.
Try a direct USB port instead of a hub or dock.
Test in brighter, even light to separate exposure blur from low frame delivery.
Compare another current browser and the operating-system camera app.
Use a known-good cable where the webcam cable is detachable.
Repeat the same symptom after a restart before calling it a hardware failure.

Privacy and browser support

The diagnostic requests camera permission only after you press Start Camera. The resulting media stream is attached to the preview in this page; GearCheck Lab does not record or upload webcam video. Stopping the test or leaving the page releases its active tracks.

Camera access requires a compatible browser in a secure context. Device labels and additional cameras may remain hidden until permission is granted. A browser can expose different modes or devices than a native camera application, so compare both when the result is unclear.

Webcam test FAQ

Does GearCheck Lab record or upload my webcam video?

No. The browser media stream is attached to the local preview and is not recorded or uploaded by this diagnostic.

Why is the camera name hidden before permission?

Browsers often hide device labels until camera permission is granted. After access is allowed, the test refreshes the browser-visible camera list.

Why is observed frame rate different from reported frame rate?

Reported frame rate comes from the negotiated track settings. Observed callback rate counts frames presented to the page and can be affected by browser scheduling, tab visibility and system load.

Why is a 1080p webcam showing a lower resolution?

The page reports the active browser stream, which can be limited by camera mode, lighting, USB bandwidth, another application, the operating system or the browser.

Can this test prove a webcam is good enough for video calls?

It can confirm local browser capture and reveal the active stream settings, but call quality also depends on the conferencing app, network, compression, lighting and microphone.

Why does the preview work here but not in another app?

The other app can use a different camera, permission state, resolution mode or virtual-camera setting. Compare its selected input and privacy controls.