How to turn a website into an app on a Mac

The quickest way to turn a website into an app on a Mac is built into Safari: open the site, choose File, then Add to Dock, and click Add. It needs macOS Sonoma 14 or later and costs nothing. Chrome and Microsoft Edge have their own install commands, and dedicated wrapper apps cover what the browsers leave out, such as choosing the browser engine or running many separate logins. This guide walks through each route with the exact menu names, then compares what each does to sign ins, notifications and extensions, with prices checked on official pages on October 18, 2026.

Safari: Add to Dock

Apple's Use Safari web apps on Mac is the reference for the built in method.

  1. Open the website in Safari. Go to the exact page that should open every time, and sign in first.
  2. From the menu bar, choose File, then Add to Dock. The Share button in the toolbar has the same command.
  3. Type a name for the app, then click Add.

The new web app is saved to the Applications folder inside the home folder. It opens from the Dock or Spotlight and appears in Command Tab like any other app. Apple's Safari User Guide adds that if the site was already signed in, the web app is usually signed in too.

After that, the web app is separate from Safari. Apple states that it shares no browsing history, cookies, website data, or settings with Safari. Its own Settings, reached by clicking the app's name in the menu bar, change the name, the starting URL and the icon. The same window has an option to show or hide navigation controls, a Privacy tab to clear the site's cookies and caches, and an Extensions tab to turn Safari extensions on or off for that app.

To delete it, open the home folder with Finder, Go, then Home, open Applications, and drag the web app to the Trash.

This route suits most people starting out. It is free, already installed, and needs no account anywhere.

Chrome and Edge: install the site as an app

The two largest Chromium based browsers have their own version of the same idea.

Chrome

Google's help page Use web apps gives these steps:

  1. Open Chrome and go to the website.
  2. At the top right, select More, then Cast, save, and share, then Install page as app.
  3. Follow the on screen instructions.

On some sites an Install icon also appears at the right end of the address bar. Installed apps are listed at chrome://apps. To remove one, open it, select More, then Uninstall, and optionally delete its data from Chrome as well.

Microsoft Edge

Microsoft's article Install, manage, or uninstall apps in Microsoft Edge describes the menu path Settings and more, then More tools, then Apps, then Install this site as an app. Installed apps are managed at edge://apps, where each one has a card for pinning, privacy controls and removal.

What changes compared with Safari

An app installed from Chrome or Edge runs on that browser's engine, which matters for sites that work best in Chromium. Gmail is the clearest case: Google's help page on Gmail offline says offline mail works only in Chrome, and not in an Incognito window. The trade-off is that the installed app sits inside the browser's own profile, so a second account for the same site generally means setting up a second browser profile first.

Dedicated tools that turn websites into Mac apps

A separate category of Mac apps exists just for this job. They build each website into its own app bundle and add settings the browsers do not offer. Prices below were read from each official page on October 18, 2026.

Tool Price shown Free option Engine Stated macOS requirement
Safari web apps Free Built in Safari macOS Sonoma 14 or later
Chrome installed apps Free Built in Chrome Chrome installed
Coherence X6 From 39.99 USD, buy once First app free Chrome and other Chromium browsers macOS 13.5 or later
Unite From 39.99 USD First app free Not Chrome based; the vendor points to Coherence for Chrome macOS 15 or later
WebCatalog Pro 5 USD a month, billed annually Basic plan with 2 desktop apps Not listed on the pricing page macOS, Windows and Linux

A few facts from those pages are worth reading closely. Coherence X6 is described as "buy once and use forever, with optional paid upgrades", and lists multiple browser engine choices. Unite's page says each app runs isolated and lists a requirement of macOS 15 or greater. WebCatalog's Basic plan includes 2 desktop apps, 2 profiles and 1 space, and Pro removes those limits for 5 USD a month on annual billing, or a 7 day trial.

The common thread is what these tools add over the built in routes: choosing a browser engine per app, a separate profile for every app, preset icons, link rules for which addresses stay inside the app, and grouping several sites into one window.

Sign ins, notifications and extensions by route

The visible difference between routes is small: every one gives a window and a Dock icon. The differences that matter show up later, in three places.

Sign ins

A Safari web app has its own cookies, separate from Safari and from every other web app. That makes it easy to keep a work account and a personal account for the same site open at once: make two web apps. A Chrome installed app shares cookies with the Chrome profile it came from, so it signs in as whoever is signed in to that profile. Wrapper tools that give every app its own browser profile behave like Safari here, and some can copy an existing sign in from a saved template so a new app does not need a fresh login.

Notifications

Notification permission is stored per site and per cookie store. A web app with its own store starts with no permission, even if the site was allowed in the browser. Apple's instructions for Safari web apps are to answer the site's request inside the web app; it then appears by its own name in System Settings, Notifications, and the Dock icon can show a red badge with unread notifications. Some wrapper tools have a per app Notifications switch that grants permission automatically.

Extensions

Safari web apps can use Safari extensions, switched per app in the Extensions tab. Extensions from the Chrome Web Store, such as a password manager or translator set up in Chrome, need an app that runs on a Chromium engine with extensions enabled. Chrome installed apps share the extensions of their profile. Wrapper tools vary: some turn extensions on per app, so a mail app can carry a password manager while a video app carries nothing.

Which websites are worth turning into apps

Not every site benefits. A useful rule: a site earns its own app when it is open for most of the day, or when it is found again many times a day.

Good candidates usually share three traits:

  • They stay open. Mail, chat, calendars, project boards, AI chat tools and music players are left running for hours. A Dock icon and a Command Tab entry turn "find the tab" into one keystroke.
  • They notify. Sites that send alerts are easier to manage when the alerts carry the app's own name and badge instead of the browser's.
  • They need a separate account. A client's workspace or a second Google account is far easier to keep straight as its own app with its own cookies.

Poor candidates are sites visited once a week, sites used mainly for reading and then closed, and anything that opens many links to other sites, since each of those links leaves the app window anyway.

A practical way to choose: look at the browser's pinned tabs. Those are the sites already being treated as apps. Start with the two or three that are open from morning to evening, live with them for a week, then add more only if the first few earned their place. A Dock with twenty web app icons is as hard to scan as a tab bar with twenty tabs.

Making the new apps easy to find

An app that looks like every other icon in the Dock solves only half the problem. A few small settings make the difference between a tidy Dock and a row of identical favicons.

Give each app a short, distinct name. The name is what Spotlight matches. "Mail", "Board" or "Calendar" reaches the app in two keystrokes. A page title like "Inbox (214) - Company Mail" competes with every other result.

Replace weak icons. Many sites ship small favicons that blur at Dock size. In a Safari web app, open Settings from the app's name in the menu bar and click the icon to choose any image file. Wrapper tools usually offer preset icons for common services and apply the rounded square shape macOS uses, so the result sits naturally next to native apps.

Pin them on purpose. A web app that is open but not pinned can drift into the recent apps area of the Dock and vanish after it quits. Control click its icon and choose Options, then Keep in Dock. Apple's Dock guide also notes that apps belong on the left of the separator line and files on the right.

Open the daily ones at login. Apple notes that a Safari web app can be added as a login item, so mail or chat is ready when the Mac starts.

Signs the built in route has stopped being enough

Safari's Add to Dock is a good fit for a handful of sites. These are the points where people usually move to something else:

  • A site needs Chromium. If a service works poorly in Safari, or relies on a Chrome only feature such as Gmail offline, a Safari web app cannot change engines.
  • Chrome extensions are part of the work. Password managers, translators and developer tools set up in Chrome are not available in a Safari web app.
  • Many accounts, many apps. Setting name, icon and URL by hand for ten apps is slow, and keeping their icons distinct in the Dock is harder still.
  • Browser updates break wrappers. Chromium based wrappers that copy or patch the browser can stop launching after a browser update. Tools that link to the installed browser instead, and repair apps after an update, avoid most of that.

A site to app tool built around these points typically offers a choice of seven Chromium based engines, per app extensions, one profile per app, a few hundred service presets with official icons, and a mode that groups several services into one app with a sidebar. The Features page shows the full set, and the Supported services page lists the presets.

What to change first

Pick the one site that is open longest each day and make it an app with Safari's File, then Add to Dock, today. If it needs Chrome, Chrome extensions, or a second account beside the first, Kagemusha builds Chromium based apps and is free for up to 3 of them.

Frequently asked questions

Is there a free way to turn a website into an app on a Mac?

Yes. Safari's File, then Add to Dock, is free on macOS Sonoma 14 and later. Chrome's More, then Cast, save, and share, then Install page as app is also free. Several dedicated tools have free options too, such as a first app free or a small number of apps.

Where does a Safari web app get saved?

In the Applications folder inside the home folder, not the main Applications folder. It opens from the Dock and Spotlight. To delete it, drag it from that folder to the Trash; removing it from the Dock only removes the shortcut.

Will a website app stay signed in?

Yes, once signed in inside the app. Safari web apps keep their own cookies, separate from Safari, so signing out in the browser does not affect them. Apple notes that a site already signed in when the web app is created is usually signed in automatically.

Do Chrome extensions work in a website app?

Not in a Safari web app, which uses Safari extensions only. An app installed from Chrome shares the extensions of its Chrome profile. Some dedicated tools that run on Chromium let Chrome Web Store extensions be switched on per app.

Which websites should not be turned into apps?

Sites visited rarely, pages read once and closed, and sites that mainly link out to other sites gain little. Apps help most for tools open for hours, tools that send notifications, and accounts that need to stay separate from the main browser.

Back to all posts