To test a controller outside Steam, verify it in three layers: the operating system must detect the wired or paired device, a browser gamepad tester must show changing button and axis values, and the specific non-Steam game or application must accept those inputs. A browser result confirms browser access to the controller; it does not prove that every game supports the device or its mapping.
Connect the controller first, wake the browser’s gamepad exposure with a physical button press or stick movement, check every control, then test the target application with Steam Input and other remappers accounted for.
As an Amazon Associate I earn from qualifying purchases.
The three checks you need
“Does my controller work?” can mean three different things. Keeping the checks separate prevents a working controller from being mistaken for an unsupported game, or a game-setting problem from being mistaken for a bad cable.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Layer | What to test | What a pass means | What it does not prove |
|---|---|---|---|
| System connection | USB data connection or Bluetooth pairing in the operating system | The computer has a controller available to applications | That a browser or game will use the device correctly |
| Browser input | A gamepad tester showing button, D-pad, trigger and stick changes | The browser can read the controller and report its inputs | That a particular game supports the controller, layout or API |
| Target application | The non-Steam game’s own settings, prompts and controls | The application recognizes and responds to the device | That another game will use the same mapping |
Test in that order. If the controller fails at one layer, fix that layer before changing settings in the next one.
#1 Best Overall
- With broad game support, the Logitech Gamepad F310 works with old standbys to today's biggest titles, so it's easy to set up and use with your favorite games.
- Profiler software allows the gamepad to be programmed to perform keyboard and mouse commands for games without gamepad support.* * Requires software installation.
- A familiar control layout that doesn't require a learning curve to be able to use, with all the same buttons as on an Xbox 360.
- The unique floating D-pad rests on four switches-instead of a single pivot point-making it responsive to quick changes in direction.
- The six-foot cord lets you lean back and play a comfortable distance from your PC monitor.
Connect the controller before opening the tester
USB
Use a USB cable that carries data, not a charge-only cable, and connect directly to the computer when possible. Try a different USB port if the operating system does not react. A light on the controller only proves that it is receiving power; it does not prove that data is reaching the computer.
Bluetooth
Pair the controller in the operating system’s Bluetooth settings before opening a test page. Put the controller into its documented pairing mode, choose it from the computer’s list of available devices, and wait until the system reports it as connected. A webpage cannot make an unpaired Bluetooth controller available.
Temporarily remove input interference
Steam Input, controller-remapping tools and similar utilities can capture a physical controller or expose a virtual one instead. For a clean diagnosis, close or disable those tools temporarily, then reconnect the controller. If the visible device changes when a remapper is closed, record both results: one describes the physical device and the other describes the virtual mapping being supplied to the game.
Use a browser gamepad tester
A browser tester is a convenient hardware-and-browser diagnostic. Controller Test provides an online tester and practical connection guidance; it is a tool provider, not an independent hardware standard. Any comparable page that exposes live gamepad values can serve the same basic purpose.
- Open the tester in a normal browser tab. Do not use a page embedded inside another application or assume that a browser extension has access to the controller.
- Focus the page and create physical input. Press a face button or move a stick after the page is open. A controller connected before page load may not appear until there is user input.
- Confirm that a controller entry appears. Note the reported name and whether the page shows a standard-looking layout or a raw, unfamiliar ordering.
- Exercise every control one at a time. Press each face button, move the D-pad in all directions, squeeze both triggers, press both bumpers, and move both sticks through their full ranges.
- Watch the values while untouched. Release every control and look for an axis that continues moving, a button that remains pressed, or a trigger that never returns to its resting value.
- Repeat after reconnecting if necessary. Reload the page after changing from USB to Bluetooth or after closing a remapper, then press a button again to wake detection.
The browser Gamepad API represents axes as normalized values from -1 to 1 and button values from 0 to 1. These are browser-facing values, not a guarantee that the game uses the same numbering or layout. The W3C Gamepad API Working Draft dated 10 July 2025 states: “If a gamepad was already connected when the page was loaded, the gamepadconnected event SHOULD be dispatched when the user presses a button or moves an axis.” The document is a Working Draft, not a final recommendation.
Rank #2
- The 2.4 GHz wireless connection uses a tiny Plug-and-Forget Nano-receiver that stays in your USB port, even on laptops, for fast data transmission with minimal delays, dropouts, or interference.
- With broad game support, the Logitech Wireless Gamepad F710 works with old standbys to today's biggest titles, so it's easy to set up and use with your favorite games
- Profiler software allows the gamepad to be programmed to perform keyboard and mouse commands for games without gamepad support.* Requires software installation
- Dual vibration motors let you feel every hit, crash and explosion in games that support vibration feedback for a more realistic and immersive experience
- A familiar control layout that doesn't require a learning curve to be able to use, with all the same buttons as on game console controllers
Interpret each control reading
| Control | Healthy observation | Warning sign | Useful follow-up |
|---|---|---|---|
| Face buttons | Each button changes state only when pressed and returns when released | Two buttons report the same input, one never changes, or one stays pressed | Reconnect, then retest with remapping software closed |
| D-pad | Each direction appears separately and diagonals behave consistently | A direction is missing, permanently active, or reported in an unexpected order | Compare the game’s expected mapping with the tester’s reported order |
| Bumpers | Left and right bumper values change independently | One bumper is stuck or activates another control | Check the physical switch and test the controller in its other documented mode, if it has one |
| Triggers | Each trigger moves through its range and returns to rest | A trigger never reaches rest, reaches only part of its range, or is merged with another axis | Check whether the target application expects the controller’s current input API and mode |
| Left and right sticks | Each axis moves smoothly from one extreme to the other and rests near center | Jitter while untouched, a dead section, a jump in value, or an axis that does not respond | Test again over USB and Bluetooth and compare the readings |
Unfamiliar controllers may be exposed with raw ordering rather than the layout a game expects. A tester can therefore show perfectly changing values while the game assigns the wrong action to each button. Treat the tester as proof that input is being reported, not as proof that the mapping is suitable.
Test the actual non-Steam game or application
- Close the tester only if it interferes. Most pages simply read input, but eliminating extra applications makes it easier to see which program owns the controller.
- Launch the target outside Steam. Start the game or application through its normal shortcut, launcher or executable rather than adding it to Steam for this test.
- Open its controller or input settings. Look for a device selector, input mode, key-bind screen or a setting that switches between keyboard and controller.
- Move a stick or press a button in that screen. Check whether the game shows a changed binding, a controller prompt or an on-screen response.
- Test in a safe part of the game. Confirm movement, camera control, an action button, a menu button and any trigger-dependent action. Do not infer full support from one working button.
- Record the exact result. “Not detected,” “detected but wrong prompts,” “some controls missing” and “works normally” point to different fixes.
A browser pass cannot establish that this application supports the controller. Games may support only particular layouts, devices or input APIs, and some expose no controller settings at all. If the game works only after a remapper is enabled, the game is receiving the remapper’s virtual device rather than necessarily supporting the physical controller directly.
Windows: account for XInput and DirectInput
On Windows, applications can use different input paths. Microsoft’s comparison of XInput and DirectInput features documents differences between the two APIs, including how controller features are exposed. A positive result through one path does not establish universal support through the other.
If your controller has a physical XInput/DirectInput switch, test each documented position separately. Move the switch while the controller is disconnected or powered down if the manufacturer’s instructions require that, reconnect it, and repeat the browser and target-app checks. The mode can change the device name, button order and trigger behavior seen by software.
Some applications expect an XInput-style controller while others read DirectInput devices. If the browser sees every control but the game sees none, try the controller’s other supported mode before assuming hardware failure. If one mode works in the game and the other does not, keep the working mode for that application; do not treat the difference as evidence that the controller is defective.
Rank #3
![ZD-V+ USB Wired Gaming Controller Gamepad For PC/Laptop Computer(Windows XP/7/8/10/11) & PS3 & Android & Steam - [Black]](https://m.media-amazon.com/images/I/41Ddk2Xp33L._SL160_.jpg)
- Support PC Windows XP / 7 / 8 / 10 / 11 & PS3 & Steam
- Support Android (version 4.0 or above, and the device must fully support OTG function). Not inlciud a OTG adapter in the package.
- Support Plug and Play, only for PC games supporting Xinput mode / PS3
- Feature: Multi-mode: Xinput & DirectInput / Vibration Feedback Function / JD-SWTICH Function (exchange the functions of D-pad and Left-Stick in Xinput mode)
- USB Wired Gamepad (PS architecture) - Does not support the Xbox 360 / Xbox One / Mac OS
Example of manufacturer mode documentation
The Logitech F310 Gamepad Quick Start Guide documents a PC USB setup and an XInput/DirectInput switch. It is an example of why a controller’s physical mode belongs in the diagnostic record; you do not need to buy that model to test an existing controller.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteTroubleshoot by the first layer that fails
The operating system does not detect the controller
- For USB, try another port and a known data-capable cable.
- For Bluetooth, remove the device from the operating system’s paired-device list, pair it again, and wait for a connected status.
- Power-cycle the controller, then reconnect before reloading the tester.
- Close Steam Input and other remappers so a virtual device does not obscure the physical connection.
- If the controller has input modes, reconnect after selecting the mode documented for the computer or game.
Do not proceed to game settings until the operating system can consistently see the controller. A webpage cannot compensate for a missing USB data connection or incomplete Bluetooth pairing.
The operating system sees it, but the browser does not
- Reload the tester with the controller already connected.
- Click or focus the page.
- Press a button or move an axis once the page is focused.
- Check whether a browser permission prompt or privacy setting is blocking gamepad access.
- Try a second ordinary browser tab or browser to distinguish a page-specific problem from a system-wide one.
The connection-sensitive behavior is expected: the W3C Working Draft describes dispatching gamepadconnected after input for a controller that was present at page load. If no device appears after a fresh connection and physical input, return to the USB/Bluetooth checks rather than changing game bindings.
The browser sees it, but the game does not
- Check the game’s own controller setting and make sure it is not locked to keyboard or a different device.
- Close Steam Input and remapping utilities, then launch the game again.
- Try the controller’s other documented input mode if available.
- Compare the game’s expected layout with the tester’s button and axis order.
- Test a second known controller if one is already available. This is optional, but it can show whether the application rejects the original device generally or only its mapping.
Do not buy another controller merely to perform the basic test. The three-layer comparison usually identifies whether the failure is connection, browser exposure, mapping or application support.
The game detects it, but controls are wrong
- Use the game’s rebind screen to assign each action manually, if available.
- Check for a prompt or layout selector that changes between controller families.
- Compare each action with the browser tester, one control at a time, rather than relying on the printed labels on the controller.
- Disable a remapper that may be translating the same button twice, or use only one remapping layer deliberately.
- Switch between XInput and DirectInput only when the controller supports both and the manual documents the procedure.
A stick moves while untouched or a trigger is stuck
First repeat the test with the controller resting on a flat surface and no remapper active. If the tester still shows movement at rest, the browser is reporting the controller’s raw state; the target application may provide a dead-zone setting, but that setting cannot repair a physically missing range or a button that remains electrically pressed. Record whether the behavior occurs over both USB and Bluetooth. Matching behavior in both connections points toward the controller or its calibration rather than one cable or radio link.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesCompare wired and Bluetooth without changing two variables at once
Use the same browser, tester page and target-app settings for both connection types. Start with USB, record detection and every abnormal control, then disconnect and repeat over Bluetooth. Change only the connection method between runs.
| Result | Likely area to investigate |
|---|---|
| USB and Bluetooth both fail at system detection | Controller power, pairing state, cable-independent hardware or selected mode |
| USB works; Bluetooth is absent | Bluetooth pairing, controller wireless mode or the computer’s Bluetooth connection |
| Both connect, but only USB has clean values | Wireless connection or its mode; repeat pairing and compare again |
| Both have clean browser values, but the game fails | Game support, API expectation, mapping or input capture |
This comparison is diagnostic, not a latency benchmark. The available evidence does not establish a universal performance difference between wired and Bluetooth connections.
Keep a short diagnostic record
Writing down the result prevents you from repeating the same test after every setting change. Record:
- Connection type: USB or Bluetooth.
- Whether the operating system detected the controller.
- The name and layout shown by the browser tester.
- Any button, D-pad, trigger or stick that failed, drifted or stayed active.
- Whether Steam Input or another remapper was running.
- The controller’s physical input mode, if it has one.
- The target application’s exact behavior: no detection, wrong mapping, partial response or normal operation.
Change one variable, reconnect if needed, and repeat the same control checklist. That method distinguishes a bad cable from a mode mismatch and a game-support limitation without guessing.
Quick Recap
Common mistakes that produce false conclusions
- Opening the tester before pairing Bluetooth. The page cannot pair a device for you.
- Waiting for a controller to appear without touching it. Press a button or move a stick after loading the page.
- Testing only one button. One working face button does not validate triggers, D-pad, bumpers or sticks.
- Assuming a browser layout is the game’s layout. Raw ordering and game-specific mappings can differ.
- Leaving a remapper active without noting it. You may be testing a virtual controller instead of the physical one.
- Calling a game unsupported because prompts are wrong. Rebind controls or test the alternate documented input mode first.
- Calling the hardware defective because one game rejects it. A browser pass plus a second application can show that the limitation belongs to the first game.
A compact decision path
- No system detection: fix USB, Bluetooth pairing, power or mode.
- System detection but no browser detection: reload, focus the page, press a control, then try another ordinary browser.
- Browser detection with bad values: isolate the connection, close remappers and inspect the controller or mode.
- Clean browser values but no target-app response: inspect the game’s controller settings, API expectations and input capture.
- Target app responds with wrong actions: compare reported order, rebind controls and test the other documented mode.
- Everything responds normally: the controller is working for that application and connection; do not generalize the result to every other game.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
