Web App Notifications Not Working on iPhone? 8 Fixes
Share
If web app notifications are not working on your iPhone, start by checking whether the site was installed as a Home Screen web app and whether that web app actually requested notification permission. On iPhone, Web Push is not the same thing as keeping a normal Safari tab open. A website must support Web Push, the site must be added to the Home Screen as a web app, and the permission request must be completed before iOS can deliver its notifications.
| Symptom | Most likely layer | First check |
|---|---|---|
| The site never appears in Settings > Notifications | Web app setup or permission request | Confirm it was added to the Home Screen with Open as Web App, then trigger the site's notification opt-in again. |
| The web app appears in Notifications but alerts never show | iOS notification settings, Focus, or the site's push subscription | Check Allow Notifications, then test with Focus off and Scheduled Summary reviewed. |
| Notifications arrive late | Focus or Scheduled Summary | Check whether the web app is being silenced or summarized. |
| One web app fails but another works | Likely site-specific push subscription or service issue | Refresh that site's notification subscription and account state. |
| No Home Screen web app can receive notifications | iPhone-wide settings or software issue | Verify permissions, restart the iPhone, and install the latest iOS update available to the device. |
What Web Push on iPhone actually requires
Apple's WebKit team introduced Web Push for Home Screen web apps in iOS and iPadOS 16.4. The feature uses standards-based Web Push, including the Push API, Notifications API, and Service Workers. A web app can request permission only after a direct user interaction, such as tapping a Subscribe button. Once permission is granted, iOS manages that web app in notification settings like an installed app. See WebKit's Web Push documentation.
That leads to an important diagnostic rule: a normal bookmark, an open Safari tab, and a Home Screen web app are not interchangeable for this feature. If a site has never completed the Home Screen web-app and notification-permission flow, changing unrelated iPhone settings will not create a push subscription.
1. Confirm the site is installed as a Home Screen web app
Apple's current iPhone User Guide shows this flow: open the website in Safari, open the sharing controls, choose Add to Home Screen, turn on Open as Web App, then tap Add. Apple notes that the resulting icon opens the site like an app and can receive notifications when the site supports them. See Apple's guide to opening a website as a web app on iPhone.
If you are troubleshooting an older Home Screen icon and you are not sure how it was created, remove only that Home Screen web-app icon if you are comfortable recreating it, then add the site again using Apple's current flow. Do not erase website data or reset the entire iPhone just to test this.
2. Trigger the site's notification permission inside the web app
Open the Home Screen web app and look for the site's own control for notifications. The wording is site-specific: it might say Subscribe, Enable notifications, Turn on alerts, or something similar. There is no universal iPhone menu that can force a website to create a push subscription if the website never requests one.
WebKit states that a Home Screen web app must request push permission in response to a direct user interaction. If you never saw an iOS notification-permission prompt, return to the web app and use the site's notification control again. If the site provides no notification control at all, confirm from the site's own help documentation that it actually supports Web Push on iPhone.
Diagnostic inference: if the web app does not appear under Settings > Notifications after you have used a genuine notification opt-in inside the web app, the permission request likely did not complete or was not granted. That is more useful to investigate than toggling unrelated battery settings.
3. Check the web app in Settings > Notifications
After the web app has requested and received notification permission, open Settings > Notifications and select the web app. Make sure Allow Notifications is enabled, then review the available alert presentation options you want to use.
Apple's current notification settings guide explains that notification behavior is managed from Settings > Notifications. If the web app is listed there but alerts are disabled, the website can have a valid push subscription while iOS still does not present the notifications the way you expect.
4. Test without an active Focus
Web Push notifications integrate with Focus just like other app notifications. For a controlled test, temporarily turn off the currently active Focus and trigger a fresh notification from the web app. If the alert appears with Focus off, review that Focus's People and Apps rules instead of repeatedly reinstalling the web app.
Do not leave Focus disabled permanently just to solve this. The goal is to isolate whether Focus is the delivery/presentation layer causing the symptom.
5. Check Scheduled Summary if notifications arrive late
If the problem is delayed delivery rather than complete failure, open Settings > Notifications > Scheduled Summary. Apple allows selected apps to be included in a notification summary delivered at scheduled times. If the web app is included, its alerts can appear later than you expect.
Remove the web app from the summary for a test if immediate delivery matters. This is especially useful when notifications eventually arrive in batches, which points to presentation timing rather than a broken Web Push subscription.
6. Refresh the website's own push subscription
If iOS permissions look correct, return to the web app and review the site's own notification settings. If the site offers a supported way to turn notifications off and back on, use that control to refresh the subscription. Also confirm you are signed into the correct site account if notifications are account-specific.
This step is intentionally site-specific. Apple provides the operating-system permission layer, but each website implements its own subscription logic and decides which events generate push messages. Avoid following instructions that invent a universal Safari setting that does not exist.
7. Restart the iPhone and install available iOS updates
If the web app is installed correctly and the permission path looks right, restart the iPhone and test again. CASEBX has a step-by-step guide for restarting or force restarting an iPhone.
Then check for the latest iOS version available to your device. Use CASEBX's iPhone software update guide if you need the exact update workflow. Web Push for Home Screen web apps has existed since iOS 16.4, so Apple Intelligence is not a requirement for this feature.
8. Isolate a site-side problem from an iPhone-wide problem
Test another reputable web app that you know supports Web Push, if you already use one. If other Home Screen web apps can notify normally but one site cannot, that pattern points more strongly to the failing site's subscription, account, service worker, or server-side push implementation. That conclusion is a diagnostic inference, not an Apple guarantee.
If every compatible Home Screen web app fails after permissions, Focus, Scheduled Summary, restart, and iOS updates have been checked, the problem is more likely to be on the iPhone side. At that point, Apple Support is a more appropriate escalation than repeatedly deleting accounts or resetting unrelated settings.
What not to reset first
Do not start with Reset Network Settings, signing out of your Apple Account, or erasing the iPhone. Those are high-disruption actions and are not part of Apple's documented prerequisites for Home Screen Web Push.
Also avoid treating Low Power Mode or Background App Refresh as required Web Push switches. Apple and WebKit do not document either setting as a prerequisite for Web Push delivery to Home Screen web apps. Troubleshooting should stay focused on the actual chain: web-app installation, site permission request, iOS notification permission, Focus or summary behavior, and the site's push subscription.
Frequently asked questions
Can a regular Safari website send Web Push notifications on iPhone?
For the iPhone Web Push flow documented by WebKit, the website is used as a Home Screen web app. Install the site to the Home Screen as a web app, then use the site's own notification opt-in when it supports Web Push.
Does Web Push require Apple Intelligence?
No. Web Push for Home Screen web apps arrived with iOS and iPadOS 16.4. Apple Intelligence is not a requirement for this feature.
Why is my web app missing from Settings > Notifications?
If you already created a real Home Screen web app, the most likely next question is whether the site successfully requested notification permission and whether you granted it. A site cannot create that permission silently; WebKit requires the request to follow direct user interaction.
Why do web app notifications arrive late?
Check Focus and Scheduled Summary first. Either can change when or how a notification is presented even when the website's push subscription itself is working.
Why does only one web app have notification problems?
If other push-capable Home Screen web apps work on the same iPhone, a problem limited to one site is more consistent with that site's subscription, account, or Web Push implementation. Use the site's own notification controls or support resources before changing system-wide settings.
Bottom line
When iPhone web app notifications stop working, troubleshoot the chain in order. Confirm a real Home Screen web app, trigger the site's notification permission through a direct interaction, verify iOS notification settings, rule out Focus and Scheduled Summary, refresh the site's own subscription, then restart and update iOS. This approach separates a permission or presentation issue from a site-side Web Push failure without resorting to destructive resets.