How to Test Controller Stick Drift and Deadzones
To check stick drift, connect your controller, release both analog sticks and inspect the inputs reported while they are untouched. Our gamepad tester includes a five-second resting-offset check, live axes, circularity tracing and a report you can export. These checks help document behavior; they do not repair or calibrate the controller.
Connect the controller before testing
Use a USB data cable or pair the controller through your operating system’s Bluetooth settings. Keep the test page visible and press a face button. Select the intended controller if several are connected. Many Xbox, PlayStation and generic controllers can be exposed to the browser, but feature support depends on the operating system, browser, controller and connection.
If the tester does not detect it, verify the cable supports data, check pairing and try another USB port. Close remapping software temporarily if it changes the inputs delivered to the browser. Change one thing at a time and note what helps.
Run a five-second resting-offset check
- Place the controller on a stable surface.
- Move and release each stick to check that it returns freely.
- Select Check drift and leave both sticks untouched for the full sample.
- Record the left and right resting-offset results.
- Repeat after moving and releasing the sticks from different directions.
Our tool reports the average distance from center during that sample, expressed as a percentage of the nominal stick radius. Accidental movement during the sample increases that reading. A repeated offset after release is useful evidence to investigate, but it is not a universal pass-or-fail threshold.
Read axes and deadzones correctly
Stick axes generally use a range from −1 to +1. The center is near zero on each axis. The values come through the browser’s Gamepad API; they may already reflect controller firmware, drivers or operating-system processing. They are not necessarily unprocessed sensor voltages.
A game’s deadzone is a region in which small stick movement does not produce an in-game action. Our deadzone slider only draws a reference around the center. It does not write a setting to the controller or change a game’s behavior. Increasing a game’s deadzone can mask small unwanted inputs, but it is different from repairing the cause and can reduce response to small intended movements.
| Observation | Metric to inspect | Interpretation limit |
|---|---|---|
| Character moves with sticks released | Repeated resting offset and live axes | The game’s settings also affect movement |
| Movement does not reach full range | Axis extremes and outer trace | Mapping and firmware can shape output |
| One direction looks uneven | Repeated traces after release and rotation | A single incomplete rotation can mislead |
| Vibration is missing | Actuator availability and physical response | Browser support may be absent |
Test circularity separately from drift
Drift concerns the resting center; circularity concerns the reported outer path. Start circularity and slowly rotate each stick along the rim for several complete circles. In this tool, angular coverage and the largest observed radius in each section contribute to the result. Follow its coverage prompt before interpreting a completed measurement.
A lower circle error describes an outline closer to the tool’s reference circle. It does not establish better aim or overall hardware quality. Some controllers intentionally produce processed or square-shaped ranges, and other testing websites may use different formulas. Compare repeated attempts using the same tool and method.
Compare USB and Bluetooth without guessing
Export a report for one connection, reconnect using the other and repeat the same sequence. Record the controller model, browser, connection and any remapping settings. This can reveal a difference in what the browser receives, but it cannot prove the full physical-button-to-game delay. The tester’s browser sampling figure is not the controller’s hardware polling rate.
Check buttons, triggers and vibration
Press each button separately and check that it returns to released. Pull triggers slowly to inspect their analog range. If vibration controls are available, run a short command and confirm whether you physically feel it. An accepted software command does not prove a motor moved, while an unavailable control does not prove broken hardware.
What to do with the result
Keep two or three repeatable reports rather than one screenshot of an accidental movement. If the same unwanted input appears in games and the browser, use the manufacturer’s support or calibration instructions for that model. Avoid opening the controller before checking warranty and official guidance.
Controller diagnostics measure reported hardware behavior. For your own response speed, use the reaction time test. For keyboard repetition, use the spacebar clicker test. Keep these results separate from drift and circularity readings.
