The State of Web Push Browser Support
Web push notifications have matured significantly over the past few years. What was once a Chrome-only feature is now broadly supported across all major desktop browsers — and increasingly on mobile too. But the picture isn't uniform, and understanding the nuances of browser compatibility is essential before you build your web push strategy.
Browser Compatibility at a Glance
| Browser | Desktop | Mobile | Notes |
|---|---|---|---|
| Chrome | ✅ Full support | ✅ Android only | Industry standard; uses FCM for delivery |
| Firefox | ✅ Full support | ✅ Android | Uses Mozilla Push Service |
| Edge | ✅ Full support | ✅ Android | Chromium-based; uses FCM |
| Safari (macOS) | ✅ macOS 13+ (Ventura) | ✅ iOS 16.4+ | Requires PWA installed to home screen on iOS |
| Opera | ✅ Full support | ⚠️ Limited | Chromium-based; same as Chrome |
| Samsung Internet | N/A | ✅ Android | Supports Push API |
| iOS Safari (pre-16.4) | N/A | ❌ Not supported | Major gap for mobile web |
The iOS Situation: Finally Moving Forward
For years, iOS was the glaring gap in web push support. Apple began rolling out Web Push support on iOS 16.4 in early 2023, but with an important caveat: the website must be installed as a Progressive Web App (PWA) to the home screen before push subscriptions can be created.
This is a meaningful barrier — it requires user intent beyond just visiting a website. For most content sites and ecommerce, this limits the practical iOS web push audience considerably. For PWA-focused products, however, it opens up genuine opportunities.
HTTPS Is Mandatory — No Exceptions
All browsers require your site to be served over HTTPS to use the Push API. This has been the case for several years, but it's worth reiterating: there is no workaround. If your site still has any HTTP endpoints or mixed content warnings, resolve them before attempting to implement push notifications.
Notification Display Differences Across Browsers
Even when push is supported, the visual appearance of notifications varies:
- Chrome / Edge: Support rich notifications with images, action buttons, and badges
- Firefox: Supports basic notifications; action buttons are supported but image display varies by platform
- Safari: Follows system notification style on macOS; action buttons supported from Safari 16+
- Android vs. Desktop: Mobile notifications have smaller display areas; keep titles under 50 characters and bodies under 100 for consistent rendering
The Role of Service Workers in Compatibility
Web push requires a registered service worker. Service worker support is now excellent across all browsers that support web push, so this is rarely a compatibility bottleneck. However, be aware that:
- Service workers are scoped to their directory — ensure your
sw.jsis at the root if you want site-wide coverage - Browsers may throttle or delay push delivery when the device is in battery-saving mode
- Service workers must be updated carefully to avoid breaking existing push subscriptions
Practical Compatibility Testing Checklist
- Test permission prompts and subscription flow in Chrome, Firefox, Edge, and Safari (macOS)
- Test notification display on both Windows and macOS desktop environments
- Test on Android using Chrome and Samsung Internet
- If supporting iOS PWA users, test the full install-to-subscribe flow on iOS 16.4+
- Verify notification click behaviour opens the correct URL in all tested browsers
Looking Ahead
Browser vendors continue to refine their push implementations. Safari's adoption of the web standard is a significant milestone for the ecosystem. As PWA usage grows, expect web push on iOS to become increasingly relevant, though the install-to-home-screen requirement may evolve over time as the technology matures.