Controller Vibration Test
Send dual-rumble effects when the browser exposes a vibration actuator.
Vibration controls
Tune weak/strong magnitude and duration, then play or loop effects.
Probe dual-rumble through the browser actuator
The Vibration page sends rumble when the Gamepad API exposes a vibration actuator, most often on Chromium desktop over a stable connection. Use short pulses to confirm motors spin, then longer patterns to feel left and right imbalance. If rumble is silent here but works in a native game, the gap is usually browser support, not dead hardware. Cross-check the pad on Controller Tester first so you know detection succeeded.
Adaptive trigger resistance, DualSense HD haptics, and vendor-specific waveforms are outside standard Gamepad vibration. The API offers a simple dual-rumble model when present. Bluetooth sessions may omit actuators even though USB rumble works. That inconsistency is a platform limit you should expect.
Checklist before declaring motors dead
- Retest over USB in an up-to-date Chromium build.
- Close exclusive apps that may lock the device.
- Confirm the gamepad remains selected if multiple pads are connected.
- Compare with brand pages like PS5 Vibration Test or Xbox Vibration Test.
For detection failures before rumble, open Controller Detection. Missing browser vibration alone is weak evidence for a repair order. Walk through the full checklist in Controller Vibration Not Working.
FAQ: can this strengthen weak rumble permanently?
No. Amplitude sliders here only affect the temporary actuator call. They do not rewrite motor firmware or fix mechanically jammed masses inside the shell.