Choosing a browser for multiple accounts on a Mac

The search for a browser that handles multiple accounts usually arrives after something specific has gone wrong. A message went out from the personal address. A shared document opened as the wrong identity and the client saw the name. A password manager filled the credentials of one company into the login page of another. The instinct after that is to look for a better browser, which is reasonable, but the browsers differ less than the marketing suggests. What separates them is where the boundary sits and how much effort each switch costs.

Two unrelated problems arrive under the same search

The first problem is holding two accounts on the same service. Two Google accounts, two Slack workspaces on different email addresses, two accounts on a client's project tool. The obstacle here is technical: a cookie belongs to a browser storage area, not to a tab, so one storage area can hold one session per site. Any solution has to create a second storage area.

The second problem is holding many services at once. One account each on mail, chat, documents, design, and a ticket tracker, all open all day. Nothing here conflicts. The cost is attention: thirty tabs that all look the same, notifications with no visible origin, and the few seconds spent finding the right tab repeated hundreds of times a day.

These need different answers. A browser that is excellent at the first can be useless for the second. Deciding which one is actually causing the damage is the step that makes the rest of the choice straightforward.

What each browser ships with, without add-ons

Everything below is built in and free.

Chromium browsers. Chrome, Edge, Brave, and Vivaldi all inherit the same profile system. A profile is a separate storage area with its own cookies, passwords, extensions, and history, and each one runs in its own window. Edge adds a workspace feature that shares a set of tabs with colleagues, which is a collaboration tool rather than an account separator.

Safari. Profiles arrived in Safari 17. Each profile keeps its own tab groups, history, favourites, and extensions, and the separation works the same way in practice as the Chromium version. Apple documents the feature in the Safari user guide.

Firefox. Two mechanisms exist side by side. Full profiles work like Chrome's and are managed outside the normal interface. Containers are the more interesting option, added through an extension Mozilla maintains:

Under the hood, it separates website storage into tab-specific Containers. Cookies downloaded by one Container are not available to other Containers. Source: addons.mozilla.org

The difference matters. A container is a property of a tab, so two accounts can sit in one window as two tabs. Every other option needs two windows.

Approach	Separation unit	Two accounts in one window	Extensions separate
Chromium profile	Window	No	Yes
Safari profile	Window	No	Yes
Firefox profile	Window	No	Yes
Firefox container	Tab	Yes	No, shared across containers
Private or incognito	Session	One extra only	Mostly disabled

The service, not the browser, sets several of the limits

Changing browser does not change what a service permits, and some of the most annoying behaviour comes from the service side.

Google allows several accounts signed in simultaneously in one storage area, which is why the account switcher exists at all. The catch is that the accounts are not equal. Google describes the arrangement this way:

You can control your settings separately for each of your accounts. When you sign in to multiple accounts, account settings usually aren't shared between accounts. For example, your accounts might have different language settings or sign-in steps. Source: support.google.com

The settings stay separate, but the routing does not. The account signed in first becomes the default, and links opened from outside the browser tend to land there regardless of which account they belong to. No browser fixes this, because the decision is made by Google before the page renders.

Chat tools behave differently again. Slack treats several workspaces joined with one email address as one identity that can be switched between, while workspaces joined with different email addresses are separate logins that a single storage area cannot hold at once. Microsoft accounts, personal and work, are two account types that frequently refuse to coexist in one session at all.

The lesson is to check the specific services in daily use before picking a browser on general grounds. If the difficult service is one that already supports account switching, the browser question is smaller than it looks.

Five questions that separate the options

Does it isolate cookies, or only appear to? Private windows and separate windows of the same profile do not. Profiles and containers do. This is the only test that matters for the first problem.

How many actions does a switch take? Counting the clicks between the current account and the target account, then multiplying by the number of switches in a normal day, converts a vague irritation into a number worth acting on.

Do notifications say where they came from? Multiple profiles produce notifications that look identical. If the answer to a notification depends on which account raised it, this question outranks most others.

Where do external links open? Links from a mail client or a calendar go to the browser the operating system considers default, and then to whichever window was last active. Any setup with more than two profiles hits this daily.

What has to be rebuilt after moving? Extensions, saved passwords, and pinned tabs do not travel between profiles or between browsers by default. The count of items to rebuild is the real switching cost.

What a browser change actually costs

Installing a new browser takes two minutes. Living in it takes longer, and the parts that take longest are rarely mentioned.

Extensions have to be reinstalled and reconfigured one at a time, and any that hold a login need signing in again. A password manager can usually be pointed at the new browser without difficulty, but the browser's own saved passwords need exporting and importing, which produces a plain text file that has to be deleted afterwards.

Then there is the default browser setting, which is a single choice for the whole Mac. Running two browsers for two purposes means one of them is not the default, and every link from every other application goes to the wrong one until the habit adjusts.

The honest version of this is that browser switching is worth doing once, not repeatedly. Trying five in a month costs more time than the original problem does in a year.

What no browser separates, whichever one is chosen

Some of the leakage people hope a new browser will fix happens outside the browser entirely, and no product on this list changes it.

Downloaded files go to one folder on the disk. A contract pulled from a client account and an invoice pulled from a personal one land in the same place, with nothing in either file recording which session fetched it. Setting a different download folder per profile is possible in Chromium browsers and is the only fix.

The network is shared. Every profile, container, and separate browser leaves the machine through the same connection and shows the same public address, along with the same screen dimensions, the same operating system version, and the same installed fonts. Separation of accounts is not separation of identity, and any expectation built on the second will be disappointed.

Access is shared too. A browser profile has no password on it. Anyone sitting at the unlocked Mac can switch to any profile in a couple of clicks. Where two people genuinely need to be kept apart on one machine, the boundary that does that is a macOS user account, not anything inside a browser.

And the system default browser is one setting for the whole Mac. Two browsers used for two purposes means every link from every mail client, calendar, and chat application goes to one of them, and correcting that by hand is a permanent small tax on the arrangement.

The count changes which answer is correct

For two accounts, the built in tools are enough. A second profile in the browser already installed, set up carefully once, solves it at no cost. Anything more elaborate is overhead.

For three or four, the arrangement starts to creak. The windows look alike, notifications arrive without origin, and switching becomes a search rather than a choice. Colour coding and dedicated launchers hold this together for a while.

Past that, the shape of the problem has changed. The difficulty is no longer holding sessions apart, because profiles already do that. It is that a browser presents every application as an anonymous tab in a stack of identical windows, and the working day is spent locating things rather than doing them.

That is the point at which a different unit of separation becomes worth considering, one built around the application rather than the account, so that mail, chat, and documents each occupy a fixed and recognisable place. The arrangement is set out in Workspaces, the list of what can be held that way is on the Supported apps page, and readers weighing this against established products of the same kind will find the differences in Compared with Wavebox and Compared with Ferdium.

How to trial one without committing the whole setup

The cheapest way to test a browser is to give it a narrow job rather than everything at once. Move one account into it, leave the rest where they are, and use it for a fortnight without changing the system default browser. Two weeks is long enough for the annoyances to appear and short enough that reversing costs nothing.

Three things are worth noting during the trial. How often the wrong window comes forward. Whether notifications from the moved account are recognisable without reading them. Whether the extensions that matter exist and behave the same way. Everything else is preference and will settle by itself.

The trial fails in a useful way as often as it succeeds. Discovering in week one that the difficult service refuses to run two sessions regardless of the browser saves a full migration, and points at the arrangement of windows rather than the choice of browser as the thing to fix.

Deciding without installing five browsers

Count the accounts that must stay signed in simultaneously, and count the services behind them. Two accounts on one service means a second profile in the current browser, and nothing else. Many services at one account each means the browser is not the variable and the window arrangement is. Both at once, at any real scale, is the case where a dedicated tool earns its place, and the cost of that is stated on the Pricing page.

What to change first

Spend one day counting switches rather than reading comparisons. If the count is low and the pain is logging in, add a profile. If the count is high and the pain is finding the right window, the browser is not the thing to change, and a tool built around per application windows such as SpaceDeck addresses the version of the problem that profiles leave untouched.