WebcamTest.com
← Back to Framing Tools

Measured Numbers, Not Just Detection

Virtual Camera Compliance Tester

Companion to the Virtual Camera Test page, which covers detection and driver troubleshooting — this measures the actual numbers: loopback latency via a flash-cue timing test, plus pass/fail against resolution and frame-rate baselines most conferencing platforms expect.

Select your virtual camera device and click Start.

Camera off

Result

—
Loopback Latency
TargetResult

Overall: —

Notes

Why "Common Baselines," Not One Platform's Spec

No conferencing platform publishes an official virtual-camera compliance specification. These four targets are drawn from what conferencing apps generally expect a camera source to deliver reliably — reasonable minimums, not a certified standard from any single vendor. Meeting them is a strong signal your virtual camera will behave well broadly, not a guarantee for any one specific application.

Reference

The Four Compliance Targets

TargetThreshold
Minimum resolution720p (1280×720)
Minimum frame rate30fps (≥28 measured)
Stable resolution reportedWidth and height both present
Loopback latencyUnder 200ms

These are this tool's own real pass/fail checks, run directly against your virtual camera's negotiated settings and measured latency.

Step-by-Step

How to Run the Test

  1. Set up your virtual camera (OBS Virtual Camera, NVIDIA Broadcast, Camo, etc.) with its real source pointed at this screen.
  2. Select the virtual camera device from the dropdown.
  3. Click "Run Test" and allow access when prompted.
  4. Wait for the flash and read your results — latency in milliseconds and pass/fail against all four targets.

Common Questions

Frequently Asked Questions

How is this different from the Virtual Camera Test page?
That page covers detection and driver/restart troubleshooting for OBS, NVIDIA Broadcast, Camo, and similar. This tool is specifically the measured numbers — loopback latency in milliseconds and pass/fail against common resolution and frame-rate baselines — which the other page does not provide.
What is loopback latency?
The delay from a real event happening in front of the virtual camera's true source (like a screen flash) to that event appearing in the virtual camera's output — measuring the full round trip through whatever software composites the virtual feed.
Where do the compliance targets come from?
No platform publishes an official spec, so these four targets reflect what conferencing apps generally expect a camera source to deliver reliably — reasonable minimums rather than a certified standard from any one vendor.
My virtual camera failed the latency target — what causes that?
Heavy compositing (multiple sources, effects, or high-resolution scenes) in the software producing the virtual camera is the most common cause. Simplifying the scene or upgrading hardware encoding support in that software often helps.
Does "No flash detected" mean my virtual camera is broken?
Not necessarily — it usually means the virtual camera's real underlying source (a physical webcam, screen capture, etc.) is not actually pointed at this screen. Double-check that source before assuming a deeper problem.