Multiple Chrome profiles: what they separate and when you need more

Multiple Chrome profiles are the quickest way to keep a work Google account and a personal one apart on the same computer. Each profile gets its own cookies, history, bookmarks, saved passwords, extensions and sign-in. What profiles don't change is everything a website learns about your connection and your device: every profile uses the same IP address, the same proxy setting and almost the same fingerprint.

In short: Chrome profiles separate cookies, history, saved passwords, extensions and sign-in. They don't separate your IP address, your proxy or your device fingerprint. Use them for a few accounts of your own; use a browser profile manager when each profile needs its own proxy, its own consistent device values or team access.

This guide shows how to add and manage Chrome profiles using Google's own steps, explains exactly which parts are separated and which are shared, and helps you decide when Chrome profiles are enough and when a dedicated tool such as an antidetect browser fits the job better.

How do you create multiple Chrome profiles?

Open the profile menu at the top right of Chrome and choose "Add Chrome profile". That's the whole process; the steps below are from Google's Manage Chrome with multiple profiles help page, checked on 25 October 2026.

Add a profile

1. Open Chrome on your computer.
2. At the top right, select Profile, then Add Chrome profile.
3. Choose a name, photo and color scheme.

You can sign the new profile in to a Google Account or leave it signed out. Google notes that signing in sets the profile name to your account name and lets you save bookmarks, passwords and settings to that account.

Switch between profiles

1. At the top right, select Profile.
2. Choose the profile you want. It opens in its own window.

Edit a profile

1. Select Profile, then under "Other Chrome profiles" select Manage Chrome profiles.
2. On the profile you want to change, select More, then Edit.
3. Change the name, photo or color theme. Changes save automatically.

Delete a profile

1. Select Profile, then Manage Chrome profiles.
2. On the profile, select More, then Delete, and confirm.

Deleting is permanent on that computer. Google says the profile's bookmarks, history, passwords and other settings are erased from the computer. If the profile was syncing to a Google Account, what was saved to the account stays there.

A practical tip: give each profile a distinct color. When three windows are open side by side, the color is the fastest way to see which account you're about to post from.

What do Chrome profiles keep separate?

Each profile has its own folder of browser data, so stored state doesn't mix. Chromium's documentation on the user data directory explains that every profile is a subfolder (the first one is usually called Default) holding profile data "such as history, bookmarks, and cookies". On Windows that parent folder is %LOCALAPPDATA%\Google\Chrome\User Data; on a Mac it is ~/Library/Application Support/Google/Chrome.

In practice, a profile keeps these apart:

• Cookies and site storage. Logging in to a site in one profile doesn't log you in anywhere else.
• History, bookmarks and open tabs.
• Saved passwords and autofill data.
• Extensions. An extension installed in one profile isn't installed in the others. Google lists extensions among the things a signed-in profile saves to your Google Account, next to bookmarks, passwords and settings.
• Sign-in. Each profile can be signed in to a different Google Account, or none.

That is a real separation, and it's exactly what most people need: no logging out and back in, no work cookies in your personal browsing, no shopping history in your work account.

Google's help page adds one warning worth repeating. Profiles aren't locked from each other: anyone using your computer can switch to any Chrome profile on it and see what's there. Google's advice is to share your device only with people you trust.

What do Chrome profiles share?

All profiles in one Chrome installation run on the same computer, the same network and the same browser build. So anything a website reads from the network or the device is the same in every profile.

The same IP address

Every profile connects through your computer's internet connection, so every website sees the same public IP address no matter which profile you use.

Usually the same proxy

Chrome doesn't have a proxy field per profile. Chromium's network settings page says the Chromium network stack "uses the system network settings", the proxy you set in Windows or macOS for the whole computer. Chromium's proxy documentation names the ways to give Chrome its own proxy instead: a command-line flag such as --proxy-server, an extension that uses the chrome.proxy API, or an administrator policy. On most setups that means one proxy for everything, or extra work per window.

The same device fingerprint

A website can also read details of the browser and the device, which together form a browser fingerprint. Profiles don't change any of these:

So two Chrome profiles look to a website like the same browser on the same computer with different cookies. That's fine for keeping your own accounts tidy. It's not separation of identity.

You can see this for yourself: open our browser fingerprint test in two profiles and compare the results. Time zone, languages, user agent platform, screen and IP will match line for line.

Can you give each Chrome profile its own proxy?

Not from Chrome's settings. The workarounds exist, but each one has a cost.

• A proxy extension in each profile. Extensions are installed per profile, so a proxy extension can go into just the profile that needs it. You now manage proxy credentials inside extensions, and time zone and language still come from your computer, which may not match the proxy's location.
• A separate launch for each profile. You can start Chrome with its own --user-data-dir and --proxy-server flags, which runs a separate instance with its own data folder. Chromium notes that two running Chrome instances can't share the same user data directory, so you keep one folder and one shortcut per identity. This works for a handful of profiles and gets messy past that.
• A system proxy or VPN. This changes the IP for every profile at once, which defeats the point if you wanted different IPs.

None of these options adjusts the fingerprint. If your proxy exits in Germany but your computer's time zone is New York, a site sees a German IP with a New York clock, which is one of the mismatches described in our guide to browser fingerprinting.

When are Chrome profiles enough?

Chrome profiles are enough when the accounts are yours, there are only a few of them, and it doesn't matter that they come from the same computer and connection. Typical cases:

• A personal profile and a work profile with your employer's Google Workspace account.
• A separate profile for a side project, with its own bookmarks and extensions.
• A profile for a family member who borrows the laptop.
• A clean profile with no extensions for testing how a site behaves for a new visitor.

In all of these, sharing an IP and a device is normal: it's the same person on the same machine. Chrome is free, Google maintains it, and sync keeps each profile's bookmarks and passwords on your other devices.

When is an antidetect browser the better tool?

An antidetect browser fits better when each profile should behave like a separate browser: its own connection, its own consistent device details and its own place in a list that a team can share. Our pillar guide, what is an antidetect browser, explains how these tools work and what they can't do.

The usual reasons people outgrow Chrome profiles:

• Many client accounts. An agency running social accounts for 30 clients needs a way to find, label and open the right profile quickly. Chrome's profile menu wasn't built for that number.
• A proxy per profile. Each client or store gets its own proxy, and the time zone and language should follow that proxy's location instead of your computer's.
• Different fingerprint values per profile. Each profile reports its own stable values for canvas, WebGL, audio and similar signals, so two profiles don't look like the same browser.
• Team access. Assistants open profiles without seeing passwords, and only one person has a profile open at a time.

A browser profile manager such as Multime handles these. Each profile there is its own Chromium-based browser with its own cookies, storage, extensions, proxy and fingerprint settings. The proxy manager takes HTTP, HTTPS, SOCKS5 and SSH proxies, sends DNS through the proxy, and checks the exit IP to set the profile's time zone, language and location.

Be clear about the limits, though. A profile manager doesn't change everything Chrome profiles share. In ours, screen size is always your real screen, and custom font lists, media devices and speech voices aren't masked. On the Windows engine, canvas masking is switched off automatically because that engine build breaks text measuring when it's on. And platform rules still apply: a separate profile doesn't change what a site's terms allow, so check each platform's own policy before you run more than one account there.

Chrome profiles vs an antidetect browser at a glance

A simple way to decide

Ask three questions:

1. Whose accounts are these? If they're all yours and few, Chrome profiles are fine.
2. Should each one connect through a different IP? If yes, you need a proxy per profile, and Chrome only does that with workarounds.
3. Will other people open them? If assistants or colleagues need access with limits, you need a tool built for teams.

If the answer to the second or third question is yes, try a profile manager. Our free plan has 5 profiles and needs no card, which is enough to move a few accounts over and compare.