Six browser diagnostics that explain the hardware tests
These six diagnostics are deliberately kept out of the main catalog, whose count is the number of hardware tests you can run (15 tools). Each one answers a question that comes up around those tests — whether a permission is blocked, what your browser can actually do, which call codecs it handles, whether WebRTC works locally, what it exposes about itself, and what DeviceTry has stored in this browser.
Advanced Diagnostics(6)
Permission Diagnostics
Read-only — never requests a permission
Read the permission states this browser reports for your site — and see exactly which ones it could not read.
A permission name this browser does not implement stays unknown; iOS Safari in particular exposes very few names, so a missing row there says nothing about the real state.
Open the check
Browser Compatibility
Passive read-only checks
See which web APIs this browser actually exposes, including APIs it ships switched off.
Available means the API is present and usable. "Exposed, off" means the browser ships it but reports it switched off — a different situation from missing, and not fixable by updating.
Open the check
Codec Support
MediaRecorder.isTypeSupported + canPlayType
See what this browser reports about recording containers and playback codecs — with "maybe" kept as "maybe".
Both probes report the browser's own capability tables. Nothing here records, decodes, negotiates or hardware-accelerates media, and no row predicts call quality.
Open the check
WebRTC Capability Test
Local loopback only — no STUN or TURN server
Run a real local peer-to-peer loopback and confirm echoed messages actually came back — no leak testing.
This is a local capability test. It is not a leak test and does not evaluate VPN or DNS behavior.
Open the check
Browser & System Info
Read-only informational snapshot
A labelled snapshot of what this browser exposes — screen, viewport, pixel ratio, and user-agent estimates.
This is an informational snapshot, not a diagnostic: it reports values and cannot pass or fail any hardware.
Open the check
DeviceTry Storage Inspector
This origin's localStorage keys only
Inventory every localStorage key DeviceTry owns, export it, and clear it with a verified result.
Clearing cannot be undone.
Open the checkWhat these checks do — and what they do not
- •They stay on your device. None of the six requests microphone or camera access, and none uploads anything. Permission Diagnostics reads the permission state your browser already holds rather than triggering a prompt, and the Storage Inspector only reports what DeviceTry itself has saved locally.
- •The WebRTC check is a local capability test, not a leak test. It creates two peer connections inside your own browser with no external STUN or TURN server, exchanges an SDP offer and answer, opens a data channel and passes five messages through it. It reports handshake time, roundtrip timing and the ICE candidate types it gathered — it does not test for IP leaks, VPN behavior or DNS.
- •Capability is not a guarantee. A browser can report support for an API or codec and still behave differently in practice, so read these results as what your browser claims it can do — not as a performance measurement.
Looking for a device test instead? Browse all 15 tools