Controller test
Connect a gamepad, then press a button once to let the browser expose it through the Gamepad API.
X 0.000, Y 0.000
X 0.000, Y 0.000
Xbox, PlayStation, Nintendo-style, and generic controllers can all work, but the browser may present different button numbers and mappings. This tester reports what the browser receives. It cannot reconfigure firmware, fix drift, or guarantee that a game uses the same mapping.
Last updated: July 25, 2026
Controller test: This controller test reads the browser Gamepad API directly and shows what games can receive: stick axes, button states, analog pressure values, device mapping, and haptic support.
How this controller test works
Connect the controller with USB or Bluetooth, focus this page, and press a face button. Browsers often hide a gamepad until the user interacts with it. Move both sticks slowly around their full circles and let them return to center. Press every face, shoulder, menu, stick, and directional button. Squeeze analog triggers gradually and watch the value rise toward 1.00.
How to read the results
Centered stick axes should sit close to 0.000 and return consistently after release. Small movement is common, but a value that pulls steadily in one direction may cause drift in games. Digital buttons normally jump from 0.00 to 1.00. Analog triggers should move smoothly. Button numbers differ by controller and browser, so diagnose the signal first and the printed label second.
Common causes of failed tests
Stick drift often comes from worn potentiometers, contamination, spring wear, calibration, or firmware. Missing buttons can involve a damaged membrane, cable, Bluetooth pairing, driver, Steam Input profile, or browser permission behavior. A controller may work over USB but expose fewer features over Bluetooth.
Troubleshooting before you replace hardware
Press a button after loading the page, try a current Chromium or Firefox browser, reconnect directly by USB, and close apps that take exclusive control. Update official controller firmware and remove custom remapping while testing. If the pad never appears, test the operating system controller panel. Vibration is optional in the API and is not available for every browser-device combination.
For setup and buying context, see the GPU price tracker and home office budget calculator.
Frequently asked questions
Why must I press a button before the controller appears?
Browsers use a user-interaction requirement to reduce passive device fingerprinting.
How much stick drift is normal?
A tiny resting value can be normal. Consistent movement that exceeds a game's dead zone is the practical problem.
Why is vibration unavailable?
The controller, connection mode, operating system, and browser must all expose a compatible haptic actuator.