Chromeのプロファイル alternatives: what you can drop

A Chrome profile looks like one feature. It is actually five unrelated jobs stapled into a single unit, and most people who go looking for an alternative only need one or two of them. Separating the jobs is what makes the question answerable, because each job has a different replacement and a different cost. Once the list is written down, the number of profiles worth keeping usually turns out to be smaller than the number currently on the machine.

The five jobs a profile performs at once

Anyone running several profiles is paying for all five of these, whether or not all five are wanted.

Session separation. Cookies and site data belong to one profile, so the same service can stay signed in under two different accounts at the same time.

Stored data separation. Bookmarks, history, and saved passwords do not mix across identities.

Extension separation. An extension installed for work does not appear in the personal window, and its settings are held per profile.

Visual identification. A theme colour and an avatar make it possible to tell, at a glance, which identity the front window belongs to.

Sync. Signing a profile into a Google Account pushes that identity's bookmarks and passwords to other machines.

Google's own description stops at the separation itself:

With profiles, you can keep all your Chrome info separate, like bookmarks, history, passwords, and other settings. Source: support.google.com

Nothing in that sentence says which of the five a given person needs. Profiles start to feel heavy at the point where someone wants one job and is administering all five. A common version of this is wanting two simultaneous logins to one service, and ending up with duplicated bookmark trees and a second copy of every extension as a side effect.

Four replacements, measured against the five jobs

On macOS there are four practical alternatives. None of them is better in general. They cover different parts of the list.

Replacement	Session	Stored data	Extensions	Visual	Sync
macOS user accounts	Separate	Separate	Separate	Separate	Per account
Guest mode	Separate	Not kept	Unavailable	Shared	None
A second browser app	Separate	Separate	Separate	Separate	Per browser
One window per app	Per window	Separate	Per window	Per window	Per service

Reading down the table, the separation gets stronger toward the top and finer toward the bottom. Stronger separation always costs more to cross, which is the trade-off that decides most cases.

macOS user accounts

This is the strongest option, and the only one on the list that asks for a password. That difference matters more than it sounds. Chrome's documentation states plainly that anyone with the device can switch to any other Chrome profile on it, and the profile picker never challenges for credentials. If something on a shared Mac genuinely must not be visible to the other person using it, a second macOS account is the replacement, not a second profile.

The cost is the crossing. Fast user switching works, but applications open in one account do not appear on the other account's screen, and background tasks continue without being visible. A workflow that touches both identities several times an hour will not survive this. A workflow where the first half of the day and the second half of the day are different contexts will.

Guest mode and Incognito

Both create a temporary identity, so neither is a replacement for a permanent one. In Guest mode, other profiles cannot be seen or changed, browsing activity is deleted from the computer on exit, and extensions do not run. Incognito keeps no history but carries the current profile's settings along with it.

What these can replace is the identity used a handful of times a month. A standing profile kept alive for an administrative account that gets opened twice a year is a maintenance cost with no return, and that slot can move to Guest mode. Anything used daily cannot live here, because every close means signing in again.

A second browser application

Safari for personal, Chrome for work. Cookie stores are entirely separate between two browsers, the Dock icons already look different, and there is nothing to buy or configure.

Two limits show up quickly. Bookmarks and extensions become two sets to maintain, and the number of identities is capped by the number of browsers installed. Someone who needs three identities ends up installing a third browser, at which point the administration grows faster than the benefit.

There is also a default browser decision attached. macOS hands links clicked in other applications to whichever browser is set as default. With work in Chrome and personal in Safari, a link from the mail client lands in one of them regardless of which context it came from. Setting the default to match whichever application produces the most links keeps this from undoing the split.

One window per application

Chrome can install a page as an app, which opens it in a dedicated window with no tab strip. That window still belongs to the profile it was created from, so cookies are shared and the signed-in account does not change. It replaces the visual identification job and gives the page a fixed location, and it replaces nothing else.

Getting a location and an identity at the same time is what an app aggregation browser does. Mail lives in the mail window, chat lives in the chat window, and the session is scoped to the window rather than to a global profile. Choosing an identity stops being a separate action and becomes a consequence of which window is in front. The arrangement is described on the Workspaces page, and the feature by feature difference from a standard browser is set out under Features.

Sync is the job that does not require another profile

The fifth job is the one most often misread. Wanting bookmarks and passwords available on a second machine is a reason to sign in, not a reason to split. Sync attaches to a Google Account, and one profile signed into one account already delivers it.

The exception is narrow. A profile can hold one signed-in account, so two accounts whose stored data must both sync do require two profiles. If only one account needs syncing, every other identity is free to live anywhere: an unsigned profile, Guest mode, or a different browser entirely.

That reduces the whole decision to a single line. Keep one signed-in profile per account that needs syncing, and choose freely for the rest. Where an employer has disabled sync by policy on a managed account, even that profile drops out of the calculation and the range of replacements widens again.

The cost that grows with every profile added

Separation is visible on the day it is set up. The cost arrives later, spread thin enough that it rarely gets attributed to the profile count.

Extensions install per profile and hold their configuration per profile. A password manager, an ad blocker, and a clipping tool across four profiles is twelve installations, twelve sets of permissions to review when one of them changes hands, and twelve places where a broken update has to be noticed. Nothing about this is difficult. It is simply four times the work of doing it once, repeated every time an extension asks for a new permission.

Saved passwords scatter the same way. A credential saved in the work profile is invisible in the personal one, which produces the familiar situation of resetting a password that is already stored twenty centimetres away in a different window. Sign-in prompts that appear for no apparent reason are usually this, not an expired session.

The picker itself changes character somewhere around five or six profiles. Names start to resemble each other, the supply of distinct theme colours runs out, and at least one card exists whose purpose nobody remembers. At that point the screen is no longer a selector. It is a search, and the cost is the pause before each click rather than the click itself.

None of this argues against profiles. It argues for counting them deliberately, because the benefit of each one is decided on the day it is created and the cost is paid every day afterwards.

Which profiles can actually be dropped

Going through the existing profiles one at a time and naming the job each performs makes the cut obvious. Three patterns account for most of them.

A profile whose only real job is visual identification, holding the same content as the main one in a different colour, can go. A different window position or a different bookmarks bar achieves the same thing.

A profile created because bookmarks were getting mixed can go as well. Folders separate bookmarks, and history is searchable.

A profile that holds a second simultaneous login to a service cannot go. One cookie store will not hold two live sessions for the same site, and no amount of organising changes that.

For a lot of people, only the third category survives. Six profiles frequently reduce to two.

Deletion carries one warning worth reading before acting on any of this. Google's documentation notes that removing a profile erases that profile's bookmarks, history, passwords, and other settings from the computer. Signing the profile into its account first, or exporting bookmarks to an HTML file, makes the step reversible.

The order of operations matters more than the decisions themselves, because attempting the whole migration at once produces a pile of sign-in screens and stalls halfway. Start with the profiles nobody can describe. Open each one, check whether anything is signed in, and if nothing is, export the bookmarks and delete it. That clears the easy slots without touching anything in daily use.

Next, move the occasional identities to Guest mode, one at a time, and give each move a week before doing the next. If a service turns out to be needed more often than expected, it becomes obvious quickly and the profile can be recreated with nothing lost.

Only then count what remains. Identities that need to be signed in simultaneously are the genuine floor, and that number is the one worth designing around. Two or fewer is comfortably handled by two browsers. Three or more is where a per window arrangement starts to pay for itself, and the list of services that can be placed in such a window is on the Supported apps page.

What to change first

Open the profile list today and read the names. Any card whose contents cannot be described from memory is the first candidate, and any identity used only a few times a month is the second. Count what is left that needs two simultaneous logins, and if that number is above two, look at a per application arrangement such as SpaceDeck before adding another profile, with the cost side covered on Pricing and the alternatives laid out under Compared with Wavebox.