Quick Answer
Plug in your controller or pair it by Bluetooth, open this page and press any button: browsers only show a controller after a button press. Every button lights up green as you press it, triggers fill up to show how far they are pressed, and the two circles show where each stick is. Let the sticks rest for a few seconds to check for drift, and press Test vibration to check the rumble motors.
Embed this calculator
Adjust the size if needed, then copy the code below into your page or blog. The calculator will load in an iframe and stay updated automatically.
Table of Contents
- Controller Tester
- Quick Answer
- Related Calculators
- How This Controller Tester Works
- How to Use the Controller Tester
- How the Drift Check Works
- Key Terms
- Worked Example
- Real-Life Examples
- Browser Tester vs Built-in Calibration
- Standard Button Layout
- Fixing Common Controller Problems
- Common Mistakes to Avoid
- Frequently Asked Questions
- References & Sources
How This Controller Tester Works
A controller that misses presses, drifts on its own or has a sticky trigger can ruin a game. This tester shows exactly what your controller sends to the computer, live, so you can tell if a problem is in the controller or in the game.
It works with most USB and Bluetooth gamepads on Windows, Mac, Linux and Android, including common console-style controllers and generic PC pads.
What it shows:
- Buttons: each one lights up when pressed.
- Triggers: how far each analog trigger is pressed, from 0 to 100%.
- Sticks: the exact X and Y position of both sticks, from −1 to +1.
- Drift check: how far each stick moves while you are not touching it.
- Vibration: a short rumble, where the browser supports it.
- Several controllers at once.
How to Use the Controller Tester
- Connect your controller by USB or Bluetooth.
- Press any button so the browser can see it.
- Press every button and pull both triggers; each should light up.
- Move both sticks in full circles, then let go for a few seconds.
- Check the drift reading, then press Test vibration.
How the Drift Check Works
- Stick position: each stick reports X and Y from −1 to +1. At rest, both should be close to 0.
- Distance from center: √(X² + Y²). For example, X = 0.06 and Y = 0.08 gives √(0.0036 + 0.0064) = 0.10, or 10%.
- At rest only: the check only counts moments when no button is pressed and the stick is near the center, so normal use does not count as drift.
- Warning level: if the largest resting distance is above your chosen level (5%, 10% or 15%), the results say possible drift.
Many games ignore small stick movements with a dead zone, often around 10% or more, so a small reading below that usually causes no problem in play.
Key Terms
- Stick drift: a stick that reports movement when nobody is touching it.
- Dead zone: a small area around the center that games ignore.
- Axis: one direction of a stick, such as left to right, from −1 to +1.
- Standard mapping: the common button numbering browsers use for most gamepads.
Worked Example
- You connect a controller and leave both sticks alone for 10 seconds.
- The left stick rests at X 0.02, Y −0.03: √(0.0004 + 0.0009) ≈ 0.036, or 3.6%. That is fine.
- The right stick creeps to X 0.15, Y 0.04: √(0.0225 + 0.0016) ≈ 0.155, or 15.5%. With the Normal (10%) level, the results show possible drift.
- In games, the camera may slowly turn on its own. Raising the in-game dead zone can hide it, but the stick may need cleaning or replacing.
Real-Life Examples
- Before buying a used controller: check all 17 standard buttons and both sticks in under a minute.
- Stick drift: a right stick resting at 15.5% from center explains a camera that turns by itself.
- New PC setup: confirm Windows or macOS sees the controller before opening a game.
- Trigger check: a trigger that only reaches 80% may not fully accelerate in racing games.
Browser Tester vs Built-in Calibration
- This tester: no install, works for any controller the browser sees, quick live view.
- System calibration tools: can recalibrate sticks and triggers, but differ by system and controller.
- Best use: test here first to find the problem, then calibrate or adjust the game’s dead zone.
Standard Button Layout
| Number | Button | Number | Button |
|---|---|---|---|
| 0 | A / Cross | 8 | Back / Select |
| 1 | B / Circle | 9 | Start / Options |
| 2 | X / Square | 10, 11 | Stick presses |
| 3 | Y / Triangle | 12 to 15 | D-pad up, down, left, right |
| 4, 5 | Bumpers | 16 | Home |
| 6, 7 | Triggers |
Fixing Common Controller Problems
- Not detected: press a button after the page opens; try another USB cable or port, or pair it again.
- Stick drift: often caused by dirt or worn parts inside the stick. Recalibrating in your system settings or raising the game’s dead zone may help.
- Wrong button names: the controller uses a non-standard mapping; the button numbers are still correct.
- Sticky button: if a button stays green after you let go, it may need cleaning.
- No vibration: some browsers and Bluetooth connections do not support rumble.
Common Mistakes to Avoid
- Not pressing a button first. Browsers hide controllers until a button is pressed.
- Touching the sticks during the drift check. Let go completely for a few seconds.
- Testing in a background tab. Keep the page in front; some browsers pause it otherwise.
- Trusting the names on odd controllers. Non-standard pads may number buttons differently.
- Expecting vibration everywhere. Support depends on the browser and connection.
Frequently Asked Questions
Connect it, open this page and press any button. Then press every button and move both sticks.
Press a button after the page loads. Browsers only reveal controllers after an input.
Let go of the sticks for a few seconds and read the drift result.
Under about 10% is usually hidden by game dead zones; more than that often shows in games.
Yes, where the browser supports it. Press Test vibration.
Most USB and Bluetooth gamepads the browser can see.
Yes. Each one gets its own panel.
No. It runs in your browser.
On Android with a connected controller, yes. iPhone support depends on the browser.
Your controller may not use the standard mapping. The numbers still match what the game receives.
No. The page measures drift; fixes include cleaning, recalibrating or replacing the stick.
It may be worn or need calibrating.
No. Inputs are only shown on screen.
It clears the highest resting readings so you can measure again.
References & Sources
| Source | Used For | Link |
|---|---|---|
| W3C, Gamepad specification | The Gamepad API and the standard button and axis mapping. | https://www.w3.org/TR/gamepad/ |
| MDN Web Docs, Gamepad API | How browsers report controllers, buttons and axes. | https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API |