Supported Controllers and Browsers

The compatibility chain

Successful testing requires the controller, firmware mode, connection, operating system, driver, and browser to work together. A controller may work in a console or native game but remain hidden from a webpage. Another may appear with a generic name or nonstandard button order and still be usable.

The tester is designed for modern desktop and mobile browsers that implement the Gamepad API. Support can change with browser and operating-system updates, so connect the device and press a button for the most reliable check.

Commonly testable controller families

• ✓Xbox Wireless Controller and many XInput-compatible gamepads
• ✓PlayStation DualSense, DualSense Edge, and DualShock 4 in supported environments
• ✓Nintendo Switch Pro Controller and Joy-Con combinations where the platform exposes them
• ✓8BitDo, GameSir, Logitech, and similar third-party controllers in a compatible mode
• ✓Generic USB and Bluetooth gamepads exposed by the operating system
• ✓Arcade sticks, racing wheels, retro controllers, and specialty devices when they present a gamepad interface

Inputs that may be limited

Capture, system, microphone, profile, paddle, touchpad, motion, battery, audio, adaptive-trigger, lighting, and vendor-specific controls are not consistently exposed to webpages. Browser haptics support is narrower than basic button and axis support. Their absence in the tester does not automatically indicate hardware failure.

Connection guidance

• ✓Use a known-good USB data cable, not a charge-only cable
• ✓Pair Bluetooth through the operating system before opening the tester
• ✓Use the manufacturer-supported wireless adapter when required
• ✓Try XInput or standard gamepad mode on controllers with a mode switch
• ✓Close duplicate mapping layers while diagnosing unexpected input
• ✓Test the same connection mode you plan to use in play

Browser privacy behavior

Many browsers do not reveal a connected controller until the page is focused and the visitor presses a controller button. This helps reduce passive device fingerprinting. Private browsing, embedded frames, remote desktop, operating-system permissions, or enterprise policies can also limit detection.

Still not detected?

Follow the controller-not-detected guide, test a direct cable, try another current browser, and confirm that the operating system recognizes the device. If native games see the controller but browsers do not, the limitation may be in browser exposure rather than the hardware.