Phone Vibration & Haptics Test
Online check for your phone's vibration motor. Offers continuous, pulse, and pattern modes to test haptic feedback strength and responsiveness.
Avoids unrelated permissions and runs in your browser with the device APIs available on this device.
Works best in current Chrome, Edge, Safari, and Firefox. Support depends on Vibration API, secure HTTPS, hardware availability, and browser policy.
How to use this page to quickly locate problems
Vibrate Guide
Test different patterns (Pulse, SOS) to check motor health.
Confirm API availability
Look at "Vibration API: Supported/Not Supported" at the top of the page and run a short pulse first.
Test different rhythms
Use "Preset Rhythm" and "Rhythm Generator" to compare the somatic differences in length, speed, and compound rhythms.
Do "strength" comparisons (approximately)
The Vibration API does not have real amplitude control. "Strength" is approximated by pulse duration and interval duty cycle.
What this tool checks
This page checks whether the browser can trigger basic vibration patterns and whether the device still responds to them.
API availability
Confirms whether the browser exposes the Vibration API on this device.
single pulse behavior
Lets you check whether a short vibration command produces a tactile response.
pattern playback
Useful for seeing whether longer vibration patterns are supported or truncated.
stop / interrupt response
Helps reveal whether ongoing vibration can be canceled or is cut off by the browser.
device-side haptic reaction
Confirms whether the phone or tablet still produces any tactile output at all.
browser compatibility hints
Makes it easier to distinguish unsupported browsers from silent-mode device behavior.
What this tool cannot confirm
This is a simple browser haptics check and does not measure vibration strength with engineering precision.
not a motor strength measurement
It cannot certify the exact physical output level or compare one motor against another scientifically.
many platforms ignore the API
Desktop browsers and some mobile browsers expose little or no practical vibration support.
silent mode and power saving matter
System haptic settings, accessibility options, and battery modes can suppress the result.
user perception is subjective
A weak vibration may feel absent depending on how the device is held or placed.
How the result is generated
The result is generated from local navigator.vibrate requests and whether the device seems to respond during the test.
API support check
The page checks whether navigator.vibrate is available in the browser.
pattern request
A vibration pulse or sequence is requested after your action.
device response window
You observe whether the device produces the expected tactile response.
interrupt / stop test
The page may send a stop or alternate pattern to reveal whether control works properly.
local result summary
The page summarizes likely support based on API availability and the perceived response.
Interpret your results
Use the result as a simple browser haptics sanity check, especially on mobile hardware.
| Observed haptic result | Likely meaning |
|---|---|
| No vibration at all | Unsupported browser, disabled haptics, silent mode behavior, or a device motor problem. |
| Only short pulses work | The browser is trimming longer patterns or the device limits extended vibration. |
| Pattern stops unexpectedly | Backgrounding, focus changes, or browser restrictions interrupted the sequence. |
| Weak or inconsistent feel | Battery saving, haptic settings, device position, or motor wear is affecting perception. |
| Expected pulses are felt | Basic browser vibration support is working on this device. |
Supported browsers and known limitations
Vibration support is strongest on certain mobile browsers and almost nonexistent in many desktop environments.
| browser | API exposure | single pulse support | pattern support | known limitations |
|---|---|---|---|---|
| Chrome | Limited on desktop; better on Android | Basic | Basic | Desktop hardware usually will not vibrate. |
| Edge | Similar to Chromium path | Basic | Basic | Useful mostly on mobile devices that expose haptics. |
| Firefox | Often limited | Limited | Limited | Support may be absent or inconsistent. |
| Safari | Very limited | Limited | Limited | Safari commonly restricts or ignores vibration requests. |
| iOS Safari | Generally no practical support | No or very limited | No or very limited | iOS browser haptics through Vibration API are not dependable. |
| Android Chrome | Often available on Android | Good | Basic to good | Vendor power modes can still suppress the response. |
Use cases
This is mainly useful when you need to verify whether browser-triggered haptics still work on a mobile device.
before a web game demo
Check whether the browser can still trigger tactile feedback on the device.
after changing haptic settings
Re-test whether system haptic controls disabled browser vibration.
after a phone OS update
Confirm that browser haptics were not changed by the update.
when a phone feels silent
Use the test to separate browser/API support from a possible hardware motor issue.
when comparing Android browsers
See which browser still exposes the vibration path for your workflow.
FAQ
Support differences, limitations, and troubleshooting suggestions for the Vibration API.
What does this page verify?
It can confirm whether the current browser is exposed to `navigator.vibrate`, and trigger vibration through preset rhythm/custom pattern to help you do somatosensory comparison of "whether there is feedback, whether the rhythm is distinguishable, and whether there is obvious delay/vibration swallowing".
Why does it say "Support" but I can't feel the vibration?
Common reasons include: the system is in power saving/do not disturb/mute or tactile feedback is turned off, the device hardware is not supported/the vibrator is weak, the browser has frequency/duration restrictions on vibration, or the current page is not in the foreground. It is recommended to click the button in the foreground to trigger and use a longer pattern (such as three consecutive earthquakes/SOS) for comparison.
How is "strength" measured? Can the amplitude be controlled?
The Vibration API only has "duration/interval" and no real vibration amplitude parameters. The "intensity" on this page is a somatosensory approximation using longer pulses and shorter intervals (higher duty cycle) for easy comparison, but does not represent real amplitude control.
Can it be used on iPhone / iOS Safari?
Not in most cases. iOS/Safari has very limited support for the Vibration API (many versions do not support it outright). If you need reliable vibration testing, it is recommended to use Android/Chrome as the main control environment.
Why is HTTPS (security context) required?
Some browsers regard vibration as a "sensitive capability" and may be restricted in non-secure contexts (HTTP). Even though it's not a requirement, using https is generally more stable.
Will any data be uploaded?
Won't. Pattern generation, triggering and logging are all done locally in your browser. This page will not upload device information or test data to the server.
Related guides
Read a few practical guides for setup, browser compatibility, and troubleshooting around this test.
Silent Phone? How to Diagnose and Fix Vibration Motor Issues with a Simple Online Test
Is your phone silent when it should be buzzing? Before heading to a repair shop, discover how to pinpoint the issue using an online Phone Vibration & Haptics Test. This guide walks you through troubleshooting common 'no-vibration' problems, validating haptic feedback after system updates, and ensuring your device's motor is functioning correctly. We explore practical scenarios for everyday users and app developers alike, offering a step-by-step workflow to test continuous, pulse, and pattern modes. Learn how to interpret test results to distinguish between software glitches and hardware failures, saving you time and money on unnecessary repairs.
Silent Phone? How to Diagnose and Fix Vibration Motor Issues with a Simple Online Test
Is your phone silent when it should be buzzing? Before heading to a repair shop, discover how to diagnose vibration motor failures using a free online Haptics Test. This guide walks you through troubleshooting common 'no-vibration' issues, validating haptic feedback after system updates, and ensuring quality assurance for new devices or repairs. We explore the science behind haptic engines, explain how to interpret test patterns (continuous, pulse, and custom), and provide a step-by-step workflow to determine if your hardware is faulty or if a software glitch is to blame. Perfect for DIY enthusiasts, app developers testing haptic designs, and anyone looking to extend their device's lifespan without unnecessary costs.
Silent Phone? How to Diagnose and Fix Vibration Motor Issues with a Simple Online Test
Is your phone silent when it should be buzzing? Before heading to a repair shop, discover how to use an online Phone Vibration & Haptics Test to diagnose hardware failures instantly. This guide walks you through troubleshooting no-vibration issues, validating haptic feedback after system updates, and ensuring quality assurance for new devices or repairs. We explore the three core testing modes—continuous, pulse, and pattern—to help you determine if the problem lies in your settings or a failing motor. Save time and money by performing a professional-grade hardware check directly from your browser.
Feedback / report a bug
Tell us your browser, device, and what happened.
Did this result look wrong?
Comments(0)