Vibration Test
Buzz the vibration motor with different patterns to check it still works.
How to use the Vibration Test
- Tap a pattern — short, long, or a repeating buzz.
- Feel for the vibration; check the phone is not on silent if nothing happens.
- Tap Stop to cut a long pattern short.
About the Vibration Test
Tap a pattern and feel whether your phone answers. This calls navigator.vibrate with several patterns — a short buzz, a longer one, and pulse sequences with gaps between them — so you can tell a motor that is completely dead from one that is weak or rattling. There is a stop button for the longer patterns.
Support matters here more than on most tests, so be clear about it: this works on Android, in Chrome, Firefox and Edge. iPhone and iPad do not allow web pages to vibrate at all — Safari has never implemented the API, so no site can do this on iOS however it is written. Desktops have no motor. Where the browser lacks support the tool disables the buttons and tells you why instead of leaving you tapping at nothing.
Even on Android there are catches. Some builds tie web vibration to the ringer, so a phone on silent stays silent. And the browser can refuse a request outright — when vibrate() returns false the tool reports that the request was refused rather than claiming it worked. If the motor is fine but the phone still feels wrong, the motion sensor test and the wider mobile and tablet tests are the next places to look.
Frequently asked questions
Why does vibration not work on my iPhone?
Because Safari does not support the Vibration API, on iPhone or iPad. This is not a limitation of this tool: no web page can vibrate an iOS device. Native apps can, through a different system that is not available to websites.
Which browsers support this?
On Android it works in Chrome, Firefox and Edge. Desktops have no vibration motor, so there is nothing to drive even where the API exists. When support is missing the buttons are disabled and the tool explains why.
I pressed a pattern and felt nothing. Is the motor dead?
Not necessarily. Check the phone is not on silent first, because some Android builds tie web vibration to the ringer switch. Also try turning the screen on and interacting with the page a little more, since a browser can refuse a request from a page you have barely touched.
What does it mean when the request is refused?
The vibrate call returns false when the browser rejects it outright, and the tool reports that honestly rather than pretending the buzz happened. It usually means the browser wants more interaction with the page, or a device policy is blocking it.
Can I control how strong the vibration is?
No. The web API only takes a pattern of on and off durations in milliseconds, not an intensity. Different patterns feel different because of their timing, but the strength is whatever the motor does at full power.