What is controller deadzone?
A deadzone is a portion of analog-stick travel that software treats specially. The familiar inner deadzone ignores small movement near the centre; an outer deadzone changes how close to the edge a stick must travel before full input is reported.
Why inner deadzones exist
Analog sticks never rest perfectly still, so without an inner deadzone a game may receive tiny constant input. The inner deadzone creates an area around centre where movement is treated as no movement at all.
The trade-off is direct. A small inner deadzone keeps slow, fine aiming responsive but lets more resting movement through. A large one hides more drift but removes the gentlest part of your input.
Inner, outer, radial, and axial deadzones
Deadzone labels are not perfectly standardised between games, so read the setting description before copying a number from one title to another.
Inner and outer deadzones
The inner deadzone starts at the neutral position and suppresses small movement. The outer deadzone sits near maximum travel and can make a game reach full output before the physical stick reaches the edge. GamePadTestLab recommends an inner deadzone from resting readings; it does not calculate a universal outer-deadzone setting.
Radial and axial shapes
A radial deadzone judges the stick by its distance from centre, producing a circular ignored area. An axial deadzone treats horizontal and vertical axes separately, which can make straight movement easier but may suppress small diagonal input. Games may also rescale the remaining travel after the deadzone is applied.
How a deadzone changes control feel
Lower is not automatically better. The useful value is the smallest setting that prevents unwanted movement without making fine control feel delayed or abrupt.
| Setting choice | Possible benefit | Possible cost |
|---|---|---|
| Smaller inner deadzone | More immediate fine movement | More sensor noise or drift may reach the game |
| Larger inner deadzone | Hides a larger resting offset | Small intentional movements are ignored |
| Larger outer deadzone | Full input is reached sooner | Less physical travel remains for high-end control |
Choose an inner deadzone from your own readings
Measure resting movement first, then add a small safety margin. The recommendation on the deadzone page uses the larger left/right 95th-percentile offset, multiplies it by 1.35, adds 0.01, rounds to the nearest 0.005, and clamps the result from 0.02 to 0.35.
That formula is a practical starting point for this site, not a universal setting. The best in-game value also depends on the game's deadzone shape, response curve, camera speed, and any platform-level processing.
- Run the timed stick drift test with the controller untouched.
- Open the deadzone tool and compare the recommendation with the live stick position.
- Start with the recommended value in the game, if that game exposes a comparable inner-deadzone setting.
- Check that menus or the camera no longer move on their own.
- Reduce the value one step at a time until unwanted movement returns, then move back up one step.
- Repeat after moving and releasing the stick, because a worn stick may not return to the same centre every time.
How to spot a deadzone problem
A deadzone may be too small if a camera or cursor moves while the controller is untouched. It may be too large if the first part of deliberate stick travel does nothing and control begins with a noticeable jump.
A stick that reaches the edge in some directions but not others is a range or calibration issue rather than an inner-deadzone issue. Use the circularity and range test to inspect directional coverage before increasing the deadzone further.
Deadzone is not a repair
Raising the deadzone does not fix a stick. It only tells software to ignore part of the signal, which can be a reasonable workaround for a small stable offset.
Browser readings may already include firmware, driver, operating-system, or remapping adjustments. GamePadTestLab can show what the browser receives, but it cannot reveal every earlier processing step or guarantee that a game's implementation matches this visualiser.
Ready to check your own controller?
Open the deadzone tool