Use this troubleshooting tree when a gamepad tester misbehaves. Work top down: detection first, then buttons, then sticks, then rumble and mapping. Skipping ahead wastes time because stick drift and deadzone pages cannot help if the browser never lists the pad. Keep the Controller Tester and Controller Detection tabs handy while you isolate the fault.
Nothing detected
Follow Controller Not Detected. Press a button after connecting, prefer USB, close exclusive apps, and retry a current desktop browser. Confirm the OS sees the device before you blame the site. Mobile browsers often lack solid Gamepad API support. After the pad appears, retest on the main controller tester so you know the snapshot is live.
Buttons work, sticks drift
Open the Stick Drift Test with thumbs off the sticks. Persistent idle magnitude points to hardware wear. Clean carefully, compare cables, and avoid treating a large deadzone as a permanent fix. Read How to Fix Stick Drift and visualize gates on Deadzone. The companion article Deadzone Explained clarifies why masking drift hurts aim quality.
Rumble missing
Try Vibration over USB in Chromium. Bluetooth paths and Firefox builds vary. Missing browser rumble does not always mean broken motors, because the Gamepad API vibration actuator is optional and inconsistently implemented. If motors work in a native game but not in the browser, treat it as an API or browser limit, not instant hardware failure. Background on those limits is in Gamepad API Explained.
Weird labels or indexes
Unknown mapping means you should trust indexes over Xbox or PlayStation names. Press each control once and write down the index that lights up. Generic DirectInput pads and some Bluetooth modes show this often. Remap inside the game after you confirm every physical control still reports a value on the tester.
PC-specific quirks
On Windows, finish Bluetooth pairing, avoid Game Bar conflicts, and compare wired versus wireless on the PC Controller Tester. More PC context is in Controller on PC. Still stuck after OS visibility is confirmed? Switch browsers, reconnect wired, and verify Device Manager or the system Bluetooth panel first. Extra case notes appear on the blog.
Good troubleshooting is boring on purpose: prove detection, prove each input family, then decide whether the fix is software settings or hardware repair. A calm pass through this tree turns confusing gamepad tester symptoms into a short list of actions you can finish in one sitting.
Related reading
- Controller Vibration Not Working
- How to Check Stick Drift
- How to Test a Controller After Repair
- Controller D-Pad Not Working: Test & Fix
Branch: buttons not registering
When some buttons work and others do not, open the Controller Button Test and press every control once, watching which index lights up. If one button stays dark across browsers and cables, that button's switch or membrane is the suspect — a hardware fault, not a setting. If no button responds at all, you are back at detection, not at buttons: check mode, cable, and exclusive locks first. If a bumper or trigger responds but with the wrong label, trust the index, not the name — generic pads and alternate modes report indexes that games then remap. Confirm every physical control reports a value before you remap anything in a game, or you will chase a mapping problem that is actually a dead input.
Branch: triggers not reaching full range
Triggers are analog, so they can fail halfway: they register, but never reach full value. On the Controller Tester, pull each trigger slowly to its stop and watch the reported value. A healthy trigger climbs smoothly to 1.00. One that stalls around 0.70 or jumps in steps has a range or spring problem, or a game threshold set too high. Compare both triggers — if one reaches full range and the other does not, the weak one is the story. Trigger issues are easy to misread as stick problems in racing and shooting games, so check trigger range before you touch stick settings.
Branch: only one stick misbehaves
Always compare sticks. If the left stick drifts and the right is clean, the fault is almost certainly that one module — sticks wear independently, and most games load one side harder. If both sticks misbehave identically, suspect something shared instead: the cable, the Bluetooth link, the mode, or a desk vibration lifting both readings. Test each stick alone on the Analog Stick Test, note both idle values, and only then decide whether you are fixing one module or fixing the connection.
Branch: works in one browser only
A pad that works in Chrome but not Firefox (or the reverse) is telling you the fault is software, not hardware. The usual suspects are a script-blocking extension, an outdated build, a private window behaving differently, or another app holding exclusive access in one session. Test in a clean profile with extensions disabled: if the pad appears there, re-enable extensions one at a time until the culprit returns. If it works in no browser on one PC but works on another PC, the first PC's OS side — drivers, Bluetooth stack, or port — is where to look next.
Branch: disconnects mid-session
A pad that connects, then drops during play, usually has a power or link problem rather than a sensor problem. Work through these in order: a loose or charge-only cable, a front-panel port or unpowered hub, a dying battery or a Bluetooth dongle too far from the pad, wireless interference from nearby USB 3.0 devices, and the pad's own sleep timer. Wired play on a rear motherboard port removes most of these variables at once. If disconnects survive a known-good cable and port, test the pad on a second device — a fault that follows the pad is hardware, one that stays with the PC is the PC's Bluetooth or USB stack.
The 10-minute isolation protocol
Run the tree on a timer and you will stop going in circles. Minutes 0 to 2: detection — does the Controller Detection page list the pad after a button press? Minutes 2 to 5: buttons — does every control light its index on the Controller Button Test? Minutes 5 to 8: sticks — do both sticks idle near zero on the Stick Drift Test and reach full travel on the Analog Stick Test? Minutes 8 to 10: rumble and mapping — does the Vibration Test pulse, and do labels match indexes? End with one written verdict: detection, button, stick, rumble, or mapping — and fix only that layer. A verdict you write down beats an hour of random setting changes.
When to stop troubleshooting and replace
Not every pad is worth saving, and knowing when to stop is part of troubleshooting. Replace or return the pad when the fault reproduces across cables and browsers, when idle offset stays high after cleaning and careful retests, when a stick or trigger has physical damage or a broken spring, or when a module replacement costs more than the pad is worth. For a used purchase, decide inside the return window: run the full protocol, keep the readings, and return a pad that fails it rather than hoping a setting will rescue worn hardware. For a beloved pad, a module swap is reasonable — but only after the tree has proven the fault is that module and nothing else.
Frequently asked questions
Should I test with a game or a browser tester first?
The browser tester first. Games add deadzones, aim assist, and remapping on top of raw input, which hides faults. The browser shows raw Gamepad API values, so a fault visible there is real, and a fault invisible there is probably a game setting.
My pad works on console but not on PC browser — is it faulty?
Not necessarily. Consoles and PC browsers reach the pad through different stacks, modes, and exclusive-access rules. Check the controller's mode switch, close Steam and wrapper tools, confirm OS visibility, and retest on the Controller Detection page before concluding anything about the hardware.
How do I know if a fault is software or hardware?
Change one variable at a time. A fault that follows the pad across cables, ports, browsers, and PCs is hardware. A fault that appears in only one app, one browser, or one mode is software — a setting, an extension, a lock, or a mapping.