Button Mapping Test
Not connectedNon-standard: numbers don't match the drawing
Non-standard: numbers don't match the drawing
TipOr skip the check: press any button to see its number.
Browsers number known controllers by the W3C Standard Gamepad layout: a position has different names on Xbox, PlayStation and Switch, but the same number. This is the Xbox, PS and Switch controller mapping in one table. When the page shows Standard mapping, every button should match it; if one doesn't, the mapping has been changed.
Standard mapping numbers a button by its position, not its letter: the bottom face button is 0 and the right one is 1. The three brands place their letters differently, so the same letter can have different numbers.
Bottom A is 0, right B is 1. The standard follows Xbox.
Same positions: ✕ is 0, ○ is 1.
A is on the right, so it's 1; bottom B is 0. Not a fault.
Some remappers make the printed A report 0, which moves all four.
A button passes through several steps on its way to a web game, and each can change its number. The browser reads only the final result, so this test shows the number a web game receives.
In standard mapping the d-pad is four buttons and the triggers are two buttons. With non-standard mapping the same buttons often report as axes, and you can see them move in the Axes card above.
A hat reports eight directions as eight values on one axis: up is −1, each step clockwise adds 2/7, and released reads about 1.29, outside −1 to 1.
At half pull, a standard trigger reads 0.5 and one on its own axis reads 0. On a shared axis the two cancel out: pulling both reads 0.
Browsers number a recognized controller by the standard layout in the W3C Gamepad spec: face buttons 0 to 3, bumpers 4 and 5, triggers 6 and 7, View and Menu 8 and 9, stick presses 10 and 11, the d-pad 12 to 15 and Home 16; the two sticks are axes 0 to 3. Web games read buttons by these numbers, so different brands work in one game.
Standard mapping goes by position, not by the printed letter. The A on a Switch controller is on the right, so by position it's number 1 (the Xbox B), and that isn't a fault. On other controllers a swap usually means Steam Input or a remapper matched buttons by letter. Press Start check to go through them, and the page lists what was swapped.
The browser doesn't know this controller, so it numbers buttons in the device's own order and buttons may land wrong in web games. Try Chrome or Edge, or set the X/D switch on the back to X (XInput). If it stays non-standard, run the check here and use the recorded numbers to set buttons in your game or emulator.
XInput is the Xbox layout with fixed numbers, read by most PC games and browsers. DirectInput lets each device report its own, so browsers often show non-standard mapping. Chrome and Edge know DualSense and DualShock 4 and give them standard mapping.
In DirectInput mode some controllers report the d-pad as a hat: eight values on one axis. In Chrome up is −1, each clockwise step adds 2/7, and released reads about 1.29. The Axes card then draws eight cells, and the log writes directions like A9↑.
In standard mapping the triggers are buttons 6 and 7, from 0 to 1. In DirectInput mode they are often axes, reading −1 released and 1 fully pressed. On some controllers both share one axis, one going positive and the other negative, so pressing both cancels out.
A controller turns them into other buttons before reporting, so the browser sees the result. A paddle set to A lights up 0. A macro shows several buttons in one frame in the log.
Browsers can only read a controller, so a web page can't change its mapping. To change controller mapping, use the game's control settings, Steam Input, or the controller maker's app.
Standard mapping covers 0 to 16. The PS touchpad press is usually 17, the Xbox Share button can't be read, and the Switch Capture number varies. Extras on sticks and wheels follow the device's order.
Two very short presses usually mean button bounce from worn rubber or dust. Press it a few times on the controller test. Controller test →