How We Test
Who builds these tools, how we check that every reading is accurate, and how you can verify — yourself — that nothing you test ever leaves your device.
Who builds these tools
Test Your Device is built and maintained by Jayadeep, a web developer who works with browser hardware APIs (Web Audio, MediaDevices, the Gamepad API, WebGL and the Battery and Screen interfaces) and a small editorial team that writes and reviews the troubleshooting guides. Every tool is a hand-written, dependency-free page — no third-party testing library sits between you and your hardware.
How we verify accuracy
Each tool reads directly from the standard browser API for that device and shows you the raw value, not a processed score. We check every tool against known-good and known-faulty hardware before it ships, and re-check after browser releases that change an API.
- Microphone, speaker & headphone tests are validated against a reference USB audio interface and a calibrated SPL meter, so the level meter and channel routing match real-world measurements.
- Controller and gamepad tests are checked on DualSense, Xbox and Switch controllers — including units with known stick drift — to confirm the resting-value and severity readouts are correct.
- Display tests (dead pixel, refresh rate, colour) are verified on OLED and IPS panels and against a high-speed camera for refresh-rate timing.
- Input tests (keyboard, mouse, CPS, double-click) are timed with the high-resolution
performance.now()clock and cross-checked against a hardware signal generator.
When a browser cannot expose a value accurately — for example, exact battery health or true polling rate — we say so on the page rather than showing a number we cannot stand behind.
How we verify the privacy claim
Every tool runs entirely in your browser. Your microphone audio, camera frames, keystrokes and controller inputs are processed on your own device and are never uploaded, recorded, or sent to a server. This is not a promise you have to take on trust — you can verify it yourself:
- Open any tool and press F12 to open your browser's developer tools, then select the Network tab.
- Run the test — speak into the mic, move the controller, click the mouse.
- Watch the request list. You will see the page, stylesheet and analytics/ad scripts load, but no request that uploads your audio, video or input data. Filter by Fetch/XHR and WS and you will see nothing carrying your test data.
You can go further and fully disconnect from the internet after the page loads: the tools keep working, because there is no server round-trip involved in the test itself. The only third-party code on the page is Google Tag Manager and Google AdSense, which power anonymous, aggregate analytics and the ads that keep the tools free — neither receives your device's raw input.
How we keep guides correct
Our troubleshooting guides are written against the current versions of Windows, macOS, iOS, Android and the major apps (Zoom, Teams, Discord), and are dated with a "last updated" line. When an OS update changes a settings path, we update the guide. Each guide links to the matching browser tool so you can confirm a fix worked the moment you make it.
Corrections
If a tool reads wrong on your hardware, or a guide step is out of date, tell us through the contact page. We keep the tools honest, and reader reports are the fastest way we catch edge cases across the huge range of devices out there.
Frequently Asked Questions
Is anything I test actually uploaded?
No. Every test runs locally in your browser using standard device APIs. Your audio, video, keystrokes and controller input are processed on your device and never sent to a server. You can confirm this in your browser's developer tools under the Network tab, or by disconnecting from the internet after the page loads — the tools keep working.
How do you know the tools are accurate?
Each tool reads the raw value from the browser API and is validated against known-good and known-faulty hardware and reference instruments before release, then re-checked after browser updates. Where a browser can't expose a value reliably, we say so instead of showing a number.
Who writes the content and tools?
The tools are built by Jayadeep, a developer who works with browser hardware APIs, and the guides are written and reviewed by a small editorial team. Each guide carries a byline and a last-updated date.
Do you use my microphone or camera data for anything?
No. The stream stays in your browser's memory only while the test runs and is discarded when you close the tab. It is never stored, transmitted, or used for training or advertising.
What third-party code runs on the page?
Only Google Tag Manager and Google AdSense, which provide anonymous aggregate analytics and the ads that keep the site free. Neither receives the raw input from your hardware tests.
How often are the guides updated?
Whenever an operating-system or app update changes the steps. Every guide shows a last-updated date so you can see how current it is.