EVERY PRESS, VISIBLE
Controller button test
Press each control and watch the button grid respond. With a standard mapping, analog trigger values appear as live bars.
Connect with USB or Bluetooth, focus this page and press a controller button.
Resting-stick measurement
This describes the input exposed by your browser. Firmware and remapping software can already apply deadzones. These readings do not certify hardware condition.
Raw readings & input history
Indices are shown as reported by the browser. Unknown layouts are not assigned stick or trigger names.
Waiting for controller input.
Check every control.
- Buttons
- Triggers
- Stick drift
- Stick range
- Results
Connect a controller to begin.
Saved snapshots & comparison 0
Saved only when you choose, in this browser. Compare readings taken under the same conditions.
What to look for
Press and release each button separately. An active chip shows a current press; an observed chip records that the browser saw that button during this session. Hold a button to check whether the reading stays steady.
Slowly squeeze each analog trigger. A supported analog input should produce intermediate values. Some controllers have digital shoulder triggers that report only on/off, so the absence of intermediate values is not always a fault.
When the labels do not match
Choose a familiar label set or use button indices. This changes presentation only. For non-standard mappings, the tester keeps the browser’s raw indices and does not guess which axes are sticks.
System buttons, extra rear buttons and vendor-specific controls may not be exposed independently. Browser sampling can also miss very short events. Use the advanced panel to inspect what was actually reported.