Chrome profiles vs separate Chrome copies on Mac: which should you use?

For most people, profiles inside one Chrome are the better choice: they use less memory, share one update, and each profile already keeps its own logins, history and extensions. Separate Chrome copies make sense only when you need each account to act like a truly separate app on your Mac. If the real problem is that all profiles share one Dock icon, you can fix that without copying Chrome.

The two approaches

Profiles in one Chrome. You add profiles from Chrome’s avatar menu. Each profile has its own cookies, history, bookmarks, saved passwords and extensions. All of them run inside the same Chrome app, so macOS sees one app with one Dock icon.

Separate copies of Chrome. Here each account runs as its own app. There are a few ways to get there:

• A separate data folder. You launch Chrome with the --user-data-dir flag pointing at a new folder. That gives you a second, fully separate Chrome with its own data.
• A duplicated Chrome.app. Tools like Unbundle build a standalone copy of Chrome.app for each profile, each with its own Dock icon.
• Instance apps. Mac App Store apps such as Parallel Spaces and Parall launch separate app instances with their own data and icons. See our Parallel Spaces comparison.

Memory

Every copy of Chrome runs its own set of processes. Profiles in a single Chrome share one browser process and a lot of the work behind it.

One published measurement by Superdock put numbers on this: three separate Chrome instances used about 4.6 GB across 33 processes, while one Chrome running three profiles used about 1.67 GB across 11 processes. That is roughly 2.8 times more memory for the separate instances in their test. Your numbers will vary with tabs and extensions.

Sign-ins

Profiles already keep sign-ins separate: your work account stays in the work profile, your personal one in the personal profile.

With a fresh --user-data-dir copy or a new instance app, you start with empty data. You sign in to every site again, set up saved passwords again, and turn on sync again if you use it.

Extensions

Each Chrome profile has its own extension list. Copies do too, but you install and configure them once per copy, which adds up.

Updates

With profiles there is one Chrome to update, and every profile gets the update at the same time.

Copies need more care. Unbundle handles this by rebuilding each copy on the next launch after Chrome updates. The DIY guide on Unbundle’s site copies Chrome.app and removes Chrome’s Keystone auto updater from each copy, which means those copies will not update themselves. Hand made copies leave you to keep them current, and an out of date browser is a security risk.

Disk space

With profiles, the Chrome app exists once and each profile stores only its own data.

A full copy of Chrome.app is large. Unbundle’s own FAQ says about 500 MB per profile, so five profiles take about 2.5 GB before any browsing data.

Isolation

This is where copies win. A separate copy is a separate app as far as macOS is concerned. That means:

• Its own entry when you press ⌘ Tab.
• It can be assigned to one desktop (Space) from its Dock icon’s Options menu.
• Quitting one copy does not close the others.
• macOS permissions, such as camera or microphone access, are handled per app.

When does that matter? It matters if you truly need two accounts to be walled off at the app level, for example a strict client policy, testing how a site behaves in a clean browser, or keeping one account pinned to its own desktop all day. For everyday separation, profiles already keep logins and data apart.

Side by side

	Profiles in one Chrome	Separate Chrome copies
Memory	Lower, shared browser process	Higher, one full browser per copy (about 2.8 times in Superdock’s test)
Sign-ins	Kept per profile, nothing to redo	Start empty, sign in again
Extensions	Per profile	Per copy, installed again in each
Updates	One Chrome, updates everything	Copies may need rebuilding; DIY copies lose the auto updater
Disk	Chrome.app exists once	About 500 MB per copy (Unbundle FAQ)
Dock icon	One shared icon by default	One icon per copy
⌘ Tab entry	One	One per copy
Isolation	Separate data, same app	Separate app

Getting one Dock icon per profile without copies

The biggest reason people choose copies is the Dock. macOS shows one icon per running app, so all profiles of one Chrome share a single icon.

Chrome Profile Switcher solves that part without copying Chrome. It is a small menu bar app from ZwayStudios that gives each profile its own Dock icon with the profile’s picture. Each icon is a tiny launcher of about 2 MB, and one real Chrome keeps running with the same logins, extensions and history, and no second browser in memory. Click an icon and that profile’s existing windows come forward; click again to cycle through them.

It does not give each profile a separate ⌘ Tab entry and it cannot pin a profile’s windows to a Space. If you need those, a copy based tool like Unbundle is the better fit, and we say so on our comparison page.

Our conclusion

For most people, use profiles in one Chrome and add per-profile Dock icons. You keep memory use down, updates simple and sign-ins intact, and you still get one icon per account. Choose separate copies only when you need app level isolation, and if you do, prefer a tool that keeps the copies updated.

For the full setup, read how to add multiple Chrome profiles to the Mac Dock, or browse all options on our compare page.

Questions

Are Chrome profiles secure enough to separate work and personal accounts? Each profile keeps its own cookies, history, passwords and extensions, so accounts stay apart for everyday use. If a policy requires app level separation, a separate copy gives you more isolation.

Why do separate Chrome copies use more memory? Each copy runs a full browser with its own processes. Profiles in one Chrome share the main browser process.

Will a copied Chrome.app update itself? Not reliably. Unbundle rebuilds its copies after Chrome updates, while hand made copies from its DIY guide have the auto updater removed.