Browser device testing, without guesswork

About XZETO

An independently built browser device testing toolkit by Tom Mcfly.

The short version
Tests start only when you ask, raw device content stays local by default, and estimates are labeled as estimates.
31

Device tests

Across audio, cameras, input devices, displays, controllers, and browser diagnostics.

Local-first

Test processing

Raw microphone, camera, keyboard, pointer, touch, and gamepad input stays in the active browser session.

No account

Access model

Open a tool and use it without creating a profile or storing a device history in the cloud.

Clear limits

Result language

Estimates and observations are labeled honestly instead of presented as hardware certification.

Why XZETO exists

Device trouble rarely arrives with a clear diagnosis: nobody can hear you, a camera freezes, a key repeats, a controller drifts, or a display simply feels wrong.

Browsers expose useful signals, but those signals need context. XZETO turns them into focused checks with a visible method, a plain-language result, and a practical next step.

What you can do inside XZETO

01

Check media before it matters

Preview cameras, inspect microphone levels, record a short local sample, test speakers, and work through a pre-call checklist before joining a meeting.

02

Inspect input and display behavior

Observe keyboards, mice, touch surfaces, displays, and gamepads with focused workspaces that explain what the browser can and cannot prove.

03

Understand browser and network limits

Check exposed capabilities, permissions, WebRTC behavior, and compatibility without disguising an unsupported or unconfigured test as a reliable result.

About the maker

XZETO is independently built and maintained by Tom Mcfly, a solo developer focused on practical software for real browser and hardware workflows.

The product is developed with an emphasis on clarity, privacy, usability, and honest measurement — not vague scores or false certainty.

How XZETO is maintained

XZETO is actively maintained with ongoing improvements to test methods, browser compatibility, accessibility, result explanations, and practical troubleshooting guidance.

Tools use feature detection instead of assuming support from a browser name or version, and every test remains readable when a required API is unavailable.

Contact and support

For product questions, reproducible issues, privacy requests, accessibility feedback, or useful feature ideas, contact XZETO through the support page or by email.

[email protected]

Report an issue or suggest a tool