Controller Vibration Test – Free Online Gamepad Rumble & Haptic Diagnostic

A controller vibration test checks whether your gamepad’s rumble motors respond correctly by sending vibration commands straight through your browser – no game required. It tells you in under a minute whether a vibration problem is your hardware, your Bluetooth connection, or a setting buried in a menu.

Press Detect Controller, then run Weak Only, Strong Only, and Both Motors. Two clearly different sensations – a light buzz and a heavy thump – means your rumble hardware is healthy. One side staying silent at every intensity means a hardware fault, not a software one. Nothing vibrating at all usually means you’re not on Chrome/Edge, not on USB, or the tab isn’t focused – background tabs are throttled and won’t fire vibration commands.

Why Run a Vibration Test

• Diagnose an existing problem – isolate whether weak or missing rumble is the controller, the connection, or the game.
• Verify a new controller before your return window closes – dead motors on arrival are common enough to be worth a 60-second check before you lose the ability to return it.
• Confirm a repair worked – after reseating a connector or resoldering a motor wire, this is the fastest way to verify the fix without launching a game.
• Compare controllers – if you own more than one pad, running the same test sequence on each gives you an apples-to-apples read on which has stronger, more reliable motors.

How Controller Vibration Actually Works

Almost every vibration complaint traces back to one of two hardware families. Knowing which one your controller uses tells you what “normal” is supposed to feel like – and stops you from diagnosing a working controller as broken.

ERM Motors – Asymmetric Dual-Motor Rumble

Eccentric Rotating Mass (ERM) motors are small DC motors spinning an off-center weight; the imbalance is what you feel. This design – sometimes called Asymmetric Dual-Motor Rumble – is used in the Xbox Series controller, Xbox One controller, PS4 DualShock 4, and most third-party pads (8BitDo, Razer, SCUF, and most HOTAS/flight-stick rumble modules). These controllers use two mismatched motors:

• A larger, low-frequency motor in the left grip – heavy, deep rumble for explosions, crashes, big impacts.
• A smaller, high-frequency motor in the right grip – light, buzzy feedback for footsteps, reloads, subtle cues.

Because ERM motors are physical spinning weights with real mechanical parts, they wear out, loosen, or snap – exactly what a vibration test is built to catch early, often before it becomes a total failure.

LRA / Voice-Coil Actuators – Modern Haptics

PS5 DualSense and Nintendo Switch controllers use voice-coil (LRA) actuators, not spinning-weight motors, so a browser-based test can only confirm basic dual-rumble response – the full textured haptic feedback these controllers produce is only accessible inside native PS5 or Switch games.

Linear Resonant Actuators (LRA) oscillate a small mass along a spring – the same working principle as a speaker coil – rather than spinning a weight. This lets them respond to precise waveforms instead of simple on/off, which is why they feel sharper and more textured. It’s the technology inside the DualSense and Joy-Con / Pro Controller (HD Rumble).

The catch is the web’s Gamepad API, standardized around the older dual-ERM model. It exposes only two parameters – weakMagnitude and strongMagnitude – through the GamepadHapticActuator interface. When you test a DualSense or Joy-Con in a browser, that interface mathematically down-mixes the controller’s advanced haptic engine into the same two-motor language. You’ll get an accurate pass/fail on whether the actuators respond, but not the layered texture effects (rain, footsteps on different surfaces, resistance) that only show up inside a native game.

Impulse Trigger Motors (Xbox)

Xbox controllers add a third element: two small motors inside the triggers, called impulse triggers, simulating directional resistance – tire slip in racing games, recoil in shooters. Because they sit outside the standard weakMagnitude/strongMagnitude model, they’re largely inaccessible through the browser’s Gamepad API. If your trigger motors don’t respond during this test, that’s expected – it isn’t a fault. Confirm trigger hardware separately with a trigger pressure test, which checks trigger sensitivity and mechanical travel directly.

Vibration Technology by Type

Type	Motor Design	Found In	Browser-Testable?
Dual Rumble (Asymmetric ERM)	2× ERM (weak/strong)	Xbox Series/One, PS4, 8BitDo, Razer, SCUF, most HOTAS	✅ Fully
Impulse Triggers	2× small ERM in triggers	Xbox controllers	⚠️ Rarely – needs native game or a dedicated trigger test
HD Rumble	LRA / voice-coil	Switch Joy-Con, Switch Pro Controller	⚠️ Basic dual-rumble only
Advanced Haptic Feedback	LRA / voice-coil	PS5 DualSense	⚠️ Basic dual-rumble only

Vibration Support by Controller

Controller	Motor Type	Browser Test Result	Notes
Xbox Series X|S	Dual ERM + impulse trigger	Full dual-rumble support	Best browser compatibility of any controller
Xbox One	Dual ERM + impulse trigger	Full dual-rumble support	Same behavior as Series controllers
PS5 DualSense	LRA (voice-coil)	Basic dual-rumble simulation	Full haptic texture only inside PS5 games
PS4 DualShock 4	Dual ERM	Full dual-rumble support	Battery level noticeably affects intensity
Switch Pro Controller	LRA (HD Rumble)	Limited, browser-dependent	Chromium-based browsers work most reliably
Joy-Con	LRA (HD Rumble)	Limited, connection-dependent	Native Switch environment recommended for full effect
8BitDo / Razer / SCUF	Usually dual ERM	Generally full support	Licensed third-party pads implement the standard spec well
Budget / unlicensed clones	Single or dual ERM, inconsistent	Often partial or none	Many cheap “Xbox-style” pads skip the vibration actuator spec entirely

How to Run a Test That Actually Tells You Something

1. Connect by USB first. Wireless adds two extra variables – battery level and signal – before you’ve confirmed the motors themselves work. Rule those out.
2. Do a quick environment check. Test somewhere quiet enough to also hear the motors – grinding, clicking, or rattling is a mechanical symptom a purely tactile test can miss.
3. Detect the controller, then run a 10-second low-intensity warm-up to bring motors to normal operating condition and avoid mistaking a cold-start delay for a fault.
4. Test motors independently. Run Weak Only, then Strong Only. You should feel two distinctly different sensations. Note which side is silent if either is.
5. Run Both Motors together. Combined output should feel noticeably stronger and layered, not identical to either motor alone.
6. Run a Pulse Pattern (rapid on/off) to expose delayed starts, sticky motors, or stuck-on behavior a static test misses.
7. Run a Ramp Up/Down. Intensity should scale smoothly. A motor silent from 0–40% that then jumps straight to full strength usually indicates a non-linear response from motor wear or a failing driver – not total failure. This “flat then sudden jump” pattern is one of the more reliable early-wear indicators, because a healthy motor’s torque curve is close to linear.
8. Switch to Bluetooth and repeat. If results are noticeably weaker or delayed only over Bluetooth, the hardware is fine – the issue is wireless power management, not the motor.
9. Keep a note of the result. If you’re planning a warranty claim, a simple written record of which motor failed, at what intensity, and on which connection type is more useful supporting evidence than a vague “it doesn’t vibrate” description.

Reading Your Results

If one motor never vibrates at any intensity while the other works normally, that is almost always a hardware fault – most commonly a wire that has snapped at the motor’s solder joint – not a software or game issue.

What You Feel	What It Means
Both motors respond, clearly different intensities, stop instantly	Healthy – no action needed
One motor silent at every intensity	Hardware fault – loose wire, dead motor, or failed solder joint
Vibration present but noticeably weak	Low battery, Bluetooth power-saving, or motor wear
Silent at low intensity, then jumps straight to strong	Non-linear response – early motor wear or a degraded driver
Delayed start (a few hundred ms lag)	Normal over Bluetooth; concerning over wired USB
Vibration continues after Stop is pressed	Stuck driver state – reconnect the controller; persistent cases suggest firmware fault
Grinding, clicking, or rattling sound	Mechanical damage – internal debris or a bent motor shaft
Works in games but not in this tool	Almost always a browser/API limitation, not a controller problem – see below

Is It Software or Hardware? A Quick Decision Path

• Vibrates in games but not in any browser → Software/API limitation. Try Chrome or Edge, confirm the tab is focused, test wired. Not a hardware fault.
• Doesn’t vibrate in this tool, a different browser, and games → Check the controller’s own vibration setting (Xbox Accessories app, PS5 system settings) before assuming hardware failure.
• Vibrates fine in most games but not one specific title → This is a per-game implementation gap, not your controller. Some games simply don’t send strong vibration commands, or let you disable rumble in their own settings menu separate from the system-level setting. Check that game’s audio/haptics options first.
• Doesn’t vibrate anywhere, on any device, wired or wireless → Hardware – most likely a disconnected wire or dead motor.
• Works fine on USB, weak or absent on Bluetooth → Almost always power management, not damage.

USB vs. Bluetooth: Why Wired Testing Is More Reliable

Bluetooth HID connections prioritize input-polling data (stick and button state) over haptic command delivery, because input latency has a bigger impact on gameplay feel than vibration timing – so the connection’s report scheduling gives vibration commands lower priority. In practice this adds somewhere in the range of an extra 20–80ms of latency compared to USB, and on some OS Bluetooth stacks, commands are dropped under load rather than delayed. Combine that with power-saving modes that reduce motor voltage to conserve battery, and it’s easy to misread a wireless-only limitation as a hardware fault. Always run your baseline test on USB, then compare. The GamepadHapticActuator interface itself is defined in the W3C’s Gamepad Extensions specification, which explicitly notes that effect delivery timing is not guaranteed to be precise – a browser-level constraint, not something any site’s implementation can fully work around. If you suspect the wireless link itself – not just vibration – is the problem, see our connection stability test.

Common Problems and Fixes

Problem	Likely Cause	Fix
No vibration anywhere	Browser lacks Gamepad Haptics support	Switch to Chrome or Edge
No vibration, but only in this tool	Vibration disabled in system/controller settings	Check Xbox Accessories app or PS5 system settings
Weak vibration	Low battery or Bluetooth power-saving	Charge fully, test wired
One motor completely silent	Loose or snapped internal wire	Reseat connector or resolder; replacement ERM motors are inexpensive
Vibration won’t stop	Stuck driver state	Reconnect controller; persistent issue may be firmware
Grinding or rattling	Mechanical damage inside motor housing	Physical inspection required; often not repairable without replacement
Inconsistent between USB and Bluetooth	Normal wireless power management	Not a fault – expected behavior
Works in most games, not one specific title	That game’s own rumble settings or implementation	Check the game’s own audio/haptics menu before assuming a controller problem

When to Repair vs. Replace

If a single motor has failed on an otherwise functional controller, replacement ERM motors typically cost only a few dollars, and the fix is often a loose connector rather than a full motor swap – check the ribbon cable or wire connection before assuming you need a new motor entirely. For controllers still under warranty, contact the manufacturer rather than opening the case, since DIY disassembly can void coverage; a written note of your test results (which motor failed, at what settings) is useful supporting detail for that claim. For older, low-cost, or heavily worn controllers, replacement is usually more practical than repair once you’re past a single loose wire.

Accessibility: Designing and Choosing for Vibration Sensitivity

Vibration isn’t a universal positive for every player. People with certain sensory processing differences, some neurological conditions, and players simply sensitive to sustained buzzing can find strong or constant rumble uncomfortable or fatiguing rather than immersive. If you’re a developer or just configuring your own setup, good practice includes:

• A clear on/off toggle, not just an intensity slider buried in a submenu.
• Multiple discrete intensity presets (Off / Low / Medium / High) rather than a single global percentage.
• Non-vibration alternatives for critical gameplay cues – a screen flash or audio tone for “low health,” for example, so information isn’t lost when vibration is disabled.
• Avoiding continuous high-intensity vibration lasting more than a few seconds by default; sustained maximum rumble is the most common source of discomfort reports.

For Developers: Using the Gamepad Haptics API

const gp = navigator.getGamepads()[0];
if (gp && gp.vibrationActuator) {
  gp.vibrationActuator.playEffect('dual-rumble', {
    startDelay: 0,
    duration: 200,
    weakMagnitude: 0.4,
    strongMagnitude: 0.8
  });
}

Practical notes for implementation:

• weakMagnitude and strongMagnitude both accept floats between 0.00 and 1.00 – treat these as relative intensity, not a guaranteed physical output, since hardware response varies by controller.
• Per the W3C Gamepad Extensions spec, effect timing is best-effort, not guaranteed – don’t build gameplay logic that depends on millisecond-precise haptic timing.
• Keep continuous effects short. Long, uninterrupted high-intensity vibration accelerates motor wear and drains wireless battery faster than intermittent bursts.
• Test on real hardware across at least an Xbox controller and a DualSense before shipping – the same magnitude values feel meaningfully different across ERM and LRA hardware.
• Always expose a way to disable or scale down vibration in your settings menu; treat it as an accessibility requirement, not an optional nicety.

How We Tested This Guide

This guide’s compatibility notes reflect testing across Chrome and Edge on Windows with wired and Bluetooth Xbox Series, PS4 DualShock 4, and PS5 DualSense controllers, cross-checked against the behavior documented in the W3C Gamepad Extensions specification. Browser and driver behavior can change with future updates; if you notice a result that doesn’t match what’s described here, that’s worth a note in your own testing rather than assuming the guide is wrong on day one.

Related Controller Diagnostics

Vibration is one piece of a full hardware check. If something else feels off, these tests isolate other components the same way this one isolates your rumble motors:

• Gamepad Button Test – confirm every button registers correctly
• Joystick Deadzone Test – check for stick drift or dead zones
• Gamepad Stick Drift Test – isolate stick drift specifically
• Gamepad Trigger Pressure Test – verify analog trigger sensitivity and impulse trigger response
• Gamepad Latency Test – measure input delay, including wired vs. Bluetooth
• Gamepad Connection Stability Test – diagnose wireless dropouts
• Gamepad Controller Mapping Test – confirm button-to-input mapping

Run the full gamepad tester for a complete diagnostic covering all of the above in one place.

Frequently Asked Questions

Get quick responses to frequently asked questions regarding the  Gamepad Vibration Test.