Gamepad Tester

Diagnose Your Controller Without Plugging Into a Console

A controller that feels slightly off mid-game — a stick that pulls left, a trigger that won't fully register, a face button that occasionally misses — is hard to confirm when you're focused on playing. The Gamepad Tester isolates every input so you can see exactly what your controller is sending, in real time, right in the browser. It uses the W3C Gamepad API to read your pad up to 60 times per second and renders each button, trigger, and stick as you move them.

What the Test Actually Checks

The tester surfaces four things the browser can read from your controller:

• Connection and identity — the controller's reported name, its slot index, and whether the browser recognizes a standard mapping.
• Buttons — every button's pressed state, plus its analog value from 0.00 to 1.00. This is what reveals partial trigger pulls.
• Axes (sticks) — each analog stick reported as an X and Y value from -1.00 to +1.00, drawn as a moving dot inside a circle so you can see the exact resting position.
• Input activity — a running counter of fresh button presses, useful for confirming a flaky button actually registers every time you tap it.

Because the API streams a live snapshot each frame, what you see is precisely what a game would receive — no smoothing, no interpretation.

How to Interpret Your Results

Start with the sticks. Release them and look at the numbers, not just the dot. Resting values within about 0.05 of zero are normal; the tiny noise you see is expected analog jitter. Sustained readings of 0.10 or higher while untouched signal drift, the most common controller failure. Next, push each stick fully in all four directions and confirm it reaches close to 1.00 and -1.00 — a stick that tops out at 0.80 has a worn or dirty gate.

For buttons, tap each one and watch the highlight and counter. A button that sometimes fails to light up is intermittent and on its way out. For triggers, pull slowly and confirm the value climbs smoothly from 0.00 to 1.00; a trigger that jumps straight to 1.00 or sticks partway has a failing sensor.

Troubleshooting Tips

If nothing appears at all, the fix is almost always to press a button — browsers won't reveal a controller until you do. Beyond that:

• Use a wired connection to rule out Bluetooth pairing or latency issues.
• Close other games or launchers (Steam, the Xbox app) that may grab exclusive control of the pad.
• Try a different cable or port — many "dead" controllers are really charge-only cables.
• Recalibrate at the OS level if axes look skewed; Windows has a built-in game controller calibration tool.
• Switch browsers if support seems missing; Chrome, Edge, and Firefox on desktop have the most complete Gamepad API support, while mobile Safari is limited.

Pair It With Your Reflex Benchmarks

A clean controller is only half the equation — your own response speed matters just as much. Once you've confirmed every input is crisp, measure how fast you act on it with the reaction time test, or sharpen your tracking with the aim trainer. Healthy hardware plus trained reflexes is what separates a frustrating session from a winning one.