A PC controller setup is only as good as the path from the pad to the game. Before you tweak Steam Input or in-game binds, confirm the hardware in a browser with the PC Controller Tester or the general Controller Tester. Those pages use the Gamepad API to show live buttons and axes without installing a special desktop app. That makes them ideal for quick checks after you change cables, dongles, or Bluetooth adapters.
USB versus Bluetooth on Windows
- USB is usually the most reliable path for browser detection and rumble on Vibration.
- Bluetooth must finish OS pairing before any gamepad tester can list the device.
- Windows Game Bar and exclusive apps can confuse detection. Close them, reconnect, and press a button.
If the pad never appears, follow Controller Not Detected and verify presence on Controller Detection. Wired connections reduce latency and dropouts for competitive play. Wireless is fine for couch sessions once pairing is stable.
Xbox, PlayStation, and generic pads
Xbox pads on PC are often plug and play. DualSense and DualShock models usually work over USB in browsers; Bluetooth behavior depends on the Windows build and whether another app already claimed the device. Generic DirectInput pads may show as unknown mapping. That is normal: press each control and map by index instead of by Xbox names. After detection works, validate sticks with Stick Drift and center gates with Deadzone so you catch hardware issues early.
Browser honesty for PC testing
The browser does not call native XInput directly. It reads whatever the OS exposes to the Gamepad API. That is enough for a solid health check, but it will not replace vendor firmware tools or guarantee adaptive triggers and touchpad gestures. For the technical limits, read Gamepad API Explained. If aim drifts on PC shooters, combine this guide with How to Fix Stick Drift.
A practical PC workflow
- Connect USB or complete Bluetooth pairing in Windows settings.
- Open the PC Controller Tester and press a button to wake the pad.
- Confirm every button, both sticks, and both triggers.
- Run stick drift and deadzone checks before ranked play.
- Only then configure Steam Input or game-specific remaps.
More PC-focused tips appear on the blog and in the Troubleshooting guide. A short gamepad tester session on PC separates cable faults, Bluetooth glitches, and true stick wear so you fix the right layer first.
Related reading
Bluetooth adapters and drivers on Windows
Not all Bluetooth is equal on PC. A built-in laptop adapter, a cheap USB dongle, and Microsoft's Xbox Wireless Adapter behave differently, and Windows may pair a pad while still giving the browser an unstable link. If Bluetooth detection is flaky, open Windows Bluetooth settings, remove the controller completely, and pair it fresh — a stale pairing from months ago is a common ghost. Check for driver updates through Windows Update and the adapter maker's software before you blame the pad. If a dongle sits behind the PC next to USB 3.0 ports and a Wi-Fi antenna, move it to a front port or an extension cable: interference there is real, and a few inches of distance often fixes dropouts that look like hardware failure. Confirm the result on the Controller Detection page before moving on.
Steam Input: when it helps and when it hides the pad
Steam Input is powerful, but it can also hide a controller from the browser. When Steam claims a pad, the Gamepad API may never see it, which is why a pad can work perfectly in Steam games yet stay invisible on the PC Controller Tester. For browser diagnosis, close Steam completely and retest — if the pad appears, Steam's exclusive claim was the cause, not a fault. For actual gaming, the reverse applies: per-game Steam Input profiles can fix mapping for pads that Windows sees as generic, and you can set deadzones and response curves per game without touching global settings. Keep the two jobs separate: browser first for honest diagnosis, Steam second for comfortable play.
Firmware and maker tools
Before you declare a pad faulty, check whether its maker ships a firmware updater for Windows. Xbox pads update through the Xbox Accessories app, and PlayStation pads have official PC updater tools — outdated firmware causes real detection and input bugs that no browser setting can fix. Update over USB, not Bluetooth, and retest on the Controller Tester afterward so you can compare before-and-after readings fairly. Vendor tools are also the only place for features browsers cannot touch: adaptive triggers, touchpad gestures, and official calibration writes live outside the Gamepad API, which is why the browser honestly reports their absence instead of faking them.
XInput versus DirectInput on PC
Windows games mostly speak XInput (the Xbox standard), while older and generic pads often speak DirectInput. A generic pad in DirectInput mode may appear in the browser with unknown mapping — buttons and sticks report values, but under unfamiliar names. That is normal, not broken: press each control, note its index, and map by index in your game or through Steam Input. If a pad has a mode switch, X-input mode is the right choice for modern PC games and browser testing alike. If it has no switch and games misread it, Steam Input's mapping layer or the game's own remap screen will bridge the gap — the browser's job is only to prove every control reports a value, which the Controller Tester does regardless of mode.
Cutting latency on PC
For competitive play, the connection path matters as much as the pad. Wired USB is the lowest-latency, most stable option, and it removes battery and interference variables entirely. On wireless, use a dedicated dongle over generic Bluetooth where possible, keep the dongle close and clear of USB 3.0 interference, and close bandwidth-hungry background transfers during ranked sessions. Windows Game Bar and Game Mode rarely break controllers, but overlays that grab exclusive access do — close them for diagnosis, then re-enable them one at a time for play. After any change, run the Stick Drift Test and Deadzone Test before ranked play: a fast connection to a drifting stick is still a drifting stick.
DualSense on PC: honest expectations
DualSense pads work well on PC over USB in browsers, with buttons, sticks, triggers, and basic rumble all visible to the Gamepad API. Over Bluetooth, behavior depends on the Windows build and whether another app already claimed the pad — if Bluetooth detection is flaky, USB is the honest baseline. Adaptive trigger effects and touchpad gestures from native PlayStation games do not come through the basic Gamepad API, and no browser tester can promise them. For stick center and range writes after a module swap, the PS4 / PS5 Calibration tool uses WebHID over USB where Chrome or Edge grants access — a separate, deeper layer from the standard browser test, and the right place for permanent calibration rather than a temporary deadzone.
Frequently asked questions
Do I need drivers for an Xbox pad on Windows?
Usually no. Modern Xbox pads are plug and play on current Windows builds, with drivers arriving through Windows Update. If a pad is invisible, check cable, port, mode, and exclusive locks before hunting for drivers.
Why does my PS5 pad show up as a generic controller?
Usually the connection mode or the Bluetooth stack. Over USB with the right mode it normally identifies correctly; over some Bluetooth stacks it appears generic. Confirm on the Controller Detection page, test over USB, and map by index if a game still shows unfamiliar names.
Is wireless good enough for competitive play?
A stable dedicated dongle connection is close, but wired USB remains the most consistent choice for ranked play — no battery fade, no interference dropouts, and the lowest latency. Test both on the PC Controller Tester and trust the readings, not the marketing.
Do I need Steam for browser testing?
No. Browser testing is independent of Steam and works with no game launcher installed. Steam matters for playing games comfortably, not for diagnosis — and closing it during diagnosis is often the fix itself.