What Is Controller Stick Drift? Causes, Symptoms, and How to Test It Properly

What is controller stick drift? Why a controller moves on its own and how to test it

Quick Answer Stick drift is phantom movement: your controller reports stick movement even though you are not touching the stick. Put it on a flat surface, leave the sticks untouched, and test for 30 to 60 seconds. A steady reading at 0.05 or higher in one direction counts as drift, while flickers within 0.02 to 0.03 are normal sensor noise. In a game that looks like: It is not a game bug if it happens in menus, in multiple games, and on a test screen. It is a hardware signal problem: the controller is telling the system the stick is off-centre when it is not. Test yours in 60 seconds: Put the controller on a flat surface, do not touch the sticks, and run our free Stick Drift Test. A healthy stick should settle at 0.0000 on both X and Y axes. How a stick actually measures position A stick reports its position from the sensor under it. When the sensor is new, rest reads 0.00. When the sensor wears, rest stops reading 0.00, and that offset is drift. To understand drift, you need to understand the sensor underneath the stick. Most standard controllers, including PS5 DualSense, PS4 DualShock 4, Xbox Series and Switch Pro controllers, use the same basic design: Newer Hall effect and TMR sticks work differently. They use magnets, not a physical wiper dragging on a track, so there is no carbon track to wear out in the same way. That is why hall effect controllers are marketed as drift-resistant. They can still develop calibration or deadzone issues, but they do not wear out by the same mechanism. The tester reads the value the Gamepad API reports for each axis. At rest, a centered stick reads 0.0000 on X and Y. At full tilt, the value reaches plus or minus 1.00. That number is the reported axis value, not a direct measurement of the physical track. A browser test reads what the Gamepad API reports. It is not a hardware diagnosis. What actually causes stick drift? There is no single cause. These are the four real causes, in order of how often they matter: 1. Potentiometer wear (the main cause) Repeated movement wears the carbon resistive track, especially near the centre where the stick rests most of the time. The wiper then reads a voltage that does not match a real position. This is why drift usually gets worse slowly, not overnight, and why heavy FPS and Rocket League players see it earlier. 2. Dust, skin oil and debris Dust, skin cells and debris get under the stick skirt and interfere with the wiper. This can cause early, jumpy drift that sometimes improves after cleaning. Cleaning helps contamination, it cannot repair a physically worn track. 3. Spring fatigue and centering shift The centering spring can lose tension over time (Tier 3, typical and community-reported cause, not a vendor-documented cause). The stick still returns, but not to exactly the same centre. The result is a small, consistent offset in one direction. 4. Calibration drift and software confusion A bad calibration, a firmware glitch, or a game with a very small deadzone can make normal sensor noise look like drift. This is why you must test on a flat surface, in a tester, before you open anything. Before opening anything, rule out software first: a game setting, deadzone setting, or connection issue can look like drift in gameplay. Test on a flat surface in a tester. That test, not gameplay alone, is the evidence. What drift is NOT: How to tell if you actually have drift: the number test Put the controller on a flat surface, leave both sticks untouched for 30 to 60 seconds, and read the X and Y values at rest in the drift test. A steady offset in the same direction is drift. A flicker that disappears is noise. Full method, step by step: How to Test Stick Drift Online. Reading at rest What it means Resting noise: 0.0000, with tiny flickers within ±0.02 to ±0.03 Normal sensor noise. Not drift. Mild drift: Consistent offset at ±0.05 to ±0.10, in the same direction Measurable drift. Mild, but real. A small deadzone will hide it, it will not fix it. Clear drift: Consistent offset above ±0.10, or a value that keeps creeping in one direction Clear drift. You will feel it in games, and cleaning or deadzone alone is unlikely to be a permanent fix. Value jumps randomly, even when untouched Could be debris, a loose stick, or a failing sensor. Clean first, retest, then decide on repair vs replace. Some other testers use above 0.15 as their replace threshold. This site uses the scale above for consistency. Test both sticks. They fail independently: left-stick drift ruins movement, right-stick drift ruins aim and camera. A steady offset at 0.05 or higher in the same direction is drift, not noise. Repeat the test before you decide. Stick drift vs deadzone vs snapback: do not confuse these three Drift is movement at rest, deadzone is the centre area a game ignores, and snapback is overshoot on return to centre. This confusion wastes a lot of money on the wrong fix. If you are not sure which one you have, test at rest first. Rest = drift. Flick-and-return = snapback. Both = test both, fix the worse one first. Problem Where it shows Test for it Stick drift At rest, untouched Flat, untouched 30-60 seconds, read X/Y Deadzone Centre area ignored by the game Smallest stable deadzone that hides mild drift, then confirm in game Snapback After a flick, on return to centre Flick and release, watch for overshoot/oscillation, not rest offset Does stick drift happen on every controller? Almost every potentiometer controller can develop it with enough hours, but timing varies a lot. Heavy daily use, aggressive stick clicking, drops, and dusty environments all shorten the time to drift. Some controllers last years, some develop it in months. Hall effect and TMR controllers are far more resistant

What Is Controller Polling Rate? Hz, Latency, and What a Good Number Really Means

What is controller polling rate? Hz explained for PS5, Xbox, PC and Switch

If your DualSense shows 250Hz wired, or your Xbox shows 125Hz wired, that does not mean the controller is broken. Those are their normal native rates (Tier 3 typical, not vendor specifications). This guide explains what the Hz number means, what to expect for your controller and connection, and when a result points to a real fault. Quick Answer Polling rate, measured in hertz (Hz), is the number of times per second your controller sends an updated input report to your device. The formula is simple: milliseconds = 1000 ÷ Hz. Polling rate Theoretical report interval 125 Hz 8 ms 250 Hz 4 ms 500 Hz 2 ms 1000 Hz 1 ms So a higher polling rate does not make your stick move faster. It makes your device hear about the movement sooner, and more often. In a fast shooter, that 7ms difference is the difference in report interval only, from 8ms to 1ms. It is one part of total lag, so it does not on its own decide whether a flick feels clean or late. Test yours now: Connect your controller, press any button, and use our free Polling Rate Test to see your live Hz, average Hz and jitter. No download, no account. Five terms, not one number. Polling rate: how often a controller reports input, in Hz. Report interval: the nominal time between reports, 1000 divided by Hz, not a guaranteed delay. Input latency: the total delay from input to game or screen response. Jitter: variation in measured intervals or update timing. Browser measurement: the timing the browser sees in Gamepad API data, not a physical press to photon measurement. No site sample size, firmware list, or measured range is claimed for the controller table until a dated test run is published; those ranges are Tier 3 typical, not vendor specifications and not site measurements. Polling rate vs input lag: they are related, but they are not the same thing Polling rate is only one slice of latency: the report interval between reports. This is the confusion most guides get wrong, and it costs readers good decisions. A 1000Hz controller can still feel laggy if it is on a weak Bluetooth link, if the game has high render latency, or if your display is slow. Likewise, a stable 125Hz controller on a clean wired link can feel perfectly fine for casual and story games. Think of it like this: polling rate sets the maximum delay from this one step. At 125Hz that step can add up to 8ms. At 1000Hz it can add up to 1ms. Everything else in the chain still matters. For the full chain, also run our Input Lag Test and compare wired vs wireless on the same controller. What polling rate should you expect? Real numbers, not marketing numbers Expect the native rate for your controller and connection, not the box peak. A steady result inside the table range for your connection is normal, and instability is the fault sign. Marketing pages often quote the best possible number. Real browser and PC tests are messier, and that is normal. Use this table as your reality check before you assume your controller is broken. How to read the table: Tier 3 typical means a community-tested range, not a vendor specification. Controller Typical wired USB Typical Bluetooth Notes PS5 DualSense / DualSense Edge ~250Hz native, up to 1000Hz with PC tools ~125–250Hz Native USB is often 250Hz, not 1000Hz. 1000Hz usually needs DS4Windows or a similar PC tool, wired only. PS4 DualShock 4 ~250Hz native, up to 1000Hz with PC tools ~125–250Hz Same pattern as DualSense: overclock is a PC-driver change, not a console change. Xbox Series X/S, Xbox One, Xbox Elite Series 2 ~125Hz about 125 Hz, lower and more variable on Bluetooth (Tier 3 typical) Xbox controllers are built around a 125Hz HID report. There is no reliable software overclock on PC. Nintendo Switch Pro ~125Hz ~125Hz Stable, but not a high-Hz controller. Steam Deck (built-in controls) ~500Hz internal (Tier 3 typical) N/A Internal controls are not a Bluetooth test. 8BitDo / GameSir pro models 250–1000Hz, model dependent ~125–250Hz The advertised Hz usually applies to wired or 2.4GHz dongle mode, not Bluetooth. Check your exact model. Generic budget USB pad ~100–125Hz (Tier 3 typical) N/A Budget pads often sit near 125Hz regardless of the box claim. The update interval is 1000 divided by Hz, so 125 Hz means a new report at most every 8 ms. On PC, Xbox-style controllers usually report through XInput, while older or generic pads often use DirectInput over USB HID. A browser test reads the reports the Gamepad API delivers, not the physical press itself. PC tools that raise the rate work through drivers you install yourself, so use them wired only. They have no effect on a console. Important honesty note for readers: if your DualSense shows 250Hz wired on our test, that is not a fault. If your Xbox shows 125Hz wired, that is also not a fault. Those are their normal native rates. A fault is instability: wild jumps, long dropouts, or a number far below the table for your connection type. USB vs Bluetooth vs wireless dongle Wired USB is the most consistent test. Bluetooth is usually lower and more variable, and can throttle idle reports on some devices, firmware and browsers. A 2.4GHz dongle, such as the Xbox Wireless Adapter, is steadier than Bluetooth for Xbox on PC, but it is not an overclock. Full comparison: USB vs Bluetooth controller polling rate. Does a higher polling rate actually help in games? Yes, but with diminishing returns. The largest single step is 125Hz to 250Hz, from an 8ms to a 4ms report interval. Above 500Hz the gains are small, and a steady average matters more than a jittery peak. Which tier fits which player: 125Hz vs 250Hz vs 500Hz vs 1000Hz controller polling rate. How to test your controller polling rate in 60 seconds Connect by USB for the ceiling number, or by