Button Mapping Test

Indices · Event log

Every press and axis movement is logged with its index, value and timestamp, next to the W3C standard layout.

Connect your controller with USB or Bluetooth and press any button to wake it up. Processed locally

Device

ID—
Mapping—
Buttons / Axes— / —

Event Log

Newest first

Axes

Press a button to see axes

Buttons

Index · standard name · value
#Standard nameValue

Reading Raw Mappings

See exactly what your controller sends before you remap anything.

Index & Value

Each button shows its index and analog value — great for emulator and Steam Input setup.

Event Log

Timestamped presses, releases and big axis moves. Copy it for bug reports.

Standard Names

Standard-mapped pads show the W3C name for every index.

How to Find a Button's Index

  1. 1

    Connect the controller and press a button.

  2. 2

    Check the mapping type. "standard" means the browser uses the W3C layout; an empty value means raw mapping.

  3. 3

    Press each button and watch its index light up in the grid and the event log.

  4. 4

    Move each stick and trigger to see which axis index changes.

  5. 5

    Copy the log if you need the numbers for an emulator or a game.

The Standard Layout

In the W3C standard mapping, buttons 0–3 are the face buttons, 4–5 the bumpers, 6–7 the triggers and 8–9 the select and start buttons.

Buttons 10–11 are the stick clicks, 12–15 the D-pad and 16 the home button. Axes 0–1 are the left stick and 2–3 the right stick.

Raw Mapping

When a browser does not recognise a pad, it passes the driver order through unchanged. Buttons and axes can then appear in any order.

Triggers often show up as axes instead of buttons in raw mode. The event log makes it easy to spot which index moves.

Using Indices in Emulators and Games

Emulators such as RetroArch can auto-configure many pads, but unusual ones need manual binding. The index list here tells you which number to choose.

For PC games that do not recognise your pad, Steam Input can translate it to an Xbox layout. After setting it up, retest here to confirm the new mapping.

Standard Button Index Map

This is the order browsers use when a pad reports "standard" mapping.

IndexRolePlayStationXboxNintendo
0Bottom face button✕AB
1Right face button○BA
2Left face button□XY
3Top face button△YX
4 / 5BumpersL1 / R1LB / RBL / R
6 / 7TriggersL2 / R2LT / RTZL / ZR
8 / 9Select / StartCreate / OptionsView / Menu− / +
10 / 11Stick clicksL3 / R3LS / RSLS / RS
12–15D-pad up, down, left, rightD-padD-padD-pad
16Home buttonPSXboxHome
17Extra buttonTouchpad clickShare (some browsers)Capture

Mapping Problems and Fixes

Wrong indices are usually a driver or mode issue.

Buttons out of order

Switch the pad to X-input mode if it has one, or try Chrome, which recognises more controllers.

D-pad shows as an axis

Some pads report the D-pad as a hat switch on axis 9. Emulators can map this, but check the value for each direction.

Double presses

If one press logs twice, the switch is chattering and may need cleaning or replacement.

Missing buttons

Some extra buttons, such as Share or the touchpad, only appear in certain browsers.

Frequently Asked Questions

Why is mapping “(empty)”?

The browser does not recognise the device as a standard pad, so indices are raw DirectInput order.

My D-pad is an axis

Many generic pads report the D-pad as a hat axis — use the Joystick Tester to decode it.

Can I remap here?

This tool only reads inputs. Use your OS, Steam Input or the manufacturer app to remap.

Does it log analog noise?

Only movements bigger than 0.25 are logged to keep the log readable.

What is the D-pad hat value?

Pads that report the D-pad as a hat use one axis whose value changes in steps for each direction.

Can I remap buttons here?

No. This page shows the mapping. Remap in your game, Steam Input or a tool like DS4Windows.

Why does my pad show more than 17 buttons?

Some pads expose extra buttons, such as macro keys or mode switches. They appear after the standard ones.

Related guides

More tools you might need