What to look for
A healthy digital button should change quickly when pressed and released. Analog buttons and triggers may show a range between 0 and 1. If a button stays active after you release it, compare the result in another browser or connection mode before assuming hardware damage.
The Last pressed area is useful when a controller shell, adapter, or driver labels buttons differently from the game you are troubleshooting.
- Pressed state confirms whether the browser sees the input as active.
- Touched state appears only on devices that expose it.
- Analog value helps identify weak pressure, noisy trigger behavior, or non-standard mapping.
- Possible stuck input appears when an input remains pressed for several seconds.
Browser and hardware limits
Gamepad API support, haptic feedback, MediaRecorder, and WebHID are exposed differently across Chrome, Edge, Firefox, Safari, Linux, mobile browsers, USB, Bluetooth, and third-party drivers. For Controller Button Test, treat that limit as part of controller button test guidance rather than as a separate verdict.
A missing feature in the browser does not prove that the controller is damaged. Use the live readings as diagnostic hints and compare results across connection methods when possible. On this Controller Button Test page, compare that note with the live module that matches pressed state, touched state, analog value, last pressed input, and possible stuck input warnings.
Controller button test patterns
A controller button test is not just a checklist of labels. Press each button lightly, press it firmly, release it slowly, and watch whether the button state changes cleanly. The controller button test is especially useful for shoulder buttons, stick clicks, menu buttons, and older face buttons that may work only when pressed at a certain angle.
If the controller button test shows a button staying active after release, repeat the check after cleaning around the edge of the button and reconnecting the controller. If the same controller button test result appears in another browser or connection mode, the symptom is stronger than a one-time browser reading.
- Use the controller button test to check release behavior, not only press behavior.
- Watch analog values when the controller button test exposes pressure.
- Record stuck inputs from the controller button test before remapping.