How the resolution check works
This page opens the camera with Highest available selected, so the size on the preview is the largest the camera offers your browser. A second after the picture appears, the Supported resolutions scan under the preview starts by itself. It asks for exactly 3840×2160 (4K), 2560×1440, 1920×1080, 1280×720 and 640×480, one after another, and records for each one what really arrives:
- ✓ Supported (native): the camera delivers that size itself, as one of its own modes. Some browsers can’t tell native modes from others; they show just ✓ Supported.
- ≈ Scaled: the camera has no mode of that size, so it sent a bigger one and the browser shrank it.
- ✕ Not supported: the camera can’t deliver that size; the row shows the size that came back instead.
The frame rate column shows the rate the camera reports for each native size. Many cameras give their highest frame rate only at a smaller size, so a 4K camera may list 30 fps at 4K and 60 fps at 1080p.
When the result is lower than the box
Work through these in order, scanning again after each step with Scan again:
- Close every other app that uses the camera, including the meeting app’s background process. A camera that is already open elsewhere may be shared at that app’s size.
- Plug the camera straight into the computer. A USB 2.0 port, hub or extension carries 480 Mb/s against 5 Gb/s for USB 3.0, not enough for 4K and sometimes holding 1080p back. The Brio 4K test shows how that looks for one popular 4K camera.
- Try another browser. Browsers and operating systems expose different camera modes; if one browser finds 1080p native and another doesn’t, the camera is fine.
For a specific model, the Logitech C920 page checks each mode its maker lists. If the size is right but the picture stutters, check the webcam frame rate next.