Gamepad Tester & Stick Drift Test

A gamepad tester displays controller inputs received by your browser. This page shows button states, stick X/Y values, trigger percentages, and eight recent button-input or connection log entries. It helps describe symptoms but does not certify hardware condition.

Connect the controller by USB or Bluetooth, select this page, and press a controller button. Then try the buttons, both sticks, and both triggers. If it remains undetected, check operating-system recognition, the connection, and browser permissions.

Yes, you can observe input while leaving the sticks untouched. The advice changes when either stick’s current X/Y vector has a radius greater than 0.18. This is a display threshold, not a measurement of sustained drift or a hardware-fault verdict.

Unintended movement can involve off-center stick input, game deadzone settings, calibration, or other software. Small center offsets may fall inside a game’s deadzone. Compare the untouched-stick readings with what happens in the game before deciding what to do.

You can try one if your operating system and browser expose it through the Gamepad API. The diagram uses familiar standard button labels as a guide. A controller name or a standard-looking display does not confirm that every model, connection mode, or special button works.

You can try these controllers when recognized through the Gamepad API. Physical labels and available features may differ from the standard diagram. This page does not test adaptive triggers, haptics, motion sensing, battery condition, or every model-specific button.

It may work when your operating system and browser recognize the controller. A/B and X/Y positions can differ from the diagram’s labels. For non-standard mappings, use the received values as observations and compare them with your physical actions; the page does not automatically remap the device.

Check the cable or Bluetooth pairing and operating-system recognition. Select the page and press a controller button; Firefox and other browsers may wait for controller interaction. Use a supported browser on HTTPS. An embedded page can also be restricted by its permissions policy. Try another browser or controller to compare.

Yes. A button is highlighted when its pressed state is true or its reported value is above 0.45. Trigger values at standard button indices 6 and 7 are shown as percentages. Some devices report digital values or use different assignments; the display does not change your physical mapping.

Button chattering can describe unintended repeated input when you meant one press. This page notes a possible rapid repeat when a new press of the same button follows the previous press in less than 90ms. Intentional rapid presses and browser sampling can affect the log, so a flag is not proof of a faulty switch.

No. It displays received input and troubleshooting guidance. It does not update firmware, calibrate the controller, repair a switch, or change deadzones. Check official operating-system, game, or manufacturer settings, and consider support if the symptom persists.

It can, if the controller is paired and exposed by the operating system and browser. USB and Bluetooth can produce different mappings or available inputs. This page does not measure Bluetooth link quality, precise input latency, or polling rate.

No. It is a browser-input check with current visual values and a rolling eight-entry log of button presses, rapid repeats, and connections. It does not continuously log every stick movement or export a report. A hidden page pauses polling; returning reads current input again without treating held buttons as new presses.

Diagnostic input is processed on this page and is not uploaded. Only when changing languages, eight structured log entries and the active slot number use a one-use session handoff valid for 30 seconds; the receiving page removes it. Device identifiers are not included in that handoff. Ordinary page requests are separate from diagnostic input.