Controller Button Test
Focus on face buttons, bumpers, D-pad, stick clicks, and any extra buttons your pad reports.
Button response panel
Buttons are generated dynamically from the Gamepad API — no fixed layout assumption.
Press every button and verify release timing
The Controller Button Test focuses on digital and analog button channels so you can confirm presses register cleanly without false holds. Face buttons, bumpers, stick clicks, share or view keys, and system buttons each get a clear visual so sticky contacts or worn membranes stand out quickly. Pair this with the broader Controller Tester when you also need stick and trigger context.
Browser Gamepad API values are normalized differently across vendors. A DualSense Share button and an Xbox View button may share similar indexes under the standard mapping, yet third-party pads often report unknown mapping. When labels look wrong, trust the raw index and value, not the marketing name printed on the plastic.
What sticky buttons look like here
- Pressed stays true after you lift your finger.
- Value never returns fully to zero on analog triggers treated as buttons.
- Double presses appear as one long hold if debounce is failing in hardware.
These symptoms usually point to membranes, microswitches, or debris rather than a site bug. Close overlays that capture exclusive input, reconnect the cable, and retest. If detection itself fails, use Controller Detection before blaming individual buttons.
FAQ: can the page remapping buttons permanently?
No. Remapping belongs in Steam, vendor software, or the game. This tool only visualizes what the browser receives. For vibration after button checks, try Vibration. For center noise on sticks, jump to Stick Drift instead of guessing from button state alone.