Do Progressive Web Apps Work on iOS? The Complete Guide for 2026

When Apple first told developers how to build apps for the iPhone, in June 2007, its answer was the web. Apple’s press release promised web apps that would “look and behave just like the applications built into iPhone.”

The App Store opened a year later, and native apps took over. Web apps never went away, though, and Apple has been adding app features to them slowly ever since, from Home Screen icons to push notifications.

But progressive web apps still don’t get the full app treatment on iPhone. Some features work as well as they do on Android, some only switch on after people add your site to their Home Screen and some aren’t available at all.

This guide covers what PWAs can and can’t do on iPhone and iPad in 2026, how installation, push and storage work, what’s different in the EU and when a native app is the better choice.

Do PWAs Work on iPhone?

Progressive web apps work on iPhone and iPad. People can add a PWA to their Home Screen, open it full screen without Safari’s toolbars, get push notifications from it and use it offline.

The catch is that most of those features only switch on once someone has added the site to their Home Screen. Apple also decides which web features iPhone supports, because every browser on iOS runs on its WebKit engine.

The result is a PWA that works, but reaches fewer people and does less than it would on Android, or than a native app does on iPhone.

How PWA Support on iPhone Has Grown

Apple has added support for web apps in steps, usually a few features at a time in a Safari update.

Each release added something, but the biggest gaps haven’t moved. Safari still can’t prompt people to install a PWA, and a PWA still can’t run in the background or appear in the App Store.

What Works and What Doesn’t: PWAs on iPhone vs Android

A PWA on iPhone supports the core features, like a Home Screen icon, push notifications and offline pages. It misses the install prompt, background work and hardware access that Chrome gives it on Android.

Two of these gaps matter most to a business: the missing install prompt and push that only works after an install. Both come down to the Home Screen.

How Do You Install a PWA on iPhone?

To install a PWA on iPhone, people add the site to their Home Screen from Safari’s Share menu. In iOS 27, the steps in Apple’s iPhone User Guide are:

1. Open the site in Safari.
2. Tap the Page Menu button, then tap Share. With the Bottom or Top tab layout, tap the Share button instead.
3. Scroll down the list and tap Add to Home Screen.
4. Leave Open as Web App turned on, then tap Add.

The icon then sits on the Home Screen like any app. Opened from there, the site fills the screen without Safari’s address bar, and it can ask to send notifications.

Since iOS 26, Open as Web App is on by default for every site, according to WebKit. Before that, a site only opened this way if its code asked for it, through a web app manifest or a meta tag.

Installing From Chrome and Other Browsers

Other iPhone browsers can install PWAs too, on iOS 16.4 and later. Apple opened Add to Home Screen to browsers other than Safari in that release, and Chrome added the option in July 2023.

Whichever browser adds it, the web app runs on Apple’s WebKit engine. A PWA added from Chrome can do the same things as one added from Safari, and no more.

Why Is There No Install Prompt on iPhone?

iPhone has no install prompt for PWAs because Safari doesn’t support the beforeinstallprompt event. On Android, that’s the event that lets a site show its own Install button.

So on iPhone, every install depends on people knowing the Share menu steps. The most a site can do is show a short banner explaining them and hope visitors follow along.

This is the biggest practical difference between a PWA and an app on iPhone. An app has a Get button in the App Store, while a PWA has a set of instructions.

Can PWAs Send Push Notifications on iPhone?

PWAs can send push notifications on iPhone and iPad running iOS 16.4 or later, but only once someone has added the site to their Home Screen. Push is a feature of Home Screen web apps, according to WebKit, not of sites open in Safari.

There’s a second step, too. The web app has to ask for permission in response to a tap, such as on a button to turn on alerts, and the person has to say yes.

Once they do, notifications behave much like an app’s. They appear on the Lock Screen, in Notification Center and on a paired Apple Watch, they follow Focus modes and people can manage them for each web app in Settings.

Web push on iPhone runs through Apple Push Notification service, the same system apps use, and you don’t need an Apple Developer account to send it.

What Is Declarative Web Push?

Declarative Web Push is a simpler form of web push that Apple added in iOS and iPadOS 18.4, in March 2025. The message carries the notification’s content in a standard format, so it can appear without a service worker running.

Apple built it for reliability. In WebKit’s announcement, Brady Eidson explains that classic web push can fail because of service worker bugs or device conditions, and that tracking prevention can delete the service worker registrations push depends on.

It’s backward compatible, so browsers that only support classic web push can still show the same message through a service worker. For a business, it means more reliable delivery to people who’ve installed your PWA, not a bigger audience.

What PWA Notifications Can’t Do on iPhone

PWA notifications on iPhone are plainer than an app’s. Safari doesn’t support images or action buttons in web notifications, while Chrome on Android does.

Silent push isn’t possible either. WebKit says a web push always shows a visible notification, so a PWA can’t use push to refresh its content in the background, as apps do.

App icon badges do work. Since iOS 16.4, a Home Screen web app can set a count on its icon, which appears once the person has allowed notifications.

Native push gets more again. Apps can send Time Sensitive notifications, which Apple says break through system notification controls, and start Live Activities that keep live updates like an order’s status on the Lock Screen.

How Much Data Can a PWA Store on iPhone?

A PWA on iPhone can store a lot: up to 60% of the device’s disk space for one site, and up to 80% across all sites, under the storage policy WebKit introduced in 2023. A Home Screen web app gets the same quota as Safari.

That’s plenty to cache your key pages, images and data with a service worker, so people can keep browsing when their connection drops. Anything live, like checkout, stock levels or search, still needs a connection.

The risk is data being cleared. When a device runs short of space, or sites together go over the overall quota, WebKit deletes stored data from the least recently used sites first.

Sites people visit in Safari, rather than from the Home Screen, face a second rule. Safari deletes a site’s stored data, service worker caches included, after seven days of Safari use without a visit, according to WebKit.

Home Screen web apps are treated better on both counts. They keep their own count of days of use, so their data isn’t expected to be deleted under the seven-day rule, and WebKit is more likely to grant them persistent storage, which can protect their data from automatic deletion.

For a store, that means anything your site saves in the browser, like a guest shopper’s cart, can disappear if they shop in Safari and don’t come back for a while. Compared with Safari, a Home Screen web app is far more likely to keep it.

What Can’t PWAs Do on iPhone?

A PWA on iPhone can only do what WebKit supports, and several features people expect from apps are missing:

• No App Store listing. People can’t find or download your PWA in the App Store (more on this below).
• No install prompt. People have to find Add to Home Screen in the Share menu themselves.
• No background work. Safari doesn’t support Background Sync, Periodic Background Sync or Background Fetch, so a PWA can’t refresh content or retry uploads while it’s closed.
• No Bluetooth, NFC or USB. Safari doesn’t support Web Bluetooth, Web NFC or WebUSB, which rules out connected devices and NFC tags.
• No vibration. Safari doesn’t support the Vibration API, which Chrome on Android does.
• No widgets or Live Activities. These come from Apple’s native frameworks, WidgetKit and ActivityKit, which web apps can’t use.
• No rich or silent push. Notifications are text and badges only, and every push has to show a visible notification.

Most of the rest of the web platform works. Safari supports the camera and microphone, location while the app is open, the share sheet, passkey sign-in and the Payment Request API, so a PWA on iPhone can use them too.

Can You Put a PWA in the App Store?

You can’t put a PWA in Apple’s App Store. Apple doesn’t list web apps, and Guideline 4.2 of its App Review Guidelines turns down apps that don’t go beyond “a repackaged website.”

Google Play is different. It accepts PWAs packaged as a Trusted Web Activity, so on Android a PWA can sit in the store next to native apps.

That gap matters more than it sounds. The App Store is where iPhone users look for apps, and a listing there comes with ratings, reviews and a one-tap download.

Getting into the App Store means building a real iOS app with native features of its own, one that meets Guideline 4.2.

Why Every iPhone Browser Runs on WebKit

Apple decides what PWAs can do on iPhone because every iPhone browser is built on its WebKit engine. App Store Guideline 2.5.6 requires apps that browse the web to use WebKit, apart from the exceptions in the EU and Japan below.

That’s why Chrome, Firefox and Edge on iPhone can’t give a PWA anything Safari doesn’t. Every gap in this guide is Apple’s to close, on Apple’s schedule.

What’s Different in the EU and Japan?

In the EU and Japan, browser makers can apply to use their own engines on iPhone, but PWAs work the same way they do everywhere else.

Since iOS 17.4 in March 2024, the EU’s Digital Markets Act has let browsers use engines other than WebKit for EU users. Apple’s rules require a separate app distributed only in the EU, an entitlement from Apple and a list of security and privacy commitments.

Japan followed with iOS 26.2 in December 2025, under its Mobile Software Competition Act, with similar conditions for apps distributed only in Japan.

Home Screen web apps haven’t changed with them. Apple planned to remove them for EU users in early 2024, then reversed course and said they would “continue to be built directly on WebKit and its security architecture,” as 9to5Mac reported on March 1, 2024.

In the UK, the Competition and Markets Authority gave Apple strategic market status in October 2025, covering browsers and browser engines. Its follow-up work through October 2026 has focused on app review, steering and NFC access, not browser engines.

For your business, the answer is the same in every market. A PWA on iPhone can do what WebKit allows, and Apple sets the pace.

Should You Build a PWA or a Native App for iPhone?

A PWA and a native app don’t compete on iPhone, because they reach different people. A PWA improves your site for every visitor, while a native app gives your regular customers a home on their phone.

You can see the split at companies that have both. Spotify’s mobile web player has a web app manifest that opens it full screen, but the same file tells browsers that Spotify would rather people install its native apps.

Its iPhone app has a 4.8 rating from more than 42 million ratings on the US App Store (October 2026). For Spotify, the web app is the fallback, and the native app is the one it wants people to use.

When Is a PWA Enough on iPhone?

A PWA on its own is enough when your iPhone visitors don’t need to hear from you between visits. It’s a strong fit when:

• Most of your mobile visitors are new or occasional, and arrive from search, ads or social media.
• Most of your audience is on Android, where PWAs get far more support.
• You run a content site or a web tool, where offline reading or a Home Screen shortcut is the main win.
• You want to improve your mobile site before you decide whether an app is worth it.

A PWA is ideal for making the mobile web faster and more reliable for everyone, and it’s worth building for most sites either way.

When Do You Need a Native iPhone App?

A native iPhone app is the better choice when your business depends on customers coming back. That’s the case when:

• Your best customers shop on iPhone and buy again and again.
• Push notifications drive revenue, from abandoned carts to restocks and new drops.
• People expect to find you in the App Store.
• You need Bluetooth, NFC, widgets, Live Activities or updates in the background.

For an online store with loyal iPhone shoppers, PWA push only reaches the ones who find the Share menu and install. A native app can ask everyone who downloads it.

A Native iPhone App Without the Cost of Building One

The biggest downside of a native app is the cost. A custom iPhone and Android app means months of development, then a second product to run alongside your website, with every promotion and new feature built twice.

MobiLoud transforms your website into a custom native app, powered by the same underlying code as your website. We build the app from your existing site, building a custom native experience around it for the phone.

Your app launches with everything you’ve already built, from your products and content to search, loyalty and subscriptions. Then it goes where a PWA can’t on iPhone:

• A listing in the App Store and Google Play, with a one-tap download
• Push notifications for everyone who downloads the app and allows them, with no Add to Home Screen step
• Native navigation, with a fully custom design for the phone
• App-only pages your team builds in your own platform, plus native features and SDKs where you need them

Because the app feeds from the same codebase as your site, it stays consistent with your site as you change it. Our team builds, launches and looks after your app, so there’s nothing for your team to maintain.

"MobiLoud enabled us to relaunch buybuy BABY's native mobile app in record time, slashing development costs by over 90%."

We’ve helped brands like John Varvatos, Jack & Jones and Tadashi Shoji launch their apps this way, and launch typically takes 2 to 4 weeks. If you already have a PWA, it can power your iOS and Android apps too.

It’s best suited to brands with a website or PWA their customers already use, and regulars they want to bring back more often.

Are PWAs Worth It on iPhone? (Final Thoughts)

PWAs work on iPhone, and for most sites they’re worth building. A PWA makes your site faster, keeps it working on a bad connection and gives your keenest visitors an icon on their Home Screen.

What a PWA can’t do on iPhone is reach people who haven’t installed it, and Apple gives them no prompt to install. It can’t appear in the App Store, it can’t send push until someone finds the Share menu and it can’t do anything in the background.

Apple has closed some of these gaps, but at its own pace, and Safari 27 added nothing new for Home Screen web apps. Plan around the iPhone your customers have today, not the one a future release might bring.

For most businesses, that means both: a fast PWA for everyone who finds you on the web, and a native app for the iPhone customers who come back again and again.