Safari push notifications on the Mac
Safari on macOS now speaks the same Web Push standard as Chrome and Firefox. The old Apple-only system with developer certificates is no longer required.
- Safari supports standard Web Push on macOS 13 Ventura and later.
- No Apple Developer account or certificate is needed — the same VAPID keys work.
- Safari requires the permission request to follow a user gesture.
- Safari 18.5 on macOS added Declarative Web Push, which can show notifications without a service worker.
Old Safari push vs. standard Web Push
| Legacy “Safari Push Notifications” | Standard Web Push (today) | |
|---|---|---|
| Introduced | OS X Mavericks era | Safari 16.1 on macOS 13 Ventura |
| Requires | Apple Developer account, website push ID, certificate | VAPID keys only |
| Code | Safari-specific API | Same Push API and service worker as other browsers |
| iPhone/iPad | No | Yes, for Home Screen web apps on 16.4+ |
If you set up Safari push years ago with a certificate, the standard approach replaces it for current macOS versions. Pusharoo uses standard Web Push only.
How Safari asks
Safari only allows the permission request in response to a user gesture such as a click. Calling it on page load fails silently. The two-step pattern — your own prompt, then Safari’s dialog after “Allow” — works naturally (opt-in). Once allowed, notifications appear in macOS Notification Center under Safari, labelled with your site.
Settings on the Mac
| What | Where |
|---|---|
| Per-site permission | Safari → Settings → Websites → Notifications |
| Stop all sites asking | Same pane → untick “Allow websites to ask for permission to send notifications” |
| Banner style, Focus | System Settings → Notifications → Safari |
| Dock web apps | System Settings → Notifications → the web app’s name |
Web apps in the Dock
Since Safari 17 on macOS Sonoma, people can choose File → Add to Dock to save a site as a standalone web app. Those web apps manage notifications separately, just like iPhone Home Screen web apps, and appear in System Settings as their own entries. A good web app manifest makes the Dock version look right.
Declarative Web Push
Apple’s WebKit team introduced Declarative Web Push — iOS and iPadOS 18.4 for Home Screen web apps, then Safari 18.5 on macOS. A push message in a standard JSON shape can be displayed by the browser without running a service worker, which is more power-efficient and more robust. It’s backwards compatible: other browsers can still handle the same payload in a service worker. We explain it in Declarative Web Push.
Safari on iPhone and iPad
On iPhone and iPad, a Safari tab can’t receive web push. Since iOS/iPadOS 16.4, a site added to the Home Screen can — the Home Screen web app gets its own notification settings. That’s a different flow from macOS, where any Safari tab can ask (iPhone steps, technical details).
Focus, Notification Summary and delivery
macOS Focus modes can silence Safari or a Dock web app entirely, and notifications can be grouped by app. If a test notification doesn’t appear, check System Settings → Notifications → Safari (or the web app) and the current Focus. Safari must be allowed to show notifications and, for alerts that stay on screen, set to “Alerts” rather than “Banners”.
What Safari notifications show
- Title, body and the site icon — no large images, no action buttons.
- Every push must result in a visible notification; WebKit can revoke subscriptions that repeatedly show nothing.
- Safari must be allowed in macOS notification settings, and Focus modes may hold banners in Notification Center.
Questions
Do I need an Apple Developer account for Safari web push?
No. Standard Web Push in Safari (macOS 13+ and iOS 16.4+) uses VAPID keys like other browsers. Only the legacy Safari push system required a developer account.
Does Safari web push work on older macOS versions?
Standard Web Push needs macOS 13 Ventura or later with a current Safari. Older versions supported only the legacy certificate-based system.
Why doesn’t Safari ask for permission on my site?
The request must follow a click. Calls made on page load or after a timer are ignored.
Do Safari notifications support images?
Safari doesn’t show large images in web notifications. Use a clear title and body instead.
Keep reading
Web push on iPhone and iPad, explained honestly
The Home Screen rule, the manifest you need, and how to guide iPhone visitors without friction.
Declarative Web Push, explained
The JSON payload format, Apple platform support, how it falls back elsewhere and when to adopt it.
Browser push notifications: who supports what
Support table for Chrome, Edge, Firefox, Safari, Opera and Samsung Internet — desktop, Android and iPhone.
PWA push notifications on iOS and Android
Manifest, service worker, iPhone Home Screen requirement, Android install, badging and a setup checklist.
More in Browsers & devices: Chrome push notifications: a complete guide · Firefox push notifications: how they work · Microsoft Edge push notifications · Web push notifications on Android · Web push notifications not working? Fix it by symptom · How to test web push notifications · How to turn off website notifications · Samsung Internet notifications, explained · Push notifications in Opera and Opera GX · Brave push notifications: why they fail and how to fix it · Website notifications on a Chromebook · How to get website notifications on your iPhone · All guides
Free for life. No limits.
Unlimited subscribers, campaigns and automations. No badges. About five minutes to install.