Webcam frame rate test
Every webcam claims 30 frames per second and many deliver half that, usually because the room is too dark. This counts frames as the browser receives them and compares the result with what the camera says it is sending.
- Frames actually delivered—
- Frame rate it reports—
- Resolution—
Reading the result
Frames actually delivered is measured over five seconds of live video.
Frame rate it reports is what the camera claims through the driver.
A gap between them is normal in the direction of fewer frames, and is almost never a fault. Treat it as a measurement of your lighting.
| Measured | What it means |
|---|---|
| Within 10% of reported | Working as intended |
| Around half the reported rate | Long exposure — the room is dim |
| Under 10 fps | Very dark, or bandwidth starved |
| Varies between runs | Automatic exposure chasing changing light |
Getting the rate up
Light the room, especially in front of you. This is the entire answer most of the time. A camera facing a bright window with the subject in shadow gets the worst of both.
Turn off automatic exposure priority, where the driver offers it. Some cameras let you prefer frame rate over exposure; the picture gets darker and smoother.
Give it its own USB port. Uncompressed video is bandwidth-heavy, and a hub shared with anything busy will cost frames before it costs resolution.
Plug the laptop in. Power saving throttles USB and the processor, and both show up here.
Windows 11
Camera settings live in Settings → Bluetooth and devices → Cameras. Selecting the camera reveals brightness and contrast, and on some models an exposure or frame rate preference. Manufacturer utilities override these, so check for one before concluding a setting does nothing.
macOS
macOS exposes no frame rate control, and its automatic exposure is aggressive about picture quality over smoothness — a dim room will drop a Mac camera to 15 fps with no way to force otherwise. Centre Stage lowers it further, because the crop is done from a larger sensor read.
Common questions
How is this measured?
Through a browser callback that fires once for every frame the camera actually delivers, rather than once per screen refresh. That distinction is the whole point: counting animation frames would measure your monitor, which is why a 30 fps camera can appear to run at 60 on a 60 Hz screen.
Why is my measured rate lower than the reported one?
Most often light. Almost every webcam lengthens its exposure in dim conditions, and it can only do that by taking fewer pictures a second — 30 fps needs each frame exposed in under 33 milliseconds. Turn a lamp on and measure again; a jump from 15 to 30 is common and tells you the camera is fine.
What else lowers it?
USB bandwidth shared with another device, a hub in the way, a busy processor when the stream is compressed in software, and power saving on a laptop running on battery. Any of these can halve the delivered rate without changing what the camera reports.
Why does Firefox say it cannot measure?
Because the per-frame callback this test relies on is not implemented there yet. Chrome, Edge and Safari have it. There is no accurate substitute — an estimate from animation frames would report the display rate rather than the camera, so nothing is shown rather than something wrong.
Does a higher frame rate matter for a video call?
Less than you would think. Most conferencing software sends around 30 fps at best and drops it under load. Where it matters is the exposure story behind the number: a camera running at 15 fps is doing so because it is short of light, and it will also be noisier and blurrier at the same time.