Start by separating hardware from software.
Online controller testers use the browser Gamepad API, which exposes buttons, axes, connection state, and limited device information for gamepads recognized by the operating system. Support is a chain: controller, cable or radio, driver, operating system, browser, and webpage must all cooperate.
Current desktop browsers generally provide the most complete experience after you connect a controller and press a button on the active page. Mobile browsers, embedded webviews, remote desktops, privacy modes, and uncommon devices can expose fewer capabilities.
Special features such as motion sensors, touch surfaces, audio, LEDs, advanced haptics, adaptive triggers, macros, rear controls, and firmware settings are not standardized browser inputs. Use official native software or the intended console for those checks.
Work through the likely causes.
- 01
Use a current mainstream browser on a supported desktop operating system and open the tester in a normal active tab.
- 02
Connect the controller through the operating system, then press a button after the page loads.
- 03
Allow the page to remain visible during timing samples because browsers throttle background tabs.
- 04
If a control is missing, compare USB and wireless modes and inspect raw mapping before assuming hardware failure.
- 05
Close virtual-controller or remote-access layers when you need to inspect the physical device directly.
- 06
Verify console-specific features on their intended platform or with supported manufacturer tools.
Check what the browser can see.
Open the full tester to inspect buttons, sticks, triggers, mapping, range, and neutral noise.
Repeat before you conclude.
A repeatable issue across connections, browsers, and native games is stronger evidence of a controller fault than a one-time browser reading. If the problem appears only in one game, review that game’s controller support, deadzone, remapping, and launcher settings.
What to keep in mind
Browser support and device mappings can change as operating systems and browsers update.
How the browser readings are defined
Our live tools use the standardized browser Gamepad interface and explain its limits in our methodology. Device mappings and proprietary features can still differ by operating system, browser, connection, firmware, and controller mode.
Questions about this issue
Which browser is best for controller testing?
A current Chromium-based desktop browser or Firefox is a practical starting point. Exact device and haptic support varies by operating system and browser version, so compare another current browser when troubleshooting.
Why does the controller appear only after a button press?
Browsers commonly require a user gesture before exposing gamepad information to reduce passive device discovery.
Does the site support every controller?
No website can guarantee that. It can test standard inputs for controllers that the operating system and browser recognize and expose through the Gamepad API.