Quick hardware check
If a gamepad connects, the visualizer updates immediately. If rumble also works, you can confirm that the browser, operating system, cable, wireless mode, and controller firmware are all exposing haptics correctly.
Press any button to connect, tune the two motors, then send a quick rumble pattern straight from the browser.
Live sticks, buttons, and trigger pressure update while you test rumble support.
Vibration testing checks whether the browser can send rumble commands to your controller and whether both motors respond at the expected strength.
If a gamepad connects, the visualizer updates immediately. If rumble also works, you can confirm that the browser, operating system, cable, wireless mode, and controller firmware are all exposing haptics correctly.
Some browsers only expose standard buttons and axes, while others also expose vibrationActuator or haptic fallback methods. Bluetooth mode, mobile browsers, and certain adapters may hide rumble entirely.
On controllers that support dual rumble, the left motor usually feels heavier and lower frequency, while the right motor feels lighter and sharper. Testing them separately makes imbalance easier to spot.
Common questions when rumble works in games but does not work inside the browser.
The button stays disabled until the page sees a connected controller and confirms that the browser exposes a usable vibration API for that controller.
Games can use platform-specific drivers or native APIs that the browser cannot access. Web pages depend on the browser's Gamepad implementation, which is more limited.
Yes. Some controllers expose richer haptics over USB than Bluetooth, and some adapters only pass through basic buttons and sticks with no rumble support.
Reconnect the controller, wake it with a button press, try USB instead of Bluetooth, and test again in the latest Chrome or Edge. If the controller still does not report support, the browser likely does not expose rumble for that device.