How to Test a Controller Online in Your Browser (Buttons, Stick Drift, Vibration)
You can test a controller online in your browser without downloading anything, as long as your browser supports the Gamepad API and your controller is connected by USB or Bluetooth. ControllerTest.io reads the raw hardware signal directly, so you can check button mapping, stick drift, trigger pressure, and vibration in one session. If the page shows "No Controller Detected," press any button on the controller once to wake the connection.
Before You Start
- Browser: Use a current version of Chrome, Edge, or Firefox. The Gamepad API is the mechanism that exposes controller input to the page.
- Connection: USB cable or Bluetooth both work. Wired is the better choice when you want to measure latency, since Bluetooth adds its own transmission delay.
- Controller: The site lists support for Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and other major controllers.
- Privacy: All input processing happens locally in the browser, so nothing is uploaded.
Step 1: Connect and Wake the Controller
- Plug the controller in via USB, or pair it over Bluetooth through your operating system's settings.
- Open the tester page.
- If the visualizer stays idle, press any button on the controller. The site notes this explicitly: the browser may not respond until a button press activates the connection.
Expected result: The player indicator (P 1–P 4) lights up and the button/stick panels begin showing live values.
Common snag: A controller that is paired but idle can look disconnected. The button press is what triggers the Gamepad API to report it.
Step 2: Check Every Button and the ABXY Layout
Press each button one at a time and watch the visual interface. The tester highlights the button and prints "Button Pressed."
- Confirm that the physical button you pressed is the one that lights up. This is how you catch a mis-mapped ABXY layout, which is common with third-party or region-variant controllers.
- Work through the full set: face buttons, bumpers (LB/RB), triggers, D-pad, stick clicks, and any menu buttons.
- The raw data panel lists buttons as numbered indices (0–17), so you can cross-check anything the visualizer doesn't label.
Expected result: Every button registers on press and clears on release, with no button stuck "on."
Step 3: Test Stick Drift, Dead Zones, and Centering
This is the part that answers "do I need to clean or replace my sticks?"
- Let go of both sticks completely. Do not rest a finger on them.
- Read the Left Stick and Right Stick coordinates. At rest they should sit near +0.00, +0.00.
- Watch the Err value. A persistent non-zero error while the stick is untouched indicates drift or a centering problem.
- Move each stick in slow circles and watch the circularity and linearity readouts. A healthy stick traces a smooth, even circle; a worn one shows flat spots, jumps, or an offset center.
How to read the result:
| Observation | What it suggests |
|---|---|
| Coordinates hold near zero at rest | Stick is centered, no drift |
| Small constant offset at rest | Early drift — cleaning may help |
| Large or wandering offset | Significant wear — consider hall effect sticks or replacement |
| Circle is lopsided or has dead spots | Dead zone or sensor wear |
The site frames this as static offset analysis, and it's the same signal you'd use to decide between cleaning the module and swapping the stick.
Step 4: Test Triggers and Vibration
Triggers: Press LT/L2 and RT/R2 gradually. The tester shows analog pressure on a 0–1 scale, so you can confirm the trigger ramps smoothly rather than jumping from 0 to 1. A trigger that only reads 0 or 1 has a failing analog sensor.
Vibration: Use the Dual Motor controls — HEAVY, LIGHT, BURST, and PULSE — to drive the left and right motors independently. If one side is silent or weak, that motor or its connection is the problem.
Expected result: Both motors respond, and each trigger produces a smooth pressure curve.
Step 5: Compare Polling Rate and Latency (Wired vs Bluetooth)
The tester measures your controller's actual polling rate and lets you compare input latency between wired and Bluetooth connections. Run the same test on both connections and compare:
- Higher polling rate + lower latency: better for competitive play.
- Noticeably worse numbers on Bluetooth: expected, and a reason to switch to USB if responsiveness matters to you.
This step is also a useful diagnostic — if latency spikes only on one connection, the issue is the link, not the controller.
What the Test Tells You
- All buttons map correctly, sticks center, triggers ramp, motors fire: the controller is healthy.
- Sticks drift but buttons are fine: cleaning or hall effect sticks are the likely fix.
- A single button or motor fails: that's a hardware fault, not a software one.
- Everything works but latency is poor on Bluetooth: use a cable.
Because the tool runs on the standard Gamepad API with no downloads, you can repeat the whole sequence after cleaning or repairing the controller and compare the numbers directly.