How to test a game controller on PC

Updated October 2026 · TapTest guides

A controller that feels fine in one game and acts up in another is one of the most confusing problems in PC gaming, because it is often impossible to tell whether the fault is in the pad, the cable, the port or the game itself. A proper test answers that question in a couple of minutes, and it is the first thing worth doing before you start reinstalling drivers or buying a replacement.

The goal of testing is simple. You want to confirm that every button registers, that both sticks reach their full range and return to centre, that the triggers read smoothly from nothing to fully pressed, and that the pad is not sending input when you are not touching it. Once you know which of those is wrong, the fix usually suggests itself.

The fastest test: use a browser-based tester

Open the controller tester, plug in or pair your pad, and press any button. The browser reads the pad through the standard Gamepad interface, so you do not need to install anything, and it works the same whether you are on Windows, macOS, Linux or a Chromebook. Here is what to work through:

Press every face button, bumper, trigger, stick click and D-pad direction one at a time, and watch each one light up on screen. Any button that does not respond is your first clue.
Roll each stick slowly in a full circle. The on-screen dot should trace a clean circle and reach the edge in every direction. If it cannot reach the edge, or the circle looks lopsided, the stick or its calibration is off.
Let go of both sticks. The dots should snap back to dead centre and stay there. If a dot drifts on its own, you are looking at stick drift, which has its own dedicated guide.
Squeeze each trigger slowly. The reading should climb smoothly from 0 to full with no jumps or dead zones.

Why a browser test is so useful

Because the tester reads the raw signal straight from the controller, it cuts the game out of the picture entirely. If a button works here but not in your game, the hardware is fine and the problem is in the game's settings or its controller support. If a button fails here as well, the fault is in the pad, the cable or the connection, and no amount of fiddling with game settings will help. That single distinction saves an enormous amount of wasted effort.

Checking it in Windows itself

Windows has a built-in panel that does a similar job. Press the Windows key, type joy.cpl and press Enter to open "Set up USB game controllers". Select your pad, click Properties, and you get a test tab showing button presses and stick positions, plus a calibration wizard on a second tab. It is a bit dated and it reads older DirectInput devices more happily than modern Xbox-style pads, but it is a handy second opinion, especially for flight sticks and racing wheels.

Steam's controller settings

If you game through Steam, open Steam, go to Settings and then Controller. Steam shows every connected pad, lets you test inputs, and controls a layer called Steam Input that remaps and translates controller signals for games. This layer is powerful, but it is also a common source of strange behaviour. If a controller works in the browser tester and in Windows but misbehaves only inside Steam games, try toggling Steam Input off for that specific game in its properties and test again.

Wired versus wireless, and what to rule out

Connection type changes what you should check first. For a wired pad, a surprising number of problems trace back to the cable rather than the controller. Many budget USB-C cables are charge-only and carry no data, so the pad charges but never appears to the PC. Swap in a cable you know carries data before you blame anything else, and try a different USB port, ideally one directly on the back of a desktop rather than a front panel or a hub.

For a wireless pad, low battery can cause inputs to stutter or drop long before the controller actually dies, so charge it fully and retest. Bluetooth pads sometimes pair but connect with a laggy or incomplete profile, in which case removing the device and pairing it fresh often clears it up. If you have an Xbox wireless dongle, plug it straight into the PC rather than through a hub.

When some buttons work and others do not

If the tester shows most inputs working but one or two buttons dead, the most likely cause is physical: dust or debris under the key, a worn contact, or in older pads a cracked solder joint. If instead the pad reads completely blank, the issue is the connection or the driver, not the buttons. On Windows you can open Device Manager, find the controller, and try removing it so Windows reinstalls it on the next plug-in, which resolves a lot of "detected but not working" cases.

Calibration and dead zones

If your sticks reach full range but the centre feels loose, a small amount of dead zone is normal and intended, since it stops tiny electrical noise from registering as movement. Problems start when the dead zone has to be set large to hide drift, because that makes the controller feel unresponsive. The Windows calibration wizard in joy.cpl can re-centre an older pad, and many modern controllers have their own firmware tools or app-based calibration. Always retest in the tester afterwards so you can see the result rather than guess at it.

Common questions

My controller works on console but not PC. Why? Consoles and PCs use different controller standards. A pad built for one console may need a specific driver, a wired connection, or a translation layer like Steam Input before a PC will read it correctly.

The tester sees my pad but my game does not. That points to the game's controller support rather than the hardware. Check the game's input settings, and if you launch through Steam, experiment with turning Steam Input on or off for that title.

Do I need to install drivers? Most modern pads work the moment you plug them in. The browser tester never needs drivers because it reads the pad through your browser. Specialist or older devices are the main exception.