HomeDevice Checkups › Buying a Used Controller

Checking a Used Controller Before You Buy

Five checks that take about six minutes and catch the fault that ends most controllers.

A used controller is the purchase where visual inspection is least informative. A pad can be immaculate — no scuffs, clean grips, tight shoulder buttons — and still have worn analog sticks, because stick wear happens entirely inside a sealed mechanism and correlates with hours played rather than with how the outside looks. The cosmetically perfect controller from someone who played one game obsessively for a year is a worse buy than the scratched one from someone who played occasionally.

Drift is the specific thing to test for, and it is worth being precise about what it is. Stick drift is when an analog stick reports movement while nobody is touching it, caused in conventional potentiometer designs by physical wear on the resistive track the sensor rides against. It is the most common controller failure by a wide margin, it is progressive, and it is not repairable by cleaning once the track itself has worn.

The good news is that it takes seconds to detect with a measurement rather than a feeling. A resting reading that sits away from centre is unambiguous, and it is the difference between a working spare pad and a piece of plastic you will be annoyed about. Ask the seller to bring a USB cable, or bring one yourself — wired is faster and removes pairing from the equation.

The checklist

Tick each step as you go. All six take about a minute each, and the drift measurement near the end is the one that decides most purchases.

0 of 5 done
  1. Connect by USB or pair over Bluetooth, then press any button — the Gamepad API reports nothing until it receives input.

    Open the Gamepad Tester →

    Pass: The controller appears and identifies itself once you press a button.

    Fail: Nothing appears even after pressing several buttons and trying another cable.

    If it fails: Controller not detected on PC — Work through pairing, cable and driver causes before writing it off.

  2. Press each face button, both bumpers, both stick clicks, and all four D-pad directions in turn.

    Open the Controller Test →

    Pass: Every input registers immediately, first press, every time.

    Fail: An input that needs a hard press, registers intermittently, or does nothing.

    If it fails: Controller buttons not responding — Separate debris and worn membranes from a dead contact.

  3. Pull each trigger slowly from rest to fully depressed and watch the reported value move smoothly through its range.

    Open the Controller Test →

    Pass: Each trigger sweeps smoothly from zero to maximum with no jumps.

    Fail: A trigger that starts partway up, stops short of maximum, or jumps between values.

    If it fails: How to test a controller in your browser — Interpret the axis readings and confirm what a healthy sweep looks like.

  4. Set the controller down on a flat surface, hands completely off, and let the test read both sticks for at least twenty seconds.

    Open the Stick Drift Test →

    Pass: Both sticks reading at or very near centre with a low severity rating.

    Fail: A consistent offset from centre, or readings that wander with nobody touching the pad.

    If it fails: Controller stick drift — Confirm the diagnosis and understand what can and cannot be fixed.

  5. Roll each stick slowly around its full circle several times, watching for dead spots or a range that does not reach the edge.

    Open the Controller Test →

    Pass: Smooth continuous movement that reaches full deflection in every direction.

    Fail: Flat spots, a range that stops short in one direction, or jumpy readings mid-sweep.

    If it fails: How to test a controller in your browser — Read the axis output properly and tell wear apart from a calibration issue.

More tests worth running here

Not essential to the checklist above, but relevant to this situation and quick to add.

Frequently Asked Questions

Can I test a controller without installing anything?

Yes. These tests read the controller through the browser's Gamepad API, which works over USB and Bluetooth with nothing installed. Bring a USB cable if you can — wired connection is faster to set up and takes pairing problems out of the equation entirely.

The controller does not show up at all. Is it broken?

Not necessarily. The Gamepad API stays silent until the controller sends input, so press a button first — this alone resolves most cases. Then check the cable, since many bundled cables are charge-only and carry no data. Failing that, try re-pairing over Bluetooth.

How much stick drift is acceptable in a used controller?

Ideally none, but small offsets are common and usually get absorbed by in-game deadzones without you noticing. What matters is whether the offset is large enough to produce visible movement on screen. If a character walks without input at normal deadzone settings, the sticks are worn enough to matter and you should price accordingly or walk away.

Can stick drift be fixed?

Sometimes, and it depends on the cause. Debris under the stick housing can produce drift-like behaviour and may clear with careful cleaning, and recalibration can re-establish the centre point. Neither reverses physical wear on the potentiometer track. If drift returns after recalibration, the mechanism is worn and needs replacing.

Are Hall effect sticks worth paying more for secondhand?

Generally yes, if you intend to keep the controller. They sense position magnetically with no physical contact to wear out, so the specific failure that ends most controllers is largely designed out. They are not immune to every fault — housings, springs and buttons still wear — but the sticks themselves last considerably longer.

Should I test a controller on the console or on a PC?

A PC browser is the more informative option, because it shows numeric axis values rather than just visual feedback. A resting X/Y reading is a measurement you can act on; a game's response to a stick is an impression. If you only have a console, the drift will still be visible in a menu, just harder to quantify.

Other checkups

Controller input is read through the browser's Gamepad API and stays on the device. Button presses and stick positions are never recorded or transmitted. See how we validate these tests.

Found an error on this page, or a result that does not match your hardware? Tell us and we will correct it.