Skip to Content
Platform.Ontology

Push, periodic sync and background fetch

Ways a site can wake its service worker after the person leaves: push messages, timed sync, long downloads.

Works without askingNotifications and backgroundAfter leavingWeb browsersAfter you leave the site

In one line

Can wake a site's background script after you leave, through push, timed sync or downloads

Ways a site can wake its service worker after the person leaves: push messages, timed sync, long downloads.

Push needs a notification permission; Periodic Background Sync needs an installed PWA and site engagement, with a minimum of about 12 hours between wakes; Background Fetch shows a download notice. Each lets a site run code with no tab open.

What it can and can't do

What the user does: You allow notifications, install a web app, or start a big download

It can

  • Wake the site through a push message once you allow notifications
  • Refresh an installed web app about once every 12 hours or more
  • Run a large download that shows a progress notice
  • Run site code with no tab open for a short time

It cannot

  • Use push without your notification permission
  • Use timed sync unless the site is installed and you use it often
  • Run in the background without limits, since browsers stop it after a short time
  • Work the same in Safari and Firefox, which support less

How it differs between platforms: Chrome and Edge support all three. Firefox and Safari, including iPhone browsers, support only some.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported422015-04-14Push 50, periodic sync 80 for installed PWAs
EdgeSupported172018-04-30None
FirefoxPartial442016-01-26Push only
SafariPartial162022-09-12Push in macOS Safari 16
Safari on iPhonePartial16.42023-03-27Push only for Home Screen web apps
Chrome on AndroidSupported422015-04-15None
Samsung InternetSupported4.02016-03-11None

How a site asks for it

APIPushManager.subscribe(), registration.periodicSync.register(), registration.backgroundFetch.fetch()
Permission namepush
Browser compat keysapi.PushManager
api.PeriodicSyncManager
api.BackgroundFetchManager
How access is grantedprompt
What the user seesNone
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsSubscriptions last until the person unsubscribes, clears data, or the push service expires them
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Push or sync events
Shape: event
How often: at wake

FieldTypeUnitRangePrecision
min_intervalintegerhoursabout 12 for periodic syncapproximate

Technical limits

  • Push requires notification permission
  • Periodic sync minimum about 12 hours and only for installed PWAs (Chrome)
  • Silent push is not allowed: Chrome and Safari require a user visible notification
  • Safari push only for Home Screen web apps on iOS

The story

What it is

Several ways a site can wake its background script after you leave: push messages, timed syncs, long downloads.

For you

After you leave the page, the site may still run small bits of code when it gets a push, a timed sync or a download event. You mostly see a notification or fresher content on return.

For makers

Makers use these to stay in touch, keep apps fresh and finish work after the tab closes. They are also a way for a site to run code you did not open. Browsers limit it by permission and by how often you use the site.

Where you see it

TypeExampleApps
messagingA web chat wakes on push and shows a new message, so you do not have to open the page.Slack
newsA news app wakes on a timer to load the latest stories before you open it.None named
videoA streaming web app finishes a movie download after you close the tab.None named
gamesA browser game wakes on push to tell you a match is ready.None named
adsAn ad network wakes a site's background script to show a promo notice.None named
analyticsA site wakes in the background to send queued usage data it could not send before.None named
securityA bank wakes on push to show a login approval prompt.None named

Risks

  • Runs after you leave
  • Spam and tracking use

What the platform says

Good uses and abuse

Legitimate uses

  • Order updates, offline sync

Known abuse

  • Re-engagement spam, hidden background work

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility4 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

  • 2016-04, Chrome 50: Web Push shipped
  • 2019-02, Chrome 74: Background Fetch shipped
  • 2020-02, Chrome 80: Periodic Background Sync for installed PWAs
  • 2023-03, Safari 16.4: Web Push for Home Screen web apps and macOS Safari

Sources

How well checked: Based on official documentation.

On this page