Free ways to keep work and personal accounts apart

Two Gmail accounts, a work Slack and a side project Slack, a Notion for the company and a Notion for everything else. The moment a second account of anything enters the picture, a browser stops being one place and becomes a stack of half remembered login states. The usual reaction is to search for a multi account browser that costs nothing, install something, and hope the problem goes away. It usually does not, because the thing that breaks is rarely the browser. It is the boundary between sessions, and most free setups draw that boundary in a different place than expected.

This is a look at what the free options actually separate, where each one leaks, and how to tell whether the remaining friction is worth paying to remove.

What a browser is actually separating

Every multi account setup comes down to one question: which pieces of state does each account get to itself. There are four pieces that matter.

Cookies and site storage are the big one. A login is a cookie, plus some local storage, scoped to a domain. If two accounts share a cookie jar, they cannot both be signed in to the same site as different users without the site doing extra work to support it.

Cache and history matter less for correctness and more for privacy. A shared history means work searches surface in personal autocomplete.

Extensions are the quiet one. A password manager unlocked for a personal vault, running on a work tab, is a policy problem in some companies and an annoyance in all of them.

The window and the app icon are the piece almost nobody counts, and the piece that decides how the day feels. Two accounts can be perfectly isolated at the cookie level and still live in the same window, which means the only way to switch between them is to find the right tab out of forty.

Free tools tend to be strong on the first three and weak on the fourth. That mismatch explains most of the disappointment.

The free options that ship with the machine

Nothing needs to be installed to get real session isolation on a Mac. Three mechanisms already exist.

Chrome profiles

A Chrome profile is a separate directory on disk with its own cookies, history, bookmarks, and extension set. Profiles open in their own windows, each with an avatar in the corner. This is the closest thing to a proper account boundary that comes for free, and it costs nothing beyond the memory of running more windows.

The catch is switching. Profiles are reached through the avatar menu or through separate dock entries created by hand, and macOS treats them all as one application. Command Tab lands on Chrome, not on the work Chrome.

Multiple sign in inside one Google session

Google lets several accounts sign in to the same browser profile at once, indexed in the URL as /u/0, /u/1, and so on. It is free, immediate, and shallow. The accounts share one cookie jar, so the index in the URL is the only thing keeping them apart. Links from outside the browser open under whichever account happens to be first, and a fair number of Google properties handle the index inconsistently. Anything outside Google ignores the mechanism entirely.

Safari profiles

Safari gained profiles in macOS Sonoma. Each profile keeps its own cookies, history, extensions, and tab groups. For someone already living in Safari, this is the cheapest possible fix, with the same limitation as Chrome: the separation is real, but the switching is still a menu.

Firefox Multi-Account Containers

Mozilla publishes a free extension that gives each container tab its own cookie jar inside a single window. Tabs get a colored underline, and a site can be pinned to always open in one container. This is the most granular free option available, and the only one that puts two accounts of the same service side by side in the same window without a second profile. The tradeoff is that everything stays in one window, which does nothing for the switching problem.

Free options compared

Approach	Cost	Separate cookies	Separate window per account	Separate extensions
Chrome profiles	Free	Yes	Yes	Yes
Google multiple sign in	Free	No	No	No
Safari profiles	Free, macOS Sonoma and later	Yes	Yes	Yes
Firefox Multi-Account Containers	Free	Yes	No	No
A second browser app	Free	Yes	Yes	Yes
Ferdium	Free, open source	Yes, per service	No, one window with a sidebar	Not applicable

The last two rows are worth pausing on. Running Chrome for work and Firefox for personal is the oldest trick in this category, and it is genuinely effective: two applications, two dock icons, two Command Tab targets, zero configuration. It falls apart when the count goes past two, because the number of installed browsers stops being funny at four.

Ferdium is a free and open source desktop client that loads web services in a single window with a sidebar, each service in its own session. It solves the account problem well. It concentrates everything into one window, which is a different answer to the switching problem than the one most people want. The comparison with Ferdium goes through where that difference shows up in practice.

Setting up a free split, in order

The tools matter less than the order they are applied in. Most free setups fail because the boundary was drawn around the wrong thing.

Split by person, not by service. A profile named "Gmail" and another named "Slack" solves nothing when both services have two accounts each. The durable boundary is the identity behind the account: the company self, the personal self, the client project self. Every service belonging to that identity goes in the same profile, and the split holds even when a new service is added later.

Move the personal side, not the work side. The work profile usually carries more state: saved passwords, extensions installed by policy, bookmarks accumulated over years. Creating a fresh profile and moving the smaller, personal set into it is faster and less likely to break something that matters on a Monday morning.

Decide the default browser deliberately. Every link arriving from outside a browser lands in the default one, under whatever profile was last active there. The default should belong to whichever identity receives the most links, which for most people is work rather than the one used for the most hours.

Pin the domains that map cleanly. In Firefox, a container can be set to always open a given domain. This removes the wrong window problem for any service used by exactly one account. It cannot help for a domain shared by two accounts, which is worth knowing before spending an hour on configuration.

Give each profile a home. On macOS, a window can be assigned to a specific desktop space through the dock icon context menu. Once assigned, switching identity becomes a trackpad swipe instead of a search through Mission Control. This single step removes more friction than any amount of tab grouping.

Run the result for a week before judging it. The first two days will feel worse, because habits point at the old window.

Where free setups start costing time

None of the free options fail at isolation. They fail at three smaller things that add up.

Link routing. A link arrives in Slack, in an email, in a calendar invite. It opens in the default browser, under whatever profile was last used. For a URL that requires the work account, this means landing on a permission error, copying the URL, switching profile, pasting. Several times a day. Nothing in the free tier fixes this, because the operating system only knows one default browser and no profile.

Notifications. Web notifications are granted per profile and per site. Three profiles means granting the same permission three times, and it means a notification with no reliable indication of which account produced it.

Window sprawl. Profiles produce windows, and windows produce Mission Control screenshots that look like a cluttered desk. The mental cost of picking the right window is the same cost as picking the right tab, moved one level up.

Restart state. After a reboot, a free setup is a set of windows to reopen by hand, in the right order, with the right tabs. There is no concept of a saved layout across profiles.

Each of these is small. The reason they matter is that they land on attention rather than on time. A five second interruption that happens twenty times a day is not a hundred seconds of lost work.

There is a second cost that shows up later. A free setup is held together by discipline, and discipline degrades. A link gets opened in the wrong profile because switching felt slow that morning, then a login happens there because the page asked, and a month later both profiles hold half of both identities. The setup has not broken. It has quietly stopped being a boundary, which is worse, because the false sense of separation remains.

When a dedicated app earns its place

The case for a purpose built tool is not that it isolates sessions better. Chrome profiles isolate sessions perfectly well. The case is about the fourth item in the earlier list, the window and the icon, and about what happens after the accounts are separated.

A tool built for this treats a web service as an application. Each account gets a persistent window, a place in the switcher, and a session that does not depend on which tab was clicked last. The layout survives a restart. Grouping accounts by project rather than by service becomes possible, which is the difference between "the work Gmail" and "everything for this client, in one place". That grouping model is what Workspaces describes, and the feature list covers what stays in the window versus what stays in the browser.

Cost is the honest tradeoff. Free options cost nothing and ask for manual discipline. Paid ones cost money and remove the discipline requirement. Anyone whose second account is used twice a week should stay free. Anyone switching accounts dozens of times a day is paying already, in a currency that does not show up on a receipt.

How to pick without installing five things

Start by counting. Not accounts, but switches per day, roughly. Under ten, profiles are enough and anything else is overhead. Between ten and forty, containers or profiles plus a deliberate window layout will hold. Above forty, the bottleneck is the switch itself and no amount of free configuration fixes it.

Then check the shape of the accounts. Two accounts of the same service, used at the same time, need real cookie separation, which rules out Google multiple sign in. Many services with one account each need window organization more than isolation, which is where a single window client fits. A mix of both is the common case and the hardest to serve with one free mechanism.

Finally, be honest about link routing. If most work arrives as links from a chat app, the profile approach will keep costing a few seconds per link no matter how well it is configured.

What to change first

Set up a second Chrome profile today, move every personal login into it, and use it for a week before installing anything. Most of the friction disappears at that step, and the friction that remains is a precise description of what a tool would have to solve. If what remains is the switching itself, compare that against the pricing for SpaceDeck rather than against another free download.