How to use: Gamepad Tester
Connect the controller before or after opening the page.
Press any controller button so the browser can expose the device.
Move every stick and trigger while watching the live map, then open the drift analyzer if the center looks unstable.
What the result actually measures
The tester reads the buttons and axes your browser exposes through the Gamepad API. It can show whether an input changes, how far an axis moves and whether a controller disconnects during a session.
Measurement boundary: Browser mappings differ by controller, operating system and driver. A missing vibration feature or unusual label does not automatically mean the controller is defective.
How to interpret the output
Button response
A button should change state when pressed and return cleanly when released. Rapid flicker without a deliberate press may indicate a switch, driver or connection issue.
Axis range
Analog axes normally approach -1 and +1 at their outer limits. Some controllers report slightly smaller ranges or use a different axis order.
Center behavior
Small movement around zero is common. Use the dedicated drift sample instead of judging a single changing decimal.
Troubleshooting unexpected results
Nothing appears
Click the test area, press a controller button, try a wired connection and check whether another tab or game is holding exclusive access.
Buttons are numbered differently
Generic controllers may not use the standard mapping. The raw index remains useful even when the on-screen label differs.
Frequently asked questions
Does this install a driver?
No. It reads only the controller signals already exposed by your browser.
Can this prove my controller is broken?
It can document observed browser input, but hardware diagnosis should also be confirmed in another browser, connection and device.
Is my controller ID uploaded?
No. The live session is processed in your browser and controller input or identifiers are not sent to Keymap Labs.