Display Modes
You'll learn how to control whether your Progressive Web App launches like a native app or stays browser-like.
What Are Display Modes?
When a user installs your PWA and launches it from their home screen, the display property in your Web App Manifest determines how much browser UI appears around your app. Think of it like choosing between a full-screen movie experience versus watching with all the streaming service controls visible—same content, very different feel.
The Four Display Modes
standalone
Your app launches in its own window without browser controls (no URL bar, back button, or tabs). It looks and feels like a native app. Most PWAs use this mode.
{
"display": "standalone"
}
fullscreen
Takes over the entire screen—no browser UI, no status bar, no navigation. Perfect for games or immersive experiences where you want zero distractions.
{
"display": "fullscreen"
}
minimal-ui
Similar to standalone but includes minimal browser controls—typically back/forward buttons and possibly a URL display. A middle ground between web and native feel.
{
"display": "minimal-ui"
}
browser
Opens in a regular browser tab. No special treatment—it's just a bookmark on steroids. Rarely used intentionally, but serves as a fallback.
{
"display": "browser"
}
Fallback Behavior
Browsers automatically fall back through the modes if one isn't supported: fullscreen → standalone → minimal-ui → browser. Always works, even on older browsers.
Key Takeaway: The display property in your manifest controls whether your PWA feels like a native app (standalone/fullscreen) or a traditional website (minimal-ui/browser), with automatic fallback ensuring compatibility.