Joystick Test

Introduction

The DeviceHub Joystick Test is a free online analog stick visualizer that plots left and right stick axes as the browser Gamepad API reports them, centering, circular range, and live deflection, without installing Xbox Accessories, DualShock calibration panels, or Steam Input overlays. Competitive FPS players hunting micro-drift, racing sim fans checking spring return, arcade stick owners validating spare thumb modules, and support techs comparing two pads on one PC use this page to see browser-visible axis values in seconds. Open the tool, wake the controller with a button press, leave the sticks alone to judge resting position, then sweep full circles while a crosshair or plot tracks normalized X/Y. Drift that slowly walks the camera in games often appears here as a resting offset away from zero even when you are not touching the module. DeviceHub states limits clearly: values are what the OS and browser expose after their own deadzones and remappers, not a laboratory measurement of potentiometer voltage or Hall-effect sensor millivolts. Mapping may differ for non-standard pads, so a “left stick” plot might follow a different axis pair than the silkscreen suggests until you confirm indices in Controller Mapping Test. Because the check runs entirely in-tab, managed school and corporate images can still diagnose pads without admin rights. Parents noticing a character that walks alone in a kids’ title get visual proof before buying a new controller. Repair shops documenting worn modules photograph the off-center rest as evidence for warranty tickets.

What this tool does

The page reads Gamepad.axes for the active controller, maps typical left and right stick pairs onto visual pads, and updates on each animation frame or poll tick. You see resting position, cardinal extremes, and whether circular travel looks clipped, egg-shaped, or asymmetric, common signs of wear or firmware limits. Numeric readouts help you narrate “axis 0 reads 0.12 at rest” on a call. Guidance explains that many titles apply additional deadzones on top of what you see here. Reset clears peak markers after you release the sticks. The tool does not rewrite OS calibration databases or flash stick modules; for structured rest and extreme capture use Controller Calibration Test, for button presence use Gamepad Test, and for LT/RT use Trigger Test. Dual-stick fight pads that expose only digital directions may show flat axes, that absence is informative. Some browsers invert an axis relative to another engine; document browser name with your screenshots. Wireless interference can stutter the plot without true mechanical drift, retest wired when the path looks noisy. The visualization is a live mirror of normalized floats, not a claim that your pad meets a console certification circle.

When to use it

Run Joystick Test whenever camera creep, unintended strafe, or weak diagonal movement appears in games, after cleaning around stick housings, after replacing thumbcap kits, and when comparing Hall-effect upgrades against stock pots on the same machine. Prefer Calibration Test when you need recorded rest and extreme numbers for a ticket, Mapping Test when left/right plots disagree with physical sticks, and Gamepad Test when digital buttons are the real failure. Esports coaches screening loaner pads before a LAN should watch resting origin for thirty seconds, slow drift often shows only after a pause. Sim racers validating a dual-analog pad for menu navigation (separate from their wheel) confirm both sticks return cleanly. After Bluetooth reconnects, re-check centering; some stacks report stale non-zero samples until the next full deflection. Use it after kids jam sticks with debris, after a drop that bent a module, and after OS “game controller” calibration wizards that may have shifted software offsets. Streamers swapping between Xbox and PlayStation pads on one PC can show chat that drift follows the hardware, not the game build.

How it works

Standard Gamepad layout commonly places left stick on axes 0 and 1 and right stick on axes 2 and 3, each roughly in the −1…+1 range, though browsers and OSes may clamp or apply deadzones before the page reads values. DeviceHub plots those floats; it cannot see underneath the HID stack. Controllers without standard mapping may put sticks on other indices or mix triggers into the axes array, Mapping Test clarifies that topology. Polling typically follows requestAnimationFrame aligned with getGamepads() snapshots; timestamps on the Gamepad object are browser clocks, not USB hardware poll proofs. No permission prompt is required. Safari/iOS and some Android browsers may omit precise axes or entire gamepad support, treat mobile gaps as platform limits. Remappers such as Steam Input can substitute a virtual Standard pad with different resting noise characteristics than the physical hardware. DualSense edge and Xbox Elite profiles that alter deadzones in companion apps change what the browser sees even when pots are healthy. DeviceHub never uploads axis streams. Focus loss does not usually stop getGamepads() while the tab is visible, but background throttling can reduce update smoothness, keep the tab foregrounded for clean plots. Compare two browsers only after the same wake gesture and connection mode so you are not mixing Bluetooth jitter with engine differences.

Step-by-step instructions

1. Open Joystick Test over HTTPS, connect the pad, and press a button so the Gamepad API exposes axes; select the correct device if multiple controllers are listed.
2. Do not touch the sticks for several seconds and confirm both markers sit near center; any steady offset is the browser-visible rest drift you should document.
3. Move the left stick through slow full circles and cardinal extremes, watching whether the plot reaches the rim evenly or clips early on one side.
4. Repeat for the right stick, then lightly release from full deflection to judge spring return and overshoot that might feel like bounce in menus.
5. If axes look swapped, inverted, or missing, open Controller Mapping Test and Controller Calibration Test to capture raw indices and numeric rest/extreme values for your notes.
6. Close the tab when finished, no special permission revoke is needed because gamepad reading never requested a Privileged Permissions API grant.

Common problems

Off-center rest is frequently genuine drift or an OS/software deadzone offset, not a DeviceHub bug. Egg-shaped travel can mean worn pots, debris, or firmware circularity limits. Axes stuck at zero may indicate a digital-only stick, a wrong Gamepad selected, or a remapper presenting empty slots. Inverted Y on one browser but not another is a known stack quirk, record both. Bluetooth latency makes plots look stepped; wired USB is cleaner for mechanical conclusions. Flight sticks and HOTAS units often need Mapping Test because they are not Standard Gamepads. If Calibration Test shows large rest values while this plot looks centered, you may be looking at different axis pairs, reconcile indices first. Kids’ sticky residue under the skirt causes intermittent jumps that vanish after careful cleaning, do not force liquids into the module. Elite back paddles do not appear on stick plots; use Gamepad Test for those. Remote desktop rarely forwards high-rate axes faithfully, test on the local machine for RMA evidence.

Privacy explanation

Analog axis samples stay in your browser session. DeviceHub does not upload stick traces, drift profiles, or controller identifiers to a server. No microphone or camera permission is requested. Closing the tab clears visualizations and peaks. Shared machines are fine for hardware checks when you only exercise sticks. Private windows help isolate Steam or vendor remappers that inject virtual pads. Screen recordings for warranty tickets should show the resting offset clearly without unrelated personal content beside the tester. Nothing continues sampling after you navigate away.