Firefox multi account containers, and where they stop helping
Firefox containers let one window hold several identities at once: a work Gmail in a blue tab, a personal Gmail in an orange tab, each with its own cookies, so neither account knows the other is signed in. Until this summer that meant installing the Multi-Account Containers add-on. Since Firefox 153, containers are also built into the browser itself as a preview feature, and the two can run side by side. This guide covers what changed, what a container actually separates, how to set one up in either form, and the specific points where containers stop solving the problem people install them for.
Facts about versions, features and numbers below were checked on Mozilla's own pages on October 18, 2026.
Built in or add-on: what changed in Firefox 153
On July 21, 2026, Mozilla announced native Containers in Firefox 153 as a preview. The announcement describes the feature as keeping separate parts of online life, such as work, shopping, personal and banking, signed into different accounts in the same window, with cookies and ad tracking isolated inside each container. The Firefox 153 release notes carry the same description.
The preview covers three things: opening tabs in a specific container, creating and managing containers with custom names, colours and icons, and controlling the setup from Firefox Settings. Mozilla is explicit that not every feature of the add-on is in the built-in version yet, and that existing add-on users do not need to do anything. The add-on can keep running alongside the built-in containers, and there is no need to uninstall it.
The add-on itself is still maintained. Its listing on Firefox Add-ons shows version 8.3.8, last updated June 25, 2026, with 427,600 users and a 4.6 rating from 8,077 reviews. It is published by Firefox under the Mozilla Public License 2.0, and its source sits in the mozilla/multi-account-containers repository on GitHub. The current Firefox release on Mozilla's release notes page is 158.0, so any up-to-date Firefox already has the built-in preview.
Which one to use comes down to a simple rule:
- Built-in containers are enough for opening tabs as Work, Personal or Shopping and keeping their cookies apart.
- The add-on is still the place for the extras that the preview has not caught up with, including the Mozilla VPN integration described on its listing.
Running both is supported, so there is no need to choose on day one.
What a container actually separates
A container is not a separate browser. It is a label added to every website's storage. Mozilla's technical notes on the Containers project list exactly what that label keeps apart and what it does not.
| Separated by container | Not separated |
|---|---|
| Cookies | Browsing history |
| localStorage | Bookmarks |
| indexedDB | Saved passwords |
| HTTP data cache | Saved search and form data |
| Image cache | Exceptions for invalid TLS certificates |
The left column is what makes two logins work. Gmail, Slack and Notion all keep the signed-in session in cookies and site storage, so a tab in the Work container and a tab in the Personal container each present their own session to the site.
The right column is where surprises come from. History is shared, so a page visited in the Personal container shows up in the address bar suggestions while working in the Work container. Saved passwords are shared on purpose, which is convenient for filling logins but means the password manager does not know which account belongs where. The same notes record that a user may browse in the Home container and then not understand why that history appears in the Work container. That is expected behavior, not a bug.
Containers separate sessions, not lives. If the goal is for a colleague looking at a work laptop to see nothing personal, a separate Firefox profile is the correct tool, not a container.
Setting up containers, step by step
With the built-in preview (Firefox 153 or later)
- Right-click any tab, or long-press the new tab (+) button, and choose to open a container tab.
- Pick an existing container, or go to Firefox Settings to create one.
- In Settings, give the container a name, a colour and an icon. Short names such as "Client A" or "Personal" read best on the tab.
The coloured line on each tab shows which container it belongs to, so a glance at the tab strip shows which identity is in use.
With the Multi-Account Containers add-on
- Install it from the add-on listing above.
- Click the Containers icon in the toolbar to edit containers: change their colours, names and icons, or add new ones.
- Long-click the new tab button to open a tab directly in a chosen container.
Keep the list short. Five containers that are actually used work better than ten that blur together.
The one decision worth making first
Decide what a container represents before creating any. The two patterns that hold up over months are one container per account (Work Google, Personal Google, Client A Google) and one container per client (everything for Client A, across all services). Mixing the two, such as one container per service in some cases and one per client in others, is the most common reason a setup becomes confusing after a few weeks.
Mozilla VPN per container
The add-on listing describes a feature that the built-in preview does not mention: individual containers can be connected to Mozilla VPN. Mozilla's example is shopping while travelling abroad but checking a bank account from a server in the home country. Each container can be routed through a different VPN location while the others use the normal connection.
That makes the add-on more than a cookie separator for people who need different locations for different accounts. The integration requires an active Mozilla VPN subscription. Availability depends on the country: Mozilla's VPN pricing page shows a waitlist instead of plans where the service is not offered, so check that page from the country where it will be used before planning around it.
What the add-on asks for
Before installing, it is worth reading the permissions on the listing, because an extension that touches every tab needs broad access. The required permissions are: access browsing history, monitor extension usage and manage themes, access browser tabs, and access data for all websites. The optional ones, requested only when a feature needs them, are exchanging messages with programs other than Firefox, reading and modifying bookmarks, clearing recent browsing history, cookies and related data, and controlling browser proxy settings. The proxy permission is what per-container VPN routing relies on. The listing also states that the developer says the extension does not require data collection.
Of the 8,077 reviews, 6,343 give five stars and 322 give one star. The rest are spread across two, three and four stars.
A worked example: three Google accounts on one Mac
Consider a common setup: a company Google Workspace account, a personal Gmail, and a client's Google Workspace account that a freelancer was invited into.
With containers, that becomes three containers named Work, Personal and Client, each opened once with Gmail and Google Calendar signed in to the matching account. From then on, each container tab presents its own session, so all three inboxes can stay open in one window.
Three things happen in the first week. The address bar suggests pages from all three accounts, because history is shared. The password manager offers every saved Google password on every Google sign-in page, because saved passwords are shared. And a calendar invitation link clicked in the Mail app opens in an ordinary tab with none of the three accounts, so it has to be copied into the right container tab.
None of these break the setup. They are the cost of keeping everything in one browser, and they grow with the number of accounts. With three accounts the cost is small. With eight, it is a large part of the day.
Where containers stop helping
Containers solve the two-accounts-on-one-site problem well inside Firefox. People who live in a dozen web apps all day tend to run into the same four limits.
1. Links from other apps land in the default context. A link clicked in Mail, Messages or a chat app opens in an ordinary Firefox tab, outside any container. When the same site is used with two accounts, nothing in the link says which account it was meant for, so the page opens either signed out or signed in as the wrong person, and has to be reopened by hand in the right container.
2. One tab strip holds every identity. Containers colour the tabs but keep them in the same window and the same strip. With twenty tabs across four containers, finding the right Slack becomes a scan of colours. Firefox profiles avoid this by giving each identity its own window, at the cost of losing the one-window convenience that made containers attractive.
3. Extensions see every container. Extensions run across the whole browser. A password manager, an ad blocker or a grammar checker behaves the same in every container, which is usually what is wanted, but it means containers are not a way to keep an extension away from one account.
4. Web apps still behave like tabs. Notifications, badges and unread counts belong to tabs, not to the account. If the Work container's Gmail tab is closed, its notifications stop. Nothing in the container model keeps an app running in the background the way a dedicated app would.
None of these are flaws in the feature. Containers were designed to separate cookies inside a general-purpose browser, and they do that. The limits appear when they are asked to act as a workspace for apps that stay open all day.
Containers compared with the alternatives
| Approach | Separates logins | Separate history and passwords | One window | Where it fits |
|---|---|---|---|---|
| Firefox containers | Yes | No | Yes | Two or three accounts on the same site, occasional switching |
| Firefox or Chrome profiles | Yes | Yes | No, one window per profile | Strict separation of work and personal |
| Private windows | Only for that session | Nothing is kept | No | One-off sign-in, nothing remembered |
| A browser that gives each web app its own space | Yes, per app | Per app | Yes | Many web apps and accounts open all day |
The last row is a different kind of tool. A multi-account browser for macOS keeps each web app in its own cookie container, so three Gmail accounts can stay signed in at once and a link from Slack opens in the app and account it belongs to. The Workspaces page shows how apps are grouped and isolated, and Pricing lists which parts are free. For readers who mainly need two accounts on one site occasionally, Firefox containers remain the lighter option.
What to change first
Update Firefox to the current release, try the built-in containers with one container per account, and keep the add-on only if per-container VPN routing or another add-on feature is needed. If the setup starts to feel like managing colours rather than work, per-app separation such as SpaceDeck is the next step.
Frequently asked questions
Do I still need the Multi-Account Containers add-on in Firefox 153 or later?
Not for basic use. Firefox 153 added containers as a built-in preview, covering container tabs and creating containers with custom names, colours and icons. Mozilla says not all add-on features are in the built-in version yet, and the add-on can run alongside it without being uninstalled.
Do Firefox containers keep history and passwords separate?
No. Mozilla's project notes list cookies, localStorage, indexedDB and caches as separated, while browsing history, bookmarks, saved passwords and form data are shared across containers. For full separation, use a separate Firefox profile.
Can I sign into two Gmail accounts at the same time with containers?
Yes. Open Gmail in one container tab and sign into the first account, then open Gmail in a tab of a different container and sign into the second. Each container keeps its own cookies, so both stay signed in within the same window.
Are Firefox containers the same as private browsing?
No. A private window forgets everything when it closes. A container keeps its cookies between sessions, so the accounts inside it stay signed in from one day to the next. Containers are for keeping identities apart, private windows are for leaving no trace.
Can containers use different VPN locations?
With the Multi-Account Containers add-on and an active Mozilla VPN subscription, individual containers can be routed through Mozilla VPN, each through its own server location. The built-in preview does not mention this, and Mozilla VPN is not offered in every country.