How the drift sample works
The tool counts down, then samples idle stick input for several seconds while you keep the controller still. Larger offsets and unstable noise can indicate drift symptoms, but the same controller may report different values by browser, connection, driver, and battery state.
Use the suggested deadzone as a starting point. Fast competitive shooters, racing games, emulators, and accessibility setups often need different deadzone choices.
- Looks centered: small average offset and low noise.
- Mild drift: visible idle offset that may be hidden by a modest deadzone.
- Noticeable drift: stronger offset likely to affect sensitive games.
- Severe drift: large or unstable idle movement that may need cleaning, settings changes, or repair.
Local report workflow
After checking buttons, sticks, triggers, drift, vibration, and microphone behavior, generate a local text or JSON report. The report is useful before changing game settings, buying a used controller, or asking a repair shop to verify symptoms. For Stick Drift Test, treat that limit as part of stick drift test guidance rather than as a separate verdict.
The report is generated in your browser and includes a reminder that browser diagnostics are not an official repair certificate. On this Stick Drift Test page, compare that note with the live module that matches idle stick offset, peak drift, stability, direction bias, and suggested deadzone.
Browser and hardware limits
Gamepad API support, haptic feedback, MediaRecorder, and WebHID are exposed differently across Chrome, Edge, Firefox, Safari, Linux, mobile browsers, USB, Bluetooth, and third-party drivers. For Stick Drift Test, treat that limit as part of stick drift test guidance rather than as a separate verdict.
A missing feature in the browser does not prove that the controller is damaged. Use the live readings as diagnostic hints and compare results across connection methods when possible. On this Stick Drift Test page, compare that note with the live module that matches idle stick offset, peak drift, stability, direction bias, and suggested deadzone.
Stick drift test evidence
A stick drift test should be quiet and repeatable. Place the controller on a table, release both sticks, wait for the sample to finish, and avoid touching the shell while the stick drift test is running. A single spike can happen when a pad is bumped, but a stable offset in the same direction deserves closer attention.
Use the stick drift test together with real play symptoms. If the stick drift test reports movement but the game feels stable, the game may already apply a larger deadzone. If the stick drift test looks clean while a game drifts, inspect that game's sensitivity, aim assist, camera acceleration, and input profile.
- Run the stick drift test twice before drawing a conclusion.
- Compare left and right stick drift test results side by side.
- Use the deadzone page only after the stick drift test pattern is clear.