1. Release the stick
Place the controller on a stable surface and let the stick return to its resting position before reading center deviation.
Controller center check
Stick drift test: see how far your controller rests from center.
Connect a controller, release the stick, and inspect the center value your browser receives. A non-zero reading is not, by itself, proof of hardware failure.
2. Watch center deviation
The value is the current radial magnitude exposed by your browser and operating system.
3. Repeat the check
Move the stick normally, release it again, and compare repeated browser-observed resting values rather than relying on one sample.
Connect a controller and press any buttonThe browser will list controllers it can expose through the Gamepad API.
navigator.getGamepads(). Try a current desktop browser with Gamepad API support.Live input
Buttons
Analog input
Triggers
Left Trigger
Right Trigger
Analog position
Sticks
Left stick
Right stick
Session measurements
Stick diagnostics
MeasurementLeft stickRight stick
Center deviationCurrent radial magnitude
Observed rangeMaximum radial value in this session
CircularityRadial spread from perimeter samples
Input Threshold TestFirst observed movement above a 2% reference thresholdThis does not directly measure a controller’s built-in hardware or firmware deadzone.
Uninterpreted values
Raw input
Raw Input keeps the browser's original button and axis indices. Known controller labels appear only in the interpreted view above.
Browser metadata
Controller information
Results reflect input values exposed by your browser and operating system and may differ from raw hardware measurements. Session measurements describe only the values observed while you run them; they do not diagnose hardware failure.
What does a non-zero center value mean?
Small values can appear because of controller mechanics, operating-system processing, browser mapping, or normal input variation. This page does not apply a universal percentage that proves stick drift.
Can this test repair stick drift?
No. The page only visualizes and summarizes the controller values exposed to the browser.
Why can another game or tool show a different result?
Games, drivers, operating systems, and browsers can apply different mappings or deadzone behavior. Browser-observed values may therefore differ from raw hardware measurements or in-game behavior.