RigCheckup

Gamepad Test

Connect your controller and press any button — browsers only reveal a gamepad after its first input.

No controller detected. Plug one in (or connect via Bluetooth) and press any button on it to wake it up.

Collect all your test results on one sheet: PC Checkup Report

What this test checks

Watch the stick circles while your hands are off the controller: if a dot sits outside the dashed dead-zone ring on its own, that's stick drift — the most common controller failure. Slight drift can sometimes be fixed by recalibrating in your OS or the maker's software; drift that keeps growing means the analog module is worn out.

LT and RT show analog values from 0.00 to 1.00 — pull them slowly and check the number climbs smoothly to exactly 1.00. A trigger that jumps straight to 1 has lost its analog range, and one that never reaches 1 won't register full throttle in racing games. If the pad doesn't appear at all, try a different USB port or re-pair Bluetooth, and close other apps (Steam, remapping tools) that may be capturing it.

How this test works

Modern browsers expose controllers through the Gamepad API. Instead of sending an event when a button is pressed, the API hands the page a snapshot of the whole controller, every button's pressed state and value plus the position of each axis, and leaves it to the page to ask again. Our gamepad test asks on every animation frame, so it reads the controller roughly as often as your screen refreshes, compares each new snapshot with the last one, and lights up anything that changed. That is why a quick tap still registers: the poll runs many times faster than a human can press and release.

The reason the page shows nothing until you press a button is a privacy rule built into browsers, not a fault in the controller or the test. A website is not allowed to know that a gamepad is plugged in until the user interacts with it, because the list of connected devices could otherwise be used to fingerprint visitors. So the first press is a handshake: it tells the browser you want this page to see the controller, and from then on the test can poll it freely. Unplugging and reconnecting, or re-pairing over Bluetooth, resets that handshake.

The two stick visualisers plot the horizontal and vertical axis of each analogue stick as a dot inside a circle. The dashed ring is drawn at a radius of 0.08, about eight per cent of full deflection, and represents a typical dead zone: the region most games ignore so that a stick resting slightly off centre does not move your character. LT and RT are read as analogue axes rather than on/off buttons, which is why they show a value from 0.00 to 1.00 instead of just lighting up. Vibration goes through the controller's vibrationActuator; when the browser does not expose one for your controller the button is marked unsupported rather than failing silently. Everything runs locally in the page. No inputs are recorded or sent anywhere, and the reset button simply clears the tested-button tally.

How to read the results

Every button you press should light up on the on-screen controller, and the tested counter should climb by one for each distinct button. A button that never lights, no matter how hard or how many times you press it, is not reaching the controller's board, which usually means a worn membrane, a broken tactile switch or dirt under the cap. A button that lights when you have not touched it, or flickers while held down, is making poor contact and will show up in games as phantom inputs. Reaching the full count is the simple pass condition; if one button is missing, you have found the fault.

For the triggers, pull each one slowly from rest to the stop and watch the number. It should start at 0.00, rise steadily and end at 1.00. A trigger that reads a few hundredths above zero at rest is normal wear; one that sits noticeably higher will register as a constant light press. A trigger that jumps straight from 0 to 1 has lost its analogue range and will behave like a digital button, which matters in racing and flight games. One that climbs smoothly but stops short of 1.00 is either worn, obstructed by debris, or limited by a trigger-stop switch on the controller.

The stick visualisers are where most real faults appear. With your hands completely off the controller, the dot should settle inside the dashed ring and stay there. If it rests outside the ring, or sits inside but slowly creeps toward an edge, that is stick drift, and the farther out it rests, the more a game will interpret it as deliberate movement. A dot that trembles or jumps around while the stick is untouched points to a noisy or failing sensor. Now move the stick in a full circle along its physical edge: the dot should trace the rim smoothly without flat spots, and releasing from any direction should snap it back to centre. Finally, the vibration result needs context: unsupported means this browser cannot drive this controller's motors, which is common over Bluetooth and in some browsers, and does not by itself mean the motors are broken. If the button is available and nothing happens, that is a stronger hint.

When to use it: common situations

The most common reason people arrive here is a suspicion of stick drift in a game: the camera slowly pans, a character creeps forward, or a menu cursor keeps moving. The visualiser turns that suspicion into something you can see and measure, and lets you tell drift on the controller apart from a game's own dead-zone setting. Because it shows the raw axis position, it is also useful evidence when you contact the manufacturer for a repair or replacement under warranty.

It is just as useful before money changes hands. If you are buying a used controller, take a laptop along, open this page and have the seller press every button, pull each trigger to 1.00 and let go of both sticks while you watch the rings. Five minutes here saves a return later. The same applies to a third-party or generic pad you have just bought: the test shows which standard button each physical button maps to in your browser, so you know in advance whether a game expecting an Xbox layout will see it correctly or whether you need a remapping tool.

Run the test again after any change in how the controller is connected or configured. A firmware update from the manufacturer's app can change dead-zone handling or fix a trigger, and the test shows whether it did. Comparing the same controller over USB and over Bluetooth reveals real differences: Bluetooth often drops vibration support, and on some systems a wireless connection reports slightly different stick values. And if you have cleaned the stick module with contact cleaner or opened the shell to replace a part, this is the quickest way to confirm the repair before launching a game.

Limits of a browser test and what to check elsewhere

The browser sits between you and the controller, and that layer has quirks. Button numbering and names come from a standard mapping that the browser applies when it recognises the controller; a pad it does not recognise may appear with buttons in a different order, which looks wrong on screen even though every button works. The same controller can also present differently in Chrome, Firefox and Safari, and differently again on Windows, macOS and Linux. If the layout on screen does not match what you hold, judge the controller by whether every press lights something, not by whether the labels line up.

Some things simply are not visible to a web page. The Gamepad API does not expose battery level, firmware version, connection quality or polling rate, and the vibration test cannot report motor strength or distinguish a weak motor from a healthy one. Vibration over Bluetooth is frequently unsupported regardless of the controller's condition. Adaptive triggers, touchpads, gyroscopes and motion controls are not part of the standard API at all, so they will not appear here even on controllers that have them. For those, the manufacturer's own app or the console's settings menu is the only reliable place to check.

The test also cannot calibrate anything or change dead zones; it only shows what the controller reports. If the dot sits outside the ring, our stick drift guide explains the causes, the recalibration options in the operating system and manufacturer tools, and when the stick module itself needs replacing. If the page never shows a controller at all, the guide on a gamepad not being detected walks through charge-only cables, port and driver problems, Bluetooth pairing, and other apps such as game launchers or remapping tools that may be capturing the controller before the browser can see it.

Frequently asked questions

My controller is connected but the page still says not detected.
With this page open, press any button on the controller once. For privacy reasons, browsers do not reveal a controller to a website until the user presses a button. If that does not help, make sure you are not using a charge-only USB cable with no data wires, and try a different cable or port.
The button names or positions do not match my controller.
The on-screen layout follows the standard mapping based on an Xbox-style controller. On a PlayStation pad, Cross corresponds to A and Circle to B. Older or generic controllers that the browser has no standard mapping for may show buttons in a scrambled order — you can still confirm each button works by checking that something lights up every time you press.
The dot is not exactly centred when I let go of the stick.
If the dot stays inside the dashed deadzone ring, that is normal. Analogue sticks never return to a perfect zero, and games apply a deadzone precisely to ignore that small error. If the dot rests outside the ring or drifts slowly to one side with your hands off, that is stick drift, and our stick drift guide covers the fixes step by step.
The vibration button says unsupported.
Vibration support depends on the combination of browser and controller. It works best with Xbox or PlayStation controllers in Chromium-based browsers such as Chrome and Edge. Firefox and Safari have limited support, and some controllers do not pass vibration over Bluetooth even though they do over a cable. An unsupported label does not mean the rumble motors are broken.
My trigger never reaches 1.00 when fully pulled.
If it gets to 0.95 or above, you will not notice a problem in practice. If it stops lower than that, the trigger sensor may be worn or obstructed, which shows up in racing games as never reaching full throttle. Some controllers have trigger stop switches that shorten the pull — when enabled, the value stops partway, so check that switch first.

Related guides