Feature detection, not guesswork

Browser Support

XZETO targets the current and previous major releases of Chrome, Edge, Firefox, and Safari, while checking the actual API before every tool runs.

A browser name is not enough
HTTPS, OS policy, enterprise configuration, hardware, permissions, and mobile restrictions can change support inside the same browser family.
No permission prompt

Check this browser

Run the same feature detection used by the individual tools.

Camera and microphone

Media tests need a secure context and navigator.mediaDevices.getUserMedia. Device labels normally remain hidden until permission has been granted. A denied permission, busy device, or OS-level privacy setting needs a different recovery step.

Recording and Web Audio

Signal analysis and generated tones require Web Audio. Local recording requires MediaRecorder and a browser-supported format. Audio output selection is optional; unsupported browsers use the system-default output.

Gamepad, fullscreen, and pointer input

Controllers often appear only after a physical button is pressed. Fullscreen requires a direct user action. Pointer Events unify many mouse, pen, and touch paths, but platform gestures and side buttons can remain reserved.

WebRTC and network tests

RTCPeerConnection exposure confirms local API support, not a working remote media path. End-to-end testing needs controlled remote services. A reliable speed test additionally needs monitored regional nodes, capacity planning, and abuse controls.