A reliable controller check starts with a browser-based gamepad tester that reads live input through the Gamepad API. You do not need to install drivers for a basic pass or fail. Open the Controller Tester (or the homepage Gamepad Tester) in a current desktop browser, then work through the steps below so you know whether the pad is healthy before you blame a game or a PC setup.
Prepare the connection
Plug in with USB when you want the most stable path, or finish Bluetooth pairing in the operating system first. Many pads stay silent until you press a face button, so wake the device after it appears in Windows, macOS, or Linux. Close overlays and exclusive capture tools that sometimes lock the device. If the pad never shows up, jump to Controller Not Detected and the dedicated Controller Detection page.
Confirm identity and mapping
Once the status card lists a name, mapping string, button count, and axis count, you have proof the browser sees the hardware. Standard mapping usually means Xbox-style indexes. Unknown mapping is still usable: press each control and note which index lights up. The PC Controller Tester is a good second stop when you are validating a Windows setup specifically.
- Connect USB or complete Bluetooth pairing, then press any button to wake detection.
- Confirm name, mapping, button count, and axis count on the status card.
- Press every face button, bumper, stick click, and menu button while watching pressed and released states.
- Sweep both sticks through their full circles and return to center; note any idle offset.
- Pull each trigger from rest to full press and check for smooth analog travel.
- Optional: run Stick Drift, Deadzone, and Vibration for focused checks.
Interpret stick and trigger results
Healthy sticks rest near zero when untouched and reach near the edge of the plot when pushed hard. A stick that creeps while idle is a classic stick drift signal; confirm it on the Stick Drift tool before you change in-game settings. Triggers should climb steadily. Sudden jumps or stuck values often mean a dirty or worn sensor, not a software bug. Vibration support depends on the browser and connection: USB plus Chromium is usually the best chance to feel rumble. Missing rumble in the browser does not always mean dead motors.
When to dig deeper
If buttons work but aim feels wrong, combine this checklist with How to Fix Stick Drift and Deadzone Explained. For a plain explanation of what the browser can and cannot do, read Gamepad API Explained. Browse more how-tos on the blog when you need PC-specific or model-specific notes. A careful gamepad tester session saves hours of guessing whether the problem is the controller, the cable, or the game.
Related reading
- How to Test a Controller After Repair
- How to Check Stick Drift
- Controller D-Pad Not Working: Test & Fix
Before you start: the 2-minute setup
Two minutes of setup saves twenty minutes of confusion. Use a current desktop browser — Chromium, Firefox, or Safari — because mobile browsers expose gamepads weakly or not at all. Close games, Steam, wrapper tools, and overlays that can lock the pad exclusively, then connect over USB where possible: it is the most stable path for detection, sticks, and rumble alike. If the pad is wireless, check its charge first — a low battery causes dropouts that look exactly like hardware faults. Finally, press a face button after connecting: browsers require that gesture before they list any pad, and a never-pressed controller will stay invisible no matter how perfect the rest of the setup is. Confirm the pad appears on the Controller Detection page, then move to the full check.
Pass and fail criteria for each input family
A test without pass and fail lines is just playing around. Use these:
- Buttons: every button, bumper, stick click, and menu button should show a clean pressed and released state on the Controller Button Test, with no sticking and no double-triggering from a single press. A button that stays lit after release, or needs several presses to register, fails.
- Sticks: both sticks should idle near zero with thumbs off on the Stick Drift Test, travel smoothly to the rim in full circles on the Analog Stick Test, and return to center when released. Creep at rest, a flat spot in travel, or a stick that does not return to center fails.
- Triggers: each trigger should climb smoothly from 0 to 1.00 with no jumps and no stall below full value. A trigger that jumps in steps or stops at 0.70 fails the range check.
- D-pad: all four directions plus diagonals should register cleanly. A diagonal that only fires as a single direction, or a direction that sticks, fails.
- Rumble: a weak and a strong pulse should both be felt on the Vibration Test over USB in Chromium. No pulse at all fails only after you have confirmed USB, Chromium, and detection — Bluetooth silence alone is not a failure.
Your test report card
Write the results down — a test you cannot show anyone is worth half as much. Keep one short record per pad: model, connection type (USB or Bluetooth), browser, date, and one verdict per family (pass, fail, or note), plus the worst idle value for each stick. That card serves four purposes: warranty claims, repair-shop explanations, sale listings where a documented healthy pad sells faster, and return-window decisions on used pads. Retest under the same conditions after any cleaning, repair, or firmware update, and compare the new card with the old one — the comparison, not your memory, is the proof the fix worked.
Testing a used controller before you buy
Never pay for a used pad before a five-minute pass. Run detection first: if the pad never appears, walk away until the seller fixes the connection. Then press every button, check both sticks for idle creep and full travel, pull both triggers to full value, and try a rumble pulse. Red flags that should stop a purchase or cut the price hard: drift on either stick, a sticky or dead button, a trigger that cannot reach full value, disconnects during the test, or a seller who will not let you test at all. A pad that passes everything is worth the asking price; a pad that fails one family is worth the asking price minus the repair — and a pad that fails detection is worth nothing until it is proven otherwise.
After the test: what to do next
Let the verdict choose the next step. Everything passes: play, and retest monthly or after any drop, repair, or trip. One family fails: follow the focused guide for that family — drift goes to the stick drift guides, detection failure goes to the detection guide, rumble trouble goes to the vibration guide, and deadzone questions go to the deadzone guides. Detection fails entirely: do not test sticks or buttons yet, because every later reading is meaningless until the browser lists the pad. Whatever the outcome, keep the report card — a dated record turns the next troubleshooting session from guesswork into a comparison.
Frequently asked questions
How long does a full controller test take?
Five to ten minutes for a complete pass: detection, every button, both sticks, both triggers, and a rumble pulse. A quicker two-minute pass (detection plus sticks) is enough for a routine health check.
Do I need to install anything to test a controller?
No. Browser testing reads live input through the Gamepad API with nothing to install — that is the point. Desktop apps and vendor tools add deeper features, but diagnosis starts in the browser.
Can I test multiple controllers?
Yes. The homepage tester supports up to four controller slots at once, so you can compare pads side by side or test a second pad without unplugging the first. Record each pad's results separately.
Can I test on my phone?
Only weakly. Mobile browsers expose gamepads inconsistently, and many pads will not appear at all. For any verdict that matters — a purchase, a warranty claim, a repair decision — retest on a desktop browser first.