Controller / Gamepad Test

How to Use This Test

1. Connect your controller via USB cable or pair it via Bluetooth.
2. Press any button on the controller — the browser only detects gamepads after the first input, so nothing shows until you do this.
3. Press each button one at a time. Working inputs light up green on the on-screen diagram.
4. Squeeze each trigger from rest to full press. The readout should go from 0.00 at rest to 1.00 fully pressed.
5. Move each analog stick through its full range in all directions, then release. Watch the resting value return to near 0.00.
6. Leave the sticks completely untouched and watch the resting values for 10 seconds — any consistent drift from 0.00 indicates stick drift.

What Your Results Mean

All buttons light up on press: Every button's microswitch and firmware mapping are working correctly.

A button doesn't register: The internal contact is worn, the button is stuck, or the firmware hasn't mapped that input. A button that physically clicks but doesn't register usually has a failed switch.

Trigger shows a non-zero value at rest: Trigger drift — the sensor reports a small value even when fully released. This can cause unintended acceleration in racing games or actions that fire without deliberate input.

Stick resting value consistently above 0.05 in any direction: Stick drift — the potentiometer is worn and sending a signal at rest. Values above 0.05 cause noticeable unwanted movement in most games. Values above 0.15 cause obvious constant movement.

Stick doesn't reach 1.00 in all directions: The stick range is limited — possibly from calibration drift or mechanical wear.

D-pad direction intermittent: On a digital D-pad, any direction that sometimes works and sometimes doesn't indicates a worn contact pad.

Common Problems and Fixes

Controller not detected despite being connected

Press a button first — always required. Then check: USB cables must be data-capable (some USB-C cables carry power only). For Bluetooth, confirm it's paired in your OS settings. On Windows, open joy.cpl from the Run dialog to confirm Windows itself detects the controller independently of the browser.

PlayStation or Switch controller not recognized properly

PS4 and PS5 controllers work in Chrome and Edge over USB and Bluetooth. For using these in PC games, Steam Input provides the best compatibility. Nintendo Switch Pro Controllers work in most browsers but may need a button press to activate.

Stick drift on one or both sticks

Blow compressed air into the base of the affected stick from several angles first. If drift persists, apply a small amount of electronic contact cleaner around the stick base while working the stick through its range. Persistent drift that returns after cleaning means the potentiometer is mechanically worn and the stick module needs replacing.

Trigger non-zero at rest after reset

Use the controller's reset button (small pin-hole on the back of most controllers) and recalibrate. If the trigger value remains non-zero after a reset, the trigger mechanism or sensor has sustained wear.

Button registers inconsistently

Disassemble if comfortable and clean the contact pads or PCB under the button with isopropyl alcohol on a cotton bud. Intermittent inputs on modern controllers are often caused by contact corrosion from humidity.

Why This Test Matters

Stick drift is frustrating precisely because it's intermittent at first. Your camera drifts slightly. Your character veers. You second-guess your own input. This test shows you exactly how much drift exists, in which direction, and on which stick — answering the question definitively before you spend hours troubleshooting elsewhere.

Testing before buying a second-hand controller is the most direct use. A 60-second full input test here catches drift, dead buttons, and trigger issues that sellers may not disclose.

Why Controller Problems Happen

Most controller issues come down to detection, drift, or mode — these six causes account for nearly all of them.

1. It isn't detected at all. The browser's Gamepad API only sees a controller after it sends input, so press any button first. If it's still invisible, the cable may be charge-only rather than data-capable (a very common culprit), or Bluetooth hasn't paired. On Windows 11 24H2 you can confirm the OS sees it: press Win+R, type joy.cpl, and check it appears under game controllers.

2. Stick drift. A resting stick value that won't sit at 0.00 means drift — debris or oxidation on the potentiometer, or mechanical wear. Values above about 0.05 cause unwanted movement in games. Compressed air and electrical contact cleaner fix many cases; worn modules need replacing.

3. The wrong input mode. Some controllers (many 8BitDo and third-party pads) have a mode switch between Xbox/XInput and DirectInput, and the wrong one makes buttons map oddly or vanish. And on a PC, Steam Input can quietly remap everything — see the next section.

4. Bluetooth latency or dropouts. Low battery and 2.4 GHz interference cause lag and disconnects. Charge it, move closer, and re-pair. A wired connection rules this out instantly.

5. A trigger or bumper not registering. Analog triggers wear and bumpers collect grime. The live trigger values on this page show whether they sweep smoothly from 0 to 1 or stick.

6. Vibration won't fire. Browser rumble support varies — Chrome and Edge on Windows usually work, other combinations often don't — so no rumble here doesn't prove the motors are dead. Updating controller firmware (the Xbox Accessories app, or Sony's PC updater for a DualSense) resolves some genuine motor and connection faults.

It Works Here But Not in My Game or Steam

If every button and stick responds on this page, the controller hardware is fine, and a problem inside a game is configuration. The biggest source of confusion is Steam Input: with it enabled, Steam intercepts the controller and presents a remapped virtual one to the game, which can override your expected layout entirely.

If a game behaves strangely, open its controller or key-binding menu and check the mappings, then in Steam right-click the game → Properties → Controller and try toggling Steam Input off (or on) to see which the game prefers. Many PC games expect the Xbox/XInput standard, so a PlayStation or third-party pad in the wrong mode can misbehave until you switch it or let Steam translate it. Because this page reads the raw Gamepad API with no remapping, it's the clean reference: pass here, and the fix lives in the game or in Steam.

How to Get the Best Controller Results

1. Press a button to wake it. Nothing appears until the controller sends its first input — this is the number one reason people think a working pad is "not detected."
2. Use a known data cable. Test wired with a cable you know carries data, which removes Bluetooth from the equation entirely.
3. Read drift with hands off. Let both sticks rest untouched to see their true resting values, then nudge and release to confirm they snap back to centre.
4. Match deadzone to drift. For minor drift under 0.05, a small in-game deadzone hides it; above that, clean or repair the stick rather than masking it.
5. Update firmware. Xbox controllers update through the Xbox Accessories app; a DualSense updates via Sony's PC tool. This fixes a surprising number of connection and rumble quirks.
6. Disable Steam Input when testing raw hardware. So you're seeing the controller itself, not Steam's remapped version.

Frequently Asked Questions

Next: Test your mouse →