How to Calibrate a Controller on Windows 11

Windows 11 hides controller calibration well enough that most people never find it. The tool is still there, unchanged in appearance since roughly Windows 98, sitting behind a command most users have never typed.

It also does not do what a lot of people expect. Calibration corrects where the system thinks your stick's centre and limits are. It does not repair worn hardware, it does not remove noise, and running it on the wrong kind of device makes things worse rather than better.

Here is how to do it properly, which of the four available layers to use for your particular controller, and how to tell when calibration is not the answer.

What calibration actually does

Your controller reports a raw value for each axis. Calibration builds a mapping between those raw values and what the system reports to games. It records three things: where centre is, how far the axis travels in each direction, and how to scale everything in between.

That means calibration can fix:

• A resting position that reads slightly off centre
• An axis that does not reach 100 percent at full deflection
• An axis that reaches 100 percent well before the physical stop
• Asymmetry, where the stick reaches further one way than the other

It cannot fix:

• A worn potentiometer track, which is what causes most stick drift
• Electrical noise, which makes a value wobble rather than sit at an offset
• The shape of the physical gate, which is what causes diagonals to fall short

Knowing the difference saves an afternoon. If your problem is wear or noise, no amount of calibrating will touch it.

Step 1: measure before you change anything

Run a stick drift test with the controller flat on a table and your hands off. Write down the resting values for both sticks.

You need this number for two reasons. It tells you whether calibration is even the right tool, since a wandering value points at noise rather than an offset. And it gives you a baseline so you can tell afterwards whether anything actually improved.

Close Steam and any other input software first. Steam Input and tools like DS4Windows apply their own processing, so testing with them running measures the software rather than your hardware.

Step 2: the built-in Windows tool

Press Windows + R, typejoy.cpl, and press Enter. You can also search the Start menu for "Set up USB game controllers", which opens the same panel.

Select your controller and click Properties. There are two tabs: Test, which shows live axis and button state, and Settings, which contains the Calibrate button.

The wizard walks you through:

1. Centre position. Leave the stick alone and click Next. Do not touch it, and do not rest a finger on it "to keep it steady"
2. Axis range. Move the stick in full circles, reaching the outer gate in every direction, several times
3. Z axis and rudder, if your device has them. Sweep each through its full travel
4. Point of view hat, if present. Move through all eight positions

Then click Finish and return to the Test tab to check the result. Centre should read dead centre and full deflection should reach the edges.

The most common mistake is holding the stick during the centring step. The wizard records whatever it sees as centre, so a stick held slightly off-centre gets baked in as the new zero point, and you have created the exact problem you were trying to solve.

Our joystick calibration tool shows you whether the calibration took, which is worth checking rather than assuming.

The catch with Xbox controllers

Here is the part most guides skip.

Windows 11 handles Xbox controllers through XInput, which applies its own internal processing before anything reaches joy.cpl. The calibration wizard may open, and it may appear to complete, but the effect on an XInput device is limited or nonexistent because XInput is not reading the registry calibration that DirectInput devices use.

If you have a drifting Xbox pad, joy.cpl is generally not your tool. Use Steam's calibration instead, or a third-party layer.

DirectInput devices are where joy.cpl earns its keep: flight sticks, older gamepads, arcade sticks, generic USB controllers, and most third-party pads not pretending to be Xbox controllers.

Step 3: Steam's calibration, which is better for most people

Steam has its own calibration, and it is the more useful option for modern controllers.

Steam, Settings, Controller, select your device, then Calibration and Advanced Settings. You get stick calibration, gyro calibration on supported devices, and per-device deadzone controls.

Three reasons this is generally the better layer:

It works for XInput devices, where joy.cpl does not. It stores the correction per device rather than system-wide, so it will not surprise you later in unrelated software. And it applies to Steam games automatically, including non-Steam titles added to your library as shortcuts.

The trade-off is that it only applies where Steam is involved. A game launched outside Steam gets none of it.

Step 4: manufacturer and third-party software

The fourth layer, and for some hardware the only correct one.

Xbox Accessories app. No stick calibration, but it does offer stick sensitivity curves and trigger ranges, which solve some of the same problems from a different direction.

DS4Windows and reWASD. Both include stick calibration for PlayStation and third-party pads, along with deadzone control. Useful when you need the correction to apply outside Steam.

Flight stick software. VKB and VIRPIL calibrate in firmware, which means the correction lives on the device and travels with it. For these, do not use joy.cpl at all. Layering Windows calibration on top of a correct firmware calibration produces axes that behave oddly at the extremes.

Racing wheel software. G HUB, Thrustmaster Control Panel, the Fanatec driver, and Moza Pit House all handle their own calibration. Force feedback wheels calibrate themselves during the startup sweep, and running the joy.cpl wizard on one writes registry data that fights the wheel's firmware. Do not do it.

The principle across all of these: calibrate at the lowest layer that owns the data. If the device calibrates itself in firmware, leave the operating system out of it. Our hardware calibration guide covers this across device types, and the gamepad calibration guide goes deeper on gamepads specifically.

Resetting a bad calibration

If you have made things worse, or inherited a machine with strange calibration data, you can clear it.

Windows stores DirectInput calibration in the registry at:

HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM

Each device has a subkey. Deleting the subkey for your controller and reconnecting the device forces Windows back to defaults. Export the key first so you can undo it.

This is worth knowing because a corrupted calibration produces symptoms that look exactly like hardware failure: axes that saturate early, centres that sit off, ranges that behave asymmetrically. Clearing it is the first thing to try when a controller starts behaving strangely on one PC but works fine on another.

For a guided version of this and the other common calibration faults, our controller calibration fix page walks through the process without the registry editor.

Step 5: Verify

Do not assume it worked. Re-run the same test you started with.

Check that the resting value is closer to zero than before, that each axis reaches full deflection at the physical stop, and that the two sticks behave consistently with each other.

If nothing changed, calibration was not the answer, and you are looking at wear or noise rather than a mapping problem.

When calibration will not help

Four situations where you should stop calibrating and do something else.

The value wobbles rather than sitting off centre. That is electrical noise, not a calibration offset. Calibration has nothing to correct.

Drift returns within hours. A worn track will keep moving away from wherever you calibrate it. Repeated calibration on a failing stick is a treadmill.

Diagonals fall short while cardinals are fine. That is the shape of the physical gate, which calibration cannot change.

It works on one PC and not another. Look at software layers and USB before the controller. Something on the problem machine is intercepting or interfering.

A short decision guide

• Xbox controller: Steam calibration. Skip joy.cpl
• DualSense or DualShock 4: Steam calibration, or DS4Windows if you need it outside Steam
• Switch Pro Controller: Steam calibration
• Flight stick: the manufacturer's own tool, in firmware. Not joy.cpl
• Racing wheel: the manufacturer's control panel. Never joy.cpl
• Generic or older USB gamepad: joy.cpl is the right tool
• Arcade stick: usually digital, so nothing to calibrate

Get the layer right, and calibration takes two minutes. Get it wrong, and you spend an evening making a working controller worse.