Set up several Chrome profiles on a Mac

Adding a second profile takes about a minute. The interesting part starts on day three, when there are four of them, they all look the same in the Dock, and half the links opened from Mail land in whichever one happened to be running. Profiles are the strongest separation the browser offers on macOS and they stop at a very specific boundary. Knowing where that boundary sits is what turns a pile of profiles into a setup worth keeping.

What a profile actually is on disk

A profile is a directory. Everything that makes a browsing session personal lives inside it: cookies, history, saved passwords, bookmarks, extensions, site permissions, and the signed in state for every service. Two profiles are two of those directories, and for practical purposes they behave as two separate browsers that happen to share one application binary.

Those directories sit under the browser's support folder in the user library, named Default, Profile 1, Profile 2, and so on. The names are assigned in creation order and never change afterwards. Renaming a profile in the interface changes only its display name, which is stored separately in a state file in the same directory, alongside the avatar and the colour.

This split between folder name and display name is the single most common source of confusion. A profile called Client A might live in the folder Profile 3, and nothing in the interface says so. Deleting a profile does not renumber the others, so gaps appear. Anything that automates the browser, whether a launch command, an alias, or a shortcut, addresses the folder name, so the mapping has to be looked up once and written down.

Display names are for people. Folder names are for commands. They never match by accident.

Creating profiles that stay distinguishable

The creation flow itself is short. Open the profile chip at the top right, choose to add a profile, sign it in or leave it signed out, and pick a name, an avatar, and a colour. Three decisions inside that flow decide whether the setup survives.

Colour first. The window frame is tinted with the chosen colour, and since two windows are otherwise pixel identical, this tint is the only signal available while moving fast. Colours need to be far apart. Two blues fail immediately.

Sync second. Turning on sync in a profile carries its bookmarks, passwords, and extension list to every machine signed in with that account. That is convenient for a personal profile and risky for a client profile, because the client's extensions and saved sessions will follow the account onto other hardware later without asking again. A profile that exists to seal something off should usually have sync left off.

Signed out profiles third. A profile does not need a Google account at all. A profile with no account attached is a clean container with its own cookies, useful for testing, for a shared machine, or for a client environment where a personal identity should never appear. Guest mode looks similar and is not the same thing: guest sessions discard everything on close and cannot hold extensions, which makes them a testing tool rather than a workspace.

A reasonable structure for most people is one profile per organisation rather than one per account. Organisations bring a bundle of things that belong together: a mail account, a document store, a ticket system, a set of extensions, a set of saved passwords. Splitting by account instead produces profiles that each hold a fragment of a job.

Launching a specific profile directly

The browser on macOS does not offer a menu item that creates a Dock shortcut for one profile, which the Windows build does. The equivalent is a launch flag passed through the system open command.

open -na "/Applications/Google Chrome.app" --args --profile-directory="Profile 1"

The n flag forces a new instance instead of raising an existing window, the a flag names the application, and everything after the args separator is handed to the browser. Appending a URL to that line opens the URL inside that profile, which is the piece that makes the command genuinely useful rather than a curiosity.

Two cautions apply. Use the full path to the application bundle. Several products on the market wrap the same engine and run under a process name that also reads as the browser, and naming the app without a path can hand the command to the wrong one. Also expect that when the browser is already running, some builds ignore the profile flag and simply focus whatever window exists, which is exactly why the new instance flag belongs in the command rather than being optional.

That command can be saved as a shell alias, wrapped in a small application built with the system automation tools, or bound to a launcher. Wrapping it as an application is the version that produces a real Dock icon with its own name, which is the closest the platform gets to per profile applications.

Where the separation ends

Profiles isolate the session completely and isolate nothing above it. Every profile window still belongs to one application, and the operating system works at the application level.

Layer	Separated by profiles
Cookies and logins	Yes
History and bookmarks	Yes
Extensions and their permissions	Yes
Saved passwords	Yes
Application switcher entry	No
Dock icon and badge	No
Notification permission	No
Default browser for links from other apps	No

The last row causes the most damage. A link clicked in a mail client, a chat app, or a calendar invitation goes to the default browser, and the default browser opens it in whichever profile it decides to use. The careful separation built inside the browser is bypassed by every link that arrives from outside it. Handling this properly requires a link router, a third party utility that inspects the URL and chooses a target, which is another piece of software to maintain.

The application switcher row causes the most friction. Command Tab moves between applications, so it cannot move between profiles. Cycling windows within the application reaches them, but the cycle includes every window of every profile in an order that is not stable enough to build a habit on.

When more profiles stop helping

Profiles scale badly past a certain count, and the count is lower than most people expect. Somewhere around four, the cost of finding the right window starts to exceed the cost of the problem the profiles were created to solve. The symptoms are consistent: hunting through Mission Control, opening the wrong window and typing into it, and a Dock badge that means something unknown until clicked.

The reason is that profiles solve identity and leave place unsolved. Two clients in two profiles are correctly isolated and both live in the same rectangle of screen, reachable by the same keystroke, showing the same icon. Attention needs place, not just isolation.

The alternative model gives each web app its own window with its own storage, so that switching context is switching window rather than switching a hidden setting inside one application. That approach is described on Workspaces, and the services already handled are listed on Supported apps. The isolation is per app rather than per browser session, which is why two accounts on the same service can stay signed in at once without either one signing the other out.

Several products build on this idea and they differ in ways that matter before paying for any of them, particularly memory use, how notifications are surfaced, and which platforms are covered. Compared with Wavebox and Compared with Sidekick list those differences item by item rather than in general terms.

Moving profiles to a new Mac

Profiles are directories, which makes migration simpler than it looks and easier to get wrong than expected. There are two routes and they suit different situations.

The account route uses sync. Signing the same account into a fresh profile on the new machine pulls back bookmarks, saved passwords, history, and the extension list. What it does not carry is anything that was never syncable: site permissions granted case by case, active sessions, and any profile that had no account attached at all. A machine rebuilt this way looks correct and quietly requires signing in to everything again.

The file route copies the directories. With the browser fully quit on both machines, the profile folders and the state file that maps them to display names can be copied across. This preserves far more, including sessions in many cases, and it carries over anything broken along with everything working. It also requires that the destination has the profiles created first, or the state file will describe profiles the interface does not show.

Three cautions apply to the file route. Quit the browser completely rather than closing the windows, because the databases inside a profile are open while the process runs and copying them mid write produces a profile that fails to load. Copy the whole folder rather than selected files inside it, since the pieces reference each other. And keep the original until the new machine has been used for a week, because a profile that appears to load can still be missing an extension's stored data.

Whichever route is used, the mapping between folder names and display names should be rebuilt afterwards. Creation order on the new machine will differ from the old one, so a launch command that pointed at one folder now opens something else. Every launcher, alias, and shortcut built around a profile directory needs to be checked once after a migration, and that check takes five minutes against an afternoon of confusion.

Maintenance that keeps a profile setup healthy

A few habits keep the arrangement from decaying.

Write down the mapping between folder names and display names once, and keep it near whatever scripts use it. Deleting a profile leaves a gap in the numbering, and a script pointed at a deleted folder silently creates a fresh empty profile instead of failing.

Audit extensions per profile rather than globally. Extensions are installed into a profile and their permissions apply to everything that profile visits, so an extension that reads page content in a client profile has access to that client's data and nothing else. That is the whole point, and it only holds if extensions are not installed everywhere out of habit.

Back up before deleting. Removing a profile deletes its directory, including bookmarks and saved passwords that were never synced. Copying the folder elsewhere first takes a moment and is the only recovery route.

What to change first

Look at how many profiles exist right now and how many are opened in a normal week. If the answer is that two are used constantly and the rest exist for occasional logins, the fix is not another profile. It is giving the two real ones their own launchers so each one opens directly, with its own icon and its own URL.

If both of those are already in place and links still land in the wrong window, the container itself is the limit, and a tool like SpaceDeck that keeps each app in a separate window is the next thing to evaluate. The cost is on Pricing.