Webcam Test

Check that a camera works and what it actually delivers — resolution, frame rate and device name, with nothing recorded.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

What the page can see

A camera exposes its resolution, frame rate and device name to the page once you allow it. Those numbers are worth checking: a camera that reports 640×480 when it claims 1080p is being limited by the cable, the port or another app holding it open.

The video element shows the stream directly from the camera. There is no canvas copy, no recording and no upload — closing the tab releases the device.

    When the camera will not start

    A blocked camera is either a permission that was denied once and remembered, or another program holding the device. The first is fixed in the address bar's site settings; the second needs the other program closed.

    On a laptop with two cameras, the picker lists both after the first permission. Switching cameras restarts the stream and re-reads the settings.

      Choosing the right camera

      Laptops with an external monitor often default to the built-in camera. The picker switches devices after permission is granted, and the settings panel updates with the new resolution.

        How Webcam Test works

        Open the camera in the page, see the resolution and frame rate it reports, switch between cameras, and stop it cleanly. The method behind Webcam Test is the single-purpose logic inside wave51.js, and this page shows the result with its assumptions in the open.

        • Open Webcam Test and provide webcam test — the page accepts it in the field it shows.
        • For Webcam Test, browser APIs and, where stated, one public endpoint do the work.
        • The Webcam Test output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.

        A worked example for Webcam Test

        A typical run of Webcam Test starts with webcam test and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.

        Repeat the check on a second network: a result that changes with the network is a routing fact, not a fault in your device. That check applies directly to Webcam Test with webcam test.

          When to use Webcam Test — and when not to

          Reasonable uses: Diagnosing a connection; Checking DNS or registration data; Testing hardware in the browser. Webcam Test is deliberately narrow: it does one job and states its assumptions instead of hiding them.

          Diagnostic apps and terminal tools go deeper but need installs or shell access. For a quick lookup or a device test, a page is the lower-friction path. The honest ceiling for Webcam Test: for Webcam Test, results reflect your network and device.

          • Best case for Webcam Test: Diagnosing a connection
          • Also fine with Webcam Test: Checking DNS or registration data
          • Not what Webcam Test is for: for Webcam Test, results reflect your network and device.

          Reading the Webcam Test result

          The output of Webcam Test is a function of the inputs alone — no hidden state and no server.

            Accuracy and limits of Webcam Test

            The method is the single-purpose logic inside wave51.js. Webcam Test prints results at the precision its inputs justify, and the limits below are the honest ones:

            • Webcam Test: For Webcam Test, results reflect your network and device.
            • For Webcam Test, pages that call an endpoint say so and call it only on your click.

            Privacy and speed on the Webcam Test page

            The Webcam Test page is a static file plus wave51.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

            Speed follows the build: Webcam Test loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

              What you get from Webcam Test

              The output of Webcam Test appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the web work finishes the moment the numbers are in.

              Because Webcam Test is built from wave51.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

                Questions

                What does Webcam Test do?

                Open the camera in the page, see the resolution and frame rate it reports, switch between cameras, and stop it cleanly. Everything runs in your browser; nothing is uploaded.

                How accurate is Webcam Test?

                The method is the single-purpose logic inside wave51.js. For Webcam Test, results reflect your network and device.

                What are the limits of Webcam Test?

                For Webcam Test, pages that call an endpoint say so and call it only on your click.

                Is anything uploaded when I use Webcam Test?

                No. Webcam Test runs entirely in the browser tab; nothing is uploaded, stored or logged.

                Can I use Webcam Test offline?

                Yes — Webcam Test keeps working offline once the page has loaded; the whole tool is a local script.

                Device tests

                Keep going

                More web tools