Site specific browser Edge setup, and its Mac limits

Microsoft Edge can take any web page and give it a Dock icon, its own window, and a place in the app switcher. On a Mac that is often the fastest route available, because Edge is already installed for work, already signed in to the company tenant, and already holds the extensions that make the internal tools behave. What is less obvious is how much of what Microsoft publishes about this feature applies only to Windows, and what happens on macOS when Edge itself moves on. Both of those decide whether the icon is still working in a year.

Where the feature is, and what it produces

Edge does not use the phrase site specific browser in its interface. The command is worded around apps.

The path is Settings and more, then More tools, then Apps, then Install this site as an app. Naming the app and confirming is the whole flow. Everything installed this way is listed at edge://apps, where each card has a Details view holding permissions, pinning, and the uninstall action. Removing one from there also offers to clear the data that came with it, which matters when the site held a session.

On macOS the result is a file, and knowing which file removes most of the confusion later. The installed app is placed in an Edge Apps folder inside the user's own Applications folder, not the system wide one at the root of the disk. Inside that bundle there is no copy of a browser. There is a small launcher binary and an icon, plus a pointer back to Edge, the identifier of the installed app, and the path of the Edge profile it belongs to.

That structure is the whole story of a Chromium based site specific browser. The app in the Dock is a shortcut with a window attached, not a program that can run on its own. Delete Edge and the icon stops working. Remove the profile it was built from and it stops working. Update Edge and it inherits the update, including the rendering engine and the security fixes, without doing anything.

Two ways in, and they behave differently

There is a second, quieter route into the same feature, and it produces a better result when it is available.

When a site publishes a web app manifest, Edge shows an App available icon in the address bar. Clicking it offers to install the site, and because the manifest supplies a name, an icon set, a start URL, and a display mode, what comes out is a properly configured app. The window opens at the URL the site nominated rather than the page that happened to be open, and the Dock icon is the artwork the site prepared.

Install this site as an app works on anything, manifest or not. That is the point of it. The trade is that Edge has to guess: the icon comes from the favicon, which is often a low resolution square that looks soft in the Dock, and the start URL is whatever page was in the tab.

Two habits follow from that. Navigate to the page that should open on launch before installing, not to the deep link that happened to be under the cursor. And check the Dock icon afterwards, because a blurry favicon is the single most common reason people abandon this route and go looking for a purpose built site to app tool instead.

Most of the documented features are Windows features

This is the part that costs Mac users time, and it is visible in Microsoft's own material rather than being a matter of opinion.

The documentation on using installed web apps in Edge lists what an installed app gets: a place in the Taskbar where it can be pinned, an entry in the Start menu, appearance in Alt+Tab, and an Auto-start on device login option set from edge://apps. Every one of those is a Windows mechanism, and the instructions are written in Windows terms, down to signing in to Windows. The end user support topic for installing and managing apps in Edge does not mention macOS at all.

None of that means the feature is broken on a Mac. A Mac gets the window, the Dock icon, Command+Tab, and the entry at edge://apps. What it does not get is the documented launch on login behaviour through Edge's own setting.

The workaround is at the operating system level rather than in Edge. Right click the running app in the Dock, choose Options, then Open at Login, or add it under Login Items in System Settings. It reaches the same outcome, but nobody finds it by reading Microsoft's page, which is why the question keeps being asked.

Documented behaviour	Windows	macOS
Own window, no address bar	Yes	Yes
Listed at edge://apps	Yes	Yes
Pin to Taskbar or Start menu	Yes	Dock, via the operating system
Auto-start on device login from edge://apps	Yes	Set as a macOS login item instead
Appears in the app switcher	Alt+Tab	Command+Tab

The macOS floor under Edge is moving, and it moves the apps with it

An installed app runs on the Edge that built it, so Edge's own operating system support decides how long the arrangement lasts. Microsoft publishes that schedule and keeps it current.

macOS 11 (Big Sur) supported from Microsoft Edge 129 through 138. macOS 12 (Monterey) supported from Microsoft Edge 139 through 150. macOS 13 (Ventura) or later required for Microsoft Edge version 151 and newer. Source: learn.microsoft.com

Read that as a countdown rather than a table. Edge is already past version 151, so a Mac on Monterey holds the last build it will ever receive, and the installed apps on that Mac are frozen with it. They keep launching. They stop getting engine updates, which is the part that matters for a site that keeps shipping new front end code.

The same document notes that Microsoft Edge has had native support for Apple Silicon Macs since stable version 88, so architecture is not the constraint on anything current. Operating system version is.

For a reader deciding whether to build a set of these apps, that turns into one question. If the Mac is on macOS 13 or later, Edge will keep moving underneath them. If it is not, this route has an end date, and a browser with a different support window is the better base.

One profile, one set of apps

Edge on a Mac is frequently a second browser rather than the main one, kept for a work account, a tenant login, or a set of internal tools that behave better in it. That makes the profile binding more consequential than it first sounds.

An app installed from a profile carries that profile's cookies, sign in state, extensions, and permissions. Two profiles in Edge produce two independent sets of installed apps, and the same site can be installed from both. That is a real feature: a personal account and a work account can each get an icon, and neither logs the other out.

The failure case is quieter. Building the app from whichever profile happened to be in front means the app may be tied to a profile that is later removed, or that is not the one holding the correct session. The window opens to a sign in screen and nothing explains why, because the app looks identical either way.

Checking which profile is active before installing takes a second and prevents that entirely. When several sites and several accounts are involved, the profile question stops being incidental and becomes the design of the whole setup, which is what the setup guide works through.

On a managed Mac, the decision may not be yours

Edge is administered through policy in a way most browsers on a Mac are not, and three of those policies act directly on this feature. Microsoft lists WebAppInstallByUserEnabled, described as enabling user web app installation from the browser, WebAppInstallForceList, which configures a list of force installed web apps, and WebAppSettings for web app management.

That has two practical consequences on a work laptop.

The first explains a missing menu. If Install this site as an app is absent or greyed out, the likely cause is not a broken Edge or an unsupported site. It is a policy set by whoever manages the device, and no amount of reinstalling changes it.

The second runs the other way. An administrator can push a set of internal tools out as installed apps, so they appear on every machine in the organisation without anyone being walked through a menu. For an internal admin panel or an intranet that everyone opens daily, that is a genuinely good use of the feature, and it is the reason Edge tends to be the browser these apps are built on inside companies.

For a personally owned Mac none of this applies, and the menu behaves as documented. It is worth checking which situation applies before spending time debugging, because the two look identical from the outside.

Edge, Chrome, and Safari on the same machine

All three can produce a Dock icon. What separates them is the engine underneath, the login that comes along, and how long the route stays supported.

Base	How to install	Session carried	Requires
Edge	Settings and more, More tools, Apps, Install this site as an app	The Edge profile used	macOS 13 or later for current Edge
Chrome	More, Cast save and share, Install page as app	The Chrome profile used	Chrome installed
Safari	File, Add to Dock	Nothing, sign in again	macOS Sonoma 14 or later

Apple states the Safari position plainly.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

For a work tool behind single sign on, that isolation usually argues against Safari and in favour of whichever Chromium browser already holds the session. For a site that should stay separate from everything else, it argues the other way. There is no general answer, only the specific one for the site being installed.

Worth noting for anyone who arrives at this question from older reading: the command line wrappers that used to fill this gap are not a live option. Nativefier was archived on GitHub in September 2023 and is no longer maintained, so anything written around it belongs to the history of the problem rather than its solution.

What to change first

Install one site, not five. Pick the tool opened every working day, navigate to the page it should launch on, confirm which Edge profile is active, and use Install this site as an app from More tools. Then check two things: that the Dock icon is sharp, and that macOS opens it at login through System Settings rather than through Edge. If the icon is soft or the profile question is going to repeat across several sites, that is the point where Kagemusha is doing work the browser menu does not.