Blog

Why gamepad buttons show unexpected numbers

Find out why a gamepad test shows button numbers that do not match the labels, and check whether the controller, browser, or game is remapping them.

Ashley MorrisGames 5 min read

You press the button marked A, but a test or game reports a different number than you expected. That does not automatically mean the controller is faulty. A button's number is usually its position in the data sent to the browser, not the number or letter printed on its face.

Use the Gamepad Test to see which inputs the browser receives, one button at a time. Then compare that behavior with the game or app where the controls seem wrong.

Check which button the browser receives

  1. Open the Gamepad Test on the device connected to your controller.
  2. If the controller does not appear right away, press a button once, then wait for the test to show its input.
  3. Press one controller button at a time. Note which numbered indicator or button response changes for each press.
  4. Repeat with the directional pad, shoulder buttons, triggers, and stick clicks. Press triggers slowly, since they may report a range of values rather than a simple on or off.
  5. Open the game or app and check its controller layout or remapping settings. Compare its displayed actions with the results from the test.

Testing one input at a time matters. If you hold several buttons together, it is easy to confuse a real mapping difference with simultaneous input or a controller's special mode.

What the result means

The number differs from the letter printed on the button

This is often normal. A browser receives a list of button values in a particular order. The list positions are called indices, and the index is not necessarily the label printed on the controller. For example, a standard gamepad layout assigns indices by button position. Index 0 is the bottom face button, 1 is the right face button, 2 is the left face button, and 3 is the top face button. The symbols on those positions vary between controller styles.

If the test responds consistently when you press each button, the controller is sending input. The number alone does not show that anything is broken.

The test and the game disagree about the same press

The game may use its own mapping, a saved control profile, or a remapping layer from the operating system or another program. The browser test shows what reaches the browser. It cannot tell you how a separate game interprets or changes that input. Check that game's controller settings, then compare with Controller buttons mapped wrong? What to do.

A different indicator changes each time you reconnect

The controller may be switching modes, or the browser or operating system may be receiving it with a different mapping. This can happen with generic controllers, adapters, wireless receivers, or controller software. Use the same connection method and mode each time you compare results.

A button does not register, sticks jump, or triggers stay active

That is more concerning than a surprising index. Test the same control several times, then reconnect the controller and repeat. If the input still fails in the test, look for a connection, switch, or hardware problem rather than changing the game's button labels.

How to fix a button mapping that feels wrong

  1. Check the controller's mode. Some controllers have a switch or button combination that changes how they identify themselves. Check the controller's manual, set the mode recommended for your device, and run the test again.
  2. Disconnect extra controllers. Unplug other gamepads and adapters, then reconnect only the one you are checking. A game can select a different controller than the one you are pressing.
  3. Check the game's control profile. Look for controller layout, remapping, or preset options in the game. Restore its default layout if you are unsure which controls were changed, then customize it again if needed.
  4. Remove and reconnect the controller. On Windows 11, open Settings › Bluetooth & devices › Devices, remove a wireless controller if it is listed, and pair it again. For a wired controller, try another USB port and avoid a hub for this check. On macOS, open System Settings › Bluetooth to forget and reconnect a wireless controller. If your Mac shows System Settings › Game Controllers, check whether a controller profile is available there.
  5. Pair it again on a phone or tablet. On Android, open Settings › Connected devices and reconnect the controller; the menu name can vary by device. On iPhone or iPad, open Settings › Bluetooth, forget the controller, and pair it again. Browser support for gamepad input varies on mobile, so if the test does not show the controller, check it on a computer too.
  6. Close remapping utilities and restart. Quit controller configuration software and games that may apply a custom profile, then reconnect the controller. Test again before opening the game.

If the numbers still seem unusual but every control responds consistently, the layout may simply be different from the one the game expects. The guide Why the browser misses some gamepad features explains why a browser may not expose every controller detail.

When it may be a hardware problem

Try the controller on another device, using a supported browser or game, and test it with a direct wired connection if possible. If the same physical button repeatedly fails, activates without being pressed, or changes only when you bend the cable or move the controller, the switch, cable, or wireless connection may be damaged.

If the controller is under warranty, save a short note of which physical input fails and how you tested it before contacting the seller or manufacturer. For an older controller, compare the cost of a repair with a replacement. A browser test can show inconsistent input, but it cannot identify the exact internal part that has failed.

Why numbers can differ between tests and games

Browsers use an interface called the Gamepad API to read connected controllers. A recognized standard mapping gives compatible controllers a shared button order. An unrecognized controller can instead expose its own order, which may not match a familiar layout. The browser does not decide what the letters on the controller mean, and the game may apply another layer of mapping after the browser or operating system receives the input.

For that reason, compare the physical control with the response, not just its number. If the same press produces the same response every time, that is useful evidence even when the index differs from a guide or a game's label.