What Are Web Push Notifications? A Complete Guide for 2026

In this article

1. What is a web push notification?
2. How web push notifications work
3. What you need to send web push notifications
4. Which browsers and devices support web push?
5. Web push vs email vs mobile app notifications
6. The main advantages of web push notifications for a website
7. What web push notifications are good for
8. How to get subscribers without annoying visitors
9. How often should you send?
10. How to increase engagement with web push notifications
11. Privacy and consent
12. How to add web push notifications to your website
13. How to turn off web push notifications
14. Frequently asked questions

Web push notifications are short, clickable messages that a website sends to people who said yes to them. They appear on the desktop or phone like an app notification, even when the website isn’t open. No app, no email address and no phone number are needed: one click on Allow in the browser is enough.

This guide explains what a web push notification is, how it works behind the scenes, which browsers and devices support it, and how to use it without annoying the people who subscribed.

What is a web push notification?

A web push notification is a message sent by a website through the visitor’s browser. It usually has:

• A title, the first thing people read, for example “New guide: how to price your services”.
• A short message with one or two lines of detail.
• An icon, normally your logo, so people know who it is from.
• An optional large image, shown on Chrome and Edge on Windows and Android.
• A link. Clicking the notification opens that page on your website.

People subscribe by allowing notifications when your website asks. From then on, you can reach that browser with a notification whenever you have something worth saying, and they can switch it off at any time from their browser settings.

How web push notifications work

Web push is an open standard built into modern browsers. Four pieces work together:

1. The visitor allows notifications. Your site asks, and the browser shows its own permission prompt. Nothing happens without that click.
2. The browser creates a subscription. It registers with its own push service (each browser maker runs one) and hands your site a unique, encrypted address for that browser.
3. You send a message. Your push provider encrypts the notification and sends it to that address, signed with a key pair called VAPID that proves it came from you.
4. The service worker shows it. A small file on your website, the service worker, wakes up in the browser and displays the notification, even if your site isn’t open in a tab.

Because this is the standard Web Push protocol, you don’t need a Firebase project or a Google developer account to send to Chrome. Push Agent, for example, encrypts each message on its own server and delivers it straight to the browser’s push service.

What you need to send web push notifications

• An HTTPS website. Browsers only allow push on secure sites (localhost works for testing).
• A service worker file at the root of your domain. A push service gives you this file or creates it for you.
• A way to collect subscribers and send messages. That is what a push notification service does: the opt-in prompt, the subscriber list, the sending and the click stats.

With Push Agent, WordPress and Joomla plugins handle all of this. On any other website you add one line of code and upload one small file.

Which browsers and devices support web push?

Web push works on almost every modern desktop and Android browser:

• Chrome, Edge, Firefox and Opera on Windows, macOS, Linux and Android.
• Safari on Mac (Safari 16 and newer on recent versions of macOS).
• iPhone and iPad (iOS and iPadOS 16.4 and newer), but only after the visitor adds your website to their Home Screen. Notifications aren’t offered to iPhone visitors browsing in a normal Safari tab.

On a computer, the browser has to be running to receive notifications, although it can be minimised or running in the background. Messages sent while it was closed are usually delivered the next time it starts, as long as they haven’t expired.

Web push vs email vs mobile app notifications

	Web push	Email	App notifications
What people give you	One click on Allow	Their email address	They install your app
Where it appears	On screen, like an app alert	In the inbox	On screen
Personal data collected	None needed	Email address	Depends on the app
Length	A title and a line or two	As long as you like	Short
Best for	Timely news, updates and offers	Detail, receipts, newsletters	Apps people use daily

The main advantages of web push notifications for a website

• Easy to subscribe. One click on Allow, with no form to fill in, so far more visitors are willing to say yes than to share an email address.
• Seen straight away. The notification appears on screen, not in an inbox where it competes with dozens of other messages.
• Brings people back. Most visitors leave and never return. Push gives you a way to invite them back when you publish something new or have an offer.
• No personal data. You don’t need names, email addresses or phone numbers, which keeps things simple for you and your visitors.
• Works without an app. You don’t have to build, publish or maintain a mobile app to reach people on their phones.
• Low cost. There are no per-message charges like SMS, and many services, including Push Agent, offer unlimited notifications.
• Easy for people to leave. Visitors can switch notifications off at any time, so your list stays full of people who actually want to hear from you.

What web push notifications are good for

• Blogs and news sites: tell readers about new posts. With automatic RSS sending, every new post can go out on its own.
• Online stores: flash sales, new arrivals and, most useful of all, order status updates. See WooCommerce order notifications.
• Services and SaaS: reminders, new features and account alerts.
• Events and education: start times, schedule changes and new lessons.

How to get subscribers without annoying visitors

Browsers now protect people from pushy permission prompts. Chrome, for example, can show a quieter prompt for sites that people often block, and it removes notification permission for sites that send abusive notifications or that a person hasn’t visited for a while. So the way you ask matters:

• Don’t ask the moment the page loads. Give people a few seconds to see what your site is about.
• Explain the value first. A small card that says what they’ll get (“New guides, about once a week”) before the browser prompt appears gets better results than the browser prompt alone.
• Ask at a natural moment. Right after checkout is perfect for order updates.

Push Agent shows an “Allow notifications” card first, and the browser’s own prompt appears only when the visitor clicks Allow on it. On paid plans you can write the card’s text yourself and choose when it appears.

How often should you send?

Send when you have something genuinely useful, and keep it consistent with what you promised. A news site can send several times a day; a small shop might send once or twice a week plus order updates. If unsubscribes rise after a busy week, slow down. Chrome has also introduced rate limits for sites that send a very high volume of notifications that people ignore, which is one more reason to favour quality over quantity (Chrome’s announcement).

Not sure which wording works best? A/B test your notifications and let your subscribers decide.

How to increase engagement with web push notifications

Engagement means people click your notifications and stay subscribed. These habits make the biggest difference:

1. Make every notification useful on its own. The title should say what’s in it for the reader: “Your order has shipped” or “How to cut your hosting bill in half”, not “News from our team”.
2. Send to the right people. Target by country, device or browser so people only get what applies to them, for example a sale that only ships to one country.
3. Pick the right time. Schedule notifications for when your audience is awake and online, in their own time zone.
4. Use a large image when it adds something, such as a product photo. It makes the notification stand out on Windows and Android.
5. Test your wording. Run A/B tests on titles and messages, and keep what works.
6. Automate what people expect. Send new blog posts automatically with RSS, and order status updates to shoppers.
7. Don’t overdo it. Keep to the rhythm you promised when people subscribed, and watch your unsubscribe numbers after busy weeks.
8. Ask at the right moment. A good opt-in message brings in people who actually want to hear from you, and they click more later.

Privacy and consent

Web push is opt-in by design: nobody can receive a notification without clicking Allow, and they can block your site again with two clicks. A subscriber is a browser, not a named person, so you don’t need to collect an email address or a name. It’s still good practice to mention push notifications in your privacy policy and to explain what you’ll send. If you have specific legal questions about consent where you operate, check with a lawyer.

How to add web push notifications to your website

1. Create a free Push Agent account. The Free plan covers up to 2,500 subscribers with unlimited notifications, and no credit card is needed.
2. Add your website in the dashboard.
3. Install the plugin or add the code: WordPress, Joomla or any other HTTPS website.
4. Open your site in a private window, allow notifications and send yourself a test.

Adding web push to a custom-built website

If your site isn’t on WordPress or Joomla, the essential steps are the same on any platform:

1. Make sure the whole site runs on HTTPS. Browsers refuse push on insecure pages.
2. Add the push service’s script to every page, usually once in a shared footer or layout template, just before the closing </body> tag.
3. Put the service worker file in the root folder of your domain, so it opens at https://your-site.com/pushagent-sw.js. It can’t sit in a sub-folder.
4. Clear your page cache and CDN so visitors get the new code.
5. Verify the setup from your dashboard, then allow notifications in a private window and send yourself a test.

Push Agent’s guide for any HTTPS website walks through each step with screenshots.

Comparing providers first? Read our comparison of free push notification services.

How to turn off web push notifications

If you’re on the receiving end and want fewer notifications, you can block one site or all of them. Blocking takes effect straight away.

Chrome on a computer

1. Open Chrome’s menu (the three dots), then Settings → Privacy and security → Site settings → Notifications.
2. Under Allowed to send notifications, find the site, open its menu and choose Block or Remove.
3. To stop all sites from asking, choose Don’t allow sites to send notifications.

Quicker for one site: open the site, click the icon to the left of the address, and switch Notifications off.

Chrome on Android

Open Chrome’s menu, then Settings → Site settings → Notifications, tap the site and block it. You can also long-press a notification and turn off notifications for that site.

Microsoft Edge

Go to Settings → Cookies and site permissions → Notifications, then block or remove the site.

Firefox

Go to Settings → Privacy & Security → Permissions → Notifications → Settings, select the site and set it to Block, or remove it.

Safari on Mac

Choose Safari → Settings → Websites → Notifications, select the site and set it to Deny.

iPhone and iPad

Web notifications on iPhone come from websites added to the Home Screen. Open Settings → Notifications, tap the site’s name and switch off Allow Notifications, or simply delete the web app from your Home Screen.

Getting notifications you don’t remember allowing?

Unwanted notifications usually come from a site where someone clicked Allow, sometimes after a misleading message such as “Click Allow to prove you’re not a robot”. Don’t click those notifications. Block the site using the steps above, and run Chrome’s Safety Check, which can also remove notification permission from sites you don’t use.

Frequently asked questions