Buttons
Connect a controller and press a button if the browser has not exposed it yet.
Gamepad Button Test: Controller Buttons, D-Pad, Face Buttons, Shoulders, And Browser Gamepad API Input
Test controller buttons and D-pad presses with the browser Gamepad API.
What this test checks
- Controller API detection
- Button, stick, trigger, or haptic behavior
- Live polling and input state
- Watch Live Button State Changes
How to read the result
Buttons depends on the browser Gamepad API, so connect the controller and press a button first. Repeated drift, low polling, or missing button states usually deserve a second pass with the related controller diagnostics.
Connect A Controller To The Browser
The page waits for a gamepad exposed through the browser Gamepad API. Pressing any controller button often wakes the device and makes it visible to the tester.
Press Face Buttons, D-Pad, And Shoulders
Each physical control can be checked for registration. This helps users diagnose unresponsive A/B/X/Y buttons, sticky D-pad directions, shoulder buttons, and menu buttons.
Watch Live Button State Changes
The tester shows active button states and update counts, making it clear whether the browser receives button down and release events consistently.
Retest After Reconnecting The Controller
If a controller is not detected, reconnecting USB or Bluetooth and pressing a button can refresh the browser state. A clean retest helps separate pairing issues from button failure.
Related I/O Checkup Tools
What does Buttons measure?
Test controller buttons and D-pad presses with the browser Gamepad API.
Do I need to install anything for Buttons?
No. Buttons runs directly in a modern browser. Some checks may ask for permission when they need camera, microphone, gamepad, pointer lock, touch, or audio output access.
Are results uploaded?
The test runs in your browser and uses local input events or browser hardware APIs for the visible diagnostics.
Why should I run related tests too?
Related tools help separate hardware issues from browser timing, display behavior, input device settings, or permission problems, which makes the final diagnosis more useful.
Detailed Testing Guide
Controller symptom
This controller page checks one part of the Gamepad API signal instead of assuming one button press proves the whole pad is healthy.
Start with a baseline run before changing device settings. Record any repeated symptom so the next comparison is useful.
API evidence
Watch button state, stick axes, trigger values, vibration response, polling updates, and whether the controller stays visible.
Watch Controller API detection, Button, stick, trigger, or haptic behavior, Live polling and input state, Watch Live Button State Changes. These observations come from the browser; they do not reveal hidden firmware or factory calibration data.
Controller test method
Press a button to expose the pad, then test one control group at a time.
Keep the test conditions stable. Changing browser, cable, port, lighting, surface, volume, grip, or selected device all at once makes the result harder to trust.
Result reading
Browser support, Bluetooth latency, driver mapping, and firmware can all change what the page receives.
A repeated pattern matters more than a single spike. When something looks wrong, confirm it with another pass and compare a related tool before deciding the device itself is defective.
Limits and next checks
Use button, stick drift, trigger, vibration, and polling tests together for a complete controller pass.
For a closer comparison, try Gamepad Button Test, Stick Drift Test, Trigger Test, Polling Rate Test. Keep the same device and connection while you investigate the next symptom.