This gamepad tester reads the browser's Gamepad API directly, so it shows exactly what inputs your computer receives from the controller, not what the label on the pad says. Press a button to connect it (browsers hide a gamepad until you do, for privacy), then every button lights up as you press it and each stick and trigger shows its live value. It's the quickest way to find a dead button, a drifting thumbstick, or a trigger that doesn't travel its full range.
How to test your controller
Plug the controller in over USB or pair it over Bluetooth, open this page, and press any button. The browser only reveals a gamepad after a button press, so the page stays empty until then. Once it connects you'll see the controller's ID and button and axis counts, a grid of buttons that light up as you press them, and a row of axes (the sticks and, on many pads, the triggers) with a live value from -1 to 1. Work through every button, push both sticks to all edges, and pull each trigger fully.
Finding stick drift and dead buttons
A healthy thumbstick rests near 0 on both axes when you aren't touching it. If an axis reads a steady non-zero value (say 0.15) with your hands off the pad, that's stick drift, the wear that makes a character walk on its own. A button that never lights up when you press it is dead, usually a worn contact or dirt under the cap. A trigger that stops short of 1.00 at full pull has a worn spring or sensor.
Why the button numbers may not match the labels
The page shows button index numbers (0, 1, 2โฆ) rather than A/B/X/Y, because the browser reports positions, not brand labels. Most modern controllers report a "standard" mapping, where button 0 is the bottom face button, the triggers are 6 and 7, and the D-pad is 12 to 15. A controller reporting a non-standard mapping often works fine in games that let you rebind, but the indices here won't line up with the printed letters.
Controller not showing up?
If nothing connects, press a button first, since that's what wakes the API. Check the cable or Bluetooth pairing, and try a different USB port. Some controllers need a specific mode: a few PlayStation and third-party pads sit in a vendor mode until you hold a button combo to switch them to a standard one. If it works here but not in a game, the problem is the game's input settings, not the controller.
Privacy
Everything runs in your browser. The page reads the controller state locally and sends nothing to a server. Vibration, where the controller and browser support it, is triggered locally too.