Why this exists
Almost everyone has joined a call where someone spends the first two minutes saying "can you hear me?". The frustrating part is that the person usually has no fast way to tell whether the fault is their microphone, their headset, their browser, or the app itself.
These tools separate those causes. If your camera works here, the hardware and the driver are fine, and you can stop looking at them. That single piece of information saves most of the time people waste on device problems.
Our approach
Everything runs locally. Asking someone to point a camera at their face is a request for trust. We keep that trust by having no server-side component that could receive media, and by publishing readable, unminified source you can inspect. See how it works.
Show real numbers. The readout panels display what your device is actually producing: measured frame rate, negotiated resolution, real sample rate. Not the specification printed on the box.
Explain the result. A green tick is not much use on its own. Each test explains what the result means and what to do next.
No friction. No account, no email, no upsell, no popup asking you to subscribe before you have finished what you came to do.
What is here
Accessibility problems
If something on this site is unusable with a screen reader, keyboard or magnifier, please report it. Our accessibility statement sets out the standard we aim for and what we already know is imperfect.
Corrections
If something on this site is wrong, or a test behaves oddly on a device we have not seen, we would like to know. The contact page is the fastest route.