Joystick TesterEvery axis. Every button.
Raw and live.
For flight sticks, throttles, wheels, arcade sticks and any gamepad. Connect it, press a button, and watch the raw values the browser receives.
Checking browser…
One moment.
Controller input is processed locally in your browser and is not uploaded.
max 0%
X +0.000
Y +0.000
X +0.000
Y +0.000
max 0%
Buttons tested
0/ —
Waiting for a controller.
Stick drift
Let go of both sticks and do not touch the controller for 3 seconds.
Left stick
0.000, 0.000Connect a controller to measure.
Right stick
0.000, 0.000Connect a controller to measure.
The dead zone slider only changes this display; raw values are always shown. Controller hardware, browser mapping and calibration can all affect readings, so treat results as a measurement, not a diagnosis. Ratings: under 2% excellent, 2–5% minor, 5–10% moderate, 10%+ significant.
Stick range
Roll each stick slowly around its outer edge.
Left stick
- Left0%
- Right0%
- Up0%
- Down0%
Right stick
- Left0%
- Right0%
- Up0%
- Down0%
A direction counts as reached at 90% travel. Many sticks read slightly past 100% on diagonals; a stick that stops well short in one direction may be worn or obstructed.
Controller check
Waiting for a controller
Results appear here as you test: buttons, both sticks, triggers and vibration.
This summary only reports what the browser observed. It can't detect every hardware fault, and readings depend on the browser, driver and connection.
Vibration
Connect a controller to check vibration support.
Raw input
No controller connected.
How axis visualization works
The browser reports every analog input as an axis with a value from −1 to +1, and every switch as a button with a value from 0 to 1. The tester shows each axis as a centered bar and each button by number, updating on every frame.
Axes are also grouped in pairs (0 · 1, 2 · 3) and plotted on 2D targets, since devices usually report a stick's X and Y back to back. For a flight stick, axes 0 and 1 are typically roll and pitch. Twist, throttle and sliders appear as further axes.
The Raw input panel is open by default here. It lists the device ID, mapping, timestamp and four-decimal values for every input.
Standard vs. non-standard mapping
Browsers recognize common gamepads and rearrange their inputs into a standard layout, where button 0 is always the bottom face button and axes 0–3 are always the two sticks. That's what allows this site to draw a controller diagram with correct labels.
Most joysticks, HOTAS setups, wheels and many older or unusual controllers don't get that treatment. The browser reports them with an empty mapping and passes the inputs through in whatever order the device describes them. Button 3 on one device may be a trigger; on another it may be a hat direction.
Tips for flight sticks and other devices
- Hat switches are often reported as a single axis that jumps between fixed values, and may rest outside the −1 to +1 range (commonly around 1.29 in Chromium browsers). That's the device's encoding, not a fault.
- Throttles usually sweep from −1 to +1 rather than 0 to 1, so the halfway point reads 0.
- Axis pairs in the generic view are a guess. If a 2D target moves oddly, check the individual axis bars instead.
- Drift on non-standard devices: the drift test measures the first two axis pairs. Only trust it for pairs that are actually a stick.
- Multiple devices: if you have a separate stick and throttle, each appears as its own controller. Use the selector in the status box to switch between them.
Frequently asked questions
Does this work with HOTAS and flight sticks?
Yes, as long as the operating system sees the device as a game controller. Most USB HID joysticks work in Chrome, Edge and Firefox. Safari support is limited to controllers Apple's framework recognizes.
Why are my buttons numbered instead of named?
Your device doesn't use the browser's standard layout, so there's no reliable way to know what each button is called. Numbering them avoids showing wrong labels.
Some of my axes or buttons are missing. Why?
Browsers cap how many inputs they expose and may skip vendor-specific ones. Very large button counts, extra hats and mode switches on complex HOTAS setups sometimes don't come through.
Can I calibrate my joystick here?
No. The browser can only read input. Use your operating system's game controller settings or the manufacturer's software to calibrate, then come back to verify the result.