Input index diagnostics

Button Mapping Test

Press each control and this button mapping test will show browser indexes, labels, analog values, axes, and the latest press sequence.

Button Mapping Matrix

Press each control to confirm browser index, label, analog value, and order.

No Controller Detected

Connect via USB or Bluetooth, then press any controller button to activate detection.

Axes

Axis 0+0.00000
Axis 1+0.00000
Axis 2+0.00000
Axis 3+0.00000

Buttons

A0

+0.000

B1

+0.000

X2

+0.000

Y3

+0.000

LB4

+0.000

RB5

+0.000

LT6

+0.000

RT7

+0.000

Back8

+0.000

Start9

+0.000

LS10

+0.000

RS11

+0.000

Up12

+0.000

Down13

+0.000

Left14

+0.000

Right15

+0.000

Home16

+0.000

Share17

+0.000

Press sequence

Waiting for the first mapped input.

Embed This Tool

Use this iframe code to place this exact diagnostic widget on another page.

Button mapping widget

Embed the mapping matrix for raw button indexes, axes, and press order.

https://gamepadtesteronline.org/embed/button-mapping-test/

<iframe src="https://gamepadtesteronline.org/embed/button-mapping-test/" title="Button mapping widget" width="100%" height="560" loading="lazy"></iframe>

Why Mapping Problems Feel So Confusing

A button mapping test shows the controller layout that the browser actually receives. Physical labels are useful, but games, emulators, and web apps usually bind to Gamepad API indexes. If a button works on the controller but triggers the wrong action, the controller mapping test can show whether the browser index, game profile, or user binding is the likely source.

This gamepad mapping test combines a compact raw grid with a press sequence. The grid shows every button value and axis, while the sequence tells you the order in which controls were detected. That is useful when testing fight sticks, adapters, third-party pads, cloud gaming sessions, or controllers with nonstandard firmware.

Analog controls can appear in surprising places. Triggers often appear as button entries with values between zero and one. Some wheels and joysticks expose pedals as axes. The button mapping test does not hide those details behind friendly labels; it displays the raw browser structure so advanced users can configure bindings accurately.

How To Build A Reliable Map

Press one control at a time and wait for it to release before pressing the next. The controller mapping test updates the last input and keeps a short sequence, which makes stuck buttons and double activations visible. If two physical buttons report the same index, check whether a driver or adapter is merging them.

Move each stick and trigger after the digital buttons. A clean gamepad mapping test should show axes changing smoothly and returning to center. If an axis never changes, the control may be unsupported in the current browser mapping. If an axis is inverted, that may be expected for vertical controls, but your game binding should account for it.

For adapters and specialty hardware, save the result by noting the indexes rather than relying on button names. A fight stick may label buttons differently from a standard controller. A racing wheel may expose shifter paddles as buttons and pedals as axes. The button mapping test gives the translation layer.

Using Mapping Results In Games

When a game asks for a button, compare its binding screen with the controller mapping test. If the game waits for button 0 and this page shows your desired button as index 2, adjust the binding or switch the controller mode. If this page never sees the input, the problem is below the game and belongs in support troubleshooting.

For web developers, this controller mapping test is a quick sanity check before writing custom mappings. It shows whether a device reports standard layout values and where analog buttons appear. It also makes clear that browser mappings can differ by operating system and connection type, so robust code should avoid hard assumptions for unusual hardware.

Mapping results pair naturally with latency and polling checks. If the right button is detected but feels late, test timing. If detection is stable but the action is wrong, fix the binding. If detection is missing, try another browser, cable, adapter, or driver mode.

Diagnostic Glossary

Button index

The numeric button position exposed by the browser.

Analog button

A button entry that reports a value between zero and one.

Axis inversion

A direction convention where up may report negative or positive values depending on mapping.

Questions Users Ask

Short answers for common diagnostic decisions on this page.

Why do labels differ from my controller?

The page shows common labels, but raw indexes are the reliable browser values. Specialty hardware may use different physical labels.

Can this create a remap file?

No. It identifies indexes and values so you can configure games or development code manually.

Why does one trigger show as a button?

That is common in the Gamepad API. The button entry can still carry an analog value.

Useful Next Checks

Run a stick drift test

Check idle offset and deadzone before changing in-game sensitivity.

Check polling rate

Sample browser input intervals while moving or pressing controls.

Compare input latency

Look at event timing clues and optional HID capability.

Read troubleshooting paths

Fix detection, Bluetooth, permission, browser, and mobile issues.