Controller and gamepad test

How to test a controller on PC

Press a button to expose the pad. The gamepad tester cannot read a controller that the browser has not made available. Once its name appears, press and release face buttons, shoulders, triggers and stick clicks in a fixed order. Record which value changes rather than guessing from a game prompt.

Move each stick, then let it rest. Does the page show the corresponding axes? A missing axis is incomplete evidence, not a centred stick. This controller test must not substitute zero for an absent axis or claim that every extra control has a standard mapping.

Use the stick drift test for an untouched resting sample after confirming both sticks are exposed. The base page displays mapped values during movement. One visible offset cannot identify the physical cause of controller stick drift.

Supported controllers

Support depends on whether the operating system and browser expose the device through the Gamepad API. A USB and Bluetooth connection can present different mappings. Test the connection you use, then change one route if the expected input is absent.

Is a trigger missing or labelled differently? Compare the visible button values with the affected game's mapping. Vendor paddles, touchpads and motion controls may lack a standard entry. An absent accessory label is not proof that its physical control failed.

This controller tester online records only inputs available in the tab. It cannot inspect firmware, battery condition or the raw report stream. A connected name confirms recognition, not every button, axis or feature on a specific model.

Controller not detected?

Check the system connection first, then keep the browser foreground and press a controller button. If it remains absent, compare a documented connection or another browser without changing game bindings at the same time.

Buttons can arrive while required stick axes do not. Treat the stick check as inconclusive in that case. Do not read an absent X or Y axis as 0.00, and do not infer a hardware repair from one browser mapping gap.

Does the pad work here but fail in one game? Compare that game's selected input, bindings and remapping profile. If the device disconnects, record the route and restart a fresh run. The browser can report loss of access but cannot distinguish power, cable and radio causes by itself.

Read button labels, values and the counter

B0, B1 and the other B labels are browser button indexes. They are not universal names for the physical labels printed on every controller. Press one physical control at a time to see which displayed entry changes, then release it before the next check.

The value beside a button is the mapped value received by the page. A slow trigger squeeze may show intermediate values or a digital change, depending on the mapping. A missing entry is not a healthy zero and does not identify a broken component.

Verified buttons counts distinct browser button indexes seen as pressed or with a mapped value greater than 0.1 during this run. Repeating the same index does not increase the count. A value at or below 0.1 does not count unless the browser also reports that entry as pressed.

When the button array is non-empty, the denominator is its number of exposed entries: 17 entries show /17, while 12 entries show /12. When the button array is empty, the display falls back to /17 as a placeholder; it does not prove that 17 buttons were exposed or tested. Before a run starts, the counter displays a dash. Missing input is not a healthy zero, and a placeholder cannot establish controller health.

This counter does not count every physical feature your controller might have. A full button count alone says nothing about an unobserved stick, motion sensor, touchpad or later behaviour in a game.

Finish, reset and compare a fresh run

After checking the exposed buttons, move both sticks and note the available axes. Select Finish and read result to review the sample. A pass or concern refers to the data collected in this run, not a warranty decision or a guarantee that all controller features work.

For this base test, the result can say pass once at least four distinct button indexes have counted, provided at least four stick axes are exposed. For example, a pass with 4/17 does not mean all 17 entries were checked. The pass threshold is separate from the displayed denominator; it is not a full-coverage certificate. Fewer than four counted buttons means the sample is incomplete, and fewer than four exposed stick axes produces an incomplete result even when four or more buttons counted.

If a required stick axis is absent, treat that part of the test as incomplete. Keep the observed label and value in your notes; do not replace an absent entry with 0.00. The browser cannot identify the physical cause of a missing or unexpected signal.

Choose Reset before changing the device or connection. Keep the same order for the repeat. If the controller disconnects, reconnect it and start a fresh run instead of combining observations from different connections. For a complete browser-versus-game checklist, use how to test a controller.

What this browser sample cannot measure

This page reads mapped Gamepad API inputs during animation frames. Its sampling frequency is not a raw USB or Bluetooth controller report rate, and it cannot measure end-to-end button latency or inspect firmware calibration.

Mapping, remapping software and the active connection can change which inputs reach the tab. Compare the same setup in the application where the symptom occurs. A browser result cannot rule out every intermittent fault or tell you which component needs replacement.

Use the stick drift test for an untouched resting sample, the controller vibration test for a separate rumble request, or the controller polling rate test for its documented browser-observed timestamp check. These are separate tasks; this base test does not certify their results.