Gamepad test
Connect a controller and press any button to wake it up. Every button and axis is shown live, which is the quickest way to find stick drift or a trigger that no longer reaches its full range.
No controller detected. Connect one and press any button on it.
- Controller
- —
- Buttons
- —
Finding stick drift
Let go of both sticks completely. The axis readings should sit at or very near zero. A stick that reports movement while untouched has drift, and it is the most common controller failure — in a game it shows up as slow unwanted movement that you keep correcting.
Small non-zero values are normal; games apply a dead zone to hide them. Readings that wander while your hands are nowhere near the controller are not.
Triggers that no longer reach the end
Pull each analogue trigger slowly to its stop. The reading should travel smoothly from 0 to 1 without jumping or stalling. A trigger stopping short of its maximum will feel unresponsive in any game that maps acceleration to it.
Nothing here leaves your device
Every one of these tests runs entirely in your browser using standard web APIs. No audio, video, keystroke or controller input is uploaded, recorded on a server, or stored anywhere — there is no upload endpoint for any of it to go to. Closing the tab discards everything.
Common questions
Why is my controller not detected?
The browser only reveals a gamepad after you press a button on it — this is a privacy protection, not a fault. Press any button. If nothing appears, try a different cable or re-pair over Bluetooth.
How do I check for stick drift?
Release both sticks and read the axis values. They should rest at or near zero. Values that move on their own indicate drift.