How to test the rumble motors
Connect the controller and press a button. The sliders set each motor’s strength separately, from 0 to 100%, and the duration applies to the single-motor buttons:
- Both motors, Strong motor and Weak motor play one effect at the strengths you set.
- Pulse, Heartbeat, Ramp up and Alternate motors play patterns, scaled by the same sliders.
- Trigger rumble appears when the browser can drive the impulse triggers of an Xbox One, Series or Elite controller.
- Keep going until I press Stop repeats the effect or pattern. It stops when you press Stop, switch tabs, disconnect the controller, or after two minutes.
Afterwards, tell the tester whether you felt it: the answer goes into the controller’s health report.
Finding a weak or dead motor
Start at 100% with Alternate motors. Each half should be clearly different: the strong motor is a heavy, low rumble, the weak one a higher buzz. Then use Ramp up: a healthy motor grows smoothly through all five steps. A motor that only starts at the last step, rattles, or cuts out when you tilt the controller usually has a loose weight or a broken wire. Low battery weakens rumble first, so test while charging or over a cable.
If nothing vibrates at all, check the browser before the controller: the limits under the test say whether your browser and this controller support rumble.
Browser support
Rumble comes from the Gamepad API’s vibration actuator (MDN). Chrome has supported the dual-rumble effect since version 68 and trigger rumble since version 126. Safari added dual-rumble in 16.4 on macOS; its trigger rumble is still behind an experimental flag. Firefox doesn’t support it. Each effect can last at most 5 seconds in Chrome (source), which is why continuous mode chains effects.
Some controller and connection combinations offer no actuator even in Chrome. A cable is the most reliable route. Run the other checks on the controller tester, and check your headset or speakers with the speaker test.