In short
If your webcam delivers about 15 fps instead of 30, first compare its configured frame rate with the measured rate. A selected 15 fps mode calls for a mode change; a configured 30 fps stream delivering 15 needs checks for exposure, other apps and the connection. Add light before reducing exposure, and retest at the same resolution. These checks narrow the cause; a single FPS reading does not identify a hardware fault.
Read the two FPS numbers before changing settings
Open the webcam FPS test, select your physical camera and keep the test tab visible. After the initial measurement, open All measurements and compare Requested frame rate with Measured FPS. Requested frame rate describes the active track setting reported by the browser; it is not a count of arriving frames.
| Configured / measured | What to check next |
|---|---|
| 15 / about 15 fps | Select a faster mode. Delivery is keeping up with this setting. |
| 30 / about 15 fps | Compare lighting and exposure, then check load and connection. |
| 30 / about 30 fps, with long gaps | Inspect frame timing and background load. An average can hide pauses. |
| 30 / about 30 fps here, choppy in a call | Check the app's own mode, effects and connection. |
At 15 fps, the average frame interval is about 66.7 ms; at 30 fps it is 33.3 ms; at 60 fps it is 16.7 ms. Those are frame intervals, not measured shutter speeds or end-to-end latency. A camera running at 29.97 fps is not meaningfully falling short of a nominal 30 fps mode.
1. Check the selected resolution and frame rate
In the test, open Camera & mode. Select 30 fps and a resolution your device supports, then read the actual delivered resolution and FPS again. A requested setting may be unavailable or negotiated differently. Try 1080p or 720p as a comparison if the maximum-resolution mode is slow.
Use Webcam Benchmark to request the standard resolution/FPS combinations and compare them. Not offered means this browser setup could not obtain that exact mode; it does not prove the sensor can never produce it. Consult your manufacturer's mode list, driver requirements and connection specifications.
If a lower resolution delivers 30 fps while a higher one does not, you have found a useful working configuration. That comparison alone does not tell you whether the limit is the camera, transfer format, connection or processing load. Keep the two runs separately labeled.
2. Compare lighting before adjusting exposure
Leave the camera mode unchanged. Add steady light in front of you or compare in daylight, allow automatic exposure to settle, and press Re-measure. Avoid aiming a bright lamp directly into the lens. If FPS rises repeatedly with more light, exposure or the camera's low-light processing is a plausible contributor.
A 30 fps cadence leaves about 33.3 ms between frames. Exposure settings that require longer than that can limit the available frame rate, but not every dark scene triggers the same behavior. Do not infer the shutter setting from FPS alone.
If the manufacturer's camera software exposes exposure, low-light compensation or frame-rate priority, note the original value before changing one control. Shorter exposure may make the image darker or noisier. Restore the value if the result worsens. Controls differ by camera, OS and software; this website does not provide an exposure slider.
Logitech's settings guide describes exposure and low-light options on supported devices. It is a source for the available kinds of controls, not proof that a particular webcam exposes them here.
If you see rolling bands rather than simply low FPS, consult the 50/60 Hz anti-flicker guidance. Match settings to the actual lighting; the screen pattern is not a lamp-frequency detector.
3. Isolate other apps, USB connections and load
- Close competing camera apps. Exit other calls, recording apps and camera tabs. Select the physical camera instead of a virtual-camera output for the baseline.
- For an external USB camera, compare a direct connection. Use a port and cable meeting its documented requirements. Disconnect other high-bandwidth devices for the comparison. A USB 3 port cannot make a USB 2 camera support a new mode, and a connector's shape does not establish its speed.
- Reduce processing load. Pause resource-heavy tasks and temporarily disable background effects in the application being tested. Keep the test in the foreground and the computer in the same power mode across runs.
- Inspect Frame timing trend. Repeated long gaps can explain choppiness even when average FPS is close to the target. Compare after each change instead of changing every setting at once.
Built-in laptop and phone cameras do not have a USB cable to swap. Skip that step. Browser and driver differences also matter: a comparison in another supported browser is useful evidence, not a guarantee that either reading represents the camera's maximum capability.
4. If only OBS, Zoom or Teams looks choppy
Stop this test before reopening the other app. Check that app's selected camera and video mode, then compare with its effects disabled. A smooth browser preview does not establish the frame rate another app captures, encodes or sends over the network.
In OBS, inspect the camera's Video Capture Device properties. On Windows, Resolution/FPS Type, Resolution, FPS and Configure Video expose source settings where supported; changing the project's output FPS alone does not make the camera deliver more frames. The controls differ on macOS and Linux. See the official OBS source documentation.
For a video call, distinguish a choppy local preview from a problem only the other person sees. The latter also needs a check of the app's connection and encoding conditions. CamTestKit does not measure the call's network performance or certify readiness for a particular meeting platform.
5. Save a comparison you can act on
Use Copy results or Save test record in the webcam test before and after a change. Keep camera position, resolution, requested FPS and test duration comparable. Record:
- Camera and browser; physical camera or virtual source.
- Delivered resolution, configured FPS, measured FPS and frame timing.
- The one change: added light, selected mode, direct cable or closed app.
- Whether the improvement repeats when you restore and reapply the change.
The test's Compare before & after panel can compare the look of two frozen frames. Still images cannot establish motion smoothness: use the FPS readings and timing trend for that. A saved record documents browser-observed conditions; it is not a hardware-defect certificate.
Return to the webcam test and re-measure, or compare supported modes if the resolution/FPS combination remains the main question.
Low webcam FPS: common questions
Why is my webcam stuck at 15 fps instead of 30?
It may be running a selected 15 fps mode, adapting exposure in dim light, or encountering a capture or processing limit. Compare configured and measured FPS first. Keep the mode fixed while testing more light, then isolate other apps and the connection. A single reading cannot identify the cause.
Can a 30 fps webcam become a 60 fps webcam?
Only if that camera and the current setup support a 60 fps mode. Some devices offer higher FPS only at lower resolutions. Request the mode and check delivery; changing an application's output rate does not create extra camera frames.
Does 30 fps prove my webcam is working perfectly?
No. Average FPS can hide uneven timing, and it does not measure focus, color accuracy, audio synchronization or a call's network performance. Inspect the picture and timing as well as the average.
Will buying a USB 3 cable fix low FPS?
Not necessarily. The camera, cable, port and mode must support the required connection. First compare the supplied or manufacturer-specified cable directly connected to a suitable port. A faster cable does not upgrade the camera's own USB interface.
Can I fix a MacBook camera's low FPS with these steps?
You can compare lighting, selected modes, other apps and system load on a built-in MacBook camera. Skip the external USB checks. Manual exposure controls and available modes vary; do not assume the browser exposes every camera setting.
What the readings can establish
CamTestKit uses browser video-frame information to measure delivery, with a fallback on browsers without video-frame callbacks. It does not read the sensor directly or prove that every delivered frame is a different exposure. Background scheduling, display cadence and browser support can affect observation. See the test's exact verdict rules.
Technical references: MDN: video-frame callbacks and their limits; MDN: active track settings. This guide combines those API definitions, the manufacturer/application sources above and the current tool's controls; it does not report new physical-camera measurements.