21-07-2026 03:34 AM
I'm excited to announce that as of Firefox version 153, Containers are now built into the browser. More information can be found in this blog post.
In this preview release, you can:Open tabs in specifications containers:
21-07-2026 12:54 PM - edited 21-07-2026 12:54 PM
For my workflow, it would be ideal if a window could be configured with a default container, such that opening a new tab here using a keyboard shortcut would have this configured container assigned.
I know that browser profiles is a way I can get that behavior, but that has its own issues.
21-07-2026 12:59 PM
I'd like to know how it relates to the cookie isolation feature that we have now. I mean the "isolate cross-site cookies" setting. Will it work together, or will the isolation become obsolete?
21-07-2026 01:29 PM
Long time user of Multi account containers here. This is a killer Firefox feature for me as a developer. Testing IAM flows, doing demos where I'm playing multiple users interacting, keeping different sessions open so I can juggle my multiple codex subs, all valuable use cases. I find trying to do the equivalent on Chrome enormously frustrating.
Colleagues have to do demos with one edge window, one chrome window, one incognito window - agony!
21-07-2026 01:42 PM
I think profiles, the already-existing feature would allow that, for you and your colleagues, both in Firefox and in Chrome.
21-07-2026 01:44 PM
Yeah if I wanted to have to deal with lots of windows. Having per tab containers is super nice, more than one browser window per screen and I'm instantly lost trying to remember which window has which tab.
21-07-2026 02:38 PM
You'll get equally lost with containers then.
21-07-2026 10:01 PM
You might need to re read the announcement
22-07-2026 01:00 PM
I personally skipped the Profiles feature.
For many things I do want some shared things. Like bookmarks, history. But just separated session and whatever that entails.
I like the ease of multi containers. Don't want to setup complete separate profiles.
21-07-2026 07:21 PM - edited 21-07-2026 07:26 PM
I'm glad to see this becoming a mainstream focus for Firefox. Thank you.
Could you clarify what exactly is new in Firefox 153? I've been using containers in Firefox for years at this point, but I've never installed the "Firefox Multi-Account Containers" extension (only the "Facebook Container" extension, which enables container-tab features that seem to date back as far as Firefox 57).
The official release notes for Firefox 153 just list containers as "new", not as "now enabled by default" or anything.
22-07-2026 12:31 AM
The fact that the functionality is now built into Firefox, rather than the add-on, is the new part.
23-07-2026 02:03 AM
I have a couple of related questions as well:
1) Comparing the new built-in containers in Firefox 153 with the Facebook Containers extension, are the caveats in the support link below still valid?
How is Facebook Container different from Multi-account Containers?
https://support.mozilla.org/en-US/kb/how-facebook-container-different-multi-account-con
2) So if I currently uninstall the Facebook Containers extension, I will lose some functionality (as per the link above), right?
Very good move to make it built-in, looking forward to the future of this!
22-07-2026 02:55 AM
Agreed. Also glad to see them focusing more on this feature!
22-07-2026 08:34 AM - edited 22-07-2026 08:40 AM
@tree_frog, yes I too was wondering what aspect of containers is new, as my understanding is that the functionality has been available (without add-ons) for years?
But if the developers are adding more options to the native Containers then I have a suggestion. One that I know I am not the first to make.
I did use the Firefox Multi-Account Containers add-on in the past, and while it generally did the job very well, there was one major niggle. The fact that while you can set auto-switching rules to assign different sites to different containers, there was no quick way to temporarily suspend these auto-switching rules.
As There are occasions where, for example, you might want a site that would normally open in a different container to open in the current one, as a one-off.
But there seemed to be no way to do this without modifying the add-on's internal settings or site lists, and then modifying them back afterwards.
So my suggestion would be for there to be a toggle button somewhere, or a hotkey, that when activated cancels all forced auto-switching rules and just lets any site open in the current container.
Again, I know that something like this has been requested many times, but if the developers have containers currently in mind, then hopefully they will consider this suggestion for a method to temporarily toggle off site assignments.
22-07-2026 01:01 PM
Sometimes that would indeed come in handy!
I would sometimes want multiple Google sessions open. Not have them forced into the one container.
22-07-2026 12:12 PM
Firefox Multi-Account Containers is one of the reasons why I use Firefox as my main browser.
I'd love to see the containers becoming more integrated with Firefox Sync.
And since we are talking about Sync I will allow myself to go off-topic for a second and say that it would be really helpful if the Firefox team started to maintain an official docker container for Firefox sync server and fxa. I know lots of people would love to selfhost these services but Mozilla could help us a little bit by making it easier with official containers and instructions.
22-07-2026 01:04 PM
A feature that the add-on lacks is the choice to keep more separated in the container. Not all. Just some; like keeping history and bookmarks limited to a container by itself.
Profiles give that, I guess. I haven't tried it. Using that next to containers seemed too much.
23-07-2026 04:45 AM
The two most important: Open in NEW TAB & Open In NEW WINDOW.
Click memory expects that order; any NEW options should be added AFTER Open in NEW WINDOW!
Please move Open in NEW CONTAINER after NEW WINDOW.