WebcamTest.com
← Back to Performance Tests

Extended Session Monitor

Smartphone-as-Webcam Continuity Benchmark

Using a phone as your webcam — Continuity Camera, DroidCam, iVCam, and similar — trades convenience for a real risk: thermal throttling mid-call. No API reports a phone's temperature directly, so this tracks the actual symptom instead: frame rate and resolution stability over an extended session, flagged honestly as degradation rather than a fabricated temperature reading.

—

Live

Camera off

Select your phone's camera above (once connected via its app) and click Start Benchmark. Leave it running — the longer, the more revealing.

Result

  • Elapsed:—
  • Current FPS:—
  • Current resolution:—
  • Verdict:—

—

Notes

Why frame-rate stability, not a temperature number

Phones do not expose thermal sensor data to web pages — that information stays entirely inside the OS. What throttling and backgrounding both DO produce, reliably, is a measurable drop in sustained frame rate and sometimes resolution as a session goes on. Tracking that directly is honest and, for the practical question of "will my call degrade if I keep going," just as useful as a temperature reading would be.

Keeping a phone webcam stable

Keep it plugged inCharging while in use avoids the extra heat load of simultaneous battery drain and charging-while-hot cycles.
Remove the caseCases trap heat. Removing it during long calls measurably helps thermal headroom on many phones.
Keep the app in the foregroundSome phone-webcam apps get deprioritized by the OS when backgrounded, which can look identical to thermal throttling in a frame-rate graph.

Benchmark Reference

Stability Verdict Thresholds

GradeFPS drop (start to end)What it suggests
Stable< 8%Frame rate held steady through the session.
Mild degradation8% – 19%Consistent with early thermal throttling or reduced priority.
Significant degradation≥ 20%Real substantial drop — likely throttling or backgrounding.

These are this tool's own real thresholds, comparing your measured FPS in the first third of the session against the last third.

Step-by-Step

How to Run the Benchmark

  1. Connect your phone as a webcam via Continuity Camera, DroidCam, iVCam, or a similar app.
  2. Select the device from the dropdown — check the best-effort detection note.
  3. Click "Start" and allow camera access when prompted.
  4. Leave it running for several minutes — thermal throttling takes time to build up, so a longer session gives a more confident read.

Common Issues

Troubleshooting & Fixes

Camera access blockedClick the camera icon in your browser's address bar to confirm this site is allowed, or check your OS's camera privacy settings.
Device not detected as a phoneDetection relies on the device name string — some apps use generic names that don't match common patterns. This doesn't affect the actual frame-rate measurement, only the informational label.
Significant degradation detectedKeep the phone plugged in, remove the case, ensure the app stays in the foreground, and avoid direct heat sources like sunlight or heating vents.

Common Questions

Frequently Asked Questions

How does this know I'm using a phone as a webcam?
From the device name your browser reports, checked against common naming patterns from Continuity Camera, DroidCam, iVCam, and similar apps. This is best-effort, not certain — there is no API that directly reports a device's real nature, and the tool says so plainly.
Can this detect my phone overheating?
Not directly — no Web API reports phone thermal state. It measures the observable symptom instead: frame rate and resolution stability over time, since both thermal throttling and the phone app losing foreground priority show up as measurable degradation, even though the underlying cause cannot be read.
How long should I run this benchmark?
Longer is more revealing — a few minutes at minimum, since thermal throttling typically takes time to build up. A quick 30-second check is unlikely to catch it even if it would eventually happen.
Does this work with any phone-as-webcam app?
It works with any device your browser can access via getUserMedia, which covers essentially all phone-webcam apps regardless of brand. The phone-detection label is best-effort, but the actual frame-rate measurement applies to whichever device you select.
Why does my frame rate vary even without throttling?
Background app activity, notifications, and normal OS scheduling all cause minor frame-rate fluctuation even on a healthy device — the verdict looks at the overall trend from start to end, not moment-to-moment noise.