Gamepad Tester: Buttons, Sticks & Controller Drift

Test game controllers in your browser. Check every button, analog stick, trigger, axis value, mapping, connection event, and possible stick drift in real time.

Input coverage

Buttons + Triggers

Axis detail

Raw + Deadzone

Processing

Local only

Live controller input

Connect a controller, then press a button or move a stick.

Waiting for input

Activate your controller

Connect by USB or Bluetooth, keep this tab visible, then press any controller button. Some browsers do not reveal an already connected controller until the first interaction.

Result summary

A compact view of the current test state and the strongest signal detected so far.

Waiting for controller input

Current controller

-

Controllers

0

Active buttons

0

Maximum axis offset

0.000

Press any controller button so the browser can expose the device.

How to test a controller

1. Connect the controller by USB or Bluetooth. 2. Keep this tab visible and press any controller button. 3. Press every face, shoulder, menu, and D-pad button. 4. Move both sticks slowly to their full range and release them. 5. Pull each trigger from zero to full pressure and compare the values.

How to read the result

A released button should return to 0 and a fully pressed analog control should approach 1. Stick axes should return close to 0 after release. Small variation can be normal; repeat the test before treating a sustained offset as drift. Non-standard mappings may use different button and axis numbers.

Local browser diagnostics

Controller IDs and input values are read by your browser and are not uploaded by this tester. The page does not record gameplay, remap controls, or activate controller vibration.

Buttons, D-pad directions, shoulder controls, analog triggers, dual-stick position, raw axis values, standard or non-standard mapping, multiple connected controllers, and connection history.
Gamepad support varies by browser, operating system, driver, and controller. Some browsers only expose a controller after the user presses a button while the page is visible. Vendor-specific controls may appear as numbered buttons or axes.
Q: Why is my connected controller not shown? A: Keep the tab visible and press a controller button, then scan again. Q: Does an offset always mean stick drift? A: No. Release the controller, repeat the test, and compare the value with the 0.10 deadzone. Q: Why are button names different from my controller? A: Standard mapping uses position-neutral labels; non-standard devices are shown by button and axis number. Q: Can this page repair or remap a controller? A: No. It diagnoses browser-visible input only.

Related tools

Continue with the next check that best matches the symptom you are troubleshooting.

Troubleshooting Center

Start with the symptom

Best next step

Keyboard Check

Test key response, rollover, and simultaneous input behavior.

Open tool

Touch Screen Test: Multi-Touch, Pen & Coverage Check

Test touchscreen and stylus input in your browser. Visualize multiple contacts, pressure, continuous trails, screen coverage, edges, and corners.

Open tool

Trackpad Check

Check movement, drag, scroll, zoom, and secondary click behavior from one browser page.

Open tool