How to connect your controller and get testing
Got a controller in hand and ready to run some tests? This guide walks through USB, Bluetooth, the quirks specific to Windows, Mac, Android and iOS, which browsers work best, and what to do when something refuses to cooperate.
Last updated July 2026. About 3 minutes to read, 30 seconds to actually do.
Connect in four steps
Plug in or pair
Plug your controller into a USB port, or pair it over Bluetooth in your system settings.
Press a button
Come back to this tab and press any button on the controller. The browser needs a physical interaction before it exposes gamepad data.
Watch the status
The status pill on the home tester switches from Waiting for input to Live once the Gamepad API sees your pad.
Pick a test
Choose a diagnostic from the homepage or the all tools page and go.
If step 3 didn't happen, don't worry, it's almost always something small. Keep reading.
Why you have to press a button first
This trips people up more than anything else. Browsers don't hand over gamepad data automatically the moment you plug something in. That's on purpose. Web pages could otherwise fingerprint your hardware or snoop on input without you knowing, so the Gamepad API stays silent until it sees a real physical interaction, a button press or a stick movement.
That means even if your controller is plugged in correctly, showing a solid light, and working fine in every other app on your computer, this site (and every other browser-based gamepad tester) will show nothing until you physically press something. It's not a bug, and it's not specific to this site. Once you know this, half the "my controller isn't detected" confusion disappears.
Connecting over USB
USB is the most reliable way to connect any controller, and for most people it's genuinely plug and play.
- Plug the controller into any free USB port.
- Give your operating system a couple of seconds to recognize the new device. Windows usually plays a little chime.
- Open or refresh the home tester.
- Press any button. A, X, Cross, or the Home/Guide button all work fine.
A few things that trip people up
Connecting over Bluetooth
Bluetooth needs one extra step compared to USB: pairing the controller with your computer through your system settings, before this page can see it.
On Windows 11
- Put the controller into pairing mode. On an Xbox controller, hold the small Pair button on the top edge for about 3 seconds until the Xbox logo starts flashing quickly rather than staying solid.
- Click Start, then go to Settings > Bluetooth & devices.
- Turn the Bluetooth toggle on if it isn't already.
- Click Add device, choose Bluetooth, and select your controller once it shows up in the list.
- Wait for Windows to confirm the device is ready.
- Come back to this tab and press a button to wake it up.
A few Windows-specific notes: DualShock 4 and DualSense controllers pair with Share + PS held together. Switch Pro controllers use the small sync button on the top edge, near the USB-C port. If a controller was previously paired with a console, it sometimes needs to be manually forgotten from that console first. Some controllers only remember one paired device at a time. Keep the controller within about 20 to 25 feet of your PC during pairing. Range drops fast through walls, and interference from other 2.4GHz devices can cause pairing to time out. If Windows shows the device but pairing keeps failing, remove it from Bluetooth & devices entirely and start fresh.
On macOS
- Put the controller into pairing mode the same way as above.
- Open System Settings > Bluetooth.
- Wait for the controller to appear under Nearby Devices and click Connect.
- Refresh this page and press any button.
Officially supported Bluetooth controllers on macOS are first-party Xbox, PS4, PS5, and MFi-certified pads. Third-party and generic Bluetooth controllers can be hit or miss depending on your macOS version. If yours won't pair at all, use a USB cable instead.
On Linux
- Open your desktop's Bluetooth settings (varies by desktop environment, usually under Settings > Bluetooth).
- Put the controller into pairing mode.
- Select it from the discovered devices list and connect.
- If it connects but doesn't work in the browser, check that the
xpadorhid-sonykernel driver is loaded. Most distros include these by default.
On Android and iOS
Both handle Bluetooth gamepads natively, no extra app required for basic input.
- Android: go to Settings > Connected devices > Pair new device, then follow the same pairing-mode steps as above.
- iOS/iPadOS: needs version 16.4 or later for broad Bluetooth gamepad support. Go to Settings > Bluetooth and connect as usual. Earlier iOS versions only support a shorter list of MFi-certified controllers.
Which browsers work best
The Gamepad API is supported broadly, but the experience isn't identical everywhere.
| Browser | Support level | Notes |
|---|---|---|
| Chrome | Excellent | Best overall support, including vibration |
| Edge | Excellent | Same engine as Chrome, same level of support |
| Firefox | Good | Reads buttons and sticks well, vibration support is inconsistent |
| Safari | Supported (16.4+) | Solid on recent versions, weaker on anything older |
If a specific feature isn't working, like vibration testing, before assuming your controller is broken, try the same test in Chrome or Edge. It rules out a browser limitation versus an actual hardware issue.
Wired or wireless, which should you use
Both work fine for testing and for most games, but if you're chasing every millisecond for competitive play, here's the honest breakdown.
Wired (USB) gives the most consistent, lowest latency connection, and polling rates on wired controllers can reach 500 to 1000Hz depending on the pad. There's no battery to manage, and no chance of interference dropping your connection mid-match.
Bluetooth is more convenient day to day, but typically runs a lower polling rate, often 125 to 250Hz, and can occasionally suffer from interference in crowded wireless environments. For casual play it's rarely noticeable. For ranked or competitive play, wired is the safer bet.
You can measure the real difference on your own setup with our Polling Rate Test and Latency Test, comparing the same controller wired versus wireless.
Platform-specific notes
| Controller | What to know |
|---|---|
| Xbox (Series X/S, One) | Works instantly over USB-C. For Bluetooth, make sure you're using actual Bluetooth pairing mode, not the older Xbox Wireless protocol, which needs a separate USB dongle. |
| PlayStation (DualSense, DualShock 4) | USB-C cable works immediately. Bluetooth pairing uses Share + PS held together until the light bar flashes rapidly. |
| Nintendo Switch Pro / Joy-Con | Pairs over Bluetooth using the small sync button. Joy-Cons are tested individually, connect one at a time if you want to check each separately. |
| Generic USB/Bluetooth pads (8BitDo, Logitech, etc) | Usually works fine, but check for an Xinput/Dinput switch on the back. It changes how the browser reads the controller entirely. |
Keeping your controller in good shape
A little maintenance goes a long way toward avoiding the problems this whole guide exists to solve.
- Store it somewhere dust-free. Dust inside the stick housing is the number one cause of stick drift over time. A drawer or a dedicated case beats leaving it sitting out.
- Don't let the battery sit fully drained for long periods. If your controller has a built-in rechargeable battery, deep discharges for extended stretches can shorten its lifespan. Topping it up every few months when not in regular use helps.
- Update the firmware occasionally. Manufacturers push out updates that improve deadzone handling, connection stability, and battery efficiency. Worth checking every so often through the official companion app (Xbox Accessories, DualSense companion app, etc).
- Avoid high-wattage fast chargers unless the manual says it's fine. Some controllers charge fine on a basic 5W brick but can have issues on aggressive fast-charging bricks meant for phones.
Still not working? Troubleshooting checklist
Work through these in order. Together they resolve nearly every connection issue we hear about.
Refresh the page, then press a button
Browsers only expose gamepad data after they see a physical interaction. If your controller was already connected before you opened this tab, it may just need a fresh button press.
Try a different USB port or cable
Covered above, but worth repeating because it's genuinely the most common fix.
Check for other software holding the controller
Steam can grab exclusive access to a controller through Steam Input, which can block the browser from seeing it. Try closing Steam, or disabling Steam Input for that specific controller in Steam's settings, then reload this page.
Re-pair from scratch on Bluetooth
Rather than just reconnecting, remove the controller entirely from your Bluetooth device list and pair it again as if for the first time. This clears out stale connection data that can cause silent failures.
Charge it up
A controller running low on battery will sometimes still show a light and connect briefly, but fail to hold a stable connection. Give it 15 to 20 minutes on the charger and try again.
Test in a different browser
If you've tried everything above and it's still not working, open the same page in Chrome (if you were using something else). This isolates whether the issue is your controller, your OS-level pairing, or just that particular browser.
Try a different USB device entirely
If none of the above works, plug in a different USB device (a mouse, a flash drive) to confirm the port itself is working. Rules out a dead port versus a controller issue.
Frequently asked questions about setup
Do I need to install anything?+
Can I test more than one controller at once?+
Why does my controller work in Steam but not here?+
My controller shows as connected but none of the buttons register.+
Does this work on a Chromebook?+
Once you're connected
With the status pill showing Live, you're ready for any test on the site. A few good starting points depending on why you're here:
- New controller, just unboxed? Start with Button Mapping Test to catch factory defects early, before a return window closes.
- Buying used? Run Button Mapping, then Stick Drift Test, then Vibration Test in that order.
- Something feels off in your aim? Go straight to Stick Drift Test.
- Setting up for competitive play? Compare wired versus wireless with Polling Rate Test and Latency Test.