Yes, you need HTTPS to send web push notifications. The Push API and service workers only run in secure contexts, so visitors can subscribe only on an HTTPS page. The one exception is localhost during development. Your push panel or server should use HTTPS as well, because it handles logins and subscriber data.
This is one of the most common questions I see from site owners who still run an old HTTP site. The short version: the HTTPS requirement isn’t a vendor rule you can negotiate around. It’s built into browsers. Below is what the rule covers, why it exists, and what to do if your site isn’t on HTTPS yet.
Why does web push require HTTPS?
Web push requires HTTPS because browsers restrict the Push API, the Notifications permission flow and service workers to secure contexts. On a plain HTTP page, the browser doesn’t expose the APIs a push script needs, so there’s nothing to subscribe to.
MDN marks the Push API and Service Worker API as available only in secure contexts. The reason is simple. A service worker can intercept requests and run in the background, so an attacker who could inject one over plain HTTP would gain a lot of power. HTTPS makes sure the script really came from your site.
Which parts of a web push setup need HTTPS?
Every part that runs in or talks to the browser needs HTTPS: the page where visitors subscribe, the service worker file, and the push panel or API your site calls. The connection from your server to the browser push service is HTTPS by design.
| Part | Needs HTTPS? | Why |
|---|---|---|
| Your website (subscribe page) | Yes | Push API and service workers need a secure context |
| Service worker file (for example sw.js) | Yes | Must be served from the same secure origin |
| Push panel or dashboard | Yes, strongly recommended | Logins, API keys and subscriber data |
| Server to push service (FCM, Mozilla, Apple) | Yes, always | Push services only accept HTTPS requests, per RFC 8030 |
| Local development (localhost) | No | Browsers treat localhost as a secure context |
If you want the bigger picture of how these pieces connect, see how push notifications work and my guide to the service worker for web push.
Can you send web push notifications from an HTTP site?
Not directly. A visitor on an HTTP page can’t create a push subscription for that HTTP origin. However, some providers used to offer a workaround: a pop-up or redirect to an HTTPS subdomain on the provider’s domain, where the actual subscription happened.
That workaround has real downsides. The subscription belongs to the provider’s domain, not yours. The extra window lowers opt-ins, and moving away later is hard, because subscriptions are tied to the origin that created them. I explain that last point in what happens to web push subscribers if you change domain. In 2026, moving your site to HTTPS is cheaper and cleaner than any workaround.
Is a free SSL certificate good enough for web push?
Yes. Browsers care that the certificate is valid and trusted, not what it costs. A free certificate from Let’s Encrypt works exactly like a paid one for web push.
What matters is that it stays valid. If a certificate expires, browsers show warnings, the push script may fail to load, and new subscriptions stop. So turn on automatic renewal and check it once in a while. Most hosting control panels and managed WordPress hosts issue and renew free certificates automatically.
Does the whole site need HTTPS, or only one page?
Technically, only the origin where people subscribe needs HTTPS, and an origin is the scheme, host and port together. In practice, run the whole site on HTTPS and redirect HTTP to HTTPS.
There are two reasons. First, https://example.com and http://example.com are different origins, so a mixed setup splits your subscribers. Second, a service worker’s scope covers paths under its location on that origin, so a single HTTPS section limits where the prompt can work. Full-site HTTPS avoids both problems and is good practice for SEO and user trust anyway.
What about iPhone and Safari?
Safari has the same HTTPS rule. On iPhone and iPad, web push also requires iOS 16.4 or later, and the site must be added to the Home Screen as a web app, as Apple explains in WebKit’s web push for iOS announcement.
So HTTPS is necessary but not sufficient on iOS. You also need a web app manifest so the site can be added to the Home Screen. For browser-by-browser details, see which browsers support web push.
How do you move a site to HTTPS before adding push?
Move to HTTPS in a few steps: install a certificate, update internal links and settings, redirect HTTP to HTTPS, then check for mixed content. After that, add the push script and service worker on the HTTPS site.
- Issue a certificate through your host or with Let’s Encrypt.
- Change the site URL to https:// (on WordPress, under Settings, General).
- Add a 301 redirect from HTTP to HTTPS.
- Fix mixed content, such as images or scripts loaded over http://.
- Update the property in Google Search Console and your sitemap.
- Install the push script and service worker, then test a subscription.
Do this before you collect any subscribers. If you add push first and switch protocols later, subscribers from the HTTP origin won’t carry over automatically.
Where does LaraPush fit?
LaraPush is a self-hosted panel that you install on your own VPS, on a domain or subdomain such as push.example.com. Installation is free and automated from the customer portal. You then add your HTTPS website, connect its Firebase configuration, and place the JavaScript and service worker, or use the free WordPress plugin.
You still need HTTPS on your own site, and you run the VPS. The licence covers one server, and there’s no free plan. Plans start from $499 one-time; see the pricing page for the current price and the features overview for what’s included. To compare tools first, read my guide to push notification services.
Frequently asked questions
No. Browsers only expose the Push API and service workers in secure contexts, so a visitor on an HTTP page can’t subscribe to that origin. Some providers used a pop-up on their own HTTPS subdomain as a workaround, but the subscription then belongs to their domain, not yours.
Yes, on localhost. Browsers treat localhost as a secure context, so you can develop and test a service worker and push subscription on your own machine without a certificate. As soon as the site runs on a real domain, it needs HTTPS.
Yes. Web push only needs a valid, trusted certificate, and Let’s Encrypt certificates are trusted by all major browsers. Make sure automatic renewal works, because an expired certificate stops the push script from loading and blocks new subscriptions.
Not automatically. HTTP and HTTPS are different origins, and subscriptions belong to the origin that created them. Visitors will need to subscribe again on the HTTPS site, which is why it’s best to move to HTTPS before you start collecting push subscribers.
Yes, in practice. The panel handles admin logins, API keys and subscriber data, so it should always use HTTPS. Browsers may also block your HTTPS site from calling an HTTP endpoint as mixed content, and push services only accept HTTPS requests from your server.




