Do I need a push notification provider for browser notifications?

Usually, yes—if you mean web push notifications that can appear even when the browser tab isn’t open.

Browser notifications vs. push notifications

There are two related things:

1. In-page browser notifications

   • Shown only while the site is open.
   • Can be triggered directly from your web app using the Notifications API.
   • No push provider needed for this.

2. Web push notifications

   • Can be delivered when the user is not actively on your site.
   • Requires:
     • a service worker
     • user permission
     • push service infrastructure
   • You can send them yourself, but in practice you often use a push notification provider or a backend implementation that talks to push services.

Do you need a provider?

• If you only need notifications while the user is on the site: no.
• If you want true push notifications to the browser/offline/background: generally yes, or at least some backend capable of sending web push.

Common options

• Self-managed web push with a library like web-push
• A third-party provider like OneSignal, Firebase Cloud Messaging (commonly used), etc.

If you want, I can explain the exact setup for Chrome/Edge/Firefox web push or help you choose between self-hosted vs provider.