A vibration test exists to answer one specific question that's surprisingly hard to answer by feel alone: is every motor in this controller actually working, at every intensity, independently of the others. Rumble is easy to notice when it's obviously broken and easy to miss when it's partially broken, because a controller with one weak motor out of four still vibrates, just with less information in the vibration than it's supposed to carry.
Running the test is the easy part. Knowing what the result is actually telling you, and what it isn't, is where most of the value lives.
What a vibration test actually checks
A controller rumble test fires each motor individually, usually followed by combinations, and asks you to confirm what you feel and, where the tool supports it, reads back whether the operating system successfully commanded each motor. The reason this matters more than it sounds: most controllers don't have one vibration motor, they have two, three, or four, and each one is responsible for a different part of what you feel.
A standard dual-motor pad, which covers most Xbox and third-party controllers, has a heavier motor on the left side producing a stronger, lower-frequency rumble and a lighter motor on the right producing a faster, higher-frequency buzz. Games mix the two to suggest everything from footsteps to explosions, so testing them independently rather than just confirming "it vibrates" is the only way to know both halves of that range still work.
The DualShock 4 and DualSense go further. Sony's HD dual actuators in the DualSense are a genuinely different kind of motor from the ERM units in older pads, built to reproduce texture and sharp transients rather than just generic buzz, and they're why a DualSense can make a sandy surface feel different from a wet one in a supporting game. The DualSense's adaptive triggers add a third category entirely: motors inside the trigger housing itself that create physical resistance you push against, not just vibration you feel. A full test checks these as their own category, separate from the handle motors, and our dedicated adaptive trigger test guide covers what a failure there looks like specifically.
Xbox Series X and S controllers add Impulse Triggers, vibration motors built into the trigger housings rather than the main grips. These are genuinely separate hardware from the two main rumble motors, which is why a controller can fail one category while the other works perfectly.
ERM, LRA, and why motor type changes what you should expect
Not all rumble motors behave the same way physically, and knowing which type is in your controller changes what a "working" result should feel like.
ERM (eccentric rotating mass) motors are the older, simpler technology: a small offset weight spun by a motor, producing vibration as a byproduct of imbalance. They're cheap, durable, and have a noticeable spin-up and spin-down time, meaning they can't start or stop a vibration instantly. Most budget controllers and the heavier of the two motors in an Xbox pad are ERM.
LRA (linear resonant actuator) motors move a weight back and forth along a single axis using a magnetic field rather than spinning it, which lets them start and stop almost instantly and respond more precisely to different frequencies. They're the reason newer high-end controllers can produce sharper, more textured feedback than older pads. A test result on an LRA motor should feel crisp and immediate; a muddy, delayed response that should be sharp is itself a sign of a problem rather than just a weak motor.
Knowing which type sits in each slot explains behavior that otherwise looks like a fault. An ERM motor that takes a fraction of a second to ramp up isn't broken, that's how the technology works; an LRA motor behaving the same way usually is.
Reading a healthy result
A fully working controller should show four independent signals on a pad with adaptive triggers and dual HD actuators, or two on a standard pad: each motor firing cleanly on command, at a felt intensity that scales with the commanded strength rather than jumping straight to maximum or staying flat, and stopping promptly when the signal ends. Running left and right together should produce a combined sensation that's clearly the sum of both, not one masking the other.
Test at multiple intensities if the tool offers them, not just full strength. A motor that works fine at maximum but produces nothing at low intensity has a real fault, even though a simple on/off test would have missed it entirely, and that's exactly the kind of subtle wear you want caught before it becomes the only setting that works at all.
Reading a failed result, and what it actually tells you
One motor silent, the others working. This is the single most common failure pattern and it almost always points at that specific motor or its connection, not the controller as a whole. On a disassembled or aging pad this is frequently a dry solder joint rather than a dead motor, which is why some failed-motor symptoms come and go with how the controller is held or flexed.
Everything silent in the tester but rumble works in a specific game. This points away from hardware and toward the browser or operating system's vibration permission layer instead. Some platforms require an explicit interaction before granting a page access to haptics, similar to the activation gesture the Gamepad API itself requires, so a genuinely working controller can show nothing in a test page it hasn't been given permission to vibrate.
Everything silent everywhere, including in games. Check the obvious things first: a vibration intensity setting turned down to zero at the system level, a power-saving mode that disables haptics over Bluetooth specifically, or a controller that vibrates fine over USB but not wirelessly, which is a connection bandwidth issue rather than a motor fault. Our guide on turning controller vibration on and off covers where that setting actually lives across platforms, since it moves around between system settings, game settings, and sometimes both at once.
Weak but present on every motor evenly. Usually a worn ERM motor's bearing or a general power delivery issue rather than a single failed part, since a true single-component failure tends to kill one channel rather than dim all of them equally.
Platform-specific behavior worth knowing before you panic
The PS5 controls vibration intensity at the system level independently of any individual game, which means a DualSense that feels weak everywhere might just have its system-wide haptic intensity turned down rather than a hardware fault. Check Settings, then Accessories, then Controllers, for the haptic feedback intensity slider before assuming anything is broken.
Nintendo's Joy-Con and Switch Pro Controller use what Nintendo calls HD Rumble, a deliberately subtle, high-resolution vibration designed to simulate specific textures like ice cubes in a glass. It's genuinely quieter and more restrained than Xbox or PlayStation rumble by design, not by fault, and comparing it directly against a DualSense's intensity will make a perfectly healthy Joy-Con seem weak when it isn't.
Bluetooth itself imposes real limits on some pads. A controller that rumbles correctly wired but noticeably weaker or with audible motor whine over Bluetooth is usually running into bandwidth or latency constraints in the wireless link rather than developing a fault, and testing both connection types before concluding anything is broken saves a lot of unnecessary troubleshooting. If you suspect the connection itself rather than the motors, our breakdown of PS5 vibration not working and the equivalent Xbox rumble troubleshooting guide both separate connection-layer causes from genuine hardware failure in detail.
Third-party controllers and what to expect
Budget and third-party pads vary more in vibration quality than in almost any other spec, because motor choice is one of the easiest places to cut cost without it showing up on a feature list. A controller advertised as having "dual vibration motors" tells you nothing about whether those are ERM or LRA, strong or weak, or matched well to each other, and this is where a hands-on test earns its keep over trusting a spec sheet.
8BitDo, GuliKit and similar brands generally use ERM motors even in their premium lines, which is not a defect, just a cost and durability tradeoff that happens to also mean a slower, buzzier feel than a DualSense. Where third-party controllers do fail more often than first-party ones is consistency between units: two controllers of the exact same model, bought at the same time, sometimes show a noticeably different vibration strength out of the box, which is a real quality control gap worth testing for immediately after a purchase rather than assuming your unit matches the one a reviewer tested.
Getting an accurate reading
A few habits separate a test result you can trust from one that just adds confusion.
Hold the controller the way you normally would rather than resting it on a table, since some motors, particularly LRA units, transmit through the grip in a way that's harder to feel when the shell isn't making contact with your hand. Test each motor in isolation before testing combinations, so a weak signal from one channel doesn't get masked by a stronger one running at the same time. Run the test at least twice, since a connection-related dropout can look identical to a hardware fault on a single pass but will usually behave differently the second time if it's actually a loose connection rather than a dead motor. And test both wired and wireless if your controller supports both, specifically because some bandwidth-limited wireless links genuinely do suppress fine vibration detail that the same controller reproduces fully over a cable, which is a connection limitation rather than anything wrong with the hardware itself.
When a result is worth acting on
A single motor that's gone completely silent and stays that way across multiple tests, multiple connection types, and multiple games is a real hardware fault worth pursuing through warranty or repair rather than troubleshooting further. A controller still inside its warranty window with a reproducible, isolated motor failure is exactly the kind of clean, well-documented case that makes a replacement claim straightforward, and running the test two or three times and noting exactly which channel fails is worth doing before you contact support, since it saves a round of "have you tried turning it off and on again."
For the general step-by-step process of running a check across every input type, not just vibration, our broader guide on testing controller vibration walks through the practical setup across PS5, Xbox and Switch specifically.