Browser Push Notification Test
Test Web Push functionality online. Verify browser and OS notification permissions. Send custom test messages to troubleshoot issues with receiving alerts.
Requests notifications only while the test is active and keeps processing in your browser whenever possible.
Works best in current Chrome, Edge, Safari, and Firefox. Support depends on Notifications API, secure HTTPS, hardware availability, and browser policy.
How to use this page to quickly locate problems
Notify Guide
Request permission, trigger notification, check callback.
Confirm that the environment meets the conditions
Notification capabilities typically require a secure context (HTTPS) and browser support for Notification and Service Workers.
Request notification permission
Click "Request notification permission" and let the browser pop up asking whether to allow notifications.
Trigger in-page notifications and test click callbacks
In-page notifications can verify Notification.onclick/onclose (while the page is alive).
Register a Service Worker and trigger system notifications
SW notification is closer to real push/background notification interaction, click and go notificationclick.
What this tool checks
This page checks whether browser notifications can be requested, created, and surfaced in a visible way on this device.
permission state
Shows whether notification access is granted, denied, or still waiting for user approval.
test notification display
Helps confirm whether the browser can actually create a visible notification.
delivery visibility
Useful for spotting cases where permission is granted but the notification still does not appear clearly.
click response
Can help verify whether notification interaction returns to the page or triggers expected focus behavior.
basic browser support
Confirms whether the current browser exposes the notification APIs needed for the test.
user-side suppression hints
Makes it easier to consider quiet mode, focus assist, and OS-level blocking.
What this tool cannot confirm
A simple browser notification check is not the same as a complete push-messaging or service-worker delivery test.
not a push infrastructure test
It does not validate your full server push pipeline, service worker registration, or background subscription flow.
OS settings may override browser results
Focus modes, quiet hours, system-level muting, and notification grouping can suppress what you see.
mobile behavior differs a lot
Some mobile browsers limit or reinterpret notifications compared with desktop implementations.
permission granted is not everything
A granted state does not guarantee audible alerts, banners, or lock-screen visibility.
How the result is generated
The result is generated from browser Notification API state and whether a local test notification can be created from the page.
permission check
The page reads the current notification permission state from the browser.
permission request
If needed, the browser asks you whether this site may send notifications.
local notification trigger
The page attempts to create a local test notification after permission is granted.
interaction observation
The page watches whether the notification appears and whether user interaction returns to the session.
result summary
The result reflects the permission state and visible notification behavior on this setup.
Interpret your results
Use this result to decide whether your issue is basic notification support, permission state, or OS-level suppression.
| Observed notification result | Likely meaning |
|---|---|
| Permission denied | The browser or user has explicitly blocked notifications for this site. |
| Granted but nothing appears | OS quiet mode, notification center behavior, or browser suppression is hiding the alert. |
| Notification appears without sound | The visual notification works but system sound or alert style is disabled. |
| Click does nothing obvious | The OS handled the interaction differently or the browser did not refocus the page. |
| Notification appears normally | Basic browser notification capability is working on this device. |
Supported browsers and known limitations
Notification support depends on permission state, secure context rules, and how the operating system surfaces browser alerts.
| browser | permission behavior | test notification support | interaction behavior | known limitations |
|---|---|---|---|---|
| Chrome | Strong on desktop HTTPS | Strong | Good | OS focus modes can still suppress visible alerts. |
| Edge | Strong on desktop | Strong | Good | Enterprise policy may disable or centrally manage notifications. |
| Firefox | Good on supported desktop paths | Good | Good | Behavior differs more on mobile and some Linux setups. |
| Safari | Supported with Apple platform rules | Basic to good | Basic to good | Platform-specific restrictions are more significant. |
| iOS Safari | More limited and platform-dependent | Limited | Limited | iOS notification support in browsers remains more constrained. |
| Android Chrome | Varies by Android and browser build | Basic to good | Basic to good | Power saving and vendor notification controls can interfere. |
Use cases
A notification check is most helpful when you need to know whether the browser itself can still surface alerts right now.
before relying on browser reminders
Confirm that the site can still show visible notifications on your current setup.
after changing OS focus settings
Re-test whether alerts still appear after enabling do-not-disturb or quiet modes.
after resetting browser permissions
Verify whether notification permission was removed or denied by mistake.
when a web app says alerts are enabled
Use the test to see whether the browser can display a simple local notification at all.
when comparing desktop and mobile
See how differently notification support behaves across device types.
FAQ
Compilation of high-frequency issues regarding notification permissions, on-page notifications and Service Worker notifications.
What is this page mainly used for?
Used to verify browser notification capabilities: including permission status (default/granted/denied), whether the Notification (new Notification) in the page can pop up, and whether the showNotification of the Service Worker can pop up and return click/close events.
Why doesn’t the “Request notification permission” pop-up window pop up?
Common reasons: The current is not a secure context; the browser has remembered previous choices (especially denied); or is blocked by enterprise policy/browser settings. First confirm that the "Security Context" is yes, and go to the site settings to check the notification permissions.
What should I do if the permission is denied?
The page cannot automatically change denied back to granted. Please go to the site settings (or system notification settings) in the browser address bar, change the site notification to "Allow", then refresh the page and try again.
Does iOS Safari support system notifications?
iOS Safari's notification capability support is limited, and it usually requires an "Add to Home Screen" PWA form to use the notification capability; even then, it will be affected by the system version and permissions policy.
Why does triggering the notification fail and prompts that a user gesture is required?
Some browsers restrict non-user gestures from triggering notifications. Please use button clicks on the page to trigger (rather than automatic triggering/scheduled triggering), and make sure the tab is not in the background.
SW notification is not returned to the log after being clicked?
First click "Register Service Worker" and confirm that SW ready is yes, then trigger the SW notification and click. If there is still no response, check whether there is `/notification-sw.js`, whether the background notification is intercepted by the browser, and whether there are Service Worker related errors in the console.
Why can I trigger notifications but the system doesn't show them?
It may be intercepted by the system's "Do Not Disturb Mode/Focus Mode", the system notification master switch, and the browser's own notification switch; it may also be affected by site silence or aggregation policies. It is recommended to check the system notification center and browser site permissions.
Related guides
Read a few practical guides for setup, browser compatibility, and troubleshooting around this test.
Silent Alerts: How to Troubleshoot Missing Browser Push Notifications Before Launch
Missing push notifications can cripple user engagement and break critical operational alerts. This practical guide leverages the Browser Push Notification Test tool to help developers and QA teams diagnose permission errors, OS-level blocks, and delivery failures. We walk through a three-step workflow: granting necessary permissions, executing live delivery tests across multiple devices, and validating results to ensure your web app's alert system works flawlessly. Whether you are preparing for a major feature launch or investigating regression issues after a browser update, this article provides actionable steps to verify your Web Push functionality and restore reliable communication channels with your users.
Why Your Users Aren't Getting Alerts: A Step-by-Step Guide to Testing Web Push Notifications
Web push notifications are a critical channel for user engagement, yet delivery failures often go unnoticed until it's too late. This practical guide explores common pitfalls in notification permissions, browser updates, and cross-device compatibility that silence your alerts. We introduce a streamlined workflow using the Browser Push Notification Test tool to proactively verify system permissions, troubleshoot delivery issues, and validate operational alert channels before feature launches. By following our three-step testing protocol—granting permissions, running core workflows, and validating outcomes—developers and product teams can ensure their critical messages reach users reliably across all platforms.
Feedback / report a bug
Tell us your browser, device, and what happened.
Did this result look wrong?
Comments(0)