HardwareTestingPro
Home / Camera Tools / Camera Resolution & FPS Test

Camera Resolution & FPS Test

See your webcam's real active resolution and a genuinely measured frame rate, counted live from actual delivered video frames.

● Click below and allow camera access to begin
Active Resolution
-
Measured FPS
-
Requested FPS (from driver)
-
Frames Counted
0

Measurement runs for 5 seconds after starting, then reports your real average frame rate over that window. Not all browsers support precise per-frame counting - this tool tells you honestly if yours doesn't.

What Is a Camera Resolution & FPS Test?

This tool reports your webcam's actual active resolution the instant it starts streaming, and - where your browser supports it - counts real delivered video frames over a 5-second window to calculate a genuine measured frame rate. This is different from simply reading a "requested" frame rate value your camera driver reports, since a camera can be asked for 30fps and still deliver less in poor lighting or under system load; this test counts what's actually arriving, not just what was requested.

How to Use the Camera Resolution & FPS Test

  1. Click "Start Camera" and allow camera access when prompted.
  2. Wait for the 5-second measurement window to complete.
  3. Check "Active Resolution" for your camera's actual current resolution.
  4. Compare "Measured FPS" against "Requested FPS" to see if your camera is delivering its expected rate.
  5. Click "Restart Test" to measure again, for example after changing lighting conditions.

How It Works

Resolution comes from the active video track's getSettings() data, which reports the real width and height currently being streamed. Frame rate measurement uses the requestVideoFrameCallback API, which - where supported - fires a callback exactly once for every actual video frame delivered to the page, letting this tool count real frames over a fixed 5-second window and calculate a true average frames-per-second figure. Where that API isn't available, this test reports only the resolution and the driver-requested frame rate honestly, rather than guessing at a measured number it cannot actually calculate.

Understanding Your Results

  • Measured FPS closely matches Requested FPS - your camera is delivering its full expected frame rate under current conditions.
  • Measured FPS noticeably lower than Requested FPS - commonly caused by low lighting, since many cameras automatically reduce frame rate to gather more light per frame, or by high system CPU load competing for processing time.
  • "Not supported" for Measured FPS - your browser doesn't implement requestVideoFrameCallback yet; resolution and requested FPS are still accurate, just not the real measured count.
  • Resolution lower than your camera's advertised maximum - some cameras default to a lower resolution unless a specific higher resolution is explicitly requested by the application using them.

Browser Limitations

Frame rate measurement via requestVideoFrameCallback is currently best supported in Chromium-based browsers like Chrome and Edge; Firefox and Safari support varies and may not expose this API. Where it's unavailable, honest reporting of that limitation is more useful than a fabricated number this tool has no way to actually calculate.

Common Mistakes to Avoid

  • Testing in low light and expecting full frame rate - many cameras automatically drop frame rate in dim conditions to improve exposure; this is a driver decision, not a bug in this test.
  • Running other camera-heavy apps at the same time - video calls or recording software running simultaneously can compete for camera bandwidth and processing.
  • Expecting measured FPS in an unsupported browser - switch to a Chromium-based browser if you specifically need the measured frame-count reading.

Frequently Asked Questions

What's the difference between "Requested FPS" and "Measured FPS"?

Requested FPS is what your camera driver reports as its configured target frame rate; Measured FPS is the actual number of frames counted arriving at the browser over the test window, which can differ from the request under real-world conditions like low light.

Why does my measured FPS drop in a dark room?

Many cameras automatically lower their frame rate in low light to increase exposure time per frame, producing a brighter but slower video feed - this is expected camera behavior, not a fault.

Why does my browser show "Not supported" for measured FPS?

The requestVideoFrameCallback API needed for real per-frame counting currently has limited support outside Chromium-based browsers.

Is any of my video recorded during this test?

No. Video is only displayed live and analyzed for frame timing; it is never recorded, saved, or transmitted anywhere.

Can I change which resolution my camera streams at?

This tool reports whatever resolution your camera and browser negotiate by default; changing that typically requires adjusting settings within the specific application requesting the camera, since this test is a diagnostic reader rather than a camera configuration tool.

Conclusion

Seeing your camera's real measured frame rate next to what it was asked to deliver gives you a genuine read on how it's performing right now, not just what the spec sheet claims. For a broader look at your camera feed and overall quality, pair this with the Webcam Tester.