Controller Stick Drift: How to Check It and What the Browser Can Show
Character or camera moving on its own? Read your sticks' raw values in TryYourGear's Controller Test and learn how drift differs from dead zone and mapping.
Stick drift is when a controller reports movement while you aren't touching the stick, or when the stick doesn't come back to the center after you let it go. In a game it looks like a character walking on its own, a camera turning slowly or a cursor creeping across the screen. The same symptom can come from the stick itself, from a setting that decides how much movement to ignore, from calibration, or from the way a game reads the controller, so it's worth looking at the raw values before you decide.
TryYourGear's Controller Test shows what your browser receives from the controller through the Gamepad API: every button and trigger, and the position of the two analog sticks as x and y numbers. It doesn't inspect the hardware. What it gives you is a way to look at the signal itself, without a game's settings on top of it.
What this guide can and can't tell you
Seeing a stick rest away from zero tells you the controller is reporting an offset, and that is useful evidence. It doesn't prove that the parts inside the stick are worn, and a reading that isn't perfectly centered isn't automatically a fault: it matters how big the offset is, whether it changes and what your game does with it.
What the Controller Test shows
The page waits until a controller is detected. Browsers only expose a controller after you press a button on it while the page is visible; MDN explains that this is a security policy. Once it is connected, the page shows the name the browser reports, a tile for every button (a trigger that reports partial values shows a bar between 0 and 1 while you press it) and a circle for each stick.
In each circle a dot follows the stick, and the x and y values appear below with two decimals, from −1.00 to 1.00. Pushing left gives a negative x and pushing up gives a negative y. The values come straight from the controller's axes: the page applies no dead zone, no correction and no calibration. It reads them about twenty times a second, it only reads the first controller the browser reports, and the right stick's circle appears only if the controller reports at least four axes.
Drift, dead zone, calibration and mapping are not the same thing
| Term | What it is | How it shows in the Controller Test |
|---|---|---|
| Drift | The controller reports movement at rest, or the stick doesn't return to the center. | Values away from 0.00 with the stick untouched, values that keep changing on their own, or a dot that doesn't come back to the middle after you release it. |
| Dead zone | A setting in a game, a driver or a console that ignores small movements near the center. Its job is to hide small offsets. | Not applied by this test. You see the raw offset that a game's dead zone may be hiding, or failing to hide. |
| Calibration | An adjustment of where the system or the controller considers the center and the limits to be. | Not shown as such. A wrong calibration looks like a steady offset at rest or a range that doesn't reach ±1.00, and the test can't tell it from wear. |
| Mapping | How the browser or a game assigns the controller's inputs to sticks and buttons. | A dot that moves when you press something else, labels that don't match the button you pressed, or a trigger that shows up as a stick. |
MDN notes that gamepads can get dusty and then don't reliably reach exact −1 or 1 values, which is why programs work with thresholds instead of exact comparisons. That is a good reason not to treat a slightly off-center reading as proof of a fault on its own.
Run the test and check the sticks
Look at the sticks at rest
Put the controller down on a table, or hold it without touching the sticks, and press any button so the page detects it. Note the x and y values of both sticks and watch them for 15 to 20 seconds. Do they sit still or wander?
Move each stick and let it go
Push it slowly all the way around its edge, then release it from different directions. After each release, check where the values settle and whether they come back to about the same place.
Check the whole range
At the edge, the values should get close to ±1.00 in every direction. If one direction stops well short, note which.
Compare with another game or app
If a game drifts while the test shows values near 0.00, look at that game's controller settings, including its dead zone. If the test shows an offset and the game doesn't drift, the game's dead zone may be hiding it.
Try another controller or another connection
Test a second controller on the same computer, and your controller on another device or with a cable instead of Bluetooth. A fault that follows the controller points to the controller; one that stays with the computer doesn't.
Reading what you see
| What TryYourGear shows | What it suggests | What it doesn't show |
|---|---|---|
| Both values sit near 0.00 and stay still | The controller reports the stick as centered. If a game still drifts, look at that game's settings, its dead zone and how it maps the controller. | What the game does with those values. |
| A steady offset at rest: one or both values sit clearly away from 0.00 | The controller reports a constant off-center position. Wear, dirt, calibration or the sensor can cause it. A game's dead zone may hide a small offset and not a large one. | Which of those causes it, or how large an offset your game tolerates. |
| Values that wander or jump at rest | An unstable signal. A worn or dirty stick can do this, and so can a poor connection. | Whether the fault is in the stick or in the link. Repeat with a cable. |
| After release, the stick settles somewhere other than the center, or somewhere different each time | The stick isn't returning to its resting position reliably, or the center the controller reports has moved. | Whether the cause is mechanical or electrical. |
| One stick is fine and the other isn't | The problem is limited to one stick, not to the connection or the browser. | Anything about what is inside that stick. |
| A dot moves when you press a trigger or a button, or the labels don't match | A mapping difference: the controller reports its inputs in a layout the browser or the page doesn't treat as standard. | The layout your game uses. Games often apply their own mapping. |
| Nothing appears until you press a button | Normal browser behaviour: it only exposes the controller after you interact with it. | Nothing wrong: it isn't a fault. |
What the browser can't prove
- A worn or damaged sensor. The test sees the value the controller reports, not the parts behind it.
- How much drift a game will show. That depends on the game's dead zone, its response curve and its settings.
- Whether an offset is “too much”. There is no universal limit, and the test doesn't apply one.
- Differences between browsers, systems and controllers. The values and the layout depend on the API, the browser and the controller, so a reading here can differ from the same controller on a console.
- Wireless quality, vibration, motion sensors, touchpads or battery. None of these is tested.
- A second controller. When several are connected, the page reads only the first one it finds.
What to do with your result
The test shows values near zero but the game drifts
The controller isn't reporting an offset to the browser. Look at the game's own settings (dead zone, sensitivity), any input-remapping software running on your computer, and whether the game is reading another controller or profile.
The test shows an offset or unstable values
Repeat the check with a cable and, if you can, with another controller and another device, to see whether the fault follows the controller. If it does, contact the manufacturer or the seller and tell them what you saw: which stick, the values at rest and whether they change. Some platforms and manufacturers offer a calibration or dead-zone setting for their controllers; where there is one, it lives in the platform's, the game's or the manufacturer's own software. Don't open the controller unless the manufacturer's guidance says it is safe.
Summary
- Stick drift is a controller reporting movement at rest or failing to return to the center. The Controller Test shows the raw values your browser receives, with no dead zone applied.
- Drift, dead zone, calibration and mapping are different things. The test helps you tell a reported offset from a game's own settings.
- Check the sticks at rest, after release and at the edge, then compare with another game or app and another controller or connection.
- A reading that isn't perfectly centered isn't automatically a fault, and the test can't see inside the stick.