Controller Deadzone Test and Calibration Guide

Understand and calibrate your controller deadzone using live axis values. Learn how to match your deadzone setting to the specific game you are testing against.

Controller Deadzone Test and Calibration Guide

A deadzone is a circular region around a thumbstick's center position where software ignores small input values. The Web Gamepad API reports axes as analog values in the range -1.0 to 1.0, and the specification defines the standard stick layout as axis 0 for left-stick horizontal, axis 1 for left-stick vertical, axis 2 for right-stick horizontal, and axis 3 for right-stick vertical.1 MDN describes Gamepad.axes as the array of axis controls present on the device, such as analog thumbsticks, with each entry stored as a floating-point value in that same range.2 In practice, a fresh stick may still sit a few thousandths away from zero because of calibration, noise, or surface friction, so a small ignored region keeps tiny resting values from becoming constant movement.3

The deadzone threshold is the radius of the ignored zone. A deadzone of 0.05 means the game treats any stick reading with a magnitude below 0.05 as zero. Smaller thresholds feel more responsive but allow more hardware noise through. Larger ones filter noise effectively while reducing how precisely your intentional small movements register near the center. Microsoft's XInput guidance normalizes the remaining range after the deadzone is enforced and notes that driving games may transform the result to preserve lower-range precision, which is why matching the game's value matters more than guessing a universal threshold.3

What to look for

  • -0.14

Opens the Gamepad Tester with this page's reference values shown at the top of the tool.

Open in the tool →

Matching the tester to your game

Some games expose a numeric deadzone value in controller options; others hide it behind sliders, presets, or separate left and right stick settings. XInput's dead-zone guidance treats the threshold as the point where stick movement is considered valid, and its example checks the stick magnitude against a circular deadzone before normalizing the result.4

Copying the game setting into the tester

To calibrate for your specific game, note the deadzone value from the options menu and set the slider on this tester to the same number. Consequently, any drift you see outside the ring on this page will also register as real movement in that game. Matching the deadzone here to the game's value gives you a direct comparison of what the game actually receives from your hardware.

After you set the slider, press a face button and move each stick through its range so you can confirm the tester is reading the controller before interpreting the ring. A deadzone comparison only means something once the browser is receiving live axis values, because a controller that has not registered will leave the ring empty and make the calibration look cleaner than it really is.

What the deadzone ring shows

The colored ring drawn around the center of each stick canvas provides a direct visual representation of the deadzone threshold you have currently set with the slider control. Use the slider below the left stick canvas to adjust the ring size up or down, and the ring will dynamically resize to match your chosen threshold value in real time. Your practical goal is to find the smallest deadzone value where the resting dot stays reliably inside the ring at all times without ever drifting past the boundary edge during a calm, undisturbed measurement period.

When the ring cannot hide drift

If the resting dot consistently wanders outside the ring even when you push the slider to its maximum position, your stick has accumulated hardware drift that exceeds what any reasonable deadzone setting can reliably mask during normal gameplay. Increasing the deadzone further would hide the drift temporarily while the underlying hardware continues to degrade, at the cost of noticeably reduced precision for small intentional movements. Testing raw axis values here reveals what the hardware actually produces before any game applies its own software-level filtering or deadzone compensation.1 At the lower platform layer, XInput exposes each thumbstick axis as a signed value centered at 0, with negative and positive values describing the direction of offset and a configurable deadzone constant available to filter out that small resting input.4

Per-game deadzone settings and where to find them

Many games with dedicated controller options show a deadzone setting, but the location and label vary across titles. In first-person shooters the setting often appears under a label such as Left Stick Deadzone or Inner Deadzone within the controller section of Options. Some games show a single value for all sticks; others let you configure the left and right sticks independently. Some racing games split steering and throttle input, since those controls ask for different kinds of precision.

To use this tester for calibration, read the deadzone value from the game's options screen first, then set the slider on the stick canvas here to the same number, the match your game's deadzone to the tester ring step that shows what the game actually receives. Any resting axis value that falls outside the ring at that slider position will also register as movement in the game. If the dot sits cleanly inside the ring, your hardware drift is within what the game's deadzone can absorb.

Deadzones in racing games versus first-person shooters

Racing titles and first-person shooters usually ask you to balance different priorities. Racing games reward small steering corrections, so a lower deadzone can make the wheel feel more direct. Shooters often prioritize stable aim, so the aiming stick may use a wider ignored region than the movement stick. Steam Input exposes controls such as Dead Zone Shape and Output Anti-Deadzone, and community configuration guides use anti-deadzone to recover precision after a large in-game deadzone.5 The safest calibration path is still the same: copy the game's visible value here, watch the resting dot, and adjust only if the game exposes a setting you can change.

When to use this

Use this when you want to find the minimum viable deadzone setting for a specific game, or to confirm whether your controller's drift falls inside or outside the deadzone that game applies.

Examples

Matching tester deadzone to a specific game setting

Before
Game deadzone: 0.10 / Stick reading at rest: 0.07
After
Slider set to 0.10, matching the game's deadzone

The game should filter out the drift at its current level. Retest if the resting value grows beyond the ring.

Drift that exceeds even a generous deadzone

Before
Axis 1 (LY): persistent -0.14 at rest / deadzone slider at 0.20
After
Drift still partially outside ring at maximum slider position

A stable -0.14 reading is hardware drift. A larger deadzone can mask it, but movement precision in every game will suffer at that setting.

New controller confirming factory center accuracy

Before
Axis 0 (LX): 0.00391 / Axis 1 (LY): 0.00195
After
Both readings remain inside a 0.01 deadzone ring

Small resting values can be normal noise. Watch whether the dot stays inside the ring over multiple readings.

Sources
  1. 1.

    W3C, "Gamepad," w3.org, July 2025. https://www.w3.org/TR/gamepad/

  2. 2.

    MDN, "Gamepad: axes property," developer.mozilla.org, December 2025. https://developer.mozilla.org/en-US/docs/Web/API/Gamepad/axes

  3. 3.

    Microsoft, "Getting Started With XInput in Windows applications," learn.microsoft.com, July 2025. https://learn.microsoft.com/en-us/windows/win32/xinput/getting-started-with-xinput

  4. 4.

    Microsoft, "XINPUT_GAMEPAD structure (xinput.h)," learn.microsoft.com, October 2023. https://learn.microsoft.com/en-us/windows/win32/api/xinput/ns-xinput-xinput_gamepad

  5. 5.

    Valve Software, "Deadzone Configurations: Add Shape Selection for Output Anti Deadzone," GitHub, accessed June 2026. https://github.com/ValveSoftware/steam-for-linux/issues/6290

FAQ

Use the value shown in the game's controller options. CapyToolkit lets you copy that value into the tester so the ring matches the game threshold. If the game only gives you a slider, start near the current setting and move it down until the resting dot stays inside the ring, then move it back up slightly if small intentional movements feel unreliable.

Possibly. A deadzone that is too large makes the stick feel unresponsive because you must push it further before any movement registers. If your stick reads near 0.0 at rest and the game feels slow or imprecise, try reducing the in-game deadzone setting.

The deadzone ring is a visualization only. CapyToolkit does not apply a real software deadzone to the reported values. The canvas always shows raw hardware output. The ring shows whether those values fall inside or outside a hypothetical threshold at the chosen level.

It hides it. The hardware is still sending a non-zero value. The game ignores it because it falls within the deadzone. Increasing the deadzone to mask drift reduces the effective precision of the stick for intentional inputs throughout its entire range.

Inner deadzone is the region near center where small inputs are ignored, which is what this tester and most gaming guides refer to. Outer deadzone, also called anti-deadzone or maximum input zone, is a boundary near the edge where the axis is clamped to 1.0 before full physical travel. Not every game exposes both settings.

Additional resources

Guides

PlayStation Controller Test: DualShock 4 and DualSense Test a DualShock 4 or DualSense for analog stick drift, read the trigger axes, and document the result for a repair, with the model-specific notes for both PlayStation controllers in one place. Nintendo Controller Test: Switch Pro Controller and Joy-Con Drift Test a Nintendo Switch Pro Controller or Joy-Con for stick drift, read the trigger axes, and document the result for Nintendo's repair process, with the per-model notes for both controllers in one place. Third-Party Controller Test: 8BitDo, Logitech, PowerA and Razer Test an 8BitDo, Logitech, PowerA or Razer controller for stick drift, trigger range and button response, and see how each third-party pad presents itself to the browser Gamepad API. Xbox Controller Drift Test and Per-Model Notes Test an Xbox controller for analog stick drift across the Xbox 360, Xbox One, Xbox Series X/S and Elite Series 2, and see what each generation changes about the same test. Controller Deadzone Test and Calibration Guide Understand and calibrate your controller deadzone using live axis values. Learn how to match your deadzone setting to the specific game you are testing against. Controller Not Detected in Browser Fix a controller that is not showing up in your browser. Step-by-step troubleshooting for USB and Bluetooth gamepads on Windows, Mac, and Linux. Controller Trigger Test: Diagnosing LT and RT Issues Test your controller triggers in your browser. Diagnose triggers that do not register, do not reach full range, or do not return to zero after release. Flight Stick and HOTAS Test - Joystick Axis Calibration Guide Test your flight stick, joystick, or HOTAS in your browser using the Gamepad API. Read axis values, hat switch position, and throttle range without any software install.