Skip to content
SavedCompare

Controllers / Tester

Controller diagnostics.

See your inputs. Run a check. Understand what happens.

No account or installation neededSomething not responding? Get help ↓
Checking browser support…
Inputs stay on this device
Your controllerConnect a controller to identify the input connection.Connection not specified Setup & model

Once the browser sees your controller, its reported name and available inputs appear here.

Your model selection adds context; it does not change the browser’s input mapping. A reconnect starts a new connection record.

INPUT MONITOR

See every movement.

NO SIGNAL

Connect. Press. Test.

Connect a controller to this device, then press a face button to make it visible to the browser.

  1. 1USB, receiver or Bluetooth
  2. 2Press a controller button
  3. 3Choose a guided check
Controller not appearing? Connection help ↓

Vibration support depends on the controller, connection and browser.

SESSION NOTEBOOK

What the checks recorded

Up to 12 recent checks. Download a report to keep them after leaving this page.

No checks recorded yet

Start with a rest check, move both sticks, then test the buttons. Each result includes the observed values and your connection setup.

WHEN SOMETHING DOESN’T RESPOND

What to check next

Start with the symptom you can reproduce.

No controller appears
  1. Keep this page visible and press a face button on the controller. Connecting it alone may not expose it to the browser.
  2. Confirm your computer or phone has connected to it. For USB, use a cable that carries data, not only power.
  3. Check your controller’s documented mode for this device. Reconnect after changing modes, then press a button again.
  4. Try an up-to-date browser or a different supported connection. On iPhone, pair in Bluetooth settings first; supported models and features depend on iOS and the browser.

A controller that does not appear here is not necessarily broken. This page cannot pair a device for you.

How browser detection works ↗
A stick moves while untouched
  1. Place the controller on a steady surface. Run the five-second rest check without touching either stick.
  2. Move both sticks and release them, then repeat. Compare the observations under the same connection and settings.
  3. Check the confirmed model’s official calibration and firmware instructions. Any deadzone adjustment must be made in the game or supported controller software; this page does not change it.

Small offsets alone do not establish a defect. Firmware, drivers and remapping software may change the values reaching this page. Zero movement here does not rule out a problem in another mode or game.

A button or trigger does not respond
  1. Use the button check and press each input slowly, then release it. Watch for an input elsewhere on the map.
  2. Review any remapping or trigger-stop settings you intentionally enabled.
  3. If the browser has no standard mapping, use the numbered raw inputs. Back paddles and system buttons may duplicate another button or be unavailable independently.
  4. Compare with the manufacturer’s input test, if offered for your model.

“Not recorded” means the test did not observe the action. It is not a failed hardware diagnosis.

It works here, but not in my game

This confirms that this browser receives inputs in the current setup. It does not confirm that a particular game supports that setup.

  1. Check the game’s supported controller and input settings.
  2. Review Steam Input or any other remapping tool you use. Change one setting at a time and retest.
  3. Use the connection mode documented for your model and platform.
The controller disconnects or vibration is unavailable

Check charge, cable and pairing, then compare a supported wired connection if available. Repeat interrupted checks; they are not marked complete.

Vibration needs support from the controller, connection and browser. An unavailable or interrupted request does not identify a motor fault.

Browser vibration support ↗
What this test can and cannot tell you

Measurements describe inputs exposed to this page. No software deadzone is applied by the tester. The controller, driver or browser may already have processed them.

We do not measure physical input latency, certify hardware polling rates, verify authenticity, identify stick sensor technology or predict remaining life. There is no universal pass/fail score.

Standard mapping follows browser positions; printed button names can vary. A manually confirmed model helps you find documentation and does not override the browser’s mapping.

Controller inputs and notes stay in this page’s memory until you leave or reload. Export only if you want a local copy. The report includes the browser-reported name, your notes and observed values. It is not uploaded by this tool.

Gamepad API specification ↗