The web apps a Mac never came with

Most of the software used on a Mac during a working day never shipped as a Mac app. Google Calendar, Gmail, a billing dashboard, an internal admin console: they live at web addresses, and they live in tabs. Turning those sites into web apps for Mac means giving each one its own window, its own Dock icon, and a place in Cmd+Tab, without changing the site itself. There are two built-in ways to do it, Safari's Add to Dock on macOS Sonoma 14 or later and Chrome's Install page as app, plus a set of third party tools that do the same job with different trade-offs. The right choice depends on three things: which browser the sites already run best in, whether any service needs two accounts at once, and whether extensions such as a password manager have to come along.

This site is published by the developer of a site to app tool, which is one of the options compared below.

What a web app on a Mac actually is

A web app made this way is the same web page in a different container. No new code is written, and the page gains no features it did not have in a tab. What changes is where it lives. It opens in its own window with a slim toolbar or none, it has an icon in the Dock and in Spotlight, and its notifications arrive under its own name.

That sounds small, and for a site opened twice a month it is. For a site opened twenty times a day it changes the shape of the work. The calendar stops being one tab among thirty. A support queue that raises notifications becomes something that can be found by Cmd+Tab in under a second. And a site that should never be closed by accident, such as a music player or a call, is no longer one Cmd+W away from disappearing.

The detail that separates the options is not the window. It is the session behind it. Some routes share cookies and sign in with a browser profile. Some keep a separate session for each app. That one difference decides whether two accounts on the same service can stay signed in side by side, and what happens to every app when a browser profile is reset.

Sites can also tell the browser how they want to look when installed, through a web app manifest that sets a name, icons, and a display mode. Sites without one still work. They simply get a generated icon and default behavior.

Safari: Add to Dock

Apple's guide to turning a website into an app in Safari describes the steps:

1. Open the site in Safari.
2. Click the Share button in the toolbar and choose Add to Dock, or choose File, then Add to Dock.
3. Click Add.

The icon appears in the Dock and in Spotlight. Apple notes that if the site was already signed in, the web app is signed in too in most cases. Apple's longer article on Safari web apps adds that the feature starts with macOS Sonoma 14, that the app is saved to the Applications folder inside the home folder, and that it shares no browsing history, cookies, website data, or settings with Safari.

Each web app has its own Settings, opened from the app's name in the menu bar. The options listed by Apple are Application Name, Application URL (including Set to Current Page), Icon, Show navigation controls, and Show color in title bar. A Privacy tab clears the site's data, and an Extensions tab turns Safari extensions on or off for that app. Notifications work as in any app, and the Dock icon can show a red badge with the number of unread notifications.

To remove one, open the Applications folder inside the home folder and drag the web app to the Trash.

The limits are clear from the same pages. Only Safari extensions apply, not Chrome Web Store ones. The feature does not exist before Sonoma. And the engine is always Safari's WebKit, which matters for the occasional site that behaves best in Chrome.

Chrome: Install page as app

Chrome Help gives the route: More at the top right, then Cast, save, and share, then Install page as app. Some sites also show an Install button at the right end of the address bar. Installed apps are managed at chrome://apps, and an app is removed from its own window through More, then Uninstall, with an option to also delete its data from Chrome.

Since Chrome 128, Create shortcut in the same menu makes a bookmark that opens in a tab. Anyone following an older guide that mentions an Open as window checkbox will not find it, because that behavior moved to Install page as app.

The result opens in its own window and can use the extensions of the Chrome profile it came from, which is the practical advantage over Safari. The catch is the same profile. The app shares cookies and sign in with it. Two installed apps for the same service in the same profile open with the same account. A second account means a second Chrome profile, kept straight by hand.

Third party tools that make web apps

Beyond the two browsers, several tools build Mac apps from websites. Three are representative, and their published terms differ a great deal. Where a vendor's page does not state a detail, the table below says so rather than guessing. All figures below were checked on the vendors' pages on October 18, 2026.

Fluid

Fluid is the long standing original of the category. Its page lists version 2.1, a 6.3 MB download, and a requirement of Mac OS 10.12 or later. Creating apps is free with no limit on the number. A $5 license adds pinning apps to the menu bar, userscripts and userstyles, and full screen mode. The page footer reads Copyright 2019.

WebCatalog

WebCatalog's pricing page lists a free Basic plan with 2 desktop apps, 2 profiles, and 1 space. Pro is $5 per month billed annually, plus local taxes, with unlimited desktop apps and profiles and a 7 day free trial. It runs on macOS, Windows, and Linux.

A site to app tool built on an installed browser

This approach uses a Chromium browser already on the Mac, such as Chrome, Brave, Edge, or Vivaldi, rather than bundling its own engine. One example creates up to 3 apps free with every feature, and offers unlimited apps for $24.99 as a one time purchase, as shown on its pricing section. It gives each app its own browser profile, lets Chrome Web Store extensions be switched on per app, and includes presets for common services so the URL, icon, and name are filled in. It requires macOS 12 or later.

Its guide documents a few settings that matter for everyday sites. Tab Bar is off by default, so the app shows only the page, and can be turned on for sites that need several tabs. Quit Confirmation adds a dialog to Cmd+Q for apps that should not close by accident. Window Handling has a Smart mode that lets sign in popups through while blocking others. A Space mode combines several services, such as mail, calendar, and chat, into one app with an icon sidebar for switching between them.

Option	Cost	Separate session per app	Chrome extensions	Engine
Safari Add to Dock	Free, macOS 14 or later	Yes	No, Safari extensions only	WebKit
Chrome Install page as app	Free	No, per Chrome profile	Yes, from the profile	Chrome
Fluid	Free, $5 license for extras	Not stated on its page	Not stated	Not stated
WebCatalog	Free for 2 apps, Pro $5 a month billed annually	Profiles, 2 on the free plan	Not listed on the pricing page	Not listed on the pricing page
Browser based site to app tool	Free for 3 apps, $24.99 one time	Yes, a profile per app	Yes, per app	Installed Chromium browser

Choosing which sites deserve a window

The common mistake is converting everything. Twenty site icons in the Dock recreate the problem of twenty tabs, one layer down.

Three traits make a good candidate. The site is opened on most working days. It is a place where work is done rather than read once. And it benefits from being reached instantly, either because it is checked constantly or because its notifications matter. Mail, calendar, chat, the main project tool, and the admin console that runs the business usually qualify.

Three traits make a poor one. The site is usually reached by following links, so links will keep opening it in the default browser and the app will sit unused. It is read occasionally, where a bookmark costs nothing and does the job. Or it constantly sends the reader to other sites, so every outbound link lands back in a browser.

For most people the useful number is between three and six. That is few enough to learn by icon and position, which is the point of having icons at all.

Two accounts on one service deserve a special mention, because they decide the tool. A personal and a work Gmail, or two client accounts on the same dashboard, need a separate session per app. Safari web apps, WebCatalog's profiles, and a profile per app tool handle this. Chrome's install needs a second profile.

What a web app changes, and what it does not

Being clear about the ceiling avoids a disappointment a week later.

Nothing gets faster. Every route renders the same page with a browser engine, so a site that is heavy in a tab is equally heavy in its own window. Offline support is whatever the site already offers, and for most business software that is very little. The site's own keyboard shortcuts stay the same, and printing works as it does in a browser.

What changes is location, attention, and sign in. The page has a fixed place in the Dock and in Cmd+Tab. It stops competing with every other tab. Its notifications carry its own name, and with a separate session it stays signed in regardless of what happens in the main browser.

Update behavior is the other quiet difference. Safari web apps update with macOS. Chrome installed apps update with Chrome. A tool that bundles its own engine updates on that vendor's schedule, while a tool that points to an installed browser picks up that browser's updates. For a signed in work account, an engine that keeps receiving security fixes matters more than any feature in the comparison table.

What to change first

Pick the one site opened most often and give it a window today with Safari's Add to Dock or Chrome's Install page as app, both free. Live with it for a week. If a second account, a Chrome extension, or a second and third site comes up, a profile per app tool such as Kagemusha is the next step to look at.