How the controller test works
The page reads your controller through the Gamepad API, the same interface browser games use. About 60 times per second it reads the state of every button, every trigger and both sticks, and draws it on screen.
- Buttons light up while pressed. Labels follow your controller family: A/B/X/Y on Xbox, ✕/○/□/△ on PlayStation, B/A/Y/X on Switch.
- Triggers show their analog travel from 0.00 (released) to 1.00 (fully pressed). A trigger that never reaches 1.00, or rests above 0.00, is worn or dirty.
- Sticks show their position on two axes from −1 to 1. The dashed circle marks a 0.10 radius, a common default deadzone in games.
How to read the result
| What you see | What it means |
|---|---|
| A button does not light up | Worn contact or dead button. Test again over USB to rule out Bluetooth. |
| A button lights up on its own | Stuck or dirty button, or a ghost input from a damaged board. |
| Trigger stuck between 0.05 and 0.20 at rest | Worn trigger spring or potentiometer. Usually harmless in games. |
| Stick dot moves when you let go | Stick drift. Run the stick drift test for a precise measure. |
| Stick does not reach the outer circle | Limited range: the stick will feel slow at full tilt. |
Limits of a browser test
Browsers only expose what the Gamepad API standardises. You will not see the DualSense touchpad, gyroscope, adaptive trigger resistance, the Switch Pro motion sensors or back paddles mapped by vendor software. Bluetooth adds a few milliseconds of delay, so this page is not an input lag test.
If your controller works here but not in a game, the problem is in the game or launcher settings (Steam Input, controller emulation), not in the hardware.
Frequently asked questions
Why doesn't my controller show up?
Browsers hide controllers until you press a button, so a page cannot fingerprint your devices. Press any face button. If it still does not appear, unplug it, plug it back in, close other apps that grab the controller (Steam Big Picture, DS4Windows) and reload the page.
Does it work with a PS5 DualSense or PS4 controller?
Yes, over USB or Bluetooth, in Chrome, Edge, Firefox and Safari. Buttons, triggers and sticks are read. The touchpad, gyroscope and adaptive triggers are not exposed by browsers.
Can I test vibration?
Yes in Chrome and Edge, which support the rumble motors of most Xbox and PlayStation controllers. Firefox and Safari do not expose vibration to web pages yet.
What does "non-standard mapping" mean?
The browser did not recognise the controller layout, so it reports raw button numbers. Every input still works, but the labels on screen may not match the ones printed on your controller.
Is my controller data sent anywhere?
No. The test reads the Gamepad API locally in your browser. Nothing is recorded or uploaded.
Updated October 26, 2026