Separating work and personal on one MacBook

One MacBook, two lives. The work Slack and the personal Slack. The company Google account and the one holding six years of family photos. A browser that autofills a billing address into an expense form and a work address into a shopping cart. Searching for different profiles on a MacBook returns three unrelated sets of instructions, because the word profile gets applied to at least three separate mechanisms in macOS, and they draw the boundary in completely different places.

The useful question is not how to create a profile. It is what needs to be separated, because the answer decides which mechanism is worth the setup time. Someone who needs two different sets of logins has a small problem. Someone who needs two different mental states has a much larger one, and no amount of profile creation solves it on its own.

The word profile covers three different mechanisms

macOS does not have a single feature called profiles. What exists is a stack of three, sitting at different levels of the system.

A macOS user account is the operating system level boundary. It has its own home folder, its own Keychain, its own Desktop, its own login items, its own Screen Time record, and its own copy of every application's preferences and local data. Applications installed in /Applications are shared, because the executable is shared, but everything each application remembers is not.

A browser profile is one level down. Chrome, Edge, Firefox and Safari all support them. Safari gained the feature in Safari 17, which shipped with macOS Sonoma. A browser profile carries its own cookies, history, extensions, autofill entries and bookmark set, and it stops there. It is a folder of browser data, not a separate application.

An in-app account switcher is the narrowest of the three. Slack lets one client hold several workspaces. Gmail on the web lets one browser session hold several signed-in accounts under numbered URLs. Notion, Figma and Linear all have their own versions. The separation applies to that one service and nothing else.

Mechanism	What it separates	Cost of switching	What stays shared
Second macOS user account	Home folder, Keychain, app data, notifications, settings	Log out, or Fast User Switching	Installed applications, disk, hardware
Browser profile	Cookies, history, extensions, autofill, bookmarks	A menu click, or a second window	Everything outside the browser, plus the browser's identity to macOS
In-app account switch	One service's session	A menu inside that app	Everything else on the machine

Most people searching for this arrive wanting the first row and hoping the cost column reads like the second row. That combination does not exist in stock macOS, which is the real reason the search feels unresolved.

What a second macOS user account really separates

This is the strongest boundary available without buying a second machine. Create it in System Settings under Users & Groups, and the new account starts from a clean home directory. Mail, Messages, Photos, Notes, Calendar, the browser and every third party application see a machine they have never run on before.

Three consequences matter more than the rest.

The Keychain does not cross

Saved passwords, certificates and app tokens live in a per-user Keychain. The work account cannot silently reach personal credentials, and the personal account cannot reach work credentials. For anyone whose employer has an opinion about credential handling, this is usually the only boundary that satisfies the policy.

Notifications only reach the account in front

Fast User Switching keeps both sessions alive at once. Both consume memory, both keep background processes running, and both continue to receive mail. What the background session does not do is show its notifications. A message that arrives for the personal account while the work account is in front is simply not seen until the switch happens. That is either the entire point or a serious problem, depending on whether the two lives are genuinely independent.

Switching is a full context change

Fast User Switching takes a few seconds and swaps the whole screen. Every window, every unsaved document, every terminal session belongs to one side or the other. This is excellent for a boundary crossed twice a day and unusable for a boundary crossed forty times a day. Someone who checks a personal calendar between meetings will abandon this setup inside a week.

One practical note before building it: a second account signs into iCloud separately, so an Apple Account can only be active in one macOS user session at a time on that Mac. Files that need to exist on both sides have to go through the shared folder at /Users/Shared or through a cloud service, and neither is as convenient as it sounds when the file in question is a screenshot taken thirty seconds ago.

Browser profiles are cheaper and stop sooner

For most people the actual friction is inside the browser, not across the operating system. Two Google accounts, two sets of bookmarks, an extension that must not run on the work side. A browser profile handles all of that, and creating one takes under a minute.

In Chrome, the avatar button at the top right opens the profile list and the add option. Each profile gets its own directory under ~/Library/Application Support/Google/Chrome, and the folder names do not match the display names, which matters later if anything scripts against them. In Safari, profiles are under Settings, and each one can be given its own Tab Group set and its own extension state. Firefox has both profiles and container tabs, which are not the same feature: containers isolate cookies within a single window, profiles isolate everything.

What a browser profile does not do is change how macOS sees the browser. Chrome is one application bundle with one bundle identifier, so:

• Cmd+Tab lands on Chrome, not on a profile. Getting to the right window still means reading the window list afterwards.
• Notification Center shows the site name and no account. A badge says Slack, not which Slack.
• The Dock shows one icon regardless of how many profiles are open.
• Quitting the browser quits every profile at once.

These are not defects. They follow from a profile being a data directory rather than an application. The mismatch only becomes painful when someone tries to use browser profiles as a substitute for the operating system boundary, which is exactly what the cost table pushes people to attempt.

The part that surprises people later

Browser profiles are also the layer most likely to be reset by something outside the reader's control. A profile can break after a crash, a sync conflict or a forced update, and the recovery path is a folder full of SQLite files rather than a menu option. Bookmarks and passwords usually come back through sync. Extension configuration, per site permissions, and the specific set of tabs that made the profile useful frequently do not, because they were never uploaded anywhere. Anyone building an important boundary out of browser profiles should know where that data sits and how it is backed up before treating the arrangement as permanent.

The four places the boundary leaks

Whichever mechanism gets chosen, the same four leaks show up. Naming them in advance saves the weekend spent discovering them one at a time.

Link routing. macOS has one default browser per user account. A link clicked in Mail, Slack or a PDF opens in that browser, in whichever profile happened to be frontmost. This is the single most common way a work document lands in a personal session. The fix inside one user account is a link routing utility that reads the URL and picks a target, and there are several on the Mac. The fix across user accounts is that the leak cannot happen, because the other account is not running in front.

The Downloads folder. Browser profiles share it by default. Two profiles writing to one folder produces a directory where the origin of a file is unknowable an hour later. Set a different download directory per profile before the folder fills up, not after.

Menu bar utilities. Password managers, clipboard managers, screenshot tools and note capture utilities are launched per user session, and they see everything in that session. A clipboard manager running in a session that holds both work and personal browser profiles has a full history of both. Under separate macOS user accounts, it does not.

Muscle memory. The most reliable leak of all. Every switching mechanism that requires a decision will eventually be skipped when the reader is in a hurry. Boundaries that hold are the ones where the wrong thing is not reachable, not the ones where the wrong thing is merely discouraged.

Choosing by what actually goes wrong

Rather than picking a mechanism and hoping, it is faster to name the failure that prompted the search.

If the failure is credentials and compliance, the answer is a second macOS user account, and the switching cost has to be accepted. Nothing weaker satisfies a rule about where work credentials may live.

If the failure is the wrong account autofilling, a browser profile is enough, and building a second user account is a large amount of work for a problem that a five minute change already solves.

If the failure is not knowing which account a notification came from, neither mechanism helps much. Both put every web service behind one application identity, and identity is precisely what the notification is missing.

If the failure is losing the window arrangement every time the machine restarts, that is a window management problem wearing a profile costume. macOS restores applications, not layouts, and no profile feature changes that.

The last two are the cases where people cycle through setups for months without relief, because the mechanism they keep reaching for was never built to address what is actually wrong.

A fourth option that sits between the two

There is a middle path that neither the operating system nor a standard browser offers on its own: giving each web service its own window, with its own session, under one running application.

Chrome can do a limited version of this by installing a single page as an app, which produces a real bundle in ~/Applications/Chrome Apps.localized with its own Dock icon and its own Cmd+Tab slot. It inherits the profile that installed it, and it works per site rather than per identity, so five services means five installs and no shared arrangement between them.

The more complete version of the idea is a browser built around it, where each service is a window with an isolated session and the whole set can be saved as a layout. That is what an app aggregation browser does, and the feature set is worth reading against the four leaks above rather than against a list of browser features. If the reason for the search was two Slack workspaces and two Google accounts rather than a compliance rule, grouping them as workspaces addresses the switching cost that made a second macOS user account unattractive in the first place.

What to change first

Write down the one failure that prompted the search, then match it to the table above before creating anything. If it is credentials, build the second macOS user account this week and accept the switch. If it is accounts and windows, start with browser profiles, and if the notification and Cmd+Tab leaks are what keep biting, try a browser that gives each app its own window, such as SpaceDeck.