TestBenchmark logoTestBenchmark

Gamepad Test

This gamepad test checks whether your controller is actually healthy — every button, both sticks, both triggers, stick drift, circularity, vibration and update rate — in one guided check with a plain-English report at the end. One honest limit up front: a web page only sees a controller after you press a button, and it never sees the touchpad, motion sensor, adaptive triggers or battery — so connect the controller, press a button, and the test begins.

Your controllerXbox layout

Pick the layout printed on your controller — the same physical button just gets its proper name. The test itself is identical for every layout: the browser sees the standard button order whatever is printed on the plastic.

No controller detected — connect your controller, then press any button on it.

1 · Live controller diagram

Press every button on your controller — each one lights up here and keeps a tested outline once pressed. The two sticks show their live position below, and the trigger bars show how far L2 and R2 travel. The numbers under each stick are its live X and Y, to three decimals.

Left stick

x +0.000 · y +0.000

Circularity: draw a full circle — 0 of 8 sectors.

Right stick

x +0.000 · y +0.000

Circularity: draw a full circle — 0 of 8 sectors.

Left trigger (L2 / LT / ZL)0% · max 0% · rest 0%
Right trigger (R2 / RT / ZR)0% · max 0% · rest 0%

No buttons pressed yet — press any button on your controller.

A button that never lights up is either dead or not reaching the browser — press it in the checklist below before you conclude anything. On a Switch controller, ZL and ZR jump straight from 0% to 100% by design: they are digital buttons, not analogue triggers.

2 · Guided checklist

Work through the steps in any order — each one ticks itself off as you do it. A step only counts when the controller really does it: 18 real button presses, both triggers pulled all the way, full circles on both sticks, a hands-off drift audit and a vibration check.

○ Press every button once0 of 18 buttons pressed
○ Pull both triggers to 100%LT 0% · RT 0%
○ Full circles with both sticksLeft 0/8 · Right 0/8 sectors
○ 5-second drift audit, hands offNot run yet
○ Vibration checkNot tested yet

3 · Stick-drift audit — 5 seconds, hands off

Take your thumbs off both sticks and press Start. The test samples each stick about 60 times a second for five seconds and scores the drift: under 3% is no drift, 3–8% is slight, 8–15% is noticeable and over 15% is severe. If you touch a stick or press a button during the audit, it asks you to run it again.

Not run yet — leave both sticks alone for the whole 5 seconds.

Left stick drift

—

Right stick drift

—

4 · Vibration test

Press a rumble button and feel the controller in your hands. Weak fires the light motor, Strong fires the heavy motor, Dual fires both at once. This uses the browser's built-in vibration feature — it works in Chrome and Edge, and only partly in Firefox and Safari. After each test, tell the page honestly whether you felt it.

Not tested yet.

5 · Update rate — 3 seconds

Press Start, then wiggle a stick or press buttons for three seconds. The test counts how many fresh controller states the browser delivers per second — that is the update rate in Hz. Be honest about what it is: this is the browser's rate, capped at your screen's refresh rate, not the controller's hardware rate. A wired DualSense can report at 250 Hz and an Xbox controller at 125 Hz, but most browsers will still show you about 60 Hz.

Update rate

— Hz

Peak

— Hz

States counted

0

Not measured yet.

6 · Your controller report

The report reads everything the test has seen so far and names the faulty part — or tells you the controller is healthy. Run the checklist first for a full score; the report also works on partial data and says plainly what was not tested. Copy the text version to paste into a support ticket or a repair-shop message.

Honest limits

A web page only sees what the browser passes on. The touchpad, motion sensor, adaptive triggers and battery never reach a web page, so this test cannot check them — and a controller stays hidden until you press a button, because browsers hide gamepads for privacy. Steam, DS4Windows or similar software can take exclusive control and hide the controller from the browser entirely — close it first. Some browsers cap readings at the screen refresh rate, so the update rate here reads about 60 Hz even on a faster controller. Touchscreens cannot test a controller at all: use a computer, or an Android phone with a real controller.

How to test your controller in 5 steps

1 · Connect it and press a button. Plug the controller in with a data cable, or pair it over Bluetooth. Then press any button — the browser only shows the controller after a button press, so the diagram stays empty until you do. If nothing appears, read the “Why isn't my controller detected?” answer in the FAQ below before anything else.

2 · Press every button once. Work around the controller: face buttons, bumpers, triggers, Start and Back, the D-pad in all four directions, and click both sticks in (L3 and R3). Each press lights up its chip on the diagram and adds one to its counter. A button that never lights up is either dead or not reaching the browser.

3 · Pull both triggers all the way. Squeeze L2 and R2 slowly from released to fully pulled and watch the bars climb to 100%. A trigger that stalls below 90% at full pull is worn, and one that sits above 2% when released is dragging. On a Switch controller, ZL and ZR jump straight from 0% to 100% — that is by design, not a fault.

4 · Draw full circles with both sticks. Rotate each stick slowly around its outer edge, a full turn, and watch the dot trace the circle. The test records how round the trace is: a healthy stick reaches nearly the same distance in every direction, while a worn one flattens on one side and the circularity error climbs past 25%.

5 · Run the drift audit, then read your report. Leave both sticks alone and press “Start 5-second drift audit”. The test samples each stick about 60 times a second and gives a verdict per stick with the deadzone that would hide it. Then press “See my controller report” for a score, a plain list of any faults found — with the faulty part named — and what to do about each one.

What is stick drift?

Inside each stick is a tiny sensor that measures how far the stick is tilted. On most controllers that sensor is a potentiometer: a small track the stick's wiper slides across, and the position of the wiper tells the controller where the stick is. Over time the track wears thin, dust works its way in, and the spring that pulls the stick back to centre weakens — and the stick starts reporting a small tilt even when your thumb is nowhere near it. That is drift: your character walks forward on its own, your aim creeps sideways, menus scroll without you touching anything. Hall-effect and TMR sticks use magnets instead of a sliding contact, so they barely drift at all — which is why replacement sticks with those sensors are the usual fix for a drifting controller. Drift always gets worse, never better: the worn track only wears further, so a stick at 3% today will be at 8% in a few months of regular play.

How much drift is too much? The thresholds this test uses

The audit measures the stick's average offset from dead centre at rest, as a percentage of full tilt. The bands are:

Under 3% — no drift. Every stick wobbles a little at rest and every game ignores it. Nothing to do. 3% to 8% — slight drift. You will not notice it in most games, but it is real and it will grow. Raise the deadzone and keep an eye on it. 8% to 15% — noticeable drift. Menus move and aiming creeps without input. Clean the stick, recalibrate, raise the deadzone — and start thinking about a repair. Over 15% — severe drift. The stick is failing. Cleaning rarely saves it now; the stick module needs replacing or the controller does.

Here is a worked example from the audit itself. A left stick sitting at rest reads x +0.024, y −0.018. Its offset is the square root of 0.024² + 0.018², which is exactly 0.030 — 3.0% of full tilt, so the verdict is slight drift. If its 95%-deviation over the five seconds is 3.9%, the recommended deadzone is 5%: the deviation rounded up, plus one point, with a 5% minimum. A right stick reading x +0.060, y +0.080 sits at 10.0% — noticeable drift — and its recommended deadzone is 11%. Same maths, different stick, different answer: that is why the test measures each stick on its own.

Deadzone: what it is and where to set it

A deadzone is a ring around the stick's centre inside which the game ignores all input. With a 5% deadzone, the stick has to tilt more than 5% of full travel before anything happens — so a stick drifting at 3% is silenced completely, at the cost of a slightly less responsive stick. Set it where the game lets you: most games have a deadzone slider in their controller settings, and Steam Input lets you set one per game for any controller. This test recommends a deadzone per stick — the 95%-deviation plus one point, minimum 5% — because a single number for both sticks is always wrong for one of them. Remember what a deadzone cannot do: it hides drift, it does not fix it. If the drift number keeps climbing month after month, the sensor is wearing out and no deadzone will save it for long.

Connecting your controller

PS5 DualSense: plug in with a USB-C data cable, or hold the PS button and the Create button together until the light bar flashes, then pick the controller in your computer's Bluetooth settings. PS4 DualShock 4: micro-USB cable, or hold the PS button and the Share button together until the light bar flashes, then pair. Xbox One / Series: USB-C cable (micro-USB on older Xbox One pads), or hold the Pair button on top until the Xbox button flashes, then pair — the Xbox Wireless Adapter works too. Switch Pro Controller: USB-C cable, or hold the Sync button on top until the lights flash, then pair. Joy-Cons: hold the small Sync button on the side of one Joy-Con until its lights flash, then pair — each Joy-Con appears as its own controller, or the pair in the grip appears as one. 8BitDo and generic pads: most have a mode switch — pick X-input mode (sometimes marked X) so the browser sees the standard button layout; D-input mode can scramble the mapping.

Which browsers can test a controller?

Chrome and Edge have the fullest support: controller detection, all buttons and sticks, and vibration. Firefox detects controllers and reads buttons and sticks, but vibration only partly works. Safari's gamepad support is the most limited — many controllers are not detected at all, and vibration is not exposed. Whatever the browser, a web page only sees a controller after you press a button, and it never sees the touchpad, motion sensor, adaptive triggers or battery. If your controller works in Chrome but not in your usual browser, the browser is the limit, not the controller.

How to fix stick drift

Work through it in order, cheapest first. First, recalibrate: on Windows open joy.cpl, pick the controller, and run the calibration; on Steam, use the controller calibration in Steam Input. Second, clean it: blow compressed air around the base of the stick and work the stick in circles — dust under the stick is the most common fixable cause. A drop of isopropyl alcohol around the stick base, worked in by rotating the stick, helps too. Third, raise the deadzone: use the number this test recommends, in the game or in Steam Input — this hides the drift while you decide. Fourth, update the firmware: Xbox Accessories, PlayStation's updater or the maker's app sometimes fix drift that is really a firmware bug. Fifth, the warranty: drift on a controller still under warranty — Joy-Cons especially — is often repaired free of charge. Last, replace the stick module: a repair shop can solder in a new stick, ideally a Hall-effect one that will not drift again.

Repair or replace?

Repair it when the controller is under warranty, when only one stick drifts slightly, or when it is a premium controller worth more than the repair costs. Replace the stick module — not the whole controller — when the drift is severe but everything else works: a Hall-effect replacement ends the drift problem for good. Replace the whole controller when both sticks drift severely, when a trigger is also failing, or when the repair costs more than half a new controller. And when you do replace it, check the drift on the new one the day it arrives, while the return window is still open — a stick that drifts on day one only drifts more with use.

What this test cannot see

A web page only sees what the browser passes on. The touchpad, motion sensor, adaptive triggers and battery never reach a web page, so this test cannot check them — test those in the console or the maker's app. Some browsers cap readings at the screen refresh rate, so a fast controller can read as 60 Hz here — that is the browser's limit, not the controller's. A charge-only USB cable carries no data at all, so the controller stays invisible until you swap the cable. And touchscreens cannot test a controller: taps arrive as touch events, not gamepad input. Within those limits, what this page measures is what your games see too: the same buttons, the same sticks, the same triggers.

Frequently asked questions

How do I test my gamepad/controller online?

Connect your controller to your computer, then press any button on it — the browser only shows a controller after a button press, so the page stays blank until you do. Every button you press lights up on the diagram and adds one to its counter. Then work through the checklist: press every button, pull both triggers to 100%, draw full circles with both sticks, run the 5-second drift audit and try the vibration test. Nothing to install, no sign-up, nothing uploaded — the whole test runs in your browser.

Why isn't my controller detected by the gamepad test?

Almost always one of five things. First, press a button on the controller — a web page cannot see it until you do, because browsers hide gamepads for privacy. Second, check the cable: many USB cables only charge and carry no data, so try a data cable or another port. Third, close Steam, DS4Windows or any controller software — they can take exclusive control and hide the controller from the browser. Fourth, try Chrome or Edge, which have the fullest gamepad support. Fifth, if you are on Bluetooth, unpair the controller and pair it again; on some controllers you also need to switch it to X-input mode first.

What is stick drift and how do I test for it?

Stick drift is when a stick reports movement while you are not touching it — your character walks, your aim creeps, menus scroll on their own. It is usually a worn stick sensor: the little potentiometer inside wears down, dust gets in, or the centring spring weakens. To test it, leave both sticks completely alone and press “Start 5-second drift audit” above. The test samples each stick about 60 times a second for five seconds and reports a verdict per stick — no drift, slight, noticeable or severe — plus the deadzone that would hide it.

How much stick drift is too much, and what deadzone should I use?

Under 3% offset at rest is no drift — every stick wobbles a little and games ignore it. From 3% to 8% is slight drift: you will not notice it in most games, but it is there. From 8% to 15% is noticeable: menus and aiming start to move on their own. Over 15% is severe: the stick needs cleaning, repair or replacement. The deadzone this test recommends is your 95%-deviation plus one point, with a 5% minimum — so a stick that wanders up to 3.9% gets a 5% deadzone, and one that reaches 10% gets 11%. Set it in the game's settings or in Steam Input. A deadzone hides drift, it does not fix it — if the number keeps growing, the stick is wearing out.

Can I test a PS5 controller on a PC?

Yes — a PS5 DualSense works on a PC in this test. Plug it in with a USB-C data cable, or pair it over Bluetooth by holding the PS button and the Create button together until the light bar flashes, then choosing the controller in your computer's Bluetooth settings. The browser sees the standard button layout, so the test works exactly the same as on an Xbox controller. Two things a web page cannot see: the touchpad and the adaptive triggers — those never reach the browser, so they are not part of this test.

How do I test controller vibration?

Press the Weak, Strong or Dual rumble buttons above and feel the controller in your hands. The test uses the browser's built-in vibration feature, which works in Chrome and Edge; Firefox and Safari only partly support it, so if nothing happens there, try Chrome before concluding the motor is dead. If the controller still does not vibrate anywhere, the rumble motor may have failed — or the controller may not have one at all, which is true of some cheap third-party pads. Tell the test whether you felt it, and the report records the answer.

Can I test a Nintendo Switch controller or Joy-Cons?

Yes. A Switch Pro Controller connects over USB-C or Bluetooth — hold its Sync button until the lights flash, then pair it. Joy-Cons pair the same way, one at a time: each Joy-Con appears as its own controller, or the pair in the grip appears as one. Two honest notes: the ZL and ZR buttons on a Switch controller are digital, so they jump straight from 0% to 100% by design — that is not a trigger fault. And Joy-Cons are famous for drift, so if the audit flags yours, you are far from alone — Nintendo has repaired many of them free of charge.

Does the gamepad tester work on mobile (Android / iPhone)?

On Android, yes — with a real controller. Connect one over Bluetooth or USB-OTG and open this page in Chrome; the browser sees the controller the same way a computer does, and the buttons, sticks and drift audit all work. On iPhone it mostly does not: Safari's gamepad support is very limited and most controllers are simply not detected. And a touchscreen on its own cannot test a controller — there is nothing to press. Use a computer or an Android phone with a real controller for this test.

How this test works: every number is measured in your browser from the Gamepad API — navigator.getGamepads() read about 60 times a second — with no downloads, no sign-up and nothing uploaded. A web page only sees a controller after you press a button; the touchpad, motion sensor, adaptive triggers and battery never arrive here.