Controller Input Viewer
A live JSON view of all buttons and axes, with a local event-trace recording you can download for debugging.
This feature isn’t available here
Controller support isn’t available here.
Commonly supported by: Chrome, Edge, Firefox, Safari (desktop).
What you can do: Use a recent desktop browser.
01How this test works
Gamepad tests only see your controller after you press a button on it — that is simply how browsers work. From then on we read the current state of every connected controller many times a second: its buttons, triggers and stick positions.
Stick positions are shown on a −1 to +1 scale. Drift and deadzone tests watch the sticks while you leave them alone, so you can see how far they rest from center and how much that reading wanders, instead of judging from a single glance.
Vibration is only offered when your controller and browser actually support it, and the strength and length are kept within safe limits. We never show a fake rumble.
02How to use it
- Connect your controller by USB or Bluetooth.
- Press any button — the browser hides gamepads until they send input.
- Watch buttons, triggers and sticks respond live in the visualization.
- For drift tests, leave the sticks untouched to sample their resting position.
- For vibration, use the bounded intensity and duration controls to trigger a rumble.
03What this test covers
What it detects
- Whether the browser sees the controller and its standard or custom mapping
- Button pressed states and analog trigger values
- Stick axis positions, resting offset (drift) and suggested deadzones
- Whether vibration is available for your controller
What it can’t detect
- A definitive ‘broken’ verdict from one short sample
- Hardware wear versus a mapping or calibration difference
- Vibration on controllers or browsers that don’t support it
04Troubleshooting
| Symptom | What to do |
|---|---|
| Controller not detected | Press any button first — browsers hide gamepads until they receive input — and confirm it’s connected and powered. |
| Wrong button mapping | Non-standard controllers may not match the standard layout; the raw indices are still shown. |
| Small stick offset at rest | A tiny resting offset is normal; only a consistent, larger off-center reading suggests real drift. |
| Vibration does nothing | Your controller or browser may not support vibration; we never fake a successful rumble. |
05FAQ
Why isn’t my controller detected?
Press any button first — browsers hide gamepads until they receive input. Also make sure it’s connected and powered.
Is a little stick drift normal?
A tiny resting offset is normal. Consistent, larger off-center readings may indicate real drift.
Does vibration work?
Only where your controller and browser support it. We never fake a successful rumble.
Which controllers are supported?
Most standard USB and Bluetooth controllers (Xbox, PlayStation, and many others) that your browser recognizes.
Can I test multiple controllers at once?
Yes — connect several and each appears separately once you press a button on it.
Is my controller input sent anywhere?
No. Button, trigger and stick data are processed locally and never uploaded.
Related tests
Connect a controller and see live button values, analog triggers, axes and mapping for one or more devices.
Sample your sticks at rest to see resting noise and a suggested deadzone. It never changes system settings.
Check every button and analog trigger with press counts and a stuck-input indicator.