Do I still need to update my Apple certificate for Safari web push notifications?

Whether you still need an Apple certificate depends on which macOS/Safari versions you want to reach.

macOS Ventura (13) and newer

Modern Safari supports the standard web push protocol, just like Chrome and Firefox. These browsers are covered by the All browsers configuration (VAPID keys) in Settings > Platform Configuration > Web Push Notifications. A separate Apple Website Push ID certificate (.p12) is not required.

macOS 10.14–12 (Mojave through Monterey)

To keep reaching Safari users on these older macOS versions you must maintain the separate Safari Configuration, which requires a Website Push ID certificate issued from your Apple Developer account, exported as a .p12 and uploaded to Pushwoosh. Apple certificates expire, so this configuration has to be renewed.

In short:

• Only supporting macOS Ventura and newer → you do not need the certificate; the All browsers configuration is enough.
• Still supporting macOS 10.14–12 → keep the legacy Safari configuration and renew the certificate before it expires.

How to size your legacy Safari audience

There is no default tag that records the Safari version, so filtering by "Device Model is Safari 15" will not work. Instead, look at your web audience by operating-system version:

1. Go to Segments for your project and create a new segment.
2. Add a filter on the OS Version default tag (Version type — supports less than or equal, between, and similar operators) combined with your web application.
3. Calculate the segment size to estimate how many subscribers are on older macOS versions.

If that number is negligible, you can drop the legacy Safari configuration and stop renewing the certificate.

Note: Safari downloads the push package (site name, icon, signature) only once, at subscription time, and it cannot be force-updated on already-subscribed devices.