ControllerTest.io

Button Mapping Test

Not connected
Connect a controller and press any button

Non-standard: numbers don't match the drawing

Extra buttons
Press the touchpad, share or capture button; its number appears here
—
Press any button on the controller
Its number, name on each brand and position
Value—
Presses—

Check each button

Not started
0/17
Press each ringed position in turn
17 positions, about 30 seconds
Face
A0B1X2Y3
Shoulder
LB4RB5LT6RT7
D-pad
↑12↓13←14→15
Middle
View8Menu9Xbox16LS10RS11
  • Mismatches are listed here after the check
Connect a controller to start

Axes

Move a stick to see its number —
A0Left X−1 left+1 right0.00
A1Left Y−1 up+1 down0.00
A2Right X−1 left+1 right0.00
A3Right Y−1 up+1 down0.00

Press log

Buttons in one frame share a row Records: 0
TimeEventNumberNameHeld
—No records yetPress a button to start
—————
—————
—————
DownUpAxisLast 200 entries · Stored on this page only

How to test

About 1 min
01
Press a buttonIts place and number light up on the drawing.
02
Extra buttonsNumbers from 17 up show under the drawing.
03
Start the checkPress the 17 ringed positions in turn.
04
Look for amberAmber means another number came in.

TipOr skip the check: press any button to see its number.

Controller button number table

17 buttons · 4 axes

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.

No.PlaceXboxPlayStationSwitchOn the pad
B0A✕BFace bottom
B1B○AFace right
B2X□YFace left
B3Y△XFace top
B4LBL1LLeft bumper
B5RBR1RRight bumper
B6LTL2ZLLeft trigger
B7RTR2ZRRight trigger
B8ViewCreate−Middle left
B9MenuOptions+Middle right
B10LSL3LSLeft stick press
B11RSR3RSRight stick press
B12↑↑↑D-pad up
B13↓↓↓D-pad down
B14←←←D-pad left
B15→→→D-pad right
B16XboxPSHomeCenter
No.PlaceAxisEnds
A0Left stick X−1 left, +1 right; 0 in the middle
A1Left stick Y−1 up, +1 down; 0 in the middle
A2Right stick X−1 left, +1 right; 0 in the middle
A3Right stick Y−1 up, +1 down; 0 in the middle
Numbers from 17 up are brand-specific buttons, shown under the drawing

Why pressing A shows B

By position

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.

Xbox

Bottom A is 0, right B is 1. The standard follows Xbox.

PlayStation

Same positions: ✕ is 0, ○ is 1.

Switch

A is on the right, so it's 1; bottom B is 0. Not a fault.

Matched by letter

Some remappers make the printed A report 0, which moves all four.

Standard numberNumber doesn't match positionThe check here calls this Swapped

Why controller buttons get mapped wrong

5 causes

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.

  1. ControllerPaddles, macros
  2. ModeXInput or DirectInput
  3. RemapperSteam Input, DS4Windows, BetterJoy
  4. BrowserStandard if known, raw if not
  5. Web gameStandard buttons
CauseWhat you see hereWhat to do
DirectInput modeNon-standard mappingSet the back X/D switch to X (XInput)
Unknown to the browserNon-standard in FirefoxTry Chrome or Edge
Steam Input runningSwapped or renumbered buttonsQuit Steam, or turn off Steam Input for this controller
DS4Windows, BetterJoyPS or Switch shows as XboxExpected: shown as Xbox
Paddles, macrosOne button reports another's numberRestore defaults in the maker's app
If a button does nothing at all, press it a few times on the controller testController test

D-pad and triggers: buttons or axes

DirectInput

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.

D-pad: one axis, eight values

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.

Triggers: 0 to 1, or −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.

In the check, the d-pad and triggers may respond as axes, recorded as A9↑ or A2+

Frequently asked questions

10 questions

What is standard mapping (Standard Gamepad)?

A W3C numbering

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.

Why does pressing A show B?

It goes by position

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.

What should I do about non-standard mapping?

Numbers may not match games

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.

What is the difference between XInput and DirectInput?

Two connection modes

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.

Why is the d-pad an axis and not buttons?

A hat switch

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↑.

Why are triggers sometimes buttons and sometimes axes?

It depends on the mode

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.

How do paddles and macros show up here?

As the mapped button

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.

Can I remap controller buttons on this page?

No

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.

What are the buttons from 17 up?

Brand-specific buttons

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.

Why does one press show twice?

Possibly button bounce

Two very short presses usually mean button bounce from worn rubber or dust. Press it a few times on the controller test. Controller test →