Controller TestConnect your controller.
Know if everything works.
Test buttons, analog sticks, triggers and stick drift directly in your browser. Nothing to install.
Checking browser…
One moment.
Controller input is processed locally in your browser and is not uploaded.
max 0%
X +0.000
Y +0.000
X +0.000
Y +0.000
max 0%
Buttons tested
0/ —
Waiting for a controller.
Stick drift
Let go of both sticks and do not touch the controller for 3 seconds.
Left stick
0.000, 0.000Connect a controller to measure.
Right stick
0.000, 0.000Connect a controller to measure.
The dead zone slider only changes this display; raw values are always shown. Controller hardware, browser mapping and calibration can all affect readings, so treat results as a measurement, not a diagnosis. Ratings: under 2% excellent, 2–5% minor, 5–10% moderate, 10%+ significant.
Stick range
Roll each stick slowly around its outer edge.
Left stick
- Left0%
- Right0%
- Up0%
- Down0%
Right stick
- Left0%
- Right0%
- Up0%
- Down0%
A direction counts as reached at 90% travel. Many sticks read slightly past 100% on diagonals; a stick that stops well short in one direction may be worn or obstructed.
Controller check
Waiting for a controller
Results appear here as you test: buttons, both sticks, triggers and vibration.
This summary only reports what the browser observed. It can't detect every hardware fault, and readings depend on the browser, driver and connection.
Vibration
Connect a controller to check vibration support.
Raw input
No controller connected.
How the controller test works
Your browser has a built-in Gamepad API that lets a web page read a connected controller's buttons and axes. This page polls it around 60 times per second and draws what it receives: pressed buttons light up, sticks move, and trigger meters fill from 0 to 100%.
While you play with the controller, the tester keeps track of:
- which buttons have registered at least once,
- the furthest each stick has travelled in every direction,
- the deepest each trigger has been pressed, and whether it reports in-between values,
- the stick's resting position when you run the drift test.
Everything happens on your device. No readings are uploaded, and there's no account or download.
How to connect a controller
- USB: plug the controller in with a data cable (some charge-only cables won't work). It should be recognized immediately.
- Bluetooth: put the controller in pairing mode and pair it in your computer's Bluetooth settings first. The browser can't pair devices itself.
- Press a button. Browsers hide controllers from web pages until you press something while the page is open, so the status box stays on “No controller detected” until you do.
Using a specific controller? See the PS5 DualSense guide or the Xbox controller guide for model-specific tips.
What stick drift means
Stick drift is when an analog stick reports movement even though nobody is touching it. In a game, it shows up as a camera that slowly pans on its own or a character that creeps forward. It's usually caused by wear or debris in the stick's sensors.
The drift test above asks you to let go of the controller, then samples both sticks for three seconds and reports how far their average resting position sits from dead center. Small offsets are normal; nearly every stick rests a little off zero. For a deeper explanation, use the dedicated stick drift test.
How dead zones work
A dead zone is a small area around the center of a stick where games ignore input. It exists precisely because sticks rarely rest at a perfect zero. If a stick rests 3% off center and the game's dead zone is 8%, you'll never notice it.
The dashed circle in the drift test shows a dead zone you can resize (default 8%). It only changes the display; the raw numbers are always visible, so you can compare your stick against the dead zone your game uses. Drift becomes a real problem when the resting offset is larger than the game's dead zone.
Troubleshooting controller detection
- Press a button with this tab in focus. Clicking the page first, then pressing a controller button, fixes most “not detected” cases.
- Close Steam or other remapping tools. Steam Input, DS4Windows and similar tools can hide the real controller or present a virtual one with different buttons.
- Try a different cable or port. Charge-only USB cables carry no data.
- Re-pair over Bluetooth if the controller was last paired to a console.
- Reload the page after connecting, or try another browser. Detection is handled by the browser and operating system, not by this site.
Browser compatibility notes
The Gamepad API is available in current versions of Chrome, Edge, Firefox and Safari on desktop, and in most mobile browsers. What differs is how each browser maps buttons and whether vibration is exposed:
- Chrome and Edge map most Xbox and PlayStation controllers to the standard layout and support rumble for many of them.
- Firefox reads controllers reliably but generally doesn't expose vibration.
- Safari (macOS, iPhone, iPad) supports controllers that Apple's Game Controller framework recognizes, such as Xbox, PlayStation and Switch Pro controllers.
Frequently asked questions
Is this controller test free?
Yes. There's no signup, no download and nothing to pay. It runs entirely in your browser.
Which controllers can I test?
Any controller your browser can see: Xbox, PlayStation (DualSense and DualShock 4), Switch Pro, 8BitDo, generic USB gamepads, flight sticks and more. Controllers using the standard layout get the full diagram; others get a raw button and axis view.
Why does it say “No controller detected” when my controller is plugged in?
For privacy, browsers don't reveal controllers until you press a button while the page is open. Press any button. If it still doesn't appear, see the troubleshooting tips above.
Can this test tell me my controller is broken?
It shows what the browser receives: whether each button registers, how far sticks travel and how far they rest from center. That's strong evidence, but it isn't a hardware diagnosis. A problem can also come from a driver, cable or remapping software, so repeat a suspicious result before drawing conclusions.
Is my controller input sent anywhere?
No. Controller input is processed locally in your browser and is not uploaded.
Does it work on phones and tablets?
Often, yes. Android Chrome and iPhone/iPad Safari both support Bluetooth controllers. Support depends on the device and operating system, and vibration is less commonly available on mobile.