Stick drift signals this page checks
This page isolates joystick drift instead of mixing it with every controller feature. It watches raw Gamepad API axes while the sticks are untouched, then compares those values with the selected dead zone.
Controllers
Stick drift test for left and right stick center offset, X/Y axis drift, maximum offset, return-to-center stability and deadzone behavior.
Idle offset
X / Y
Deadzone slider
0.02 - 0.35
Axis duration
Local
This page isolates joystick drift instead of mixing it with every controller feature. It watches raw Gamepad API axes while the sticks are untouched, then compares those values with the selected dead zone.
Use it when a character moves without input, a camera pans by itself, aiming feels uneven, or a controller behaves differently over USB and Bluetooth.
Record the controller model, connection mode, browser, dead-zone setting, resting X/Y values for each stick, and whether the same movement appears in a game or system calibration panel.
Connect a controller, then press a button or move a stick.
Connect by USB or Bluetooth, keep this tab visible, then press any controller button. Some browsers do not reveal an already connected controller until the first interaction.
A compact view of the current test state and the strongest signal detected so far.
Current controller
-
Controllers
0
Active buttons
0
Maximum axis offset
0.000
Press any controller button so the browser can expose the device.
1. Connect the controller by USB or Bluetooth and keep the tab focused. 2. Press one button so the browser exposes the controller. 3. Release both sticks and leave the controller on a flat surface for several seconds. 4. Adjust the dead-zone slider to match the game or calibration value you normally use. 5. Move each stick slowly to the edge, release it, and watch whether the axis returns close to zero. 6. Compare left stick X/Y and right stick X/Y separately before deciding that the whole controller has drift.
A short spike during release is not enough evidence of drift. Stronger evidence is a repeated resting value outside the selected dead zone, especially when it stays there for more than two seconds without any button press. One axis drifting usually points to the stick mechanism, calibration, debris, or wear on that side. If the drift disappears in another browser or connection mode, the next step is software, driver, or profile isolation rather than hardware replacement.
The page reads controller axis values locally in the browser. It does not upload raw controller input, game profiles, account data, calibration files, or gameplay activity.
Use it when a character moves without input, a camera pans by itself, aiming feels uneven, or a controller behaves differently over USB and Bluetooth.
The test highlights raw axis values, processed dead-zone output, maximum offset, time outside the dead zone, left/right stick separation, and a resettable calibration snapshot for repeat checks.
1. Connect the controller by USB or Bluetooth and keep the tab focused. 2. Press one button so the browser exposes the controller. 3. Release both sticks and leave the controller on a flat surface for several seconds. 4. Adjust the dead-zone slider to match the game or calibration value you normally use. 5. Move each stick slowly to the edge, release it, and watch whether the axis returns close to zero. 6. Compare left stick X/Y and right stick X/Y separately before deciding that the whole controller has drift.
Match what you see with the page records first, then decide whether the next check is settings, connection, drivers, or the device itself.
Release the sticks and watch whether X/Y axes stay away from center.
Record the idle value, then compare what happens after increasing deadzone.
Check each direction's maximum offset and return-to-center position.
One-direction drift points more to wear, dust, or calibration.
Start with a small deadzone and increase it step by step.
If a large deadzone is required, consider cleaning, calibration, or repair.
Compare idle values in wired and wireless modes.
Wireless-only jumps point first to battery, interference, or receiver position.
Gamepad API support varies by browser, operating system, controller mode, and driver. The page can show browser-visible drift, but it cannot recalibrate firmware or inspect internal stick sensors.
The page reads controller axis values locally in the browser. It does not upload raw controller input, game profiles, account data, calibration files, or gameplay activity.
Still narrowing it down? Open the next page that matches the symptom you can actually see.
Troubleshooting Center
Start with the symptom
Start here
Gamepad test for connection status, buttons, D-pad, stick axes, trigger values, mapping type and browser Gamepad API detection.
Controller trigger test for LT/RT or L2/R2 minimum value, maximum value, return-to-zero state, left/right range mismatch and analog mapping.
Gamepad button test for face buttons, D-pad, shoulder buttons, menu buttons, stick clicks, press counts, release events and possible stuck buttons.