Controller Lab // Digital Input Diagnostics
GAMEPAD BUTTON TEST
Press every controller button and watch the browser-reported input in real time. The test records which buttons have been seen, how many are active together, their current values, and the most recent press events.
LOCAL TESTButton values are read and processed only in this browser session.
How to test every gamepad button
- Connect the controller and press any button to activate it in the browser.
- Press each face button, shoulder button, stick click, menu button and D-pad direction one at a time.
- Then press common combinations together to check whether simultaneous inputs are reported.
- Watch for a button that stays active after you release it, never reaches an active value, or activates another index unexpectedly.
- Use the tested counter as a checklist, but remember that different controllers can expose different numbers of buttons.
Why button numbers and labels can differ
Browsers expose gamepads through the Gamepad API. When a device uses the standard mapping, common indices are broadly consistent, but physical labels still differ between Xbox, PlayStation and Nintendo-style layouts.
GearCheck Lab shows a conventional label plus the underlying button index. Treat the index and live value as the authoritative browser reading, not the printed face-button name.
What a healthy button should look like
Most digital buttons should move from 0 to an active value when pressed and return to 0 after release. Some controllers expose triggers as analog button values between 0 and 1; those are covered more deeply in the separate trigger diagnostic.
A repeated missed press, a button that stays partially active, or a different button index activating can justify retesting by USB, updating controller firmware, and comparing another browser or device.
Simultaneous presses and rollover
Gamepads are generally designed to report multiple buttons at once. Use the ACTIVE NOW count to test combinations you actually use in games. If a specific combination consistently drops one input, repeat it several times before concluding there is a controller issue.
Browser, driver and game mapping layers can affect what this page sees, so compare suspicious results with the full controller test and the affected game.
Gamepad button test FAQ
Why does my PlayStation Cross button show as A?
The page uses conventional standard-mapping labels for readability. The physical symbol differs by controller family. The numeric browser index shown on each tile is the more neutral reference.
Why are LT and RT included here?
The Gamepad API often exposes analog triggers in the button array. This page confirms that they report input; the dedicated trigger test will focus on travel, resting value and full-range behaviour.
Does this test remap buttons?
No. It only reads the values the browser exposes and does not change your controller, operating-system mapping or game settings.
Related controller diagnostics