Vibration test - check your phone vibration motor

Vibration tester

Checking vibration support…

Custom pattern 0 ms
Pattern builder Edit durations, drag blocks to reorder, or add your own.

    Sent to navigator.vibrate: []

    Vibration API
    Last request
    Requests sent0

    Pick a pattern, hold your phone, and press Vibrate.

    The browser only reports that a vibration request was accepted - it cannot tell whether the motor moved - so this page asks you. Silent mode, Do Not Disturb and battery saver stop web vibration far more often than a broken motor. The web API has no strength control, so the Ramp pattern grows by duration, not intensity.


    Before you conclude the motor is broken

    Almost every "my phone stopped vibrating" turns out to be one of these, and none of them is a hardware fault:

    • Silent or vibrate-off mode. On many phones the physical switch or the volume menu disables vibration entirely.
    • Do Not Disturb, or a focus mode, which suppresses it for most events.
    • Battery saver. Several manufacturers turn off haptics when the battery is low.
    • Per-app settings. Vibration for notifications is configured per app on Android, so one app being silent proves nothing about the motor.
    • Safari on iPhone and iPad, which does not support browser vibration at all, on any version. No web page can vibrate an iPhone - a limitation of the browser, not a fault with the phone.

    Work through those first. This page will tell you when the browser itself has refused the request, which usually points at one of the above.

    Why the page asks whether you felt it

    The browser reports whether the vibration request was accepted, never whether the motor actually moved - there is no feedback channel from the hardware. Only the person holding the phone knows.

    So this page asks you rather than printing "working" from a value that does not mean working. Tools that declare success on the strength of that return value are reporting something they cannot know.

    The patterns

    • Short buzz - the usual notification length. Fine for checking the motor runs at all.
    • Long buzz - reveals a motor that starts and then dies, or one that buzzes weakly.
    • Triple pulse - checks the motor can stop and start crisply. A worn motor smears the gaps.
    • Rapid then long - the hardest pattern, and the one where a failing motor is most obvious.

    If nothing works after all of that

    Restart the phone first - the haptics service does occasionally hang, and a restart is free. Test in another app, such as by toggling a keyboard's haptic feedback, to confirm the problem is not confined to the browser. If nothing anywhere produces vibration, the motor or its connector is the likely cause, and on most phones it is an inexpensive part to replace.

    Privacy

    Everything happens on your device. Nothing about your phone is transmitted or stored.

    Rate this tool

    Was this tool useful? Your feedback helps us improve it.

    No ratings yet — be the first to rate this tool.
    Your rating (required)
    0 / 2000

    Please do not include passwords, payment details or other sensitive information.

    Your feedback is sent privately to the A2Z.Tools team and will not be posted publicly.