Gamepad Tester

How to use

1. 1Plug your controller in over USB, or pair it over Bluetooth from your operating system settings.
2. 2Press any button on the pad so the browser wakes the connection. Connected pads appear as a Pad #N chip at the top.
3. 3Pick a pad to inspect. The active card shows ID, mapping, button and axis counts, and whether the pad exposes vibration.
4. 4Move sticks and pull triggers to see the live button grid, the analog stick squares, and the per-trigger percentage bars.
5. 5Drag the deadzone slider to preview filtered stick values, and read the press / release log to catch ghost inputs or stick drift.
6. 6Click Vibrate for 600 ms to confirm haptics work (when supported), or Copy snapshot to grab a full report for a bug ticket.

About this tool

Gamepad Tester reads every controller your browser exposes through the HTML5 Gamepad API and turns the raw state into a live, readable diagnostic. Plug in an Xbox, PlayStation (DualShock or DualSense), Switch Pro, 8BitDo, Stadia, Logitech, racing wheel, arcade stick, or any generic HID pad over USB or Bluetooth, then press any button to wake the connection. The tool lists every detected pad with its index, vendor and product ID, connection state, and the standard mapping flag (the W3C remapping so button 0 is the bottom face button on every brand). Buttons are shown in a grid that highlights green the moment they go pressed and reverts when released, and analog inputs (the LT and RT triggers, plus any pad that exposes intermediate values) render a live percentage bar from 0 to 1 so you can see exactly how far a trigger is pulled. Two square stick views plot the left and right analog sticks in real time. A deadzone slider from 0.00 to 0.50 lets you preview filtered axis values so you can compare raw drift against the filtered output a game engine would actually feed your code. A press and release event log captures the last 30 transitions per pad with the button index and standard label, useful for catching ghost inputs, sticking buttons, hair-trigger misfires, and stick drift that ranges across the dead zone. When the connected controller exposes vibrationActuator.playEffect (modern Chromium and Edge for Xbox, DualShock, and DualSense pads), a Vibrate for 600 ms button runs a full dual-rumble pulse so you can confirm the haptics work end to end. All polling runs inside a requestAnimationFrame loop that idles automatically when no input changes, so the tool stays smooth on a laptop on battery. Everything runs locally; the Gamepad API does not contact a server and this page does not upload, log, or transmit any of the input. Common uses: confirming a controller is recognised by Windows, macOS, or Linux without installing a vendor app; checking stick drift before sending a controller back under warranty; verifying that a new bluetooth pairing exposes vibration; mapping a generic pad before writing keybindings; and giving QA testers a quick way to repro a controller-specific bug with a copyable snapshot.

Free to use. Works in your browser. No signup, no login.