Chrome profiles are separate browser environments within a single Chrome installation. Each profile has its own bookmarks, saved passwords, browsing history, extensions, settings, and login sessions — completely isolated from every other profile on the same computer. Think of it as having multiple different browsers without actually installing multiple browsers. For the bigger picture, our How to Manage Google Chrome pulls everything together.
The most common use case: a Work profile signed into your work Google account (with work bookmarks, corporate extensions, work email always logged in) and a Personal profile with your personal setup. Switching between them takes one click. You’re never accidentally logged into personal accounts on work pages or vice versa.
Creating a new profile
Click the profile icon (your avatar or a generic icon) in the top-right corner of Chrome → “Add” at the bottom of the dropdown → “Continue without an account” to create a local profile without signing into Google, or sign in with a Google account to connect the profile to an account and enable sync.
The new profile opens in its own Chrome window. It’s a completely blank slate: no bookmarks, no extensions, no saved passwords. You build it up as you use it — or sign in with a Google account and let Chrome sync your data from that account immediately.
Managing existing profiles
Profile icon → “Manage profiles” → shows all profiles with options to edit each one. From here: rename a profile, change its avatar, remove it, or set whether it’s associated with a Google account. You can also reorder profiles if you switch between them frequently — the order affects which appears first in the picker.
Profile names matter practically: when you open a Chrome window from the taskbar or dock, the window title shows the profile name. If you have three different profile windows open: “Chrome – Work,” “Chrome – Personal,” and “Chrome – Client X” are distinguishable in the taskbar. Generic names (“Profile 1,” “Profile 2”) make this confusing. Name profiles meaningfully at creation.
Switching between profiles
Profile icon → select any other profile from the dropdown → Chrome opens a new window for that profile. Both profiles’ windows can be open simultaneously. You can have a Work Chrome window and a Personal Chrome window active at the same time, each completely separate, each in their own login sessions.
Keyboard shortcut: Ctrl+Shift+M also opens the profile picker. Useful when you want to switch without navigating to the toolbar with the mouse.
What’s isolated between profiles
The complete list of what stays separate:
- Bookmarks and bookmark bar configuration
- Saved passwords (each profile has its own password manager)
- Browsing history and search history
- Extensions (installed extensions and their settings)
- Login sessions (cookies) — being logged into Gmail in one profile doesn’t log you in in another
- Site permissions (notifications, location, camera, etc.)
- Chrome settings (startup pages, search engine, theme, font size)
- Chrome flags settings
- Downloads history (though files download to the same system folder by default)
Not isolated: the default download folder (all profiles save to the same system Downloads folder unless changed per-profile), Chrome version and updates (Chrome the application is shared), and installed plugins or system-level components. These are at the browser application level, not the profile level.
Profiles vs Incognito — the important distinction
Incognito doesn’t persist anything — when you close the window, the session, cookies, and history disappear. Profiles persist everything in that profile. Use Incognito when you want a temporary session that leaves no trace. Use a separate profile when you want a permanent, separate environment that you’ll return to repeatedly.
A common misuse: treating Incognito as a “second browser” by opening it alongside a normal window to access two different accounts on the same site. Incognito works for this temporarily but the session is lost when you close the incognito window. A second profile retains the login, the history, and the context — it’s the right tool for semi-permanent account separation.
Profile sync and Google accounts
Signing a profile into a Google account connects it to Chrome Sync — bookmarks, passwords, history, and extensions sync to the cloud and appear on any other device signed into the same account. Each profile can be signed into a different Google account, with each account’s data syncing independently.
A profile doesn’t have to be connected to a Google account. A local profile (no sign-in) stores everything locally on the device. If the computer is wiped or Chrome is reinstalled: local profile data is lost without a backup. Signed-in profiles can be restored by signing into Chrome on the new installation — the account’s synced data downloads automatically.
Our guide on Chrome account sign-in settings covers how signing into Chrome affects which Google account manages the browser, and our Chrome extension management covers installing and managing extensions across profiles. For Chrome Profile management in enterprise environments, Google’s Chrome Enterprise documentation covers managed profile configuration including forced sign-in and profile data policies.
Profile shortcuts on the Desktop
Chrome can create Desktop shortcuts that open a specific profile’s window directly. Right-click the Desktop → “New” → “Shortcut” → in the location field: "C:Program FilesGoogleChromeApplicationchrome.exe" --profile-directory="Profile 1". Change “Profile 1” to match the profile folder name (check %localappdata%GoogleChromeUser Data for folder names like “Default,” “Profile 1,” “Profile 2,” etc.).
This lets you have separate taskbar shortcuts for each Chrome profile — clicking “Chrome Work” opens directly in your Work profile, “Chrome Personal” opens in your Personal profile, without going through the profile switcher. More efficient for users who consistently work in specific profiles rather than switching between them during the day.
Use cases for multiple profiles
| Scenario | Profile setup |
| Work/personal separation | Work profile (work Google account) + Personal profile (personal account) |
| Client-specific browsing | One profile per client — separate bookmarks, logins, contexts |
| Family members sharing a computer | One profile per person — each with their own bookmarks, passwords, login sessions |
| Testing websites | Clean test profile with no extensions, no login state — baseline browser environment |
| Teaching/presentation mode | Clean profile with only relevant bookmarks and no personal data visible |
| Different search and content preferences | Profile with specific search engine, language, or accessibility settings |
The “testing” use case is underrated for developers and QA teams: a Chrome profile with no extensions and no login sessions is the closest thing to “a fresh user’s browser” without having a separate test machine. It’s faster to switch to a clean test profile than to reset an extension-heavy development profile for each test run.
Profile data storage location
Each profile stores its data in %localappdata%GoogleChromeUser Data → a folder named “Default” (the first profile) or “Profile 1,” “Profile 2,” etc. for additional profiles. Knowing this location is useful for: backing up a profile before a clean reinstall, copying a profile to a new machine manually, or troubleshooting by creating a fresh Default folder when the existing one is corrupted.
Profile folders can get large over time — a well-used profile with years of cached data, downloaded extensions, and stored passwords can reach multiple gigabytes. If Chrome is consuming more disk space than expected: checking the size of each profile folder in User Data identifies the storage consumers.
Chrome profiles are one of the more powerful but underused browser features. For anyone managing multiple contexts — work vs personal, multiple client projects, different personas for testing — profiles offer genuine separation that tabs and windows can’t provide. The setup is a one-time five-minute investment for a lasting workflow improvement.
Deleting a profile
Profile icon → Manage profiles → hover over the profile to delete → the three-dot menu → “Delete.” Chrome shows a warning that all data in that profile (bookmarks, passwords, history) will be permanently deleted. If the profile is signed into a Google account with sync enabled: the data also exists in the cloud and isn’t deleted from there — only the local copy is removed. You can re-sync by signing into a new profile with the same account.
For profiles not connected to a Google account: deletion is permanent. There’s no cloud copy to restore from. If you want to delete a profile but preserve its data: export bookmarks first (Bookmarks Manager → three dots → Export bookmarks) and export passwords (chrome://settings/passwords → three dots → Export) before deleting. These files can be imported into another profile or another browser.
Guest mode — profiles without persistence
Chrome’s Guest mode (Profile icon → Open guest window) creates a session that behaves like a temporary profile: no extensions, no saved data, no login sessions. When the guest window is closed: everything from that session is deleted. It’s appropriate for letting someone else use your computer without accessing your data, and for one-off sensitive sessions where you want zero trace.
Guest mode is more isolated than a regular profile because it has no access to your installed extensions, your bookmarks, or your saved passwords. It’s not just a clean profile — it can’t see any of your existing profile data at all. Regular profiles are isolated from each other but coexist in the same browser installation; Guest mode is completely separate.
Profile import from other browsers
When creating a new Chrome profile: Chrome offers to import bookmarks, passwords, and history from other browsers installed on the same machine. Chrome menu → Bookmarks → Import bookmarks and settings → select the source browser. This is useful when transitioning from Firefox or Edge to a new Chrome profile — your existing data comes across without manual export/import steps.
The import is one-directional and one-time: it copies data at import time. Changes made in the source browser after the import aren’t reflected in Chrome, and vice versa. For full migration: import once, then stop using the source browser so the data doesn’t diverge.
Chrome profiles are a feature that rewards intentional setup. Deciding upfront which contexts get separate profiles — and naming them clearly, connecting them to the right Google accounts, and installing context-appropriate extensions in each — creates a browsing environment that’s more organised and more private than trying to manage multiple contexts in a single profile. The investment is the 10 minutes to set up the second profile; the return is permanent context separation that makes every subsequent browsing session cleaner.
Enterprise profiles and managed Chrome
In organisation-managed Chrome environments: IT can configure profile behaviour through Google Admin Console or Active Directory policies. Managed profiles may require sign-in with the work Google Workspace account, restrict what data syncs, or prevent users from creating additional profiles on managed devices.
Managed Chrome installations often show a “Managed by [organisation]” indicator below the profile name. This means profile-level configurations — which extensions are installed, what the search engine is, whether personal account sign-in is allowed — are controlled at the organisation level rather than the individual level. Users can typically still use their managed profile normally; the restrictions appear in configuration options rather than day-to-day browsing.
Profile-specific search engines and home pages
Each Chrome profile can have a different default search engine, different home page, and different startup behaviour. This is part of what makes profiles genuinely useful for different contexts: a Development profile might use DuckDuckGo and start on localhost:3000; a Personal profile uses Google and starts on a news site; a Work profile uses the company’s internal search or Google Workspace search.
Configure per profile: chrome://settings/searchEngines → change while that profile is active. These settings don’t sync between profiles — they’re specific to that profile’s context, which is exactly what you want when profiles represent different use cases with different workflows.
For users who haven’t used Chrome profiles before: the single most useful first step is creating a separate work profile if you do any work browsing, or a separate personal profile if you’re on a work machine. The separation between work and personal browsing contexts — different login sessions, different history, different bookmarks — is something most people want and don’t realise is achievable within a single browser installation. One click to switch; complete isolation between the two environments. You might also run into Chrome Accessibility Features.
One thing worth emphasising again: on shared home computers, profiles are the right answer to the “multiple people use this computer” problem. Without profiles, everyone’s bookmarks, saved passwords, and browsing history accumulate in the same place. With one profile per person, each family member has their own completely separate browsing environment that doesn’t interfere with anyone else’s. It’s one of the practical quality-of-life improvements that makes a meaningful difference to daily computer use — especially compared to the alternative of everyone fighting over the same set of bookmarks and saved logins. Related: Chrome Energy Saver.
