Why does a trigger appear as a button?
The Gamepad API exposes many triggers in the button array with both a pressed flag and an analog value between their resting and full range.
CONTROLLER BUTTON TEST · LOCAL INPUT
Controller Button Tester
Check every browser-exposed controller button, analog value, touched state, and sampled press edge without uploading input.
BUTTON INPUT · LOCAL OBSERVATION
No controller selected
No controllers detected.
Waiting for controller
Browsers expose a controller after it sends an input. Keep this page active, then press a physical controller button.
- Index
- Not available
- Mapping
- Unmapped
- Connected
- No
- Stale
- No
Last input
No button input observed
Current button states
Every raw button stays visible; press counts cover this connection session.
No button values available.
Raw buttons
| Raw index | Value | Pressed | Touched |
|---|---|---|---|
| No button values exposed. | |||
Button event history
Newest 100 sampled edges in deterministic raw-index order.
No button changes observed yet.
Local report
The report is created in this browser and downloaded directly to your device. Nothing is uploaded.
This tool exports summary data only.
Raw and focused
See every browser-observed button
This focused controller button test keeps raw indices visible while adding standard labels only when the browser provides a standard mapping. Held combinations stay highlighted together, and cumulative counts make repeated inputs easier to compare.
Three steps
How to test controller buttons
01
Connect and activate
Connect one controller, keep this page active, and press a physical button so the browser can expose it.
02
Press every control
Press and release buttons individually, then hold combinations to confirm simultaneous states remain visible.
03
Compare the evidence
Review the raw index, mapped label, analog value, touched state, press count, and bounded edge history.
Sampled evidence
Measurement limitations
Results reflect input exposed through the browser after controller firmware, transport, operating-system, driver, and mapping effects. They do not certify hardware health, prove the cause of a missed press, or guarantee every transition was sampled.
If presses stay idle
Troubleshooting button input
- Keep the page active and press a physical controller button after connecting.
- Select the intended controller when more than one device is listed.
- Close games or remapping tools that may hold exclusive access.
- Try another cable, USB port, Bluetooth pairing, or current desktop browser.
Plain answers
Frequently asked questions
Why is touched always unavailable or false?
Touched-state support varies by controller, operating system, mapping, and browser. A false value does not prove the sensor is absent or broken.
Can fast presses be missed?
Yes. This history records browser-observed frames, so a complete press and release between two samples may not appear.
Does this upload my controller data?
No. Observation stays in browser memory, and the optional JSON download contains summary values only without the raw device identifier or browser user agent.