Controller & Gamepad Test

Connect a controller by USB or Bluetooth, then press any button to activate it in your browser. Press every button and trigger and move both sticks to check they all respond correctly.

No controller detected yet. Connect one and press any button on it.

This test uses the browser's Gamepad API, which reports most controllers using a normalized "standard" button layout — the labels shown are a best-effort match to that standard and may not match your exact controller if it uses a non-standard or proprietary mapping. Some browsers only detect a controller after you press a button on it, which is a browser security requirement, not a bug in this page.

What the Controller Test checks

It checks what your browser receives from a game controller: every button and trigger it reports, and the two analog sticks. Connect the controller by USB or Bluetooth and press any button; browsers only expose a controller once you press something. The page then shows the name the browser gives it and reads the buttons and axes about twenty times a second.

What each part of the display shows

The parts of the Controller Test and what each one shows
Part	What it shows
Buttons	One tile per button the controller reports. A tile is highlighted while pressed and turns green once it has been pressed at least once. Names follow the browser's standard layout (A/B/X/Y, LB/RB, LT/RT, D-pad, Home) as a best-effort match; buttons beyond that layout appear as Button plus a number.
Triggers	A trigger that reports partial values shows a bar between 0 and 1 while you squeeze it, so you can watch it move gradually.
Left and right stick	A dot moves inside a circle and the x and y values are shown from −1.00 to 1.00. Pushing left gives a negative x and pushing up gives a negative y.

Reading the sticks and triggers

What you might see in the Controller Test, what it may mean and what to try
What you see	What it may mean	What to try
The page keeps saying no controller was detected	The browser hasn't reported a controller. It may not be connected properly, or no button has been pressed since it connected, which browsers require before they expose it.	Press a button, reconnect the controller, try a USB cable instead of Bluetooth or try another browser.
At rest a stick reads close to 0.00 but not exactly	Small offsets are what a game's deadzone setting is designed to absorb. This test shows the raw value, with no deadzone applied.	Note the value with the stick untouched. If it's large or changes by itself, try another system or game to see whether it follows the controller, and follow the stick drift guide.
A stick never reaches about ±1.00 in one direction	The controller, or its driver mapping, is reporting a reduced range.	Push slowly all the way around the edge and compare with another controller or computer.
A trigger jumps from 0 straight to 1	That trigger is being reported as a digital button. Some controllers do this by design.	Check whether the bar ever shows intermediate values on another game or system.
A different tile lights than the button you pressed	The controller uses a non-standard mapping, so the labels don't match.	Go by the button number when the name is wrong, or try another cable, browser or the controller's mode switch, if it has one.

What this test can't do

It reads only the first controller the browser reports, and it can't test vibration, motion sensors, touchpads or battery level. It shows raw values but can't judge whether a stick is drifting: that depends on how large the offset is and how a game treats it, and the stick drift guide explains how to tell drift from a deadzone or calibration setting. It doesn't measure input latency, and a controller that drops its wireless connection can look the same as one you aren't pressing. The labels are a best-effort match, and the browser's mapping isn't always the one your console uses.

What to do next

If a button or axis misbehaves, repeat the test with a USB cable instead of Bluetooth, in another browser and on another device to see where the fault follows. For calibration or firmware options, use the controller's own software or your operating system's game-controller settings. The Keyboard Test and Mouse Test cover the rest of your input devices.

[ Controllers ]Troubleshooting

Controller Stick Drift: How to Check It and What the Browser Can Show

Character or camera moving on its own? Read your sticks' raw values in TryYourGear's Controller Test and learn how drift differs from dead zone and mapping.

Read guide

Methodology

What a Browser-Based Hardware Test Can and Can't Measure

How TryYourGear's 12 browser tests work: what each observes, what it can't measure and what result it gives, from key codes to refresh rate and latency.

Read guide

Try next

[ Input devices ]

Keyboard Test

Test your keyboard online for free. Check that every key registers, spot stuck keys and repeated input, and watch your key presses live. No download needed.

Open test