Connect, wake, and test

Connect by USB, Xbox Wireless adapter, or Bluetooth as supported by your system. Then start monitoring and press a controller button so the browser can expose it.

  1. 1Choose Start monitoring, then press A or another button.
  2. 2Test each control while watching both the Xbox-position view and raw values.
  3. 3Clear the session before a repeat pass so coverage and observed ranges start fresh.

Ready. Start monitoring, then interact with a connected controller.

Capability and privacy details

This tool uses only the browser Gamepad API after you choose Start. It reads the browser-reported controller ID, mapping, buttons, axes, connection state, and optional vibration actuator. The API usually opens no permission dialog, but a browser can withhold controllers until a button press or block the API by policy. Readings, samples, and the recent-input list stay in this page and are not saved by this tool. A rumble command is sent only when you choose its button. Monitoring and rumble stop when you stop, reset, leave, or hide the page.

Live browser readings

The reported ID is shown verbatim and does not independently prove make, model, connection type, or authenticity.

Browser-reported ID
—
Mapping
—
Buttons
—
Axes
—

Waiting for a controller. The Xbox-position diagram stays unavailable until the browser reports a standard mapping.

Xbox-position input map

The dashed rings show your chosen comparison threshold, not a game or hardware dead zone.

Waiting
Start monitoring and press a controller button. Xbox-position labels will appear only for a standard mapping.

Neutral stick observation

For a standard mapping, leave both sticks untouched during a three-second session sample. Results describe browser-reported values after any platform processing; they do not diagnose the controller.

No neutral sample yet.

Optional rumble command

If the browser exposes a dual-rumble actuator, you can send one short command. Browser support varies by controller, driver, platform, browser, and connection.

Connect a controller to check browser-exposed rumble support. Command completion cannot measure motor strength.

Raw controls and observed ranges

Buttons

Browser index, pressed flag, and analog value from 0 to 1.

No button readings yet.

Axes

Live values from −1 to +1 and min/max observed this pass.

No axis readings yet.

A useful Xbox test pass

  1. Buttons and D-pad: press and release each once; confirm the expected control changes and returns to zero.
  2. Triggers: pull LT and RT slowly; watch the analog value rise and note the session range.
  3. Sticks: move each through its edges and a circle, release it, then run the neutral observation without touching it.
  4. Repeat: clear the session and repeat. If relevant, compare USB and wireless connections separately.

What the browser cannot prove

  • A standard map describes control positions, not controller brand. A compatible non-Xbox pad can use it too.
  • Unmapped devices can reorder buttons or axes, so this tool uses raw indices and withholds Xbox labels in that state.
  • The browser or operating system may normalize, filter, or omit inputs. The Xbox/Home and Share buttons are often unavailable to pages.
  • This page does not measure hardware latency, USB/Bluetooth report rate, electrical sensor output, battery health, or game-specific dead zones.
  • An unusual value, missing rumble command, or short sample is an observation—not proof of a defective controller.

If a result is unexpected, reconnect the controller, close software that may capture or remap gamepad input, repeat the pass, and compare with Windows controller settings or the manufacturer’s official utility before considering repair.