About · Reviewed August 18, 2026

About Device Bench

Device Bench is a set of small hardware tests that run in your web browser. When a key, microphone, camera, speaker, controller, or screen is giving you trouble, start with one question: what does this device report right now? The tests answer it without an application to install, an account to create, or a recording sent to a server.

What the results are based on

Each summary comes with the observations behind it. The keyboard tester shows individual key events before it reports rollover, and the gamepad tester shows raw axis values before it describes drift. The microphone test shows its level windows and distinguishes digital full scale from physical loudness. In the video-call test, each row says where its evidence came from: reported by the browser, measured by the page, or confirmed by you.

The tools are built to hold back a result the evidence cannot support. The pitch tools report no note from silence, and a browser capability that is unavailable never counts as a pass. A camera preview cannot show you what a remote caller sees, and a web page cannot see the light leaving your display. Each tool's limits section says which conclusions its readings support.

How tools are checked

Every new tool is tested on its main success path and on at least one failure or refusal path. Where the browser allows it, the tests feed in known inputs: known event sequences, known audio samples, known elapsed times, and known geometry. Structural checks tie the numbers in explanatory text to the thresholds and formulas the engine uses. Checks in a real browser cover the security policy and visual behavior, which a simulated document cannot reproduce.

The methodology page, How Device Bench tests its browser instruments, explains the full checking process and the difference between reported, measured, and confirmed values. It also covers the privacy boundary, browser limitations, source policy, and correction process.

How the site works

Local execution. Tests use capabilities already built into the browser: keyboard and pointer events, the Gamepad API, Web Audio, camera and microphone tracks, animation timing, and fullscreen rendering. Tool inputs and results stay in your browser. Cloudflare serves the site files and receives ordinary page requests. There is no upload endpoint, analytics collector, account system, or database behind a test.

Published methodology. Every tool explains what it measures, how it works out the result, and where the method stops being reliable. Guides show a Device Bench byline, publication and review dates, and the standards or platform documentation supporting their factual claims.

No accounts or dark patterns. There are no sign-ups, email capture forms, artificial run limits, or locked results. The site shows no ads and sets no ad cookies.

Corrections

Device Bench is responsible for the claims it publishes. If you find a mistake, send the page, your browser and operating system, the value shown, what you expected, and the shortest steps that reproduce the problem. Do not send recordings, screenshots containing personal information, or other private test data. Report a correction or measurement problem.

Send general questions and tool suggestions through the contact page. A new tool has to meet the same bar as the existing ones: the browser must be able to observe what is being tested, and the result must offer more than a keyword variation on an existing tool.