About Controller Tester
Controller Tester is a free collection of browser tools for checking a game controller: whether every button registers, whether the sticks drift or reach full travel, whether the triggers report the whole analog range, whether the motors vibrate, and how fast the controller talks to the computer over USB or Bluetooth.
What the site is
Controller Tester is a small, independent site with one job: telling you whether a gamepad works. The tests are free, need no download and run on any current browser on Windows, macOS, Linux, ChromeOS, Android and iOS.
Why it exists
Controllers rarely fail all at once. One stick starts to creep, a shoulder button needs a harder press, a trigger stops at 80%. These faults are hard to prove inside a game, where overlays, dead zones and remapping software all sit between the hardware and what you see. Most people only want a straight answer: is it the controller, or is it the game?
Each test on this site isolates one behaviour and shows the raw values the browser receives, so you can decide for yourself and show the evidence to a seller, a repair shop or a support agent.
How the tests work
Every test uses the standard Gamepad API that browsers already provide. The browser reports each connected controller as a list of button values and axis values, updated each time the controller sends a new report. The gamepad tester maps those values onto a diagram, the stick drift test samples the axes for ten seconds with your hands off, and the polling rate test counts how often the report changes.
Nothing is uploaded. The values are read in your browser, drawn on screen and discarded when you close the tab.
What the tests cannot see
The Gamepad API exposes buttons, axes and basic rumble. It does not expose battery level, adaptive trigger resistance, touchpad finger position, motion sensors, speakers or light bars, so no page on this site can test those. The support table on the home page lists the practical limits per controller and browser.
Contact
Questions, corrections and reports of a controller that the tester misreads are welcome at [email protected]. See the contact page for what to include.