What are web push notifications? How Web Push works
A web push notification is a browser message sent by a website after a visitor grants permission. It uses a service worker and browser-issued subscription, so the website does not need an email address or phone number.
A useful return channel, with clear technical boundaries
Web push can bring a reader back after they leave your site, but it is not a shortcut around consent. The browser owns the final permission decision. The browser vendor operates the push service. The operating system controls presentation and interruption settings.
PushNotifications.org currently manages registered origins, encrypted subscriber records, message composition, future scheduling, plan allowances, 24-hour repeat protection, permanent endpoint cleanup, and accepted-attempt or failure totals. Advanced segmentation, quiet hours, and click analytics are not presented as shipped features.
Validated by the open web platform
The implementation follows published browser APIs rather than a private delivery format.
W3C Push API
The specification defines how an application server sends a message through a push service to a service worker, including delivery while the web application is inactive.
Read the W3C Push API specificationMDN implementation guidance
MDN documents the service worker requirement, the subscription endpoint and encryption keys, permission behavior, and browser compatibility.
Review the MDN Push API guideWebKit on iPhone and iPad
WebKit documents standards-based Web Push for Home Screen web apps on iOS and iPadOS 16.4 or later, with permission requested after a direct interaction.
Read the WebKit implementation notesHow one notification reaches one browser
The browser creates a subscription for one service worker. The application server encrypts the message for that subscription, the vendor push service routes it, and the service worker asks the browser to display it.
The browser grants or denies permission
Your site can explain the value first, but it cannot bypass the browser prompt or reverse a denial.
An endpoint and encryption keys are created
The active service worker requests a PushSubscription, then the application stores it for the registered origin.
The payload travels through the vendor push service
Your application server encrypts the message for that subscription. The browser vendor transports it.
The service worker shows the notification
The browser and operating system determine the final appearance. A click opens the destination you configured.
Use cases that start with a real event
Each message should connect a specific trigger to a destination that fulfills the promise. These are design patterns, not claims that the current release automatically evaluates these triggers or exclusions.
New article
Trigger: a post is published in an opted-in topic.
Exclude: visitors who already opened the article.
Destination: the canonical article URL.
Account activity
Trigger: a meaningful account event needs attention.
Exclude: resolved or acknowledged events.
Destination: the authenticated activity screen.
Price or stock change
Trigger: a watched item crosses a subscriber-defined condition.
Exclude: alerts sent inside the frequency window.
Destination: the exact item or watchlist entry.
Abandoned task
Trigger: an unfinished workflow remains inactive.
Exclude: completed, expired, or unsubscribed records.
Destination: the recoverable step, not a generic homepage.
Design the permission explanation in site code
A pre-prompt can explain the message type and frequency before the browser-owned permission request appears. The current SDK exposes an explicit subscription action; timing and explanatory UI remain the responsibility of the integrating website.
- Attach the subscription call to a direct user action
- Explain the message category before the browser prompt
- Respect the browser’s dismissed or denied state
- Keep iPhone and iPad Home Screen requirements visible
Generate a bounded draft without automating delivery
Start with approved source text and generate one short title and message. A person still chooses the registered website, verifies the destination, edits the wording, and schedules the campaign.
- Source text between defined request limits
- Title and message returned as fixed JSON fields
- No autonomous audience, destination, or schedule decision
- Human review before a generated draft becomes a campaign
Browser support, without pretending every device behaves the same
Use feature detection and test the actual operating system path. Browser support does not guarantee identical prompts, layouts, quotas, Focus settings, or background behavior.
Desktop
Standards-based Web Push is broadly available in current Chromium browsers, Firefox, and Safari on supported desktop operating systems.
Best practice: test notification actions, icon treatment, and truncation per operating system.Android
Supported browsers can receive Web Push through their vendor delivery services after the visitor grants permission.
Best practice: test battery restrictions and notification channel settings on representative devices.iPhone and iPad
Web Push applies to Home Screen web apps on iOS and iPadOS 16.4 or later. Permission must follow a direct user interaction.
Best practice: explain Add to Home Screen before offering the subscribe action.Measure provider responses without calling them views
The current application records accepted attempts and failures. A successful provider response does not prove notification display, attention, or a click, so the reporting language keeps those outcomes separate.
- Attempted
- The worker consumed one account delivery allowance for a subscriber.
- Accepted
- The push request completed without a provider exception.
- Failed
- The provider rejected the request or the send path raised an error.
- Retired
- A 404 or 410 response removed the endpoint from future sends.
What happens when delivery fails
Endpoint cleanup is implemented for permanent failures. Automatic retry for temporary provider failures is not currently implemented and should not be implied.
Temporary server response
The current worker records a failed attempt without automatically retrying it. A future retry policy should be bounded by message usefulness and idempotency.
Rate limiting
The current worker records the failure. A future implementation should respect Retry-After and avoid turning throttling into an immediate retry storm.
Expired subscription
Mark the endpoint inactive and stop future sends. Expired endpoints should not remain in campaign denominators.
Revoked permission
Honor the browser state and subscriber preferences. A revoked permission is not a lead to be reacquired through another prompt.
Common web push questions
Short answers first, followed by the technical constraint that changes implementation decisions.
Does web push require an email address or phone number?
No. The browser creates a PushSubscription containing an endpoint and encryption keys. The endpoint is a unique capability URL and must be protected like a delivery credential.
Does web push work when the website is closed?
Yes. The Push API supports delivery when the web application is not in the foreground or currently loaded. Delivery still depends on the browser, operating system, device settings, and vendor push service.
Does web push work on iPhone and iPad?
Yes, for Home Screen web apps on iOS and iPadOS 16.4 or later. The permission request must follow a direct interaction such as tapping a subscribe button.
Can a subscriber turn notifications off?
Yes. Subscribers can revoke browser or operating system permission. Your site should also expose preference and unsubscribe controls that are easier to find.
Do websites need Firebase to use Web Push?
No. A website can use the standards-based Push API without the Firebase SDK or dashboard. Browser vendors still operate the delivery services used by their browsers, so the network path is not fully independent.
Technical sources and review notes
This page separates product capabilities from browser behavior. Browser and standards claims were checked against the following primary references. For a structured reading sequence, use the Web Push fundamentals learning path; for implementation details, continue to the Web Push API and SDK documentation. Product interface images are workflow previews created for PushNotifications.org and do not represent third-party customer data.
Build a web push channel people can trust
Start with unlimited subscriber records and 1,000 free delivery attempts each day. Keep permission, 24-hour repeat protection, provider responses, and endpoint cleanup visible from the beginning.