What this test checks
Test a gamepad in your browser and check buttons, triggers, analogue sticks, live values and connection changes without installing software.
InputAnalyzer processes test events locally and does not upload your raw inputs or result values.
How to run the test
Connect and activate the gamepad
Connect it by cable or Bluetooth, then press any button so the browser can detect it.
Check every control
Press each button and trigger once, then move both sticks slowly through their full range.
Review the event history
Look for controls that never respond, remain active after release or produce repeated activations.
How to read the result
Observed signals, not artificial certainty.
Consistent response
Controls activate once, return to rest and move smoothly across the values reported by the browser.
Possible issue
A missing, stuck or repeated response is worth confirming after reconnecting and in a second browser or game.
What this test cannot prove
What the browser cannot see
- Button names and axis order can differ on controllers that do not expose the standard gamepad mapping.
- This test reads browser events; it cannot identify the physical component responsible for a fault.
- Results are browser-based estimates, not a physical hardware diagnosis.
Useful next tests
Frequently asked questions
Short answers before you test again
Why is my gamepad not detected?
Press a button after connecting it, keep this tab active and try a wired connection. Browser, operating-system and controller support can vary.
Does InputAnalyzer store my controller inputs?
No. The test processes button and axis events locally in this browser and does not upload the raw values or result.