How to Test a Game Controller Online on PC
A practical step-by-step guide to checking controller inputs in a browser, understanding the readings and identifying the next troubleshooting step.

A controller can connect successfully and still behave strangely in a game. A button might not register, a trigger may respond inconsistently, or the camera may move even when you release the right stick. The fastest way to narrow down the problem is to check what inputs your computer and browser can actually see, then compare those readings with what happens inside the game.
You can perform a basic game controller test without installing a dedicated testing app. You'll need a computer, a USB or Bluetooth controller that the operating system recognizes, and a browser that supports the Gamepad API. Browser support and input mapping vary by device, so a browser test is a useful diagnostic—not a guarantee that the hardware or every game is working perfectly.
Quick checklist: What should you test?
| Input | Action | What to look for |
|---|---|---|
| Face buttons | Press and release each one | The corresponding reported button changes state and returns to released |
| D-pad | Press up, down, left, right separately | The appropriate direction or reported input changes |
| Shoulder buttons | Press each bumper | Each press registers without missing or repeated input |
| Left and right triggers | Squeeze slowly, then release | The value changes as you squeeze, if the controller exposes analog triggers |
| Analog sticks | Move each stick in a circle and release | Both axes respond and return close to their resting position |
| Stick clicks | Press L3 and R3 | The click registers as a button input, if exposed |
Step 1: Connect the controller to your PC
For a wired controller, connect it using a USB cable that supports data. Some USB cables supply charging power only, which can make a controller light up without sending input to the computer. If detection fails, try a different cable or USB port.
For a Bluetooth controller, pair it in your operating system's Bluetooth settings and confirm that it shows as connected. Bluetooth pairing instructions depend on the controller model; use the manufacturer's instructions if you are unsure how to enter pairing mode.
If you use Windows, you can make a quick operating-system-level check: press Win + R, enter joy.cpl, and look for your controller in the Game Controllers panel. Where supported, select Properties to examine its test inputs. This is a useful comparison if a browser or game is not detecting the device.
Step 2: Open a live browser input tester
Open JoystickCheck's online gamepad tester in a browser. Keep the tab active and press a button on your controller. Some browsers do not expose a connected controller to a page until the user interacts with it. When detected, the tester can show browser-reported buttons, D-pad input, analog axes, triggers and device mapping details.
The tester reads inputs provided through the browser's Gamepad API. It does not install drivers, control your game settings or directly inspect the controller's internal hardware sensors.
Step 3: Check each button and the D-pad
Press one control at a time. Check that the reported input changes when you press it and returns to its previous state when released. Test the face buttons, bumpers, menu buttons, D-pad directions and stick clicks.
If a label does not match the physical controller, check the reported mapping before assuming the button is broken. Non-standard controller mappings may expose inputs with different indexes or labels. A control that works in the browser but not in a particular game points toward a game-side configuration or compatibility issue rather than proving hardware failure.
Step 4: Check both analog sticks
Move the left stick horizontally, vertically and around the full edge. Repeat with the right stick. Observe whether both axes change smoothly and whether the stick comes back near its resting values after release.
In a standard browser gamepad mapping, a stick axis is commonly reported in the range −1 to +1, with a neutral position near 0. Small non-zero readings are not automatically evidence of defective hardware. Controller calibration, sensor behavior, browser processing and the game's own deadzone may all affect the experience.
If your camera drifts in a game, compare the browser readings at rest with the same controller in another game. For a deeper explanation, read our guide to checking analog stick centering and deadzones.
Step 5: Check triggers gradually
Slowly squeeze and release the left and right triggers. With a standard mapping, analog triggers may be reported on a scale similar to 0.00 (released) to 1.00 (fully pressed). Some controllers expose a trigger as a digital button or use a non-standard mapping, so a sudden on/off change is not automatically a fault.
Look for an input that never releases, stays at a fixed value or fails to register despite a working connection. Repeat the test with another connection method if possible.
Step 6: Compare browser results with the game
A browser test tells you what the browser receives, not necessarily what the game is using. A game may apply its own button mappings, deadzones, sensitivity curves, controller compatibility rules or input translation layers.
Try this simple isolation sequence:
- Works in the browser, not in one game: check that game's controller mode, bindings and input settings.
- Works over USB, fails over Bluetooth: investigate Bluetooth pairing, compatibility and wireless interference.
- Fails in the browser and Windows controller test: try another cable, port or device before concluding the controller is faulty.
- Only the stick center is inconsistent: inspect resting axis values and compare them with the game's deadzone setting.
For controller aiming differences across games, see FixGamerHub's Controller Sensitivity Converter. It compares supported game settings; it is not a hardware diagnostic tool.
Controller not detected in the browser? Try these fixes
Confirm the operating system can see it
Check Windows' Game Controllers panel or the equivalent device settings for your OS. If the system cannot see the controller, a webpage usually cannot see it either.
Activate the browser tab and press a button
Keep the tester visible and press a face button or move a stick. The Gamepad API may not make the device available until after user interaction.
Switch the cable, port or connection method
A charge-only cable, unstable USB connection or failed Bluetooth pairing can prevent data input. Test a known working data cable if available.
Check for software that changes controller mappings
Steam Input and controller remapping utilities can alter what games or browsers see. Record your current settings before changing them, and test only one change at a time.
Try a second browser
Browser implementations and permissions differ. If the same controller works in another browser, focus on browser compatibility or configuration rather than immediately replacing the controller.
What an online controller test cannot prove
A browser tester is useful for observing input behavior, but it cannot by itself certify hardware health, actual input latency, battery condition, vibration functionality or physical polling rate. Nor can it verify that every game supports the controller. Use manufacturer diagnostics or a repair professional where necessary.
Frequently asked questions
Can I test an Xbox or PlayStation controller online?
You can try any controller that your operating system and browser expose through the Gamepad API, including many common PC-compatible Xbox and PlayStation controllers. Exact behavior depends on the device, connection and browser; compatibility is not universal.
Do I need to install a controller testing program?
Not for a basic browser-based input check. You may still need the operating system's normal device support, drivers or pairing setup for the controller itself.
Why does my controller work in a browser but not in a game?
The game may use different controller APIs, mappings, bindings or supported-device rules. Check the game's input settings and test the same controller in another title.
Does a small non-zero stick value always mean drift?
No. A small offset in browser-reported axis values does not establish a hardware fault. Look for repeatable unintended input, compare with the game's deadzone and test across more than one environment.
