Which symptom should you compare first?
Watch the controller appear after the first button press, then compare each face button, shoulder button, D-pad direction, trigger value, and left/right stick axis while the device is idle and while it moves.
Controllers
Online Gamepad Tester
Gamepad test for connection status, buttons, D-pad, stick axes, trigger values, mapping type and browser Gamepad API detection.
Online Gamepad Tester
Live controller input
Connect a controller, then press a button or move a stick.
Live controller inputWaiting for input
buttons—
active0
axes—
Max offset0.000
Activate your controller
Connect by USB or Bluetooth, keep this tab visible, then press any controller button. Some browsers do not reveal an already connected controller until the first interaction.
Waiting for input
What this tester checks
Buttons, D-pad directions, shoulder controls, analog triggers, dual-stick position, raw axis values, standard or non-standard mapping, multiple connected controllers, and connection history.
Controller connection, button, stick, and trigger overview test
- Connect the controller by USB or Bluetooth.
- Keep this tab visible and press any controller button.
- Press every face, shoulder, menu, and D-pad button.
- Move both sticks slowly to their full range and release them.
- Pull each trigger from zero to full pressure and compare the values.
How to read the result
A released button should return to 0 and a fully pressed analog control should approach 1. Stick axes should return close to 0 after release. Small variation can be normal; repeat the test before treating a sustained offset as drift. Non-standard mappings may use different button and axis numbers.
Waiting for controller input
No controller detected
Controller connected
Controller disconnected
Gamepad API unsupported
Current controller
Controllers
Active buttons
Maximum axis offset
A sustained axis offset was detected. Release both sticks, avoid touching the controller for a few seconds, and repeat the test.
Local browser diagnostics
Controller IDs and input values are read by your browser and are not uploaded by this tester. The page does not record gameplay, remap controls, or activate controller vibration.
Browser and controller compatibility
Gamepad support varies by browser, operating system, driver, and controller. Some browsers only expose a controller after the user presses a button while the page is visible. Vendor-specific controls may appear as numbered buttons or axes.
Focused controller checks
Use the full Gamepad Check above for a broad controller pass, then open a focused page when the symptom is specifically stick drift, a missing button, or LT/RT trigger range.
Controller detection, drift, and mapping questions
Q: Why is my connected controller not shown?
A: Keep the tab visible and press a controller button, then scan again.
Q: Does an offset always mean stick drift?
A: No. Release the controller, repeat the test, and compare the value with the 0.10 deadzone.
Q: Why are button names different from my controller?
A: Standard mapping uses position-neutral labels; non-standard devices are shown by button and axis number.
Q: Can this page repair or remap a controller?
A: No. It diagnoses browser-visible input only.