Connect a controller over USB or Bluetooth and press any button to wake it up.
Controller Info
Live Stats
Why AI Cannot Test Your Gamepad
The AI chatbot you chat with has no physical wires to the buttons or the potentiometers inside your controller, so it cannot tell you whether one button is dead, how far an analogue stick really travels, or whether it is sitting off-centre while you are not touching it. Stick drift, a worn trigger, or an unresponsive face button are hardware facts that only appear in the raw input your browser gets directly from the controller. This tester reads that data, lights up the exact control that fired, measures range and drift numerically, and hands you a deterministic pass, fail report you can show a repair shop or use for a warranty claim.
Every Button, Live
Face buttons, shoulder buttons, triggers, D-pad, sticks and system keys light up the moment they register
Stick Range & Drift
Per-stick max range, resting offset and drift measured against a configurable threshold
Trigger Sweep
LT and RT tracked to the percentage of a full press to catch worn trigger sensors
Exportable Report
Copy, TXT, CSV or JSON output with tested, untested and diagnosis data for support and warranty
How the Gamepad Tester Works
- Connect and wake it - plug the controller in over USB or pair it over Bluetooth, then press any physical button. The browser quietly waits for that one press before exposing the pad.
- Feed the buttons - work through every button once at a normal pace. The matching spot on the controller diagram turns green and the tested counter climbs, while the event log times each press.
- Sweep the sticks and triggers - rotate each stick in a full slow circle to see the live gauges reach the outer ring, then pull each trigger to the end of its travel. The tool records the largest range each control reached.
- Run the drift check - in the guided test, after the circle runs leave each stick untouched for two seconds. A resting offset above the threshold is announced as drift, which most usually means a worn pot or a dirty contact.
- Read the verdict and export - the diagnosis covers untested buttons, short stick range, low trigger percent, and measured drift. Download the TXT, CSV or JSON report and attach it to a return or warranty claim.
Why does my controller only show up after I press a button?
The W3C Gamepad API is privacy aware: a connected pad stays hidden until a physical button press proves a human is there. This is standard behaviour in every browser and keeps websites from detecting your device without consent. One press is enough, and the pad stays connected for the whole test.
How accurate is the drift reading?
The resting offset is read directly from the analog axes while the stick is not being touched, reported as a percentage of the full centre to edge travel. A brand-new controller usually rests well under 5%, while drifting pads sit closer to or above the 15% default threshold. Browser and controller drivers add a little noise, so rest the stick for a full two seconds before judging it.
My trigger only reaches 60% - is it worn?
A healthy analogue triggers should reach 100% of its travel when pressed to the stop. If a trigger makes it say 60-80% no matter how hard you press, the trigger sensor or the spring behind it is likely worn or misaligned. The report records the maximum percentage it reached so the shop can check it against the good side.
Why do the button names on this layout look different from my controller?
The diagram follows the common Xbox-style standard labels because most pads map to 0-16, A on index 0, B on 1, X on 2, Y on 3, D-pad on 12-15 and the sticks on their own axes. A Switch Pro or a PlayStation paddle wears different cap names but the underlying indices are the same. Compare by the physical shape: the tests, and press each cap once even if the label on screen does not match the print on the pad.
Can the online tool corrupt or spy on my controller?
No. Everything uses the Gamepad API that browsers expose, and the tool never uploads anything. All the button and axis data stay in your browser tab and the report is generated locally. There is no telemetry, no account, and the page works offline if you cached it.
Can I test several controllers at once?
The test focuses on a single pad at a time for a clean verdict, but the browser can see multiple controllers at once. Change which controller is selected with the drop-down if you see more than one name in the device info, and test a second controller the same way to compare conditioned before any used pad you buy.
Does this work on a laptop or a Chromebook?
Yes, whenever the browser supports the Gamepad API, and Chrome, Edge and Firefox on desktops support it best. On some Chromebooks a full-size USB port may not supply enough power for a big pad; use a powered hub or a Bluetooth pad instead. Safari and iOS browsers expose the API weakly, so switch to a desktop browser for the most reliable results.
Comments & Ratings