Gamepad Tester Pro
Language
ENEnglish中文简体中文IDBahasa Indonesia

Gamepad Button Mapping Test

Press each button once and watch how the browser labels it. The gamepad button mapping test helps you verify indexes before remapping controls in a game, emulator, Steam Input profile, or repair note.

Controller Button Test

Pressed, touched, analog value, last pressed, and stuck input hints.

Last pressed: None

Button visualizer

A / CrossIndex 0
releasednot touched0.000
B / CircleIndex 1
releasednot touched0.000
X / SquareIndex 2
releasednot touched0.000
Y / TriangleIndex 3
releasednot touched0.000
LB / L1Index 4
releasednot touched0.000
RB / R1Index 5
releasednot touched0.000
LT / L2Index 6
releasednot touched0.000
RT / R2Index 7
releasednot touched0.000
Select / ShareIndex 8
releasednot touched0.000
Start / OptionsIndex 9
releasednot touched0.000
L3Index 10
releasednot touched0.000
R3Index 11
releasednot touched0.000
D-pad UpIndex 12
releasednot touched0.000
D-pad DownIndex 13
releasednot touched0.000
D-pad LeftIndex 14
releasednot touched0.000
D-pad RightIndex 15
releasednot touched0.000
HomeIndex 16
releasednot touched0.000
Touchpad / CaptureIndex 17
releasednot touched0.000

Gamepad Button Mapping Test

Press each physical button once and compare the browser index, standard label, pressed state, touched state, and analog value.

Raw

No controller selected

Mapping differences can come from adapters, Steam Input, browser support, drivers, or a controller mode switch. Confirm the same index in the game before remapping.

Local Test Report

Generate Local Report data in this browser. Nothing is uploaded or stored on a server.

Report includes the local diagnostic disclaimer at the bottom.

Local history

Stored locally on this device only.

No local reports saved yet.

Raw Input Panel

Raw values help debug non-standard mapping and multi-controller setups.

{
  "Status": "No controller selected"
}

Browser support panel

Feature detection is based on this browser session.

Chrome / Edge usually expose the broadest hardware APIs
Gamepad API

Checking support in this browser session...

Vibration API

Checking support in this browser session...

MediaRecorder

Checking support in this browser session...

WebHID

Checking support in this browser session...

Secure context

Checking support in this browser session...

Compatibility caution

Safari, Firefox, Linux, mobile browsers, Bluetooth adapters, and third-party drivers may expose incomplete features.

WebHID compatibility helper

Optional read-only permission prompt for listing HID devices. No firmware, calibration, or hardware-write operations are performed.

Trust note: Mapping labels can change by browser, driver, adapter, controller mode, and remap software.

Why mapping checks matter

A button can work electrically while still appearing under an unexpected index. That matters when an emulator, accessibility profile, adapter, or game expects a specific layout. The mapping page makes the browser index visible beside the standard label and raw value.

For non-standard controllers, use the raw panel and report output. A clear mapping record is often more useful than saying a button is wrong.

  • Press each physical button once and record the browser index.
  • Compare standard labels with raw indexes.
  • Watch for buttons that remain pressed after release.
  • Use the report when sharing remap evidence.

Browser and hardware limits

Gamepad API support, haptic feedback, MediaRecorder, and WebHID are exposed differently across Chrome, Edge, Firefox, Safari, Linux, mobile browsers, USB, Bluetooth, and third-party drivers. For Gamepad Button Mapping Test, treat that limit as part of gamepad button mapping test guidance rather than as a separate verdict.

A missing feature in the browser does not prove that the controller is damaged. Use the live readings as diagnostic hints and compare results across connection methods when possible. On this Gamepad Button Mapping Test page, compare that note with the live module that matches the article steps, the browser readings they depend on, and the practical decision the reader needs to make.

Gamepad button mapping test workflow

A gamepad button mapping test is useful when labels and physical buttons disagree. Press one control at a time, write down the raw index, then compare the browser label with the label inside your game or emulator. The gamepad button mapping test is especially helpful for Nintendo-style layouts, adapters, and older PC pads.

Do not remap everything after one surprising result. A gamepad button mapping test should first confirm whether the same index appears over USB and Bluetooth. If the gamepad button mapping test changes by connection mode, the adapter or driver may be changing the layout before the game sees it.

  • Use the gamepad button mapping test before editing emulator profiles.
  • Record one button per line.
  • Repeat the gamepad button mapping test after switching connection mode.
Quick workflow
  1. 1. Connect by USB or Bluetooth.
  2. 2. Press any button to activate detection.
  3. 3. Compare buttons, sticks, triggers, drift, and report output.
Privacy

Controller input, microphone recordings, and local reports stay in your browser unless you copy or download them.

FAQ

Gamepad Button Mapping Test FAQ

Why is the browser index different from my game?

The game may apply a mapping layer, Steam Input profile, emulator profile, or platform-specific driver after the browser reading.

Can this test help with remapping?

Yes. It shows the browser index and label so you can map the correct physical button in another tool.

Why do triggers appear as buttons?

Some controllers expose triggers as button values, axes, or both depending on mapping and driver behavior.

Should I save a report for mapping problems?

Yes. A local report can include the controller name, mapping, button count, and browser support context.