How to test a used controller before you buy
A short, repeatable check can reveal browser-visible input problems before money changes hands. It cannot guarantee future reliability, so combine the readings with a physical inspection and the seller's return terms.
Inspect before connecting
Look for a loose USB port, damaged cable socket, swollen or separated casing, sticky controls, cracked stick caps, missing screws, and signs of liquid exposure. A browser cannot inspect any of those conditions.
Ask whether the controller has been repaired, remapped, or calibrated and whether it can be returned. If possible, test the connection method you expect to use at home rather than assuming USB and Bluetooth will behave identically on your device.
The four input checks that matter
Resting drift comes first because it is easy to miss during a quick game. Put the controller flat, keep both sticks untouched, and take a full timed sample.
Then press every button once, pull both analog triggers to their stops where the controller exposes them as analog inputs, and rotate each stick slowly around its outer edge. Together these checks cover neutral position, digital inputs, trigger travel, and directional range.
A two-minute browser checklist
Keep the same browser tab focused throughout the check. If the controller disappears, reconnect it and repeat the affected step instead of treating the interruption as a failed control.
- Connect by a known data-capable USB cable or pair by Bluetooth, then press a button so the browser exposes the controller.
- Confirm that the displayed device name, button count, axis count, and mapping are plausible. A generic or virtual name is not automatically a fault.
- Run the nine-second resting drift test, move both sticks, release them, and repeat if the first result is questionable.
- Start the button sweep and press each available control once. Retest any input that was missed or remains active after release.
- Pull each analog trigger slowly, check that it returns near its resting value, and compare the maximum travel on both sides.
- Rotate both sticks around the full edge in the range test and look for a missing direction or a side that does not reach as far.
- If supported, compare USB and Bluetooth and save a report for each connection rather than assuming one result represents both.
Findings that deserve another look
A repeatable resting offset above the site's potential-drift boundary, a button that intermittently misses, a trigger that does not return near rest, or a stick that repeatedly fails to reach one direction can all affect play. Retest each finding before making a purchase decision.
Illustrative example: a trigger that reaches 0.82 in several slow pulls while the other reaches 1.00 has visibly unequal browser-reported travel. That does not prove which part is responsible, but it gives you a specific issue to verify in a game or with the seller.
Cosmetic wear and input quality are different questions. A scuffed controller may report clean inputs, while a spotless controller may still have an intermittent control that only appears after repeated use.
Keep the evidence in perspective
A downloaded report records the controller name supplied to the browser and the measurements captured during that run. It can help compare two runs or explain what you observed at the time.
The report is not proof of ownership, a hardware certificate, or a guarantee that batteries, wireless range, audio ports, motion sensors, touch surfaces, adaptive features, and future reliability are sound. Test those separately where they matter to your purchase.
Ready to check your own controller?
Start the Used Controller Check