Every deadzone thread ends the same way: someone posts the values their favorite pro uses, everyone copies them, and half the copiers end up with either a camera that pans on its own or aim that feels like it wades through mud.
Both failures come from the same mistake: a deadzone is a measurement, not a preference. The right value depends on how much your stick moves when you are not touching it - and that is a number you can record in about 10 seconds.
I published the full guide (value tables, per-game settings locations, outer deadzone, Hall effect vs TMR) here:
Controller Deadzone Explained: Test Yours & Best Settings
This is the compact version.
What a deadzone actually is
Analog sticks report a position between -1 and +1 on each axis, and they are never perfectly quiet. Even a brand-new stick rests at something like 0.01-0.03 instead of exactly zero, because potentiometer sticks read position through a resistive wiper that always carries a little electrical noise.
A deadzone tells the game to treat everything inside a threshold as "not moving." Four terms cover almost every settings screen:
- Inner deadzone - the circle around center where input is ignored. This is the drift-masking control, and the one worth tuning.
- Outer deadzone - the rim threshold where the game reads "100% deflection." Tightening it helps a worn stick that never quite reaches full range.
- Axial vs radial - radial clips the stick vector by distance from center; axial clips each axis separately, which can snap subtle diagonals onto straight lines.
- Deadzone vs response curve - the deadzone decides when input starts counting; the curve decides how fast it ramps up after that. If aim feels wrong mid-travel rather than near center, tune the curve instead.
Measure it instead of guessing
The measurement takes a minute in any browser via the Gamepad API - no game restarts:
- Connect the controller (USB or Bluetooth), open the controller deadzone test, and press any button - browsers only expose a gamepad after a real input.
- Put the controller on a flat surface, take both thumbs off the sticks, and run the timed 10-second drift test. Recording resting magnitude over several seconds gives a stable verdict instead of a flickering live number.
- Read the verdict. At or below 0.05 at rest, the stick is healthy. Between 0.05 and 0.12 it reports mild drift and suggests the deadzone that would mask it - about 1.3x what it recorded. Above 0.12 it still suggests a value, but flags the stick for repair.
- Preview the suggestion with the on-page slider: the resting dot should sit inside the deadzone ring and the readout should hold at zero. That is your number.
- Write it down as a percentage (0.07 = 7%) and carry it into your game's deadzone slider.
The slider in the tester is a sandbox applied to the tool's own readouts - it does not change your controller, OS, or any game. The value that affects gameplay lives in each game's settings.
What is a good value?
| Situation | Starting value | Why |
|---|---|---|
| Healthy stick (rest <= 0.05) | ~0.05 (5%) | Swallows sensor noise without delaying real input |
| Mild drift (0.05-0.12 at rest) | The drift test's suggestion | ~1.3x resting drift - silences it with the least responsiveness lost |
| Heavy drift (above 0.12) | Suggested value, short-term only | Near 0.20+ fine aim goes mushy; the module is worn |
| Competitive shooters | Smallest value that stays silent at rest | Every extra percent delays when a micro-flick registers |
Two things people get wrong:
- A bigger deadzone does not add input lag. It is a distance threshold, not a delay - nothing is buffered. It can still feel slower because the stick must travel further before the game sees anything.
- A deadzone never fixes drift permanently. It masks the false input while the wear keeps progressing. A stick that needed 0.08 in spring may need 0.15 by autumn. If the suggestion keeps climbing month over month, it is time for a stick-module repair or a Hall-effect/TMR controller - contactless sticks rest near zero for years, which is why new enthusiast pads advertise "zero deadzone" at all.
Where the setting actually lives
There is no single deadzone switch. Consoles mostly leave it to each game; PC adds system-wide layers:
- Fortnite: Settings > Controller > Sensitivity (separate left/right stick percentages)
- CoD/Warzone: Settings > Controller > Gameplay (min slider = the drift-masking one)
- Rocket League: Settings > Controls (numeric, default 0.50, plus a separate dodge deadzone)
- Steam (any PC game): Steam Input per-game controller layout - custom inner and outer deadzone per stick
- PS5: only the DualSense Edge exposes deadzones (custom profiles); the standard DualSense has no console-wide setting
- Switch: no deadzone setting - but stick recalibration re-centers the stick, which often removes the false input directly
One warning: layers stack. If Steam Input applies a deadzone and the game applies its own on top, the pad feels far number than either value suggests. Pick one layer to own the deadzone - usually the game's slider - and zero the rest.
The forgotten half: outer deadzone
Worn sticks also fail at the rim: left/right reach full speed but diagonals never quite hit 100%, so sprint stutters only on angled input. You can see this with a circularity sweep in the same browser gamepad tester - hold full deflection and rotate a complete circle. 0-5% error is excellent (typical of Hall-effect sticks), 8-15% is normal for stock DualSense/Xbox pads, 15-20%+ points at a worn module. If corners fall short, lower the game's outer deadzone so full output triggers before the physical rim.
TL;DR
- Hands off the sticks, run a 10-second drift test in the browser.
- Healthy stick: keep ~0.05. Drifting stick: set just above your measured resting drift (~1.3x).
- Enter that number in the game (or Steam Input) - one layer only.
- If the number keeps growing, stop tuning and fix the hardware - the stick drift guide covers cleaning, recalibration, and repair-vs-RMA.
Full version with the per-game table, anti-deadzone, and the Hall effect/TMR explanation: Controller Deadzone Explained: Test Yours & Best Settings
Top comments (0)