Frequently asked questions
Everything about the tools, the data and the privacy model in one place.
Does web.camera ever see my video or audio?
Never. The camera and microphone streams are opened by your browser and rendered directly on the page. There is no upload code, no recording server, no screenshots. The only data that can ever leave your device is the rating you explicitly submit — numbers and a line of text, no media.
Is the test really free? What's the catch?
Free, no account, no install. The site exists to build the community camera database — when users voluntarily rate their cameras, everyone gets honest, measured data instead of marketing specs. That's the whole model.
How accurate is the measured FPS?
The tool counts real delivered frames via the browser's requestVideoFrameCallback API — the same frames a video call would get. It is precise for your current conditions; test in the light you actually use for calls.
Why does my camera show a lower resolution than advertised?
Browsers negotiate the best mode your camera and driver actually deliver. Marketing resolution often requires vendor software, specific USB ports, or drops under real conditions. What you see measured here is what apps get.
What happens to a rating after I submit it?
It enters a moderation queue. Text reviews are approved by a human; text-free ratings for known camera models are approved automatically. Once a model collects 20 approved measurements, its public page goes live in the database.
How is my privacy protected when I rate?
We store the rating, optional text, measured numbers, the camera name (with its USB id, when present) plus your device type or model as the browser exposes it, coarse browser/OS family and language. Your IP address is never stored — only a salted hash whose salt rotates daily, used purely for abuse limits. After submitting you get a submission ID you can use to request deletion.
Why does the site show a cookie banner?
Because we use Google Analytics to count visits, and EU rules require your consent before those cookies are set. Until you accept, no request is made to Google at all. Decline and everything still works — the tests never depended on it. Details on the cookie page.
My camera fails to start. Where do I look first?
The tool shows targeted fix steps for your exact browser when access fails. The three usual causes: browser permission blocked, another app holding the camera, or an OS privacy switch. Start with the permission guide.