Gear test

Gamepad & controller test

Test your controller online: press any button and BenchRush shows every button, trigger and stick the browser receives — Xbox, PlayStation DualSense / DualShock, Switch Pro and generic USB or Bluetooth gamepads. No download needed.

Live controller state

No controller detected yetPress a controller button or reconnect it.

Waiting for the browser Gamepad API to expose a connected controller.

How to connect your controller

  1. Connect by USB cable or pair it over Bluetooth in your system settings.
  2. Press any button while this page is open. Browsers only reveal a controller after it has been used on the page.
  3. Press every button and move both sticks. Each input lights up in the map; triggers show how far they are pressed.

Standard button mapping

When a controller reports the "standard" mapping, browsers number the inputs the same way for every brand:

Buttons 0–3A / Cross, B / Circle, X / Square, Y / Triangle
Buttons 4–7LB / L1, RB / R1, LT / L2, RT / R2 (triggers report 0–1)
Buttons 8–11View / Share / Create, Menu / Options, left stick press (L3), right stick press (R3)
Buttons 12–15D-pad up, down, left, right
Button 16Xbox / PS / Home button
Axes 0–3Left stick X and Y, right stick X and Y (−1 to 1)

Controller not detected?

  • Press a button after the page has loaded — this is required by browsers for privacy.
  • Try Chrome or Edge; they expose the widest range of controllers.
  • Close Steam, DS4Windows or other remapping tools that can take over the controller.
  • Reconnect by cable to rule out Bluetooth pairing problems.

Seeing movement with your hands off the sticks? Measure it with the stick drift test.

Use the result as a baseline, not a diagnosis

BenchRush measures browser-visible input. If a result looks wrong, repeat the run, check focus and settings, compare another browser/device where practical, and use manufacturer diagnostics for hardware conclusions.

Test Center → · View PlayerScore →

Interpret the result

A controller test sees browser-exposed state

Use repeatable axis-center behavior to investigate drift, while keeping browser mapping, deadzones, calibration and firmware as separate layers.

Read the guide →

Questions people ask

Why does my controller not appear?

Many browsers require a button press or other user interaction before exposing a connected gamepad. Support also varies by browser, operating system and connection method.

Can this diagnose stick drift?

It can show browser-visible axis values near the center, which is useful for spotting a repeatable offset. It cannot inspect firmware calibration, raw USB packets or the physical stick mechanism.

Does this support every controller?

No. It supports controllers that the browser exposes through the standard Gamepad API. Button mapping and labels can vary by device.

Does the PS5 DualSense controller work?

Yes. In Chrome and Edge the DualSense works by USB and Bluetooth with standard mapping. Some browsers show it with a different mapping, in which case the button numbers can differ from the table.

Can I test vibration or adaptive triggers here?

No. This page reads inputs: buttons, triggers and sticks. Vibration and adaptive trigger effects need game or system tools.

Privacy by default

Your personal bests, XP and streak are stored locally in this browser. The current tool does not require an account or upload your individual run to a global leaderboard.