Platform in Installation
Desktop installation
Published Updated
Desktop installation turns a site into an OS-level app with its own window, launcher entry, and taskbar or Dock presence. Chrome 73 and Edge 79 install from the address bar, the browser menu, or beforeinstallprompt on Windows, macOS, Linux, and ChromeOS; Safari 17 on macOS 14 installs through File › “Add to Dock”; Firefox 143 on Windows pins a site as a taskbar web app, except in the Microsoft Store build (Firefox 143 release notes); earlier desktop Firefox has no built-in install (MDN points to an extension), Safari before 17 has none on the Mac, and no browser other than Chromium fires beforeinstallprompt (BCD api.BeforeInstallPromptEvent).
How it works
Section titled “How it works”Start an installation from the browser’s own surface (Chrome and Edge show an install icon at the right end of the address bar once the installability criteria are met, plus an install entry in the three-dot menu; Safari uses File › “Add to Dock”; Firefox 143 pins the site to the taskbar) or, on Chromium only, from the page’s own button backed by a stored BeforeInstallPromptEvent. The mini-infobar is a mobile feature (web.dev’s sample code comments it as “Prevent the mini-infobar from appearing on mobile”), so on desktop a page has no ambient banner to suppress.
On accept, the browser writes an OS launcher entry so the app can start without the browser being open first:
| OS | What the browser creates | Management surface |
|---|---|---|
| Windows (Chrome, Edge) | Start-menu shortcut; the app appears in the taskbar and Alt+Tab. Edge also registers it under Settings › Apps › “Installed apps”. | chrome://apps, edge://apps |
| macOS (Chrome, Edge) | An app bundle in a browser-specific folder under ~/Applications/ (Chrome Apps.localized/ for Chrome), with its icon in the Dock. |
chrome://apps, edge://apps |
| macOS (Safari 17+) | An app that opens from the Dock, Launchpad, and Spotlight in its own window; Safari copies the site’s cookies at install and shares no other website data afterwards. | Delete the app from Applications |
| Linux (Chrome, Edge) | A .desktop entry installed in user mode, by default under ~/.local/share/applications/, picked up by GNOME and KDE launchers. |
chrome://apps, edge://apps |
| ChromeOS | A launcher entry that can be pinned to the shelf; Play Store listings via TWA are separate. | Launcher › right-click › Uninstall |
Chrome and Edge take the window mode from the manifest, and Safari on the Mac opens any added site as a web app whether or not it has one. display: standalone yields a window with the OS title bar and no browser chrome; minimal-ui adds back, forward, and reload; display_override: ["window-controls-overlay"] lets the page draw into the title-bar area while the OS keeps the close, minimise, and maximise buttons, exposing the remaining area through env(titlebar-area-x), env(titlebar-area-y), env(titlebar-area-width), and env(titlebar-area-height) (Chrome 105, Edge 105, desktop only). The app name and icon come from name and icons; a new window per launch versus focusing the existing one is decided by launch_handler.client_mode.
Compared with a browser tab, the app loses the address bar and tab strip (Edge and Firefox 143 keep installed extensions and add-ons available inside the app window), and gains a separate window in Alt+Tab or Cmd+Tab, OS notifications attributed to the app’s name and icon, badging, file and protocol handling, and launch from the OS. Cookies and storage are shared with the installing browser profile on Chrome and Edge, so sign-in carries over; on Safari 17 only the cookies are copied at install, so a sign-in held in cookies carries over and anything kept in local storage does not.
Observed behaviour
Section titled “Observed behaviour”The installed artefact is visible on disk, which makes it easy to confirm what a given browser did.
A page can tell that it is running installed, and which window mode it got, without any browser-specific API. The media query reports the mode the browser applied, which may differ from the one requested when display_override lists several.
const mode = ['window-controls-overlay', 'standalone', 'minimal-ui', 'fullscreen'] .find((m) => matchMedia(`(display-mode: ${m})`).matches) ?? 'browser';
if (mode !== 'browser') { installButton.hidden = true; // already installed and launched as an app}if (mode === 'window-controls-overlay') { document.documentElement.classList.add('wco'); // draw into the title-bar area}See also
Section titled “See also”- Installing and uninstalling web apps (developer.mozilla.org)
- Progressive Web Apps on Windows: the user experience (learn.microsoft.com)
- Firefox 143.0 release notes (mozilla.org)
- beforeinstallprompt event
- Installability criteria
- Uninstalling an installed PWA
display_overridemanifest member- PWAs on macOS Safari
Specifications
| Specification | Status |
|---|---|
| None. | |