About · Reviewed August 18, 2026

About Device Bench

Device Bench runs hardware tests in a web browser. For a troublesome key, microphone, camera, speaker, controller, or screen, start with a question: what does this device report right now? You do not need to install an application, create an account, or send a recording to a server.

What the results are based on

Each summary comes with the observations behind it. The keyboard tester shows individual events before reporting rollover; the gamepad tester exposes raw axis values before describing drift. The microphone test displays its level windows and distinguishes digital full scale from physical loudness. In the video-call test, each row identifies who supplied the evidence: the browser reports it, the page measures it, or the person using the tool confirms it.

The tool should withhold a result when the evidence cannot support it. That means refusing a pitch from silence and never treating an unavailable browser capability as a pass. A camera preview cannot tell you what a remote caller sees, just as a page cannot see the light leaving a display. Each tool's limits section explains which conclusions the instrument can support.

How tools are checked

Every new instrument is exercised on its central success path and on at least one failure or refusal path. Deterministic inputs are used where the browser permits them: known event sequences, known audio samples, known elapsed times, and known geometry. Structural checks keep the numbers in explanatory text tied to the thresholds and formulas the engine actually uses. Browser checks cover security policy and visual behavior that a simulated document cannot prove.

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.

Three commitments

Local execution. Tests use capabilities already present in 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 the page. Cloudflare serves the site files and necessarily receives ordinary page requests, but there is no upload endpoint, analytics collector, account system, or database behind a test.

Published methodology. Every tool explains what is measured, how the result is derived, 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. Advertising is not active. If advertising is introduced after approval, privacy, consent, security policy, and placement review are separate changes rather than a script switched on silently.

Corrections

Device Bench is responsible for the claims it publishes. If you find a mistake, include the page, 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 requests through the contact page. A proposed tool must meet the same requirements as existing tests: 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.