Free Gamepad Tester Online
Press a button — watch it light up.
At a glance
- Input:
- Your gamepad — nothing typed or uploaded
- Processing:
- Runs entirely in your browser — the Gamepad API reads your controller locally and never leaves this page.
- Privacy:
- Nothing is stored or sent. Button presses, stick positions and the drift reading live only in this tab and disappear when you leave the page.
Last updated: 2026-11-14
Common use cases
- A new controller on arrival — press all 17 buttons and check every pad lights up.
- A controller that drifts in games — calibrate the centre and read the resting offset on each stick.
- A second-hand controller before buying — buttons, sticks and vibration checked in a minute.
- A controller after a firmware update — re-run the test and compare the drift reading with before.
About this tool
A free online gamepad tester that runs entirely in your browser: connect a controller, press a button, and watch each of the 17 standard-mapping buttons light up — action buttons, bumpers, triggers, Back and Start, the stick presses, the D-pad and Home — with a press count per button, live stick positions, a drift meter with pass / borderline / drift bands, and a vibration test when the controller exposes an actuator. The honest limits are on the page: browsers only see gamepads the operating system exposes; the drift reading only means something at rest after calibration; and vibration needs an actuator the controller may not have. Nothing is stored or sent.
How to use it
- Connect your controller by USB or Bluetooth, then press any button — the gamepad appears above the button map.
- Press each button and move both sticks — every pad lights up and the stick dots follow your thumbs.
- Press Calibrate centre with both sticks untouched, then leave them alone to read the resting drift on each stick.
- Press Test vibration if the controller exposes an actuator, then press Copy report for a plain-text summary.
Worked examples
Input: Connect a controller and press every button once
Output: 17 / 17 buttons tested — every pad lit
A full test lights every button the standard mapping defines.
Input: Calibrate centre, then leave the sticks untouched on a healthy controller
Output: Left 0.8% — Pass · Right 1.2% — Pass
A resting stick reads near 0 — the offset is sensor noise, not drift.
Input: Press the left trigger halfway
Output: LT held — pull 0.50
Triggers are analog: the pull value runs from 0.00 released to 1.00 fully pressed.
Practical tips
- Press a button first if nothing appears — most browsers only list a gamepad after a button press.
- Calibrate with the sticks untouched and your hands off the controller — a thumb resting on a stick calibrates the drift in.
- Read drift at rest, not while pushing — the meter measures the offset from centre, and a pushed stick is supposed to be far from centre.
- Flip the label switch to PlayStation names if you test a DualShock or DualSense — the buttons are the same indices either way.
Common mistakes
- Reading 2% as drift — under 4% is a pass; tiny values near zero are sensor noise, not a failing stick.
- Calibrating while holding a stick — the centre is recorded where the stick sits, so the drift reading comes out wrong.
- Judging drift while pushing the stick — the meter only means something with the stick untouched at rest.
- Assuming no vibration means a broken controller — many third-party controllers expose no actuator at all; the page says so when there is none.
How this compares
Dedicated gamepad-tester sites show the same button map and drift meter in a tab — this one adds the Xbox / PlayStation label switch, the calibrated resting-drift reading with peak tracking, and a copyable report, with the same local-only promise. The tradeoff: it tests the controller the browser can see, and says so plainly about the operating system, the calibration step and the vibration actuator.
Good to know
- Browsers only see gamepads the operating system exposes — a controller that needs a driver install will not appear until the driver is installed.
- The drift reading only means something at rest after calibration — it is a resting offset, not a measurement of stick travel.
- Vibration needs a vibrationActuator — many third-party controllers expose none, and the test cannot run on them.
- iPhone and iPad Safari have only limited Gamepad API support — the full test needs a desktop browser.
- A non-standard controller may not follow the 17-button standard mapping — button labels may not match its layout.
- Nothing is stored or sent — counts, drift readings and the report disappear when you leave the page, so there is no history to review later.
Frequently asked questions
Is my gamepad data recorded or sent anywhere?
No. The test reads the Gamepad API in this tab only — button presses, stick positions and the drift reading are counted locally, nothing is stored, nothing is sent, and everything disappears when you leave the page.
Why does my gamepad not show up?
Three usual reasons. First, most browsers only list a gamepad after a button press — connect it, then press any button. Second, the controller must be visible to the operating system first: on Windows check it shows under Bluetooth & devices, and install the maker's driver if it asks for one. Third, if you connected it after opening the page, reload the page and press a button again.
What is stick drift — and what do the percentages mean?
Drift is a stick that will not sit still: at rest it reports a position away from centre, and games read that as movement. Press Calibrate centre with both sticks untouched, then leave them alone — the meter shows the resting offset as a percentage of full deflection. Under 4% is a pass, 4–8% is borderline, over 8% is drift. The reading only means something at rest, not while you push the stick.
Why do the buttons have two names — A and Cross?
Xbox and PlayStation label the same standard-mapping buttons differently: A is Cross, B is Circle, X is Square, Y is Triangle. The switch above the button map flips the labels between Xbox and PlayStation names; the underlying button is the same one either way.
Does the vibration test work on every controller?
No. Vibration needs a vibrationActuator, which the browser only exposes when the controller and its driver offer one. Xbox and PlayStation controllers usually do; many third-party controllers do not. When there is no actuator the page says so plainly instead of pretending the test ran.
Does it work on a phone or tablet?
Only with a real controller connected and a browser that supports the Gamepad API. Plug in a USB or Bluetooth controller and test in the phone's browser. iPhone and iPad Safari have only limited gamepad support — a desktop browser (Chrome, Edge or Firefox) gives the full test.

