avatar

Jacob Morrow

Updated: 2026-07-08

3065 Views, 5 min read

Safari notifications behave differently from every other browser's push alerts. Safari hands delivery to Apple Push Notification service (APNs), so messages arrive at the operating-system level on macOS and, since iOS 16.4, on iPhone as well. That native behavior cuts both ways: users want to control when the alerts appear, and product teams want to use them to reach Apple's audience.

This guide covers both sides. You will find the exact steps to enable or silence notifications on iPhone and Mac, the APNs and PWA requirements developers deal with, and a console walkthrough for sending your own campaigns at scale.

Part 1: Safari Push Notifications Ecosystem Overview

Safari is too large an audience to leave out of a web push strategy. According to StatCounter (2026) , Safari holds roughly one in six browser sessions worldwide, second only to Chrome, and it dominates on iPhone.

Support arrived in two waves. Safari notifications started as a macOS-exclusive feature built on APNs. Then, according to WebKit (2023) , iOS and iPadOS 16.4 extended Web Push to iPhone and iPad. On those devices, a Safari notification is only available through Progressive Web Apps (PWAs) added to the user's Home Screen, which request permission and receive pushes the same way native apps do.

Technical Constraints & Differences

Architecture Comparison: Safari vs. Chrome/Firefox

Each one of the popular web browsers has a distinct architecture

Safari routes every notification through APNs, while Chrome and Firefox deliver through the standard Web Push protocol. That single architectural choice drives most of the practical differences in how alerts reach users.

Safari
  • It relies on Apple Push Notification service (APNs) for notification delivery
  • A Safari notification can appear even when the browser is closed
  • Safari requires a push package that includes icons, manifest files, and website credentials
  • The browser uses OS-level integration, making Safari website notifications feel more native
  • It supports macOS natively and iOS via installed PWAs

Chrome/Firefox:

  • These browsers use the Web Push API with VAPID keys for authentication
  • Web push notifications depend on service workers running in the browser
  • They work across all operating systems, such as Windows, macOS, Linux, and Android, without certificates
  • The notifications only appear when the browser is running, except for background service workers
  • These browsers offer more interactive features, such as action buttons and larger payloads

Certificate Requirements (APNs vs. Web Push Standard)

The main difference between browsers is the credential they require. Safari needs an APNs certificate, while Chrome and Firefox rely on Web Push VAPID keys. A developer needs this distinction clear before planning any cross-browser notification campaign.

APNs (Safari)
  • It requires a valid Apple Push Notification service (APNs) certificate for authentication
  • The developers need to create a push package that contains website credentials, icons, and manifest files
  • The certificates need periodic renewal so that the Safari push notification delivers without interruptions
  • It ensures secure, OS-level delivery directly to macOS and iOS devices
  • It is mandatory for Safari notifications on both macOS and iOS PWAs
Web Push Standard (Chrome/Firefox)
  • It uses VAPID keys for authentication instead of certificates
  • It doesn't require a push package, but only a subscription object and a service worker
  • It is easier to implement across multiple browsers and platforms
  • It relies on browser-level delivery, not OS-level integration
  • It doesn't require certificate renewal, which makes long-term maintenance much simpler

Part 2: Safari Notification Settings on iPhone and Mac

With the ecosystem clear, here is where the actual controls live on each device.

iOS Device Setup Guide

How to Turn On Safari Notifications on iPhone

On iPhone, Safari notifications only work for websites you have added to your Home Screen as web apps, and only on iOS 16.4 or later. To subscribe to a website's notifications:

  • First, launch Safari and load the website you wish to get notifications from
  • Tap the "Share " button, then tap "Add to Home Screen "
  • Rename the web app if needed and tap "Add "
  • Open the app from your Home Screen. When it asks to send notifications, tap "Allow "

Websites cannot ask for permission on page load. Apple requires a direct tap or interaction first, so a well-built site will show its permission prompt only after you engage with it.

How to Turn Off Safari Notifications on iPhone

Each installed web app behaves like a regular app, so its alerts are managed in the same place:

  • Go to Settings > Notifications
  • Find the web app on the list and switch "Allow Notifications " off
  • To cut notifications permanently, delete the web app from your Home Screen

Mac-Specific Configuration

System Settings & Safari Sync

On a Mac, notification behavior lives in Apple menu > System Settings > Notifications > Safari . From there, you can set alerts to appear as banners, alerts, or in the Notification Center. Safari also syncs website permissions across devices signed into the same Apple ID, which saves repeated setup if you work across several machines.

Bulk Notification Control Tips

Changing permissions one site at a time is slow. To manage every site from a single screen, open Safari > Settings > Websites > Notifications . The panel lists every website you have responded to, with an Allow or Deny dropdown next to each, so you can approve or block them in bulk.

How iOS and macOS Notification Behavior Compares

The two systems differ in more than persistence:

Feature / Behavior iOS macOS
Notification Availability Only works for installed PWAs Works even when Safari is closed
Display Style Standard iOS notifications (banners, alerts) Banners, alerts, or Notification Center
Persistence Temporary, disappears if the app is closed Persistent, remains in Notification Center
User Control Managed via Settings > Notifications > [PWA] Managed via System Settings > Notifications > Safari
Sync Across Devices Limited to Apple ID if PWA is installed Syncs permissions across all devices using the same Apple ID
Action Buttons / Interactivity Limited, similar to standard iOS notifications Slightly more flexible, but fewer than Chrome/Firefox
Version Support iOS/iPadOS 16.4 or later, PWAs only All modern macOS versions (APNs support since Safari 7)

Syncing Issues & Fixes

Sometimes permissions fail to sync across devices. In most cases, reinstalling the PWA, clearing the Safari cache, and checking the Apple ID credentials will solve the issue.

Security & Anti-Spam Measures

Safari blocks unsolicited permission prompts, but users should stay alert for malicious notifications. As a rule of thumb, only accept Safari push notifications from trusted websites and PWAs that you have added to your Home Screen yourself.

Some Tips to Remain Safe
  • Regularly review your active notification permissions
  • Avoid clicking suspicious notifications
  • Enable Focus or Do Not Disturb mode
  • Keep Safari and iOS/macOS updated to the latest security patches

Part 3: How to Turn Off Safari Notifications on Mac

To turn off Safari notifications on Mac, open System Settings > Notifications > Safari and switch off "Allow notifications ". To stop a single website instead, go to Safari > Settings > Websites > Notifications and set that site to Deny. The sections below walk through each path.

Stop Safari Notifications from One Website

This is the right fix when one noisy site is the problem and you still want alerts from everyone else:

  • First, open Safari and go to Safari > Settings in the menu bar
  • Select the "Websites " tab, then click "Notifications " in the sidebar
  • Find the website on the list and change its dropdown to "Deny ", or select it and click "Remove " to erase the permission entirely
  • To stop future prompts from every site, uncheck "Allow websites to ask for permission to send notifications " at the bottom of the same panel

Apple documents the same panel in its official Safari notification guide , which is the fastest reference if your Safari version shows a slightly different layout.

Turn Off All Safari Notifications at Once

If you want silence from every website Safari has permission for, cut it off at the system level:

  • Open System Settings from the Apple menu
  • Click "Notifications " and select Safari from the app list
  • Switch off "Allow notifications "

This mutes every Safari notification without touching your per-site choices, so you can re-enable everything later with one toggle.

Close or Clear Notifications You Already Received

Turning notifications off doesn't remove the ones already sitting on your screen. To close a single Safari notification, hover over the banner and click the "X " that appears. To clear the backlog, click the date and time in the top-right corner of the menu bar to open Notification Center, then use "Clear All " next to the Safari group.

Part 4: Safari Push Notifications for Developers

The Safari notifications settings above cover the user experience. Shipping notifications to those users takes a few more technical details.

Technical Implementation

Web Push API in Safari: Key Differences

A Safari notification uses the same core technologies as any other push notification, but Safari's implementation of the Web Push API has unique characteristics compared to other browsers.

The key differences include:

  • APNs Dependency: Unlike Chrome or Firefox, Safari relies on APNs to deliver notifications, even when the browser is closed
  • Payload Limitations: Safari supports smaller notification payloads, so you need to optimize the message content
  • Push Package Requirement: Safari notifications require a push package containing icons, manifest files, and website credentials for authentication
  • Subscription Management: Users can manage permissions per website, and Safari syncs these preferences across all Apple devices registered to the same Apple ID
  • Platform Differences: On macOS, notifications can appear even when Safari isn't running. On iOS, notifications only work for installed PWAs
  • Limited Action Buttons: Safari push notifications support fewer interactive buttons than Chrome or Firefox, which may affect your engagement strategies

APNs Certificate Requirements

Sending Safari push notifications requires an APNs certificate issued through an Apple Developer account. Your developers upload it to your push server or platform, and it authenticates every message you send.

Compatibility Solutions

Legacy support deserves a note. Safari 15 and below only support Safari notifications on macOS, and iOS devices before 16.4 cannot receive Safari push notifications at all. If part of your audience runs older devices, plan alternate channels such as app push notifications or email alerts, and review how to implement PWA push notifications for the installable web app route.

Multi-Browser Fallback Strategies

Full coverage means combining Safari website notifications with Chrome/Firefox Web Push. That way, users receive your notifications regardless of device or operating system. The practical route is a platform that manages both credential systems, APNs and VAPID, from one place.

Part 5: How to Send Safari Push Notifications at Scale

Web push product overview showing multi-browser notification delivery

Safari website notifications fall under web push as a product category, so the cleanest setup is a web push platform that handles APNs certificates for Safari and VAPID keys for Chrome and Firefox in the same console. EngageLab does exactly that, and adds app push, email, and SMS channels when you need them.

Key Advantages

  • Native Safari Certificate Support: EngageLab simplifies APNs certificate management. You can upload, renew, and monitor certificates without manual server configuration, which reduces errors and downtime
  • Cross-Version Browser Compatibility: The platform supports multiple browser versions, including legacy Safari, Chrome, and Firefox, ensuring notifications reach all audiences
  • Developer Workflow Enhancements: You can send test notifications, create a push plan, and troubleshoot issues directly from the dashboard

API Integration Guide

The Safari-specific certificate flow lives in the console's integration settings documentation . The short version:

  • First, create a free EngageLab account, which comes with a 15-day free trial and needs no credit card, then open the push console. The overview lists your applications and their integration status.
  • Push console overview with application list and integration status Start Your Free 15-Day Trial
  • Then go to Integration Settings > iOS .
  • Select "iOS certificate configuration " and upload the P12 certificate. The console authenticates it in the background and flags expiry dates so renewals never catch you off guard.
  • iOS certificate configuration screen under integration settings

Performance Tracking

Once the certificate is in place, you can start sending Safari website notifications and watching how they perform.

Push Analytics Dashboard

Every campaign reports in real time. EngageLab statistics track delivery rates, click-throughs, and user engagement in one dashboard, so a failing certificate or a weak message shows up in the numbers immediately.

Web push statistics overview for delivery and click tracking

A/B Testing for Campaign Optimization

The built-in A/B testing function lets you test different notification messages, send times, and targeting strategies against each other, then route the winning variant to the rest of your audience.

A/B testing setup for push notification campaign optimization

FAQs About Safari Notifications

Why do I keep getting weird or fake notifications from Safari?

A website you once allowed is abusing its permission, often with fake virus warnings or prize claims. Don't click them. Open Safari > Settings > Websites > Notifications , find the site, and set it to Deny or remove it. If you don't recognize any site on the list, clear them all and re-allow only the ones you trust.

How do I stop Safari notifications on my MacBook?

Go to System Settings > Notifications > Safari and switch off "Allow notifications" to silence everything, or use Safari's Websites settings to deny individual sites. Part 3 of this guide walks through both paths step by step.

How do I see notifications I missed in Safari?

macOS keeps delivered alerts in Notification Center. Click the date and time in the top-right corner of your screen, and scroll to the Safari group to review anything you missed. On iPhone, swipe down from the top of the screen to open Notification Center.

Why is my iPhone not showing Safari notifications?

Three requirements have to line up: the device runs iOS 16.4 or later, the website is installed on your Home Screen as a web app, and notifications are allowed for that web app in Settings > Notifications . If any one of them is missing, nothing will arrive.

The Bottom Line

Safari notifications reward whoever handles the details. Users get precise control once they know where the iOS and macOS switches live, and businesses get a native-feeling channel to Apple's audience once the APNs certificate and PWA requirements are in place. If sending is your side of the equation, a console that manages Safari and standard web push together removes most of the friction. Create a free account and send your first Safari campaign today.