How Does Browser Controller Detection Work?
Modern browsers expose connected gamepads through the W3C Gamepad API. When a controller is plugged in or paired, the browser fires a 'gamepadconnected' event, and JavaScript can then poll the controller's button and axis state on every animation frame.
This polling model is different from keyboard and mouse, which fire individual events. For gamepads you continuously read the current snapshot: pressed buttons, axis positions, trigger values: typically at 60 Hz alongside the display refresh.
One quirk: browsers won't detect a controller until you press a button. This is a security measure to prevent fingerprinting. So even with a controller plugged in, the page will show 'no controller detected' until you press a face button or move a stick.
The API also exposes vibrationActuator on supported controllers (Xbox, DualSense, and most modern wireless gamepads). This enables rumble feedback from the browser, which our tester uses for the vibration test.
Supported Controllers and Their Quirks
Xbox One, Xbox Series X|S, Xbox 360 (wired), and the Xbox Adaptive Controller all work via USB and Bluetooth on Windows, Mac, and Android. Mappings follow the standard layout (A=0, B=1, X=2, Y=3).
PlayStation 4 (DualShock 4) and PlayStation 5 (DualSense) controllers work via Bluetooth on macOS 12+ and Windows 10 1903+. On Linux, kernel 4.10+ supports them natively. Button mapping is non-standard on Windows without driver intervention: DS4Windows is a popular tool that re-maps them to Xbox layout.
Nintendo Switch Pro Controller works on PC via USB. Bluetooth pairing works on Mac and recent Windows builds. Joy-Cons each enumerate as a separate gamepad, which is unusual.
Generic USB gamepads (8BitDo, Logitech F310, GameSir) usually present themselves as a standard XInput device on Windows. Mapping varies: use our Classic Controller Test to see the raw index data for unknown controllers.
Mobile controllers (Backbone, Razer Kishi) work as standard MFi or USB gamepads. Our tester detects them on both phones and tablets.
Why Doesn't My Controller Connect to the Browser?
The most common issue is forgetting to press a button after connecting. Browsers wait for user gesture before exposing controllers. Press A, X, or any face button and the controller will appear in our tester immediately.
If pressing a button does nothing: verify the OS sees the controller first. On Windows, open Game Controllers from the Start menu (joy.cpl). The controller should be listed with full button preview. If it's not, install vendor drivers.
For wireless controllers, low battery causes inconsistent detection. The controller may pair briefly then disconnect. Charge the controller fully via USB and retry.
Bluetooth interference from other devices (especially 2.4 GHz Wi-Fi networks and other Bluetooth peripherals) can cause input dropouts. Move the controller within 3 feet of the receiver and try again.
On Mac with PlayStation controllers, the controller occasionally pairs as a separate Bluetooth device per app. If the browser doesn't see it but games do, restart the browser.
Analog Stick Drift Explained
Stick drift is when an analog stick reports a non-zero value while at rest. Our tester clearly shows this: with the controller untouched, the stick position should sit dead center at (0, 0). If it drifts to something like (0.15, -0.05), that's measurable drift.
The physical cause is wear on the potentiometers inside the stick module. These are mechanical components with carbon tracks; over thousands of hours of use, the carbon wears, the wiper makes inconsistent contact, and the reported position no longer correctly maps to actual stick position.
Xbox controllers have historically had a known issue with stick drift on the Series X|S Carbon Black controllers. PlayStation DualSense drift was the subject of a class-action lawsuit. Nintendo Joy-Con drift is legendary. None of these are user error.
The permanent fix is replacement of the stick module. Most modern controllers use TMR or Hall-effect sticks (no carbon wear) and are advertised as 'drift-free'. Replacement modules for traditional controllers are available on iFixit and AliExpress for $5–15 and can be swapped with basic soldering skills.
Temporary fixes: most games and Steam's controller settings allow a deadzone increase. Set the deadzone slightly larger than the drift value to ignore it. This costs you a bit of stick precision but eliminates unwanted input.
Testing Controller Vibration and Rumble
Modern controllers expose vibration through the Gamepad API's vibrationActuator interface. Our tester sends a 1-second 'dual-rumble' effect with strong and weak magnitudes set high enough to feel clearly.
If you press the rumble button and feel nothing, your controller may not expose vibrationActuator (older or generic controllers often don't), or the browser may not support the Gamepad Haptics extension yet. Chromium-based browsers (Chrome, Edge, Brave) have the best support; Firefox lags behind.
The DualSense controller exposes both rumble and the unique haptic actuators that allow adaptive triggers. The browser API doesn't expose adaptive triggers yet: only the basic rumble works through web pages.
If rumble works in native games but not in our tester, restart the browser. The vibration actuator handle can get stuck after a game grabs it. Closing and reopening the browser usually clears the lock.