Xbox 360 Controller Tester
Connect a controller and press any button — every input is detected and displayed live.
Connect a controller and press any button
Browsers hide gamepads until first input. Plug in via USB or pair over Bluetooth, then press any button to wake the test. On phones, pair the controller in your system Bluetooth settings first.
Buttons
Analog sticks
Circularity test
Rotate a stick around its full rim — we trace the path against a perfect circle.
How it works
The Xbox 360 controller is still one of the most-used PC pads years after the console's end of life, thanks to bulletproof XInput support. But its age shows in two places the tester exposes immediately: an imprecise D-pad and quirky trigger reporting on some drivers.
How to connect your Xbox 360 Controller
Wired USB, or the dedicated Xbox 360 Wireless Receiver for wireless pads. No Bluetooth support.
How the Xbox 360 Controller maps in your browser
Wired pads and official Wireless Receiver units map cleanly to XInput. On some Linux drivers the two triggers report as a single shared axis rather than two independent 0–1 values — if pulling one trigger moves the other's reading, that is the driver, not the pad.
Thumbstick type and drift risk
Early potentiometer sticks with a concave cap. Drift is age-related here; many surviving pads have already had one stick replacement.
Wired pads draw from USB; wireless pads use 2×AA or a battery pack and need the dedicated receiver — there is no Bluetooth.
Known issues and quirks
The D-pad is notoriously imprecise. Triggers report as a combined axis on some Linux drivers.
Once connected, press any button and the tester will detect the pad automatically. Check every button and trigger registers, watch the stick crosshairs for centering, and run the circularity test to quantify stick wear. Suspect drift? Run the dedicated controller drift test for a 10-second automated verdict.
Testing every part of your controller
Browsers hide gamepads until you press a button, so tap any button once to wake the connection. From there, every button, trigger, analog stick and (on supported hardware) vibration motor is displayed live. It works with anything your OS recognizes as a gamepad — Xbox, PlayStation DualShock 4 and DualSense, Switch Pro, and most generic USB or Bluetooth pads.
What to check, and what's normal
| Element | Healthy behavior | Warning sign |
|---|---|---|
| Face & shoulder buttons | Register instantly, release cleanly | Sticky, missed, or double inputs |
| Analog sticks (at rest) | Under 1–2% jitter around center | A constant offset = drift |
| Triggers | Smooth 0–100% travel | Jumps to 100% or won't reach it |
| Vibration | Rumbles on command (Chromium pads) | Silent on Safari/Firefox = browser limit, not the pad |
Troubleshooting connections
- Nothing appears: press any button first; if still hidden, try another USB port or re-pair Bluetooth and reload.
- Layout doesn't match your pad: unknown models fall back to a generic view, but every button and axis is still shown by index — you can fully test it.
- Vibration does nothing: rumble over the web works on Chromium browsers with most Xbox and DualSense pads; Safari and Firefox have limited or no support.
If the sticks jitter beyond a couple of percent at rest, run the dedicated controller drift test for a measured verdict.
Troubleshooting
› My controller is connected but nothing shows
Browsers hide gamepads until you press a button — press any button once. If it still doesn’t appear, try a different USB port or re-pair Bluetooth, then reload the page.
› Vibration test does nothing
Vibration via the browser works on Chromium browsers with most Xbox and DualSense pads. Safari and Firefox have limited or no support — that is a browser limitation, not your controller.
› The layout doesn’t match my controller
Unknown models fall back to a generic layout. Every button and axis is still shown by index, so you can fully test the pad even without a matching picture.
Frequently asked questions
› Which controllers are supported?
Anything your OS recognizes as a gamepad: Xbox (360/One/Series), PlayStation DualShock 4 and DualSense, Switch Pro, and most generic USB or Bluetooth pads.
› Do I need to install anything?
No. The test uses the browser’s built-in Gamepad API — just connect your controller and press a button.
› Why do axis numbers jitter slightly at rest?
Analog sticks always have a little electrical noise, typically under 1–2%. Constant offsets beyond that suggest drift — run the dedicated drift test.
› Can I test controller vibration?
Yes, on Chromium-based browsers with supported pads. Click the vibration button; if nothing happens, your browser or pad doesn’t expose rumble to the web.
Common Xbox 360 Controller problems and how to read them
These are the faults reported most often for the Xbox 360 Controller, what causes each one, and how to confirm it in the tester above before you spend money on a repair or replacement.
| Symptom | Cause | What to do |
|---|---|---|
| D-pad registers the wrong direction | The 360 D-pad is famously imprecise — a single stiff disc that rocks unpredictably. | Expected behaviour, not a defect. Roll slowly and watch which direction lights; if diagonals are unreliable, that is the known design flaw. |
| Wireless pad never appears | No Bluetooth — it needs the proprietary Xbox 360 Wireless Receiver. | Plug in the receiver (or use a wired pad). Confirmed working if a wired 360 pad registers here but the wireless one does not. |
| Both triggers move together | Combined-axis trigger reporting on older/Linux drivers. | Test in Chrome on Windows, which reports the triggers separately. A driver limitation, not stick or trigger wear. |
Testing tip: If the pad is wired via a cheap third-party cable and drops out, the cable is usually charge-only — swap to a known data cable before assuming the pad is faulty.