How to add multiple Chrome profiles to the Mac Dock
Short answer: macOS cannot pin an individual Chrome profile to the Dock, and Chrome offers no setting for it. The only thing that works is a separate application bundle for each profile. You can build those by hand with Automator, generate them with Epichrome, or have Okie Dockie create them for you in two clicks — and only the last one returns you to the window that profile already had open instead of launching a new one.
On this page
Why the Dock only gives you one Chrome icon
The macOS Dock holds applications. Google Chrome is one application, and every profile you have — Personal, Work, a client account, a throwaway — lives inside it. When you drag Chrome to the Dock you are pinning the program, not a profile, so the icon has no idea which of your five identities you meant. Click it and you get whichever profile Chrome happens to consider current.
This matters more than it sounds. Chrome profiles are the cleanest way to keep work and personal life apart: separate cookies, separate logins, separate extensions, separate history, separate saved passwords. People who use them properly often run three or four at once. And then the Dock, the one place on a Mac designed for switching between things, treats all of them as a single blob.
Windows users get this for free. Chrome on Windows writes a per-profile shortcut to the desktop and taskbar automatically, complete with the profile's avatar. On macOS that feature simply was never built.
Method 1: Chrome's own "Create Shortcut"
Chrome does have a Save and share → Create shortcut item hiding in its menu. It is the first thing everybody tries, and it does not do what you want.
It creates a shortcut to a website, not a profile. You get an icon that opens one specific page, and when "Open as window" is ticked the result is a stripped-down window with no tabs, no address bar and no extensions toolbar. For a web app like Gmail that is sometimes what you want. As a way to reach a whole browser profile, it is the wrong tool entirely.
Method 2: an Automator or shell launcher
The next thing people find is the command-line flag. Chrome accepts
--profile-directory, so this really does open your Work profile:
open -na "Google Chrome" --args --profile-directory="Profile 1"
Wrap that in an Automator application, give it a nice icon, drag it to the Dock and you have a per-profile launcher. Thousands of people run exactly this setup.
It has two problems, one cosmetic and one that will wear you down.
The cosmetic one: your profile directory is not called "Work". It is called
Profile 1, Profile 7, or Default for whichever
profile you created first. You have to go digging in
~/Library/Application Support/Google/Chrome/Local State to find out which
number is which, and the numbering does not survive a profile being deleted.
The real one: open -na always opens a new window. The -n
flag means "new instance". Every single click gives you another empty Work window on top of
the four Work windows you already had open. After a day you are drowning in duplicates, and
the one thing you actually wanted — take me back to the Work window with my email in
it — never happens.
Dropping the -n does not fix it either; Chrome treats a plain
open with a profile argument as a launch request and answers it the same way.
There is no flag anywhere in Chrome that means "focus the window this profile already
has". We go into why in
detail here.
Method 3: Epichrome
Epichrome is an open-source tool that builds standalone Chrome-based applications. Its developer has since ended development; the final release is 2.4.27. Each one is a real Mac app with its own icon, and because it is a genuine separate app, the Dock treats it properly — clicking it goes to its window.
"Standalone" here means that an Epichrome app gets its own browser data directory. It is not your Work profile; it is a new, empty profile that happens to run the same browser engine. You log in and install extensions in it separately, and it keeps its own browsing data. Updates need the Epichrome runtime kept in step, and each app is built through a multi-step wizard.
That separation suits a client account that should share nothing with your everyday browser. It is a different setup from putting the profiles you already have into the Dock.
Method 4: Okie Dockie
This is the approach Okie Dockie takes.
Okie Dockie reads the profiles Chrome already knows about — the real ones, under their real names — and builds a small launcher application for each one you tick. Setup:
- Download and open Okie Dockie. It lives in the menu bar.
- Allow it under System Settings → Privacy & Security → Accessibility. That is the only interface macOS provides for focusing another app's windows, so every window feature depends on it.
- Click the menu bar icon and choose Chrome Profiles.
- Tick the profiles you want in the Dock.
Each ticked profile gets a Dock icon badged with that profile's own picture, so Personal, Work and Client are distinguishable at a glance rather than being three identical Chrome circles.
The part that matters day to day is what a click does. Okie Dockie keeps track of which Chrome window belongs to which profile, so:
- Click a profile icon and the window that profile already has open comes forward.
- Click again and it cycles to that profile's next window, if there is one.
- Only when the profile has no window at all does it launch a new one.
Nothing about your profiles changes — same logins, same extensions, same history, same passwords. Nothing is copied or duplicated. Remove a Dock icon and Chrome is untouched.
Side by side
| Approach | Real profile names | Returns to open window | Keeps your logins | Effort |
|---|---|---|---|---|
| Chrome "Create shortcut" | No | No | Yes | Low |
Automator + open -na | No — folder numbers | No, new window every time | Yes | Medium, per profile |
| Epichrome | You name them | Yes | No — fresh profile | Wizard per app |
| Okie Dockie | Yes | Yes | Yes | Two clicks |
Epichrome creates a separate browser with its own data; Okie Dockie adds Dock icons for the Chrome profiles you already use.
Get every Chrome profile into your Dock
Okie Dockie builds a real Dock icon for each Chrome profile you use, badged with that profile's own picture. Click one and you land back in the window it already had open.
Everything except Chrome profile icons is free forever, and the profile icons come with a 7-day free trial that starts on its own — no sign-up, no card. macOS 13+, Apple Silicon and Intel.
Frequently asked questions
Can I add a Chrome profile to the Dock without any extra software?
Only partly. You can build an Automator application that runs open -na "Google Chrome" --args --profile-directory="Profile 1" and drag it to the Dock. It will open the right profile, but it opens a brand new window on every click rather than returning to the window that profile already has open, and you have to work out which numbered folder corresponds to which profile.
How do I find my Chrome profile directory name on a Mac?
Open chrome://version in the profile you want and read the Profile Path line. The last folder is the directory name — Default, Profile 1, Profile 2 and so on. The friendly name you see in Chrome is stored separately in the Local State file, which is why command-line launchers cannot use it.
Does giving each profile a Dock icon use more memory or run a second browser?
No. The launcher applications are tiny and only tell the Chrome you already have which profile to show. There is one Chrome running, with the same profiles it always had. Epichrome-style apps are different — those really are separate browser instances with separate data.
Will this work with Chrome Beta, Dev or Canary?
Yes. Okie Dockie handles Chrome plus the Beta, Dev and Canary channels. Safari cannot be supported by any tool, because it accepts no profile argument and exposes no list of its profiles.
Do the Dock icons survive a Chrome update or a Mac restart?
Yes. The launchers are ordinary applications in your Applications folder and the Dock entries are ordinary Dock entries. Chrome updating does not touch them.
Was this guide helpful?
Thank you — that tells me what to write next.