Nine Preset Intensities
From a 10ms light tap to a full one-second rumble, run the motor through short and long bursts to spot where it weakens.
Trigger your phone's vibration motor at different intensities and patterns to feel whether it's working, weak, or stuck. Best on Android — see the note below for iPhone.
A single default buzz won't reveal a motor that's weak, uneven, or only fails on longer patterns. This test runs the full range.
From a 10ms light tap to a full one-second rumble, run the motor through short and long bursts to spot where it weakens.
Double pulses, a heartbeat rhythm, and a full SOS pattern check that the motor can start and stop cleanly, not just hold one buzz.
Dial in any duration from 10ms to 2 seconds to reproduce exactly the buzz length a specific app or notification uses.
After each buzz, you confirm whether you actually felt it — combining the software signal with the physical check no browser API alone can do.
A bar visualization shows exactly when the motor is on and off for each pattern, so you can match what you feel to what was sent.
Everything runs through the browser's standard Vibration API — no app, no permission prompt, and nothing is recorded or sent anywhere.
Work through the presets from weakest to strongest for the clearest picture.
Hold the phone in your hand rather than resting it on a soft surface — a couch cushion or carpet will muffle a working motor.
Start with Light Tap, then work up to Strong Buzz. Each button fires that exact pattern immediately.
Answer "Yes" or "No" after each buzz — this builds an accurate tally of which intensities the motor can still produce.
Check the sidebar for how many patterns were confirmed felt out of ten — a low count points to a weakening motor.
Anyone who relies on their phone buzzing reliably — or who wants proof before a return or repair.
Verify before you pay
Depend on haptic alerts
Preview haptic timing
Here's how to tell a browser limitation from an actual hardware problem.
Expected. Safari on iOS has no web Vibration API, so this reflects a browser limitation, not a broken Taptic Engine. Test native app haptics instead.
Check your phone's system vibration setting isn't fully disabled, and that battery saver mode — which sometimes limits haptics — is off, then retry.
A thick case, a soft surface, or a worn motor can all mute vibration. Remove the case, hold the phone in hand, and compare Light Tap to Strong Buzz.
If simple buzzes work but multi-pulse patterns feel like one long buzz, the motor is fine — some Android skins simplify complex patterns by design.
What to expect, and what iPhone users should know before testing.
Apple has never implemented the web Vibration API in Safari on iOS, for battery and privacy reasons. This is a deliberate browser restriction, not a bug in this tool or a sign your Taptic Engine is broken — the motor itself only responds to native app and system haptics on iPhone, which a website cannot trigger.
Browsers only allow the Vibration API to run in direct response to a user action like a tap or click. This prevents websites from silently buzzing your phone in the background, so every pattern here requires you to press its button.
Not fully. The browser can only confirm it successfully sent a vibration command — it cannot sense whether the motor physically moved. That's why this tool asks you to confirm "did you feel that?" after each pattern, combining the technical check with your own physical confirmation.
On most Android phones, silent mode and Do Not Disturb only mute sound and notifications — vibration triggered directly by an app or website will usually still fire. If nothing happens at all, check your system vibration settings rather than assuming the motor is broken.
A thick case, the phone resting on a soft surface, low battery combined with battery saver mode, or a worn vibration motor can all make vibration feel weaker than normal. Try the test again on a hard surface with the case removed and battery saver off.
Yes. It uses the standard, built-in web Vibration API supported by Chrome, Firefox, Samsung Internet, and other Android browsers. No special permission or install is required, and nothing is sent to a server.