Running on your device · 0 bytes uploaded
What this browser can do
Presence probes across media, platform, connectivity, graphics, and storage — each row separating “the API exists” from “permission or configuration would let it work”, because those are different facts.
Probing after hydration — presence checks only; nothing on this page ever asks for a permission.
- Presence is measured, permissions are only QUERIED — the page never calls getUserMedia or requestPermission, so no prompt ever appears from this visit.
- “Present — permission not granted yet” and “present, but permission is denied” are distinct rows: the first needs your yes, the second needs a browser-settings change.
- Where the Permissions API itself is missing (Safari, Firefox for several names), the row says the state is not queryable — that is a fact about the browser, not a detection failure.
- Rows like WebGPU and SharedArrayBuffer carry their second gate on the face: an API can exist and still hand you no adapter / no threads depending on drivers and this page's isolation headers.
Nothing in yet
Paste, drop, or type to begin. Everything stays on this device.
the scan runs after hydration; the prerendered page contains no probe values