Skip to the benchController Test

Xbox controller test

Press a button on your Xbox controller and the bench reads sticks, triggers and buttons. The drift test checks the sticks at rest, the range check maps how far each stick reaches, and the vibration panel runs both main motors plus the trigger motors in Chrome or Edge on Windows.

Controller bench

No controller yet

Turn your phone sideways for the full bench.

Press any button on your controller — browsers only show a pad after its first press.

Stick check

Three steps: rest, circles, snap-back. Start with the controller lying on a table.

Vibration

Hold the controller and run each test. One motor at a time makes a dead or rattling motor easy to spot.

Report rate

Keep moving a stick in circles while it measures. The experimental deep mode counts every report; the Gamepad API shows what the browser sees.

Button check

Press every button once to tick it off. Then run the chatter test: press each button slowly, about 20 times.

Deep mode (WebHID)

You don't need this for the checks above: the standard test works with any controller. Deep mode is an optional extra.

Verdict

Connect a controller and run a check — the verdict shows up here.

Checklist for this controller

  • Run the drift test with the pad flat on a table.
  • Roll each stick around the edge — a squarish shape is normal for Xbox pads.
  • Pull both triggers slowly and check they reach 100%.
  • Test the main motors, then trigger rumble on Windows in Chrome or Edge.
  • Note whether the page shows XInput (cable or wireless adapter) or Bluetooth.

How to fix it

  1. Update the controller in the Xbox Accessories app, then retest drift.
  2. Two pads appear and move together: Steam Input created a virtual copy; close Steam.
  3. Only four Xbox pads show on Windows: XInput supports at most four at once.
  4. Deep mode can't see a wired Xbox pad on Windows: that's expected, it's not an HID device there. You don't need it — the standard test covers Xbox pads.

Spec sheet

USB / Bluetooth IDs
045e:0b12 (Series X|S, USB)USB ID registry045e:0b13 (Series X|S, Bluetooth)(to be confirmed on a real device)Linux hid-ids
Connections
USB-C, Bluetooth, Xbox WirelessManufacturer
Stick resolution
16-bit through XInputMicrosoft XInput documentation
Trigger resolution
8-bit through XInputMicrosoft XInput documentation
Report rate
Bluetooth ~125 Hz(to be confirmed on a real device)Measured by deep mode
Sensors and outputs
two body motors, two trigger motors (trigger rumble in Chromium on Windows)MDN GamepadHapticActuator

Known issues

FAQ

How do I test my Xbox controller on PC?

Connect it by cable, wireless adapter or Bluetooth, open this page and press a button.

Why is my Xbox stick range square?

Xbox pads report values that reach the corners of a square at the diagonals. That's by design, not a defect.

How do I test Xbox trigger rumble?

Use Chrome or Edge on Windows with an Xbox One or Series controller and run the trigger rumble test in the vibration panel.

Why do the triggers move in coarser steps than the sticks?

XInput passes sticks as 16-bit values but triggers as 8-bit, 0 to 255. Steps of about 0.4% on a trigger are normal.

Why won't my Xbox pad vibrate in Firefox?

Firefox has no vibration support for any pad. Chrome or Edge run both main motors, plus the trigger motors on Windows.

Does deep mode work with Xbox pads?

Rarely. It sees an Xbox pad only over Bluetooth and not on every OS, and a wired Xbox pad on Windows uses a driver outside HID altogether. The standard test is the main path for Xbox pads.

Other checks