Device-specific controller test
Xbox Controller Test
Connect an Xbox controller by USB or Bluetooth and this Xbox controller test will show live buttons, Share, View, Menu, sticks, bumpers, triggers, mapping, and rumble support.
Xbox Button Visualizer
Xbox controls are mapped to browser button indexes for local visual testing.
No Controller Detected
Connect via USB or Bluetooth, then press any controller button to activate detection.
A
B0Action button
B
B1Action button
X
B2Action button
Y
B3Action button
LB
B4Left bumper
RB
B5Right bumper
LT
B6Left trigger
RT
B7Right trigger
View
B8View button
Menu
B9Menu button
LS
B10Left stick press
RS
B11Right stick press
D-pad up
B12Directional button
D-pad down
B13Directional button
D-pad left
B14Directional button
D-pad right
B15Directional button
Xbox
B16Xbox button
Share
B17Share button
Analog Sticks
Crosshair scopes show center drift, range, and live trail.
Left stick
X +0.000 Y +0.000
Right stick
X +0.000 Y +0.000
Triggers
Analog pressure appears as local intensity values.
Raw Data
Latest values expose browser mapping and analog button state.
Last input
Waiting
Press a button to populate the live event log.
Vibration Test
Haptic commands run only after a user click.
Click a pattern after selecting a connected controller.
Xbox Layout Checks That Match Browser Reality
An Xbox controller test should separate the familiar physical layout from the browser mapping that games actually receive. The visual controller panel follows the standard button family: A, B, X, Y, bumpers, triggers, stick clicks, menu buttons, and d-pad directions. When you press a control, the Xbox controller test highlights the matching region and records the raw index so you can confirm both the physical action and the reported Gamepad API value.
Most modern Xbox pads report a standard mapping in desktop browsers, but connection method can still change behavior. A wired USB connection usually gives the most stable controller test, while Bluetooth can introduce pairing quirks, firmware differences, or haptic limitations. This gamepad tester keeps the device ID visible and trims long names so you can tell whether the browser has selected the intended controller slot.
Use the Xbox controller test before changing game settings. If the dashboard shows clean inputs, the problem may be game configuration. If the gamepad tester shows a stuck trigger, missing d-pad direction, noisy stick, or absent rumble actuator, you have evidence that the issue is below the game layer.
Reading Sticks, Triggers, And Raw Values
Xbox sticks should idle near zero and sweep smoothly through the scope. The controller test shows both sticks with a crosshair, deadzone ring, and trail, which makes center offset and edge clipping easy to see. If the left stick rests outside the deadzone or the right stick wanders while untouched, run the stick drift test and circularity test after this Xbox controller test.
The triggers are analog on most Xbox controllers. In this gamepad tester, LT and RT appear as pressure meters that should climb gradually when you pull them. If one trigger starts late, never reaches full value, or bounces while held still, that can affect racing games, shooters, and accessibility mappings. Raw values show whether the issue is present before any game-specific curve is applied.
Button mapping matters for launchers, emulators, browser games, and cloud gaming. The Xbox controller test shows the last pressed label and index, then the button mapping page can confirm every value in a denser matrix. This two-step workflow keeps the first visual check fast while still giving a deeper controller test when a single index looks wrong.
Connection Problems And Practical Limits
If the Xbox controller test stays disconnected, reconnect by USB, press the Xbox button once, and press a face button while the page is focused. On Bluetooth, remove old pairings if the browser sees a stale device, then pair again through the operating system. Some browsers expose the controller only after a button press, which is why the page keeps the activation instruction visible.
Rumble support is not guaranteed. Even when games vibrate correctly, the browser may not expose a vibration actuator for a specific Xbox controller, adapter, or Bluetooth stack. The vibration card uses a user click and reports the exact fallback so the gamepad tester does not imply a hardware failure when the limitation is really browser support.
The Xbox controller test is a diagnostic surface, not a firmware utility. It cannot update a controller, rewrite Bluetooth drivers, or recalibrate the internal sensors. It can show symptoms precisely enough to decide whether to update firmware with manufacturer software, change a cable, clean a control, adjust deadzone settings, or test another browser.
Diagnostic Glossary
Standard mapping
A browser layout where common buttons appear in predictable Gamepad API indexes.
LT and RT
Analog triggers that may report proportional values instead of simple pressed states.
Player slot
The browser index used when more than one controller is connected.
Questions Users Ask
Short answers for common diagnostic decisions on this page.
Does this Xbox controller test work over Bluetooth?
Usually, yes. Bluetooth behavior depends on firmware, operating system, and browser support, so USB is a useful comparison when results look unstable.
Why do Xbox triggers appear as buttons?
The Gamepad API often exposes analog triggers as button entries with values from zero to one. The tester displays those values directly.
Can I test multiple Xbox controllers?
Yes. Use the P1 to P4 selector to switch browser slots when more than one controller is connected.
Useful Next Checks
Run a stick drift test
Check idle offset and deadzone before changing in-game sensitivity.
Test vibration motors
Run user-initiated haptic patterns when the browser exposes rumble.
Inspect button mapping
Confirm indexes, labels, analog values, and unusual layouts.
Read troubleshooting paths
Fix detection, Bluetooth, permission, browser, and mobile issues.