Methodology and project
How Gamepad Bench measures controller input.
Gamepad Bench turns the values exposed by your browser into repeatable controller checks. It is designed to show useful evidence without presenting a browser estimate as a hardware-lab measurement.
What the browser exposes
The tester reads axes, buttons, timestamps and mapping information through the browser's Gamepad API. Exact values and supported features depend on the controller, operating system, browser, firmware and USB or Bluetooth connection.
How to compare results
Keep the controller, cable, port, browser and connection mode unchanged. Reset the test, repeat the same motion and compare several runs. A repeated pattern is more useful than a single spike or one unusually high polling-rate reading.
Measurement limits
Drift and deadzone values describe browser-visible stick positions. The polling-rate panel estimates update frequency from Gamepad API timestamp changes; it does not directly capture USB packets or prove end-to-end input latency. Game-specific response curves, remapping and firmware behavior can produce different results elsewhere.
Open feedback
The public Gamepad Bench repository contains screenshots, support guidance and controller-report templates. Incorrect mappings and reproducible compatibility problems can be reported there or sent to support@gamepadbench.com.
Reviewed · 4 August 2026