Skip to Content
Platform.Ontology

Notifications

Asks to show system notifications outside the browser tab.

Asks you firstNotifications and backgroundNotificationsWeb browsersWhile you use itAfter you leave the site

In one line

Can show messages on your screen outside the browser tab, once you tap Allow

Asks to show system notifications outside the browser tab.

Lets a site put messages on the person's desktop or lock screen. Reaches the person after they leave the page; abuse is spam, scams and fake alerts, so browsers add quiet prompts and auto-revocation.

What it can and can't do

What the user does: You tap Allow on the site's notification pop up

It can

  • Show alerts on your desktop or lock screen after you leave the page
  • Send chat, delivery or calendar updates you asked for
  • Keep sending until you block it in site settings

It cannot

  • Show anything before you tap Allow
  • Keep showing alerts if you block the site or the browser auto removes it
  • Use a loud pop up if Chrome decides to show a quiet icon instead
  • Ask on iPhone unless the site is installed to the Home Screen

How it differs between platforms: Chrome and Firefox ask in the browser. On iPhone, the site must be installed to the Home Screen. Chrome may show a quiet chip for sites people rarely allow.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported202012-06-26Persistent notifications from 42
EdgeSupported142016-08-02None
FirefoxSupported222013-06-25None
SafariSupported72013-10-22Desktop Safari, page notifications from 7
Safari on iPhoneSupported16.42023-03-27Home Screen web apps only, requires iOS 16.4
Chrome on AndroidSupported422015-04-15Constructor throws on Android, use showNotification
Samsung InternetSupported4.02016-03-11None

How a site asks for it

APINotification.requestPermission(); new Notification(title, options); ServiceWorkerRegistration.showNotification(); notificationclick
Permission namenotifications
Browser compat keysapi.Notification
api.Notification.requestPermission
api.ServiceWorkerRegistration.showNotification
How access is grantedprompt
What the user seesChrome: bubble with Allow or Block, or a quiet address-bar chip (Notifications blocked) from Chrome 80 for sites people rarely allow. Firefox: Allow or Not now plus Always block, needs a gesture since 72. Safari: system sheet, needs a gesture.
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsPersistent per origin; Chrome auto-revokes unused or abusive sites and tells the person; Safari ties to the Notification Center
How to take it backPadlock, Site settings, OS notification settings, Safety Hub one-tap unsubscribe on Android; Permissions API 'change' event.
Inside an iframeCross-origin iframes cannot request it; the requesting document must be top-level or same-origin with a gesture

Typical flow

  1. Call Notification.requestPermission() from a click (required in Firefox and Safari)
  2. Browser shows prompt or quiet chip
  3. Permission becomes granted, denied or stays default
  4. Show with showNotification() or new Notification()

Data you get

What comes back: Notification display with title, body, icon, actions
Shape: object
How often: on demand, no rate limit besides OS

FieldTypeUnitRangePrecision
titlestringtextanyOS truncates about 50 to 100 characters
bodystringtextanyOS truncates about 100 to 400 characters
actionslistbuttonsup to Notification.maxActions (2 in Chrome desktop, 3 Android)per platform
icon, image, badgestringURLsimages fetched on showplatform scaled
requireInteractionbooleannonetrue or falsedesktop Chrome only
silentbooleannonetrue or falsesuppress sound
tag, renotifystring and booleannonereplace earlier notification with same tagone visible per tag

Technical limits

  • No notification display when the OS denies Do Not Disturb or the browser is closed (service worker needed for push)
  • Cannot read other apps' notifications
  • Cannot request without gesture on Firefox and Safari
  • iOS only for installed Home Screen web apps

The story

What it is

A site asks to show pop up alerts on your device, even when you are not on the page.

For you

A prompt asks if the site can send you notifications. If you allow, alerts appear on screen like app alerts. You can turn them off later in site settings.

For makers

Makers use alerts to bring people back for news, messages, deals and live events. They are one of the strongest tools for return visits. Abuse is common, so browsers now quiet the prompts.

Where you see it

TypeExampleApps
newsA news site asks to alert you about breaking stories, which can pull you back several times a day.BBC News
messagingA web chat shows a pop up when a friend replies while you are in another tab.WhatsApp Web, Slack
gamesA browser game says your build has finished or a friend joined your game lobby.None named
shoppingA store alerts you about a price drop on a saved item or a delivery update.Amazon
liveA sports site sends goal alerts during a live match.ESPN
productivityA calendar or task site alerts you before a meeting or due date.Google Calendar
adsSome sites use alerts as an ad channel, sending promotions for a fee from advertisers.None named
securityA bank sends a sign in alert when a new device logs in.None named

Risks

  • Spam alerts
  • Fake alert scams

What the platform says

Good uses and abuse

Legitimate uses

  • Chat and email alerts
  • Order and delivery updates
  • Calendar reminders

Known abuse

  • Scam and fake virus alerts
  • Spam re-engagement
  • Phishing impersonation of system dialogs

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility5 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2020-01, Firefox 72: Prompt requires a user gesture and shows quiet UI
  • 2020-02, Chrome 80: Quieter notification UI for low-allow sites and abusive prompts
  • 2022-09, Safari 16: Web Push and notifications on macOS 13 (Safari 16.1 in Ventura)
  • 2023-03, Safari on iPhone 16.4: Notifications for Home Screen web apps
  • 2025, Chrome: Auto-revocation of notification permission for unengaged and suspicious sites rolls out (exact version unconfirmed)
  • 2026, Chrome: Chrome describes FCM throttling of disruptive domains at 1,000 messages per minute (exact version unconfirmed)

Sources

How well checked: Based on official documentation.

On this page