What Does a Web Application Manifest Actually Do on Safari?

With the release of Safari 16, Apple continues to refine the web app experience on iPhones and iPads, signaling a significant shift in how Home Screen websites operate on their devices. If you’re a web developer or product manager, you’ve probably encountered discussions about the web application manifest and its role in creating "app-like" experiences. But with Safari 16 making notable changes, you might wonder: what does a web application manifest actually do on Safari? And do you still need one to deliver a great Home Screen experience?

In this post, I’ll dissect the role of manifests in Safari 16—Apple’s latest update to its mobile browser engine, WebKit—explain how the new Home Screen launch behavior changes some assumptions, and clarify why manifests and other technologies like service workers still matter. Along the way, I’ll mention a few details about icons and display mode, how web app metadata is used, and why this matters for browser-first services outside of the App Store ecosystem.
Apple’s Safari 16 and the Evolution of Home Screen Web Apps
Traditionally, Safari’s handling of websites saved to the Home Screen on iPhone and iPad had subtle but important differences compared to dedicated native apps or progressive web apps (PWAs) on other platforms. One of the frequent challenges was that https://robservatory.com/author/when-a-website-is-enough/ https://robservatory.com/author/when-a-website-is-enough/ when users tapped a Home Screen icon, the website would often launch inside a simplified container with some Safari UI visible, rather than as a fully standalone app window.

Safari 16 changes the game by making Home Screen websites open as web apps by default. This means when you add a website to your Home Screen on iOS or iPadOS, it now launches without Safari’s browser chrome (the URL bar, navigation buttons, etc.), creating an experience that feels much more like a native application. Crucially, there are no special installability requirements to unlock this app-like launch behavior on Safari 16. You don’t absolutely need a manifest, service worker, or any specific criteria like those found in Google’s installability checks for Chrome.

This is great news for users and developers alike. It makes it easier to build browser-first services on Apple devices that feel app-like and are discoverable outside of the traditional App Store.
So What Exactly Does a Web Application Manifest Do in Safari 16?
While the Home Screen launch behavior is undeniably improved, the web application manifest is still an essential piece for defining how your web app should look and behave when installed. But its role is more about metadata and rich presentation than unlocking basic launch-as-app capabilities.
Manifest’s Core Functions on Safari Icons and display mode: The manifest defines which icons appear on the Home Screen, their sizes, and appropriate resolutions. It also specifies the display mode—whether the app should open in standalone, fullscreen, or minimal-ui. Safari uses this information to control the user interface’s look and feel. Web app metadata: Metadata such as the app's name, short name, theme color, and orientation preferences influence how the app is shown in the Home Screen and system UI.' Launch URLs: You can set the start URL to determine where the app opens initially.
Put simply, Safari 16’s new Home Screen app behavior means that even if you don’t include a manifest, your site will still open without a browser chrome by default. However, the manifest ensures that the experience looks polished and personalized—your chosen icons appear crisp, your defined display mode is respected, and startup/loading feels cohesive.
Why You Still Need Manifests and Service Workers Together for True PWA Experiences
Launching as a web app from the Home Screen is just one piece of the puzzle. For richer, more resilient web apps that work offline, send push notifications, or perform background sync, you still rely heavily on service workers alongside manifests. Here’s why:
Offline capabilities: Service workers cache important content and assets, allowing users to open your app even when they’re offline or have a flaky connection. The manifest doesn’t provide this. Performance improvements: Pre-caching resources can make your app load faster than a regular website returning every asset from the network. Advanced features: Things like background sync, push notifications, and periodic updates rely on service workers and other APIs that manifests alone cannot enable.
Together, manifests provide the baseline metadata that enables proper app appearance and launch, while service workers handle many of the offline and performance advantages associated with progressive web apps.
Breaking Down the Safari 16 Behavior: What Your Manifest Should Look Like
If you’re testing your website as a Home Screen app on Safari 16, a good practice is to maintain a complete manifest to control key aspects:
Manifest Property Purpose Safari Usage name and short_name Defines full name and abbreviated app name Used on the Home Screen icon label and splash screen titles icons Specifies app icons in multiple sizes Safari picks the best icon for the device pixel density start_url URL the app opens to when launched from Home Screen Used to restore app entry point accurately display Controls UI modes: standalone, fullscreen, minimal-ui Affects window controls shown during app runtime theme_color and background_color Colors for UI elements and splash screens Used for better visual integration with system UI orientation Preferred app orientation Safari honors this for smoother UX
While Safari 16 always opens Home Screen apps without browser chrome, the manifest's details ensure the app feels consistent and intentional across devices and launch contexts.
What About the Manifest's Absence? Does Safari 16 Fall Back Gracefully?
Yes and no. If your website lacks a manifest, Safari 16 will still open it from the Home Screen as a standalone web app, following its new behavior. But there are UX drawbacks:
No custom icons: Safari will try to generate a generic icon based on the site’s favicon or screenshot, often resulting in blurry or unpolished appearance on high-DPI displays. This diminishes the impact of your “app” on the user’s Home Screen. Default display mode: Your app opens in the default standalone mode but can’t be customized (e.g., you can't specify fullscreen mode if desired). Missing metadata: Without a manifest, you lose the ability to customize splash screens and lock screen appearance, impairing first impressions during app launch.
It’s a valid choice to forego a manifest if you only care about the most minimal "app-like" launch behavior. But in practice, you’ll want to add a manifest to provide a polished, branded experience—which users immediately recognize as an "app" rather than a generic website shortcut.
WebKit and the Broader Apple Platform Context
Apple’s WebKit engine underpins Safari on all Apple platforms, including iOS and iPadOS. WebKit teams have been steadily enhancing PWA capabilities, cautiously balancing security, privacy, and user experience priorities.

Safari’s updated Home Screen behavior in version 16 reflects this ongoing evolution. It loosens some installation requirements commonly found on other browsers but still respects the manifest as a way to optimize the presentation and control app metadata.

This means browser-first services—products designed first and foremost for the web—can now achieve a level of app-like feel on Apple devices without having to go through the App Store install process. From a developer perspective, that's a substantial shift and an encouragement to embrace the open web as a platform on Apple’s famously curated ecosystem.
Summary: The Web Application Manifest on Safari 16 and Beyond
Here’s a quick recap of the main points:
Safari 16 makes Home Screen websites open as standalone web apps by default, no manifest required. This removes previous barriers that required specific installability criteria. The manifest still matters for defining icons, display mode, app names, colors, orientation, and launch URLs to create a better polished experience. Service workers complement the manifest by enabling offline support, caching, and background features, providing richer web app capabilities. Browser-first services can deliver app-like experiences on Apple devices without any native App Store install, expanding opportunities for progressive web apps. Apple’s WebKit team is gradually improving PWA support while balancing platform security and user expectations.
If you maintain a web application manifest for your app, make sure it is complete and accurately reflects your desired branding and behaviors on Apple’s platforms. Meanwhile, test your site thoroughly by adding it to the Home Screen on multiple devices to verify your icons look crisp and your display modes behave as expected.
Final Thoughts: Why This Matters for Web Developers
Having spent over a decade working with mobile web and product teams, particularly focusing on iOS and its quirky Safari behaviors, I continue to be fascinated by how Apple shapes the web app developer experience. The simplification brought by Safari 16 removing strict install requirements for Home Screen launch behavior is a welcome practical improvement.

But don't get confused or complacent. The manifest remains a powerful tool for web developers to precisely control icons and display mode, inject rich web app metadata, and elevate the user experience. This is not a fickle feature; it is the foundation for taking your presence on Apple devices beyond a simple bookmark and truly into the app realm.

Apple’s continuing investment via WebKit suggests we will see expanding PWA support in coming versions—stay tuned, keep your manifest well curated, test on real devices, and consider service workers primary collaborators in this evolving platform story.

If you want a quick checklist, here it is:
Always include a proper manifest.webmanifest linked in your HTML. Ensure your icons cover multiple resolutions including 512x512. Specify a suitable display mode like standalone. Use meaningful name and short_name entries. Complement your manifest with a service worker to unlock offline capabilities. Test launching your app from the Home Screen on iPhone and iPad with Safari 16+.
By embracing these steps, you're on your way to delivering smoother, faster, and more polished browser-first experiences that run beautifully on Apple devices without the hassle of native app installs.