What deadzone actually does
Deadzone is a radius around an analog stick’s resting center within which input is intentionally ignored. Push the stick outside that radius and it registers normally; stay inside it and nothing happens, even if the stick is reporting a small nonzero value. It’s a filter applied on top of the raw signal a controller reports, not a property of the controller’s hardware.
Why it exists
An analog stick’s resting position is rarely a perfect, unchanging zero. Manufacturing tolerance, and — over time — the same mechanical wear that causes stick drift, mean the reported position at rest tends to sit slightly off-center and can drift around a little even when untouched. A deadzone exists to absorb that noise so it doesn’t translate into unwanted movement in a game.
The browser doesn’t apply one for you
The Gamepad API exposes each stick axis as a raw floating-point value with no deadzone shaping built in — that processing is left entirely to whatever reads the value afterward, whether that’s a game engine or the operating system (MDN, Using the Gamepad API). That’s useful to know if you’re testing in a browser: a small nonzero reading at rest here is normal and expected, not a sign anything is wrong — it’s exactly the noise a deadzone is designed to absorb further downstream.
How much deadzone is “normal”
There’s no single universal number, but a few concrete references give a sense of the typical range:
- Unity’s Input System ships with a default minimum stick deadzone of
0.125 (12.5%) and a default maximum of 0.925, applied
automatically to gamepad stick controls unless a developer overrides it
(Unity,
InputSettingsAPI docs). - Steam Deck’s built-in controller configuration defaults to a deadzone around 20% of the stick’s travel, adjustable per game in its Dead Zones settings (community configuration guide referencing Steam Deck’s default deadzone value).
Both sit in a similar range — roughly 5–20% of full stick travel — which is a reasonable starting point to test against on your own hardware rather than a value to copy blindly, since the right setting depends on how much noise your specific stick actually has at rest.
Too small vs. too large
A deadzone set too small lets through the same low-level noise it’s meant to filter, which can look and feel like drift even on a healthy stick. A deadzone set too large ignores genuine small, precise movements — noticeable in games that reward fine aiming or slow camera pans, where the stick can feel like it has a “dead” center that won’t respond until pushed surprisingly far.
How to measure the right deadzone for your controller
The Controller Deadzone Test shows your stick’s raw position live and lets you find the smallest radius that reliably excludes rest-state noise without cutting into deliberate small movements. If the resting value wanders more than a small amount even after you widen the deadzone, that’s worth checking with the Stick Drift Test — a deadzone can mask minor drift, but it isn’t a substitute for diagnosing it.