Skip to content

Controller Input Test

Watch every reported input stream update as you move — useful for spotting dropouts and odd mappings.

Start testing Read guide
Controller Input Test

Live input stream

A broad input overview across buttons, sticks, triggers, and axes.

See the whole input stream at once

The Controller Input Test is built for players who want a continuous picture of buttons, axes, and connection metadata while they move. It is useful during troubleshooting sessions where a single sticky bumper and a noisy left stick appear together. Start here when you are unsure which subsystem fails, then branch into Analog Stick Test or the button-focused tools once the pattern is clear.

Because the Gamepad API is a browser abstraction, timestamps, pose data, and vendor haptic channels may be missing even when the controller works perfectly in native games. Treat blank optional fields as API limits, not proof of a broken pad. Wired USB often yields stabler polling than Bluetooth on busy radios.

Practical workflow example

  1. Connect the pad and press Start or Options to wake detection.
  2. Watch axes while the sticks rest; idle should stay near center.
  3. Hold LT and RT independently to confirm separate trigger channels.
  4. Rotate the D-pad and note whether diagonals double-fire unexpectedly.

If idle axes wander, continue with Stick Drift and optionally tune visualization on Deadzone. For brand-specific DualSense checks, the PS5 Controller Tester adds PlayStation-oriented framing without claiming firmware writes.

FAQ: why do values jump when I alt-tab?

Many browsers throttle background tabs. Keep the tab focused during measurement. Exclusive capture from Discord overlays or some launchers can also interrupt Gamepad API updates until you reconnect.