What a Chrome profile is, and what it is not

The word profile shows up in at least three places inside Chrome, and each one means something different. There is the circle at the top right of the window. There is the Google account that may or may not be signed into it. There is the folder on the disk where everything actually lives. Most confusion about profiles comes from treating those three as the same thing. They are not, and the difference decides what a profile can and cannot fix.

A profile is a folder, not an account

On a Mac, Chrome keeps its profiles inside a single directory in the user library, under Application Support. The first profile ever created is stored in a folder named Default. Every profile made after that gets a numbered folder: Profile 1, Profile 2, and so on, in the order they were created.

Open one of those folders and the picture becomes concrete. Inside sits a Cookies database, a History database, a Login Data file for saved passwords, a Bookmarks file, a Preferences file holding every setting, an Extensions directory, and a Web Data file for autofill entries. That set of files is the profile. Nothing else about it is special.

Two consequences follow immediately. The first is that the folder name and the visible name are unrelated. Renaming a profile in the interface writes the new label into a separate file called Local State, which holds a small record for each profile. The folder on disk keeps the name it was born with. A profile displayed as Work can sit in a folder called Profile 7, and that mismatch is normal rather than a fault.

The second consequence is size. Every profile carries its own cache, its own history, and its own copy of every extension it uses. A profile that has been in daily use for a year is not a small object. When several of them accumulate on the same machine, the Chrome directory grows accordingly, and none of that space is shared between them.

What a profile actually keeps separate

Google states the purpose plainly in its help documentation:

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

In practice the separation covers the things a browser stores on behalf of a site or on behalf of the user:

• Cookies and site storage, which is what keeps a login alive. This is the one that matters most.
• Saved passwords and autofill entries, including addresses and payment methods.
• Browsing history and the suggestions the address bar makes from it.
• Bookmarks and the bookmark bar.
• Installed extensions, their settings, and their permissions.
• Site permissions such as camera, microphone, notifications, and location.
• The default search engine, the startup pages, and the theme.

Because cookies are per profile rather than per tab, two profiles can hold two live sessions on the same domain at the same time. That single fact is why profiles exist and why they solve the second account problem that no amount of tab arrangement can solve.

What a profile leaves shared

The separation stops at the edge of the browser, and the gap catches people out.

Downloaded files land in the same folder on the disk regardless of which profile fetched them. A document pulled from a work account and a photo saved from a personal one end up side by side, with nothing in the file to say where it came from.

The network is shared. Every profile leaves the machine through the same connection and presents the same public address. Anything a site infers from the address, such as country or organisation, is identical across profiles. The same is true of the screen size, the operating system version, the installed fonts, and the other hardware traits that fingerprinting relies on.

Access is also shared, and Google is direct about it:

Only share your device with people you trust. If someone has your device, they can switch to any other Chrome profile on it. Source: support.google.com

There is no password on a Chrome profile. Switching to another one takes two clicks and no credential. A profile is an organisational boundary, not a security boundary, and treating it as the latter is the most common mistake made with them.

Profile, Google account, and window are three different layers

A profile can exist with no Google account attached at all. It will still hold its own cookies, its own bookmarks, and its own extensions, and nothing will sync anywhere. Signing a Google account into a profile adds two things on top: sync, so the bookmarks and passwords travel to other devices, and a name, because the profile label automatically becomes the account name once signed in.

A window is a third layer again. One profile can have six windows open, and each of those windows belongs to that profile permanently. A window cannot be moved to another profile, and a tab dragged out of a window stays inside the profile it started in. That is why the browser occasionally opens a link in what feels like the wrong place. The link was handed to whichever profile window the operating system considered active, and the browser had no way to know which account the link belonged to.

Guest and Incognito are not smaller profiles

Both get described as profiles in casual conversation, and neither behaves like one.

Guest mode creates a temporary, empty session that is discarded when the last guest window closes. It has no bookmarks, no extensions, no history, and no access to the data of any other profile on the machine. It is designed for handing a laptop to somebody else for ten minutes.

Incognito is a different shape entirely. An Incognito window is opened from an existing profile and belongs to it. It starts with no cookies from that profile, keeps nothing on disk when it closes, and can optionally run that profile's extensions if they are allowed in Incognito. Two Incognito windows opened from the same profile share one session, which is why Incognito is a poor tool for holding a second account open for any length of time.

Mechanism	Own bookmarks and extensions	Survives a restart	Isolated from other profiles
Profile	Yes	Yes	Yes, for browser data
Guest	No	No	Yes
Incognito	Extensions only, if allowed	No	Belongs to its parent profile

Why the concept exists at all

Profiles are not a productivity feature that someone added to sell the browser. They are a consequence of how the web works. A cookie is scoped to a site and stored in one place per browser instance, which means a browser can hold exactly one signed in session per site unless a second storage area exists. Everything built on top of that constraint, from Chrome profiles to Firefox containers to running two different browsers, is a way of manufacturing a second storage area.

The original use case was the shared computer. One machine in a house, several people, and no sensible way to keep one person's search suggestions out of another person's address bar. Profiles solved that, and the language in the interface still reflects it: the entries are called people, and a new one is described as adding a person.

The use case that dominates now is different. One person, one machine, several roles. Chrome's design was not built for that, which explains the parts that fit awkwardly. Nothing tells a link which role it belongs to. Nothing labels a notification with the role that produced it. The person switching profiles fifteen times a day is using a mechanism designed for a household, and the friction that shows up is the gap between those two situations.

How to tell which profile a window belongs to

There is more than one way, and they answer different questions. The avatar at the top right of the window shows the current profile's picture and colour, which is the fastest check but also the easiest to misread when two profiles were given similar colours.

The window title bar shows the profile name when more than one profile exists on the machine, which is more reliable than the colour. For anyone working from the command line, the running Chrome processes list the profile directory they were launched with, which is the only method that reports the folder name rather than the label.

Setting each profile to a distinctly different colour at creation time, and giving each a short name rather than the email address Chrome fills in automatically, removes most of the ambiguity before it becomes a habit.

A Chrome profile is not a macOS user account

The two are often compared, and the scope is very different. A macOS user account separates the entire file system, the applications, the keychain, the desktop, and the running processes. Logging out of one and into another takes the whole machine with it.

A Chrome profile separates browser state and nothing else. It does not touch the Mail application, the Finder, the Terminal, or any other browser installed on the same Mac. When the requirement is genuine separation of two working identities on one machine, the operating system account is the boundary that does that job. When the requirement is holding two logins to the same website, the browser profile is the right size of tool and the operating system account is far too heavy.

Where the idea stops paying off

The model holds well for two profiles and starts to strain past three or four. Each profile is a separate window, so the count of windows grows with the count of identities. Notifications arrive from all of them at once with no clue which profile produced them. Links open in whichever window was last focused. Switching becomes a manual act of finding the right window rather than a decision about what to work on.

At that point the problem has stopped being about session separation and has become about window management. Some readers reach for a tool built around that instead, keeping each web application in a window of its own rather than stacking accounts inside one browser. The differences worth checking before changing anything are covered in the Features page and the per application view in Workspaces, and the comparison against an established option of the same kind is set out in Compared with Wavebox.

What to change first

Before adding another profile, open the existing ones and check what each is actually holding. Most machines have one profile carrying real work and two or three that were created for a single task and never cleaned up. If the count is already past three and the daily friction is finding the right window rather than logging in, the fix is a different way of holding windows, which is the problem SpaceDeck is built around.