SuperdockChrome profiles vs separate Chrome instances on Mac: memory, logins and Dock icons
Short answer: Chrome profiles share one process and one set of logins and cost almost nothing extra; separate instances give each identity its own Dock icon but multiply memory and force a sign-in per copy. In our measurement, three instances used about 2.8 times the memory of one Chrome running the same three profiles. Most people pick instances for the separate Dock icon. A dock that separates profiles gives you that icon without them.
What is a Chrome profile?
A profile is a separate set of bookmarks, history, extensions, cookies and Google account inside one running Chrome. Switching profiles opens a new window; all windows share the same process, so memory for the browser engine, extensions and GPU process is paid once. Chrome shows the profile's avatar in the window's top corner, and puts the profile name at the end of the window title.
What is a separate Chrome instance?
An instance is Chrome launched with a different data folder, so macOS sees a second app. Each instance has its own process tree, its own Dock icon, and its own copy of everything: extensions load again, the GPU and network processes start again, and every Google account signs in again. Scripts and small utilities exist to automate the launch.
How do they compare?
| Profiles in one Chrome | Separate instances | |
|---|---|---|
| Memory | One engine, shared | One engine per identity; about 2.8x for three in our test |
| Logins | Sign in once per account | Sign in again in every instance |
| Extensions | Installed per profile, loaded once | Installed and loaded per instance |
| Dock icon | One icon for all profiles | One icon per instance |
| Updates | One Chrome to update | Each instance updates itself |
| Fragility | None | Launch scripts break on Chrome updates |
Is there a way to get per-profile Dock icons without instances?
Yes. Superdock replaces the Dock and attributes each Chrome window to its profile from the window title and Chrome's own profile list. The result is one Dock icon per profile with its avatar, only that profile's windows on hover and right-click, and Chrome untouched: one process, shared memory, logins intact.
How did we measure the memory figure?
On a Mac with three signed-in profiles, we compared Activity Monitor's total memory for all Chrome processes when the three profiles ran in one Chrome against three instances launched with separate data folders, each with the same extensions. One Chrome with three profiles and about 35 tabs used 1.67 GB across 11 processes; the three separate instances used about 4.6 GB across 33. The ratio was about 2.8 to 1 for the instances. Your figure will vary with extensions and open tabs. Each instance still pays for the browser engine again.
When separate instances are the right choice
If one identity must share nothing with the others, such as a client that forbids mixing accounts, a separate instance gives you that and profiles do not. Superdock adds no isolation beyond what Chrome profiles already have.
Frequently asked questions
Can I use both?
Yes. Superdock shows each separate instance as its own tile too, named after its launcher, next to the profile tiles of your main Chrome.
Do profile tiles survive a Chrome update?
Yes. Attribution reads window titles and Chrome's profile list, both stable across versions.
What if two profiles have the same name?
Superdock cannot tell them apart from titles alone and keeps their windows on the plain Chrome tile rather than guess. Give the profiles different names in Chrome.
Download free The dock is free. Chrome profile icons: 14 days free, then $7.99 once.
Sources
- Manage Chrome with multiple profiles, Google Chrome Help
Continue reading
Independent macOS developer and the author of Superdock. I switched to a Mac from Windows, lost the per profile taskbar buttons I relied on, and built the dock I wanted instead. I write these guides from daily use of the apps in them, and I answer the support email myself.