Missing vibration is frustrating because games, browsers, and operating systems each expose rumble differently. Start with the Vibration Test on a desktop Chromium browser over USB. If the page reports no vibration actuator, that often means the web stack lacks access, not that the motors are dead.
Browser versus native rumble
Native Xbox, DualSense, and DualShock titles can use richer haptic channels than the basic Gamepad API dual-rumble model. Adaptive DualSense effects and some impulse triggers will not appear in a simple web pulse. A successful browser pulse only proves basic actuator access. A failed browser pulse needs a USB retest and a native game check before you replace hardware.
- Prefer USB for the first rumble experiment.
- Close exclusive apps that may lock the pad.
- Confirm detection on Controller Detection.
- Run a full input pass on the Controller Tester.
- Update official firmware tools from the manufacturer when available.
Bluetooth sometimes omits rumble in browsers even when games still shake the pad. That mismatch is a known web limitation. Document browser, connection type, and whether native games rumble before buying replacement motors.
When hardware is likely
If USB Chromium cannot pulse, native games also stay silent, and the OS sees the pad, then motors, drivers, or board power deserve attention. Fightsticks and some generic pads never expose vibrationActuator at all.
Continue with brand tools such as PS5 Vibration Test or Xbox Vibration Test when you already know the platform. For broader troubleshooting trees, open Troubleshooting and the blog.
Gamepad Tester will not claim a motor is destroyed based on a single missing web actuator flag. Gather USB and native evidence, then decide on repair. That approach avoids false alarms and keeps your gamepad tester workflow aligned with how browsers actually work.
Also confirm buttons and sticks still report cleanly while you chase rumble. A pad that fails multiple systems may need deeper board work than a single motor swap. Keep a short log of each test so you do not repeat the same blind steps across browsers.
Testing rumble the right way
Open the Vibration Test on a desktop Chromium browser over USB — that combination is your baseline, because it removes the two biggest variables (browser support and wireless path) before you judge anything. Try the weak pulse first, then the strong pulse, then a loop pulse. A weak pulse proves the actuator channel exists; a strong pulse proves both motors respond; a loop pulse proves sustained rumble without dropouts. Test one pulse at a time and wait for each to finish — stacking pulses tells you nothing. Write down the browser, the connection type, and which pulses worked. If the page reports no vibration actuator at all, that is a result too: it usually means the web stack lacks access, not that the motors are dead. Confirm detection on the Controller Detection page first, because a pad the browser cannot see cannot rumble for it either.
Why rumble differs by connection
The same pad can rumble over USB and stay silent over Bluetooth, and that mismatch is a known web limitation rather than a fault. Bluetooth paths in browsers often omit the vibration actuator entirely, even when native games still shake the pad over the same link. Dedicated dongles behave better than generic Bluetooth in most cases, and a wired connection removes the question altogether. If rumble works over USB but not over Bluetooth, the motors are fine — the wireless path is the limit. If it fails over USB as well, move to the decision table below before you spend money on parts.
Browser support, honestly
Chromium-based browsers offer the strongest vibration support; Firefox is partial, and Safari is the weakest, with some builds exposing no actuator at all. All of them require a secure HTTPS page before vibration is available, and private windows or script-blocking extensions can interfere. Test in a normal Chromium window over USB first. Only after that baseline fails should you compare browsers — otherwise you will chase a browser limit while believing it is a hardware fault. Brand-specific checks live on the PS5 Vibration Test and Xbox Vibration Test pages once you know the platform.
Motor types: what you are actually testing
Not all shaking is the same. Most pads use eccentric-weight rumble motors — a weak motor and a strong motor spinning at different speeds. Some newer pads add haptic actuators that can produce finer effects, and DualSense adaptive triggers are a third, separate system that the basic Gamepad API dual-rumble model cannot reproduce. A browser pulse tests only the basic dual-rumble channel. So a DualSense that shakes beautifully in a native game but only pulses weakly in the browser is not broken — the game uses private channels the web cannot reach. Fightsticks and some generic pads, meanwhile, never expose a vibration actuator at all. No actuator flag on such a pad is normal by design, not a fault — check the pad's specifications before you declare its motors dead.
Decision table: API limit or hardware?
- Browser fails, native game rumbles: API or browser limit. The motors work; the web path does not reach them.
- Browser fails over Bluetooth, works over USB: wireless path limit. Use USB for rumble checks.
- Browser fails over USB, native game also silent, OS sees the pad: hardware territory — motors, drivers, or board power.
- Browser fails, native game fails, OS does not see the pad: connection problem, not a motor problem. Fix detection first.
- No actuator flag on a fightstick or generic pad: often normal by design. Verify the specifications before buying parts.
Repair or replace?
If the decision table points at hardware, weigh the fix honestly. A motor swap is reasonable on a popular pad with available parts and guides; board-level power faults and rare-pad parts usually are not worth it. Run the Controller Tester first and confirm buttons and sticks still report cleanly — a pad failing multiple systems needs deeper board work than a single motor swap. For a used purchase, decide inside the return window with your test log in hand: USB Chromium result, native game result, and connection type, written down, beat any argument with a seller. And keep that log after repair too — a retest under the same conditions is the only fair proof the fix worked.
Frequently asked questions
Can browser rumble tests damage my motors?
No. The Vibration Test sends short, standard pulses — the same kind of signal games send constantly. It cannot burn out a healthy motor, and a motor that fails during a short pulse was already failing.
Why is browser rumble weaker than in games?
Because the browser only gets the basic dual-rumble channel. Native games use richer haptic channels, adaptive triggers, and impulse motors that the Gamepad API cannot reproduce. Weaker browser rumble is a standard limit, not a fault.
My pad vibrates in menus but not in the browser test — why?
Usually an exclusive lock or the Bluetooth path. A game, overlay, or wrapper tool may hold the pad, or the browser's Bluetooth link may omit the actuator. Close exclusive apps, retest over USB in Chromium, and check the Controller Detection page.
My fightstick never vibrates — is it broken?
Probably not. Many fightsticks and generic pads ship without a vibration actuator at all. Check the specifications first: no actuator flag on such a pad is expected behavior, not damage.