Does Zen Browser Have Multiple Profiles? The Straight Answer
Does Zen Browser have multiple profiles? Yes. Zen is a Firefox fork, so it inherits Firefox’s profile system: each profile is a separate folder on disk with its own cookies, logins, history, extensions and settings, created and launched from the about:profiles page. The catch is the interface — the profile icon that once sat in the top-left corner of the window is gone, so you have to know where to look.
📌 TL;DR Executive Summary
- Core Takeaway: Zen has real, separate profiles — separate cookie store, logins, history, its own
places.sqliteand its own extensions. You manage them inabout:profiles, because the old corner icon was removed. - Key Risk/Challenge: Workspaces look like profiles but are not: they split tabs inside one profile and share bookmarks, extensions and, by default, cookies. A second profile also needs
-no-remote, or Zen just refocuses the window you already have. - Recommended Solution: One profile per account or client, created in
about:profilesand launched from a shortcut with-Pplus-no-remote. When profiles need their own proxy, consistent fingerprint settings, cloud access and teammate sharing, that work belongs in Send.win.
What a Profile Actually Is in Zen Browser
A Zen profile is a folder. Inside it sit the files that make a browser feel like yours: cookies.sqlite for sessions, places.sqlite for bookmarks and history, logins.json with its companion key4.db for saved passwords, prefs.js for settings, and an extensions directory. Point Zen at a different folder and you get a different browser identity on the same machine — different sign-ins, different history, different extension set.
That inheritance is the whole answer to the profile question. It is not a Zen feature bolted on top; it is Gecko behaviour that Zen kept while redesigning nearly everything else. Zen is free and open source under MPL 2.0, first released on July 11, 2024, and ships for Windows, macOS and Linux — on Linux as Flatpak, AppImage and Tarball for x86_64 and ARM64. If you have ever set up Firefox profiles, every step below will feel familiar, because the underlying model is identical.
Profile, Workspace, Container — three different things
Zen ships three features people confuse constantly. A profile is a separate data directory and its own browser process. A Workspace is a named set of tabs and pinned tabs inside a single profile. A Container is Firefox’s cookie-jar mechanism, which Zen can bind to a Workspace. Only the first gives you an isolated environment; the other two organise work inside one.
How Zen’s Profile System Works Under the Hood
At startup Zen reads its list of known profiles and opens one of them. The control panel is the internal page about:profiles, which lists every profile the installation knows about, marks the one currently in use, and offers the same few actions per entry: set as default, launch in a new browser window, rename, and open the folder on disk. Everything below builds on those actions.
The switcher that disappeared
Earlier Zen builds put a profile button in the top-left of the window and shipped a dialog component called ZenProfileDialogUI. Both were removed in an earlier release, and the dialog has no direct replacement. Repository discussions point at a native profile switcher being prepared upstream in Firefox, which had not shipped when the Zen element was retired. The practical result: about:profiles is now the supported route, not a workaround around a missing menu.
The newer switcher behind a flag
Firefox Nightly has been building a Chrome-style profile menu, and Zen’s Twilight channel exposes something similar once you flip a preference. Open about:config, search for profiles.enabled and set it to true. Treat it as experimental — it is not on stable by default, and point releases ship often. Zen 1.23.3b landed on October 16, 2026, and 1.21.5b before it ran on Firefox 152.0.4 in July.
Why a second profile needs a second process
Zen behaves like Firefox at launch: run the executable again and you get a new window on the profile already running. The -P flag picks a profile by name at startup, and -no-remote (on macOS, the -n flag) stops the handoff to the running instance. Miss the second flag and your “work” window opens signed into your personal account.
about:profiles, then build a desktop shortcut with the launch flags baked in. Double-clicking “Client A” opens the right profile every time — no menu hunting, no chance of typing a client reply into the wrong window.
Why Isolated Profiles Matter — and Where Zen Stops
Anyone running several accounts of the same service on one computer hits shared state fast. A freelancer with two client ad accounts, a social media manager posting for three brands, a support agent reproducing a bug as a customer, a QA tester walking a checkout as a first-time buyer — each needs a session that does not leak into the others. One profile per account is the cleanest way to get that, and in Zen it costs nothing.
Two limits are worth knowing before you build a workflow on top. Profiles separate stored data, not the machine: every profile runs the same Zen build on the same hardware with the same fonts, GPU and screen size, and shares your network connection unless you change the connection settings inside that profile. And Zen has no proxy manager — each profile’s proxy is a manual setting, with no rotation and no per-profile proxy list to maintain from one place.
Who this affects most
Agencies holding client logins, sellers running several storefronts, and teams that hand accounts between people hit the same three walls: passwords travel through chat, profiles live on one laptop, and nobody can tell which window belongs to which client. Separate profiles fix the first wall only if people launch the correct one every time — which is what shortcuts, not memory, are for.
How to Create and Launch a Second Zen Profile
The setup takes a couple of minutes once you know where to click. Work through it in order the first time; after that it is shortcut management.
1. Create the profile
- Type
about:profilesin the address bar and press Enter. - Under “Create a New Profile”, click Create New Profile.
- Give it a name you will recognise in a taskbar — “Client A”, “Support QA”, “Personal” — and accept the suggested folder or pick your own.
- Finish. If the new profile does not open by itself, find it in the list and click Launch profile in new browser window.
2. Launch each profile from its own shortcut
The command differs by platform, but the shape is the same: executable, profile flag, no-remote flag.
| Platform | Command | What it does |
|---|---|---|
| Windows | zen.exe -P "Client A" -no-remote |
Starts a separate process on that profile from a shortcut target |
| Linux | zen -P "Client A" --no-remote |
Same flags after the binary name in a launcher, AppImage or Flatpak wrapper |
| macOS | open -na Zen --args -P "Client A" --no-remote |
-n forces a fresh instance so two profiles sit side by side |
Community reports confirm the plain zen.exe -P work form selects a profile on its own; add -no-remote when you need both open at once. Quote any name containing spaces, and rename profiles carefully — a shortcut pointing at a name that no longer exists opens the default profile instead, silently.
3. Enable the newer switcher (optional)
If you would rather have a Chrome-style menu than one shortcut per profile, open about:config and set profiles.enabled to true — the same preference Firefox Nightly users flip. On stable builds it may do nothing or appear only in Twilight, so keep about:profiles bookmarked as your fallback.
4. Migrate Firefox data into a profile (optional)
Zen’s own profile migration guide lists the files to copy into a new profile folder: places.sqlite, cookies.sqlite, cert9.db, key4.db, logins.json, prefs.js and the session store. Close both browsers first, then set the new profile as default in about:profiles.
key4.db and logins.json as a pair. One without the other leaves passwords the new profile cannot decrypt, and copying a live cookies.sqlite can leave you with a locked or half-written database.
Workspaces vs Profiles: What Is Actually Isolated
Workspaces are one of Zen’s best features and one of its most misunderstood. They separate tabs and pinned tabs, they switch with Cmd+1 through Cmd+8 for the first eight, and Split View shows up to four tabs in a grid. What they do not do is give you a second set of cookies — unless you bind a Container to a Workspace, in which case that Workspace’s sign-in lives in its own cookie jar. Everything else stays shared.
| Data | Separate profile | Workspace (default) | Workspace + Container |
|---|---|---|---|
| Tabs and pinned tabs | Own window | Separate tab set | Separate tab set |
| Cookies and sign-ins | Own cookie store | Shared | Separate cookie jar |
| Bookmarks and history | Own places.sqlite |
Shared | Shared |
| Extensions and settings | Own set | Shared | Shared |
| Default search engine | Per profile | Global | Global |
| Sync account | Per profile | Shared | Shared |
| Proxy setting | Manual, per profile | Shared | Shared |
| Hardware signals | Same machine, same build | Same | Same |
That last row matters more than it looks: splitting profiles does not change what a site can infer about your hardware, and it does not change your IP unless you configure a different proxy inside each profile. If you are weighing cookie-jar approaches against full directory separation, this Chrome profiles vs Firefox containers breakdown covers the same trade-off outside Zen.
A Workable Setup for Two to Five Accounts
Decide what has to be separate before you create anything. If two accounts on the same site only need different cookie jars, a Container bound to a Workspace is the lighter tool: one profile, two Workspaces, no second window. Go the profile route when you need different extension sets, different sync accounts, separate history, or two windows that must sit side by side as distinct tasks.
Once you commit to profiles, keep the routine boring:
- Name profiles after the account, not the person: “Client A — Ads”, “Client A — Store”, “QA — EU region”.
- Keep every launch shortcut in one folder so adding a client does not become a scavenger hunt through the Start menu.
- Decide Sync per profile. Two profiles signed into the same Mozilla account with Bookmarks enabled will merge bookmark sets on the next sync run, so leave Sync off where a clean set matters.
- Note the media gap. Zen’s FAQ says DRM-protected streaming does not work on Windows or macOS because the Widevine licence is missing, so a Netflix or Spotify profile will disappoint in every profile, not just one.
How Send.win Helps With Does Zen Browser Have Multiple Profiles
Send.win is a browser profile manager for professionals and teams: every account gets its own isolated browser profile.
- Isolated profiles – separate cookies, storage and sessions per profile
- Fingerprint protection – each profile keeps its own consistent browser fingerprint, so profiles never share one browser identity
- Desktop app + cloud browser – native app for Windows, macOS and Linux, or run profiles in the cloud with no install
- Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
- Team sharing – share a signed-in profile with a teammate without sharing the password
Try the free cloud demo — no install — or download the desktop app. Paid plans start at $19/month, and your first card purchase is covered by a 7-day money-back guarantee (see pricing).
Common Mistakes When Running Multiple Zen Profiles
- Treating Workspaces as profiles. Signing out of a service in one Workspace signs you out everywhere, because they share the cookie store. Bind a Container if you need real separation inside one profile.
- Expecting bookmarks to follow you. Each profile keeps its own
places.sqlite. Bookmarks cross over only when both profiles sign in to the same Mozilla account with Bookmarks enabled in Sync, and each one completes a sync run. A closed profile cannot sync until you reopen it. - Copying
places.sqliteby hand. It looks like a shortcut and is not: deletions recorded in one database can propagate and wipe entries in the other. Use Sync instead. - Launching without
-no-remote. The second launch hands off to the existing instance, and you end up in the wrong profile at the worst moment. - Assuming the flag is stable.
profiles.enabledis experimental and rides on frequent point releases. Check it against your installed build before you build a process around it. - Trusting community threads as documentation. Repository discussions are the best source for the removed switcher, but details shift; verify in
about:profileson the build you actually run.
Where Send.win Fits
Zen profiles are free, and for two or three accounts on one laptop they are genuinely enough. Friction arrives when profiles belong to work rather than to you: each profile’s proxy is a manual setting, nothing keeps a consistent per-profile browser identity across machines, the data never leaves that one computer, and handing a signed-in profile to a colleague means handing over the password.
Send.win is a browser profile manager built for that second case. The Sendwin Browser is a desktop app for Windows 10/11 (64-bit), macOS 12+ and Linux, built on Chromium; each isolated profile carries its own cookies, storage, sessions, fingerprint settings and proxy. Residential proxies are included on Pro and Team, or you bring your own HTTP/SOCKS5, with timezone, locale, WebRTC and geolocation following the proxy’s exit IP automatically. Fingerprint protection keeps each profile’s browser identity consistent and separate rather than shared — privacy protection applied per profile, not a claim about anyone else’s systems. For teams, sharing a profile with a paid teammate opens it already signed in, and the cloud browser runs profiles on Send.win’s server in Helsinki from any device, which helps when the person who needs the account is not on the machine that created it. If per-profile proxying is the specific problem, this guide to browser profiles with proxies covers the setup order. Note the boundary: there is no API, SDK, headless mode or Selenium/Playwright integration on any plan, so it stays a hands-on tool.
🏆 Send.win Verdict
Zen Browser answers the profile question well for a single machine: separate folders, separate cookies, separate extensions, no cost. It stops short where agency and team work begins — no proxy manager with rotation, no per-profile fingerprint settings, no shared access without passing credentials, and nothing that follows you to another device. Send.win covers exactly those gaps, and stays out of the way if you only need two profiles for yourself.
See Send.win plans — paid plans start at $19/mo with residential proxies and per-profile fingerprint protection included, backed by a 7-day money-back guarantee on your first card purchase. The free cloud demo needs no install.
Frequently Asked Questions
Does Zen Browser have multiple profiles like Chrome?
Yes, but the plumbing is Firefox’s rather than Chrome’s. Each profile is a separate folder with its own cookies, logins, history and extensions, managed at about:profiles. A Chrome-style avatar switcher exists behind the profiles.enabled preference in newer builds, but it is not the default on stable.
How do I create a new profile in Zen Browser?
Open about:profiles, click Create New Profile, give it a name and confirm the folder. If the new window does not open by itself, click Launch profile in new browser window in the list. From then on, start it from a shortcut that passes -P "name" -no-remote.
Where did the Zen profile switcher icon go?
It was removed in an earlier update, along with the older ZenProfileDialogUI component, which has no direct replacement. Community reports link the removal to a native profile switcher being prepared upstream in Firefox before it had shipped. Until that reaches stable, about:profiles is the dependable way in.
Are Zen Workspaces the same as profiles?
No. Workspaces split tabs and pinned tabs within one profile and share bookmarks, history, extensions and, by default, cookies. Binding a Container to a Workspace gives that Workspace its own cookie jar, which is enough to separate a work sign-in from a personal one. Even then, the default search engine stays global across all Workspaces.
How do I launch Zen with a specific profile?
Use the profile flag at startup: zen.exe -P "Client A" -no-remote on Windows, zen -P "Client A" --no-remote on Linux, or open -na Zen --args -P "Client A" --no-remote on macOS. The no-remote flag is what forces a separate instance instead of a new window on the running profile.
Do bookmarks and extensions sync between two Zen profiles?
Extensions do not — each profile keeps its own set. Bookmarks move only through Firefox Sync: both profiles must sign in to the same Mozilla account, have Bookmarks enabled in Sync settings, and complete a sync run while open. A closed profile cannot sync, and copying places.sqlite between folders is not a safe substitute because deletions can propagate.
Can I open two Zen profiles at the same time?
Yes, provided each starts as its own process using -no-remote or the macOS -n flag. You then have two independent windows, each with its own sign-ins and history, running side by side. Without those flags the second launch is absorbed by the instance already running.
Does a separate Zen profile change my IP address or fingerprint?
No. Profiles separate stored data; they all run the same browser build on the same hardware, with the same fonts, GPU and screen, and they share your network connection unless you set a different proxy inside each one. Consistent per-profile fingerprint settings and included residential proxies are features of a dedicated profile manager such as Send.win, not of Zen itself.