Skip to the content

Gamepad tester

Free gamepad tester: press every button, trigger and stick on an Xbox, PS5 or Switch controller and get a plain answer. No download.

  • Nothing is stored or uploaded
  • Free, no sign-up, nothing to install
  • Chrome, Edge, Firefox and Safari

Waiting for a button press

Press any button on your controller

Plug it in or pair it by Bluetooth first. A browser only shows a controller after one of its buttons has been pressed.

Pressed a button and nothing happened?
  1. Check the cable or the Bluetooth pairing. Some USB cables only charge and carry no data.
  2. Close other programs that may be using the controller, such as a game launcher, then press a button again.
  3. Reload this page with the controller already connected, then press a button.
  4. Try another browser. Chrome, Edge and Firefox all read controllers.

More help: controller not showing up

This test runs in your browser. Nothing is stored or uploaded.

This gamepad tester checks every button, trigger and stick on your controller and ends with a plain answer: Okay, Check this or Not working. It’s a free controller test that runs online, in your browser, with nothing to install. It reads Xbox, PlayStation and Switch Pro controllers, and most other pads your browser can see. Plug the controller in or pair it, press any button, and work down the list.

How to test a controller in your browser

Connect the controller first, by USB cable or Bluetooth. Then, with this page open, press any button. That first press matters. Browsers keep a controller hidden from web pages until you use it, so a pad that’s plugged in and lit up still won’t appear before you press something.

  1. Press any button. A drawing of the controller appears, with the name it reports and whether your browser recognises its layout.
  2. Press every button once: the four face buttons, both bumpers, all four D-pad directions, View and Menu (Create and Options on a PlayStation pad, Minus and Plus on a Switch Pro), then click both sticks straight down.
  3. Pull each trigger slowly, all the way to the end.
  4. Push each stick fully up, down, left and right. A slow circle round the edge does the same job.
  5. When all 18 inputs have responded, the answer appears by itself. If something won’t respond, press That’s everything: show the result and the tester lists what’s missing.

A full run takes under a minute. The counter above the list (“12 of 18 inputs have responded”) shows how far you’ve got. Anything you’ve missed stays unlit in the drawing, so you never have to remember what you’ve pressed.

If you press a button and nothing appears, the usual culprits are a USB cable that only charges, a Bluetooth pairing that has dropped, or a game launcher holding on to the controller. The guide to a controller not showing up goes through each one.

What the gamepad tester checks

Think of it as a controller input tester with a checklist. A standard controller has 18 inputs that matter: 16 buttons, counting the triggers, the four D-pad directions and both stick clicks, plus two sticks, each checked in four directions. The tester ticks each one off as it reaches the browser, so a dead button, or one that only works when you lean on it, stands out straight away.

Outline of an Xbox-style controller with its inputs labelled: triggers, bumpers, sticks, D-pad, face buttons A, B, X and Y, and View and Menu. Home, in the middle, is marked as not counted.
The 18 inputs on a standard layout: 16 buttons, counting the triggers, the D-pad and both stick clicks, and two sticks pushed four ways each. The tester doesn’t count Home.

Buttons, D-pad and stick clicks

A button counts the moment the browser reports it pressed. It’s a simple controller button test, but it catches the faults people actually have: a face button that has stopped clicking, a bumper that needs a hard press, a D-pad direction that has gone. Press any doubtful button several times. A worn switch often works on the third press and fails on the fourth, and you’ll see it light and go out in the drawing.

Stick clicks (L3 and R3 on PlayStation) are the ones people forget. They wear like any other button, so press each stick straight down until it clicks.

Triggers: how far each one travels

Triggers aren’t on-off buttons. They report how far you’ve pulled them, from 0 to 100%, and the tester keeps the furthest pull it has seen. A trigger counts once it reaches 90% of its travel. Between 15% and 90% the tester marks it partly, and the result gives the exact figure, for example “LT (left trigger) reached 82% of its travel.”

This is where a lot of controllers quietly fall short. A trigger that stops at 80% still works in menus, so you may never notice, but in a racing game it’s the difference between full throttle and nearly. Dirt under the trigger, wear in the part that senses it, or a calibration that has wandered are the usual reasons.

The gamepad tester with the left trigger outlined in amber and every other input in green, a progress bar reading 17 of 18, and the answer Check this: the left trigger reached 78% of its travel.
The tester marks a trigger that stops short as partly, in amber, and the answer gives the figure it reached. Here that is 78%.

Sticks in all four directions

Each stick has to reach 85% of its travel up, down, left and right. The line sits at 85% rather than 100% so a healthy stick with a slightly short range still passes. A direction that gets past 30% but not 85% counts as partly, and the result names it (“Left stick reached 74% going left”). Below 30% it counts as not responding, which stops the tester taking a stick that rests off centre for a push.

Two bars showing where inputs count. A trigger counts from 90% of its travel and is partly working from 15%. A stick direction counts from 85% and is partly working from 30%.
A trigger needs 90% of its travel and each stick direction 85%. The result reports anything in the middle band as partly, with the figure it reached.

What this check doesn’t do is judge drift. While you’re pushing the sticks around, the tester can’t tell a stick that rests off centre from one you’re touching. For that, put the controller down and run the stick drift test, which reads both sticks while nobody touches them.

Controller vibration test

Under the inputs there’s a Test vibration button. Press it while you hold the controller, then say whether you felt anything. If you didn’t, check that vibration isn’t switched off in your system or controller settings, and try again.

Vibration depends on the browser more than on the controller. Chrome and Edge can make most controllers rumble, and Safari on a Mac has been able to since version 16.4. Firefox usually can’t. The tester asks the browser what it can do rather than guessing from its name, and if the answer is nothing, it tells you. It also says so when a controller reports no vibration motor at all.

Raw values

Open Raw values from the browser to see every button and axis as numbers, exactly as the browser receives them. It’s the view to use when the wrong button lights up, when you want to watch a stick’s resting numbers, or when you’re checking a flight stick or wheel that the tester has no names for.

What your result means

Every run ends in one of three answers.

  • Okay: “All 18 inputs responded”. Every button, trigger and stick direction reached the browser, so as far as your computer can tell, the controller’s inputs all work.
  • Check this: “Every input responded, but not all the way”. A trigger or stick direction stopped short, and the result names it with the figure it reached. Push or pull it again as far as it goes. If it stops at the same place every time, it may be worn, blocked by dirt or in need of calibrating.
  • Not working: the result says how many inputs did not respond (“2 inputs did not respond”) and lists them. Press each one again while you watch the drawing. If it stays unlit, the press isn’t reaching the browser, which usually means a worn or broken switch.
The gamepad tester after every input has responded: the controller outline with every button, trigger and stick ringed in green, a full progress bar reading 18 of 18, and the answer Okay.
What Okay looks like: every input on the outline has turned green and the count reads 18 of 18.

The tester shows the Home button (the Xbox button, the PS button) but never counts it, and it doesn’t count extras such as Share, Capture or the touchpad click either. Your system or a launcher often keeps Home for itself, so an unlit Home button tells you nothing about the controller.

When the layout isn’t recognised

If your browser doesn’t recognise the layout, you’ll see “Layout not recognised” and numbered buttons and axes instead of names. The tester then counts every input the controller reports, and an axis counts once it moves well away from where it rested. Some controllers report inputs they don’t physically have, so in this mode the tester never says Not working. The most it gives is Check this, with something like “12 of 20 reported inputs responded”. Compare the unlit ones with the controller in your hand.

The tester showing a controller whose layout the browser doesn’t recognise: twelve numbered buttons, three of them green, and six numbered axes drawn as sliders with their values.
When the browser doesn’t recognise the layout, the tester numbers buttons and axes instead of naming them. Each one still lights up when it responds.

Under the result, How this test decides sets out the numbers: a button counts when pressed, a trigger at 90% and a stick direction at 85%. They’re starting values, and we’re still tuning them.

Testing Xbox, PlayStation and Switch controllers

The tester reads any controller your browser can read. When the browser recognises the layout, buttons get the names printed on your controller. Used as a PS5 controller tester, it shows Cross, Circle, L2 and R2 rather than button 0 and button 7.

Xbox Wireless, Elite and Series controllers

To test an Xbox controller on PC, plug it in with its cable (USB-C on the current Xbox Wireless Controller, micro-USB on older Xbox One pads) or pair it over Bluetooth. To pair it, hold the pair button on the top edge until the Xbox button flashes quickly, then add it in your computer’s Bluetooth settings. The tester names A, B, X, Y, LB, RB, LT, RT, View and Menu.

PS5 DualSense and PS4 DualShock 4

A DualSense connects by USB-C cable or by Bluetooth: hold Create and the PS button together until the light bar flashes, then pair it from your computer’s Bluetooth settings. A DualShock 4 pairs the same way with Share and PS. When the browser recognises them you’ll see the PlayStation names, from Cross and Triangle to L3 and R3.

So you can test a PS5 controller on PC for every button, stick and trigger. What you can’t test from a browser is the adaptive triggers’ resistance, the motion sensor or the touchpad surface. The touchpad click shows up as an extra button and isn’t counted.

Switch Pro Controller, Joy-Con and other controllers

A Switch Pro Controller pairs with a computer over Bluetooth: hold the small sync button on its top edge until the lights start to flash, then pair it from Bluetooth settings. Nintendo puts A on the right and B at the bottom, the other way round from Xbox. The browser’s standard layout goes by position, not by letter, and the tester knows that, so the bottom button is named B and the right one A, just as printed.

8BitDo pads and other third-party controllers work if your browser can read them. Some are recognised and named; others show as “Layout not recognised”, with numbered inputs, and that’s no fault of the controller. Many third-party pads can connect in more than one mode, chosen with a switch or a button held at power-on, and the mode changes how the browser sees them. If one mode gives you numbers, try another. We haven’t checked Joy-Con with this tester yet, so we can’t say how a single Joy-Con will read.

How to test a controller on PC or Mac without a website

Windows and the controller makers have their own tools. They’re worth knowing, because each one sees the controller a little differently. A firmware update from the maker is also worth doing before you decide a controller is faulty.

Windows 10 and 11: Set up USB game controllers

Press Windows + R, type joy.cpl and press Enter, or search the Start menu for “Set up USB game controllers”. Pick the controller, choose Properties, and the Test tab shows the sticks as crosshairs and the buttons as numbered lights. Some controllers also get a Settings tab with a Calibrate button.

It’s a fair check with one trap on Xbox controllers. That window uses an older Windows interface that combines the two triggers into a single axis, so pulling both at once looks like pulling neither. Microsoft explains why in its notes on XInput and DirectInput. The gamepad tester reads each trigger on its own, names the buttons, and tells you what’s missing instead of leaving you to spot it.

The makers’ apps

Microsoft’s free Xbox Accessories app for Windows updates an Xbox controller’s firmware and lets you remap its buttons; on an Elite controller it also sets stick sensitivity curves. Sony’s PlayStation Accessories app for Windows updates a DualSense’s firmware and, on a DualSense Edge, edits its profiles. Neither gives you a checklist of every input, which is why a test like this one is still useful after an update.

Mac and Nintendo Switch

On a Mac with a recent version of macOS, System Settings has a Game Controllers section where you choose a controller and change what its buttons do. It’s built for customising buttons rather than checking them, so a browser test is the quickest way to watch each input respond.

On a Switch, go to System Settings, then Controllers and Sensors, then Calibrate Control Sticks. Nintendo’s own steps for calibrating the controllers walk you through it, and the console then lets you check the stick on screen. That’s the right fix for a Switch stick that’s off; this tester covers every other input, or the same controller on a computer.

When a controller fails the test

Most failures fall into a handful of patterns, and each points somewhere different.

  • Nothing appears when you press a button. The browser can’t see the controller at all. Try another USB cable, since some only charge, re-pair it over Bluetooth, close any game launcher and reload the page with the controller connected. The controller not showing up guide has the rest.
  • One button never lights. Press it several times, in the middle and at the edges. If it stays dark, the switch underneath is worn, broken or blocked. If the controller is still under warranty, contact the maker before you open it.
  • A button lights only some of the time. That’s a switch on its way out, and it rarely improves by itself.
  • A trigger or stick stops short. You’ll get Check this, with the figure. Clean around it, update the firmware, recalibrate if your system offers it, and test again.
  • A stick moves on its own in games. That’s stick drift, which this tester isn’t built to judge. Run the stick drift test with the controller on the table, then read what causes stick drift and what you can do.

The last pattern catches people out most: “controller detected but not working” in a game. The tester shows what reaches the browser. A game reads the controller by its own route, and many games, Steam and other launchers have their own controller settings or only support some controllers. If every input passes here, the controller itself is fine, and the place to look is the game’s or launcher’s controller settings.

A press travels from the controller to the system, then to the browser and this test. A separate arrow runs from the system to your game. The Home button often stops at the system.
The test and your game both get the controller from the system, by different routes. Passing here clears the controller; a problem only in the game is in its settings.

Checking a used controller before you buy

If you’re buying a second-hand controller in person, take a laptop, open this page and run it on the seller’s controller. Then run the stick drift test, which also gives you a dated PDF of the stick readings. Five minutes tells you more than any listing. Use your hands as well: a rattle, a sticky button or a stick that doesn’t spring back to the middle are easy to feel before they ever show on screen.

What a browser can and cannot test

A browser reads what your operating system passes on about the controller: which buttons are down, and where each stick and trigger sits. That makes this a sound check that every input reaches your computer and how far each one travels. Some things are out of its reach.

  • Polling rate and input lag. The page reads the controller once per screen refresh. It can’t see how often the controller sends its own updates, so any figure would be a rough comparison, not a measurement. This tester doesn’t show one.
  • The motion sensor, the touchpad surface, the battery level and the DualSense’s trigger resistance. Browsers don’t pass these to web pages.
  • The Home or PS button, much of the time, because the system keeps it.
  • Which controller it is, beyond the name it reports. A browser cannot read a serial number.
  • A fault that comes and goes over an evening’s play. A test sees what happens while it runs.

Nothing is stored or uploaded. The test runs in your browser, and the button presses never leave it; the privacy page has the detail.

Questions

Why isn’t my controller detected?

A browser hides a controller until you press one of its buttons, even when it’s connected, so press a button with this page open and in front. If nothing happens, check the cable or the pairing, close any game launcher, and reload the page with the controller already connected. Chrome, Edge and Firefox all read controllers, so another browser is worth a try. The controller not showing up guide goes further.

Why isn’t the Home or PS button counted?

Your system or game launcher often uses it to open its own menu, so the press never reaches the browser. An unlit Home button isn’t a sign of a fault, which is why it’s listed as optional. The tester treats extra buttons such as Share, Capture or the touchpad click the same way.

Does it work on a phone or tablet?

Phone browsers can read controllers too, but we haven’t checked this tester on phones yet, so we can’t promise it. A computer is the safer choice for now. If you try a phone and the controller appears after a button press, the checklist works the same way.

Can I test the PS5 controller’s adaptive triggers?

Only how far they travel. A browser reads a trigger’s position, not the resistance the DualSense’s motors push back with, so the tester can tell you L2 reaches 100% but not whether its resistance works. To check that, play a PS5 game that uses it.

Can it test the touchpad, gyro or battery?

No. Browsers don’t share the motion sensor, the touchpad surface or the battery level with web pages, so no website can test them honestly. The touchpad click does show up, as an extra button.

Can I test two controllers at once?

Yes. Connect both and press a button on each. Each one gets its own tab, drawing and checklist, so you can compare a good controller with a doubtful one side by side.

Is my input sent anywhere?

No. The test runs in your browser and nothing is stored or uploaded. The page doesn’t need an account, and the button presses it reads never leave your device.

Why does a different button light up from the one I pressed?

Usually the browser doesn’t recognise the layout and is guessing, or a remapping program running in the background is changing what the controller sends. Close remapping tools and launchers, try Chrome or Edge, and open the raw values to see which number moves. If the layout still isn’t recognised, go by the numbers rather than the names.

Can a website calibrate or fix my controller?

No. A web page can read a controller but can’t change its settings or firmware, whatever a site claims. Use the maker’s tools instead: Calibrate Control Sticks on a Switch, the Xbox Accessories or PlayStation Accessories app on Windows, or the Calibrate button in Windows’ own game controller settings where your controller offers one.

My trigger only reaches about 80%. Is it broken?

Not necessarily. Pull it slowly and firmly to the end and watch the percentage. If it stops at the same point every time, it may be worn, blocked by dirt or in need of calibrating, and you’ll see Check this. Test the other trigger for comparison: if both stop short by the same amount, calibration is the likelier cause.

Does it work as a joystick tester for flight sticks or wheels?

Yes, if your browser can read the device. Flight sticks, wheels and pedals rarely match the standard controller layout, so you’ll see numbered buttons and axes, and each axis counts once it moves well away from where it rested. Open the raw values to watch each axis move through its full range.

Do I need to install anything?

No. The controller test is free, needs no sign-up and runs in a current version of Chrome, Edge, Firefox or Safari.