Firefox Containers Not Working? Diagnose It Before You Reinstall Anything
If you search for firefox containers not working, the cause is almost always one of three things: your Firefox build predates native Containers or the feature is switched off, the Multi-Account Containers add-on is disabled or cannot install, or you expected automatic site assignment the native preview does not include. A fourth pattern — cookies that collide anyway — has its own fix.
📌 TL;DR Executive Summary
- Core Takeaway: Containers became a native Firefox feature in version 153, so most “not working” reports are version, permission or expectation problems rather than bugs.
- Key Risk/Challenge: Containers isolate cookies and site storage only. Single sign-on tokens, browser fingerprints and your IP address stay shared, so some login collisions happen outside the container entirely.
- Recommended Solution: Update to Firefox 153 or newer, keep the add-on if you rely on automatic assignment or cross-device sync, and move to full browser profiles when accounts need separate cookies, fingerprints and proxies.
Which Container Feature Actually Broke?
Container complaints split into three buckets: the feature is missing completely, the feature is there but one specific action does nothing, or container tabs work and the accounts inside them still collide. Most reports of firefox containers not working land in the first two. The symptoms below map to those buckets, and the fixes do not overlap — identify yours before you touch a setting.
| Symptom | What it usually means | Fastest fix |
|---|---|---|
| No container entry in the tab right-click menu | Build older than Firefox 153, or Containers is off | Update Firefox, then search Settings for Containers |
| Add-on installed but greyed out | Extension disabled by the signing certificate or a version mismatch | Open about:addons, check the status, update Firefox |
| “Open external links in a container” lists no containers | Containers are off in Settings, or the add-on is disabled | Turn Containers on, then re-enable the add-on |
| Link to an external app does nothing | Add-on lacks the newer local file permission | Grant “Access local files on your computer” |
| The same login shows up in every container tab | The site is also open in a plain tab, or the tab was never containerised | Check the coloured tab label, close the plain tab |
| Sign-in bounces back to the login page | SAML or OIDC token cookie sits in a different container | Open the identity provider and the app in the same container |
| A prompt on every new tab | “Select a container for each new tab” is ticked | Untick it at the top of the Containers settings page |
If your symptom is not in that table, it may not be a container issue at all. The old “plugin container for Firefox has stopped working” message belongs to the retired NPAPI plugin architecture and has nothing to do with container tabs. For a full walkthrough of what containers do and how the settings are laid out, the Firefox Containers complete guide covers setup end to end.
Five Quick Wins, Ordered by Effort
Work through these in order. Each takes under five minutes, and the first two clear up most cases of firefox containers not working.
- Confirm your version. Native Containers landed in Firefox 153 on July 21, 2026. Check Settings, then About Firefox. If you are on 152 or older, nothing further in this list will work until you update.
- Check that the feature is on. Open Firefox Settings and search for Containers. The native version is managed from that surface, where you create containers and set names, colours and icons.
- Look at the add-on state. Open about:addons and find Multi-Account Containers. If it reads Disabled or cannot be verified, you are looking at the signing and version problem covered further down, not a broken container.
- Open a container tab deliberately. Right-click any tab and pick the container option, or long-press the new tab plus button. Mozilla recommends both routes, and they behave differently from the toolbar menu on some builds.
- Stop the per-tab prompt. If every new tab asks which container to use, untick “Select a container for each new tab” at the top of the Containers settings page.
How Containers Work, and Why They Fail in Specific Ways
Every container is its own cookie jar
Firefox keeps cookies, site storage and cached state separated per container. The same site opened in Work and in Shopping cannot see each other’s session, so you can stay signed into two accounts side by side in one window. Activity in one container is not visible to the others, which is the entire point of the feature. Native containers ship with four defaults — Personal, Work, Banking and Shopping — and you can add your own with custom names, colours and icons.
That design is also why breakage looks strange. Nothing crashes. A site simply does not see the cookie you assume it should, so it asks you to sign in again, and you read that as the container failing.
Single sign-on is where containers visibly break
Corporate logins use SAML or OIDC. You request the app, get redirected to the identity provider, then return with a token cookie. If the identity provider is open in Personal and the app in Work, the token lands in Personal and the app in Work never receives it. The result is a redirect loop or a login page that reappears forever. Put both domains in the same container, and test that pair on a low-risk account before you enable automatic assignment for those sites.
Firefox 153 tightened extension and local network permissions
Two changes in that release catch people out. Extensions can no longer read local files by default; that access became a separate permission called “Access local files on your computer”. Extensions that handle downloads or hand links to an external app can stop working until you grant it. Separately, Local Network Access is now on by default, so a page must ask permission before connecting to devices on your network or to an app on your machine. A container tab talking to a local development server looks broken until that permission is granted. The Firefox 153 release notes list both changes, plus Local Mode, which loads local directories through custom origins without running a web server.
Native Containers vs the Multi-Account Containers Add-On
Firefox 153 shipped Containers as a native preview, so basic use no longer needs an extension. That is also the source of a very common complaint: you update, expect your old rules to keep firing, and nothing happens. Mozilla has said not all Multi-Account Containers add-on features are available in the first-party version yet, and that the add-on can keep running alongside built-in containers without being uninstalled. Mozilla’s Containers preview announcement describes the split.
| Capability | Native Containers (153 preview) | Multi-Account Containers add-on |
|---|---|---|
| Works with no extension installed | Yes | No |
| Container tabs with cookie isolation | Yes | Yes |
| Custom names, colours and icons | Yes | Yes |
| Automatic site-to-container assignment | Not in the first-party version yet | Yes |
| Container sync between devices | Not in the first-party version yet | Yes |
| Mozilla VPN and custom proxy integration | Not in the first-party version yet | Yes |
| First available | Firefox 153, July 21, 2026 | February 8, 2017 |
If containers “stopped working” right after an update, this table is usually the whole story. The tabs still isolate cookies; the automatic site assignment you were relying on is the part that stayed with the add-on. If you manage several accounts per site, read up on multi-account management with containers before you rebuild your rules from scratch, because the order you assign sites matters when two containers point at the same domain.
Fixing Extension Install and Update Failures on Older Builds
If the container entry never appears and the add-on refuses to install at all, check the version number before anything else. Mozilla’s intermediate add-on signing root certificate expired on March 14, 2025, which disabled installed extensions and blocked new installs on Firefox versions older than 128, including ESR 115.13. A build that old cannot install a container extension no matter how many times you retry, so firefox containers not working is the only result you will get — the fix is to move to a supported release, not to reinstall the add-on.
Linux is the trap. On most distributions Firefox is packaged by the distro and does not auto-update, so the About Firefox screen can report that you are up to date while the bundled certificate is years old. Install the Mozilla build, or move to a release your package manager still supports. If you are stuck on an old build for policy reasons, the honest answer is that containers are not available to you there.
Windows has a separate startup failure worth knowing about. Firefox 153 could crash on launch when an update completed incompletely, tracked as Bug 1681745. Reinstalling Firefox over the existing installation repairs it, the fix shipped in 153.0.1, and bookmarks and passwords are unaffected by the repair. If the browser will not open at all, containers are not your problem yet.
When the Real Problem Is Mixed-Up Sessions, Not the Container
Sometimes firefox containers not working turns out to be the wrong diagnosis: the container behaves exactly as designed and the accounts still collide. That happens because containers isolate cookies and site storage, not the machine. Every container tab runs inside the same Firefox profile, so canvas and WebGL output, installed fonts, screen size and the IP address your traffic leaves from are identical across containers. If a site compares those signals and decides two logins belong to one person, the coloured tab label means nothing to it.
The second collision is plainer. An account gets opened once in a normal tab — from an email link, a bookmark, a redirect — and that site’s session now lives outside every container. Containers look broken, but the cookie you are fighting sits in the default context.
When work genuinely needs separation beyond cookies, the answer is not another container. It is separate browser profiles, each with its own cookie store, its own consistent fingerprint settings and its own proxy exit IP. Sendwin Browser takes that approach: a desktop app for Windows, macOS and Linux where every profile is isolated, takes its timezone, locale and geolocation from the proxy’s exit IP, and can be shared with a paid teammate so it opens already signed in. Send.win has no browser extension, and it is built for accounts you own or are authorised to manage. There is also a cloud browser option, running profiles on Send.win’s server in Finland, for machines where you cannot install anything. The trade-offs between the two approaches are laid out in this comparison of browser isolation vs container isolation.
How to Stop It Coming Back
- Check the tab label before you log in. One glance prevents the most common cause of “mixed-up” accounts.
- If you slip and open a managed account in a plain tab, sign out there first. Then return to the container and sign in again, so the session cookie belongs to the right context.
- Keep the identity provider and the app in the same container. Test the SSO round trip before you switch automatic assignment on for a whole domain.
- Update the add-on even if you use native containers. Automatic assignment and cross-device sync are still add-on features, and an out-of-date add-on is the most likely thing to break first.
- Use separate profiles when you need separate networks. Containers share one IP. If a task requires a different exit IP or a different browser identity, set up multiple Firefox profiles or use a profile manager, instead of stacking containers and hoping.
- Expect visual changes after Firefox 157. The September 29, 2026 release refreshed toolbars, the sidebar and menus, and enabled the new sidebar for everyone. If the container UI looks unfamiliar, that is the redesign. Setting sidebar.revamp to false in about:config restores the older sidebar, and the preference remains available until the end of 2027.
- Heed the encryption-key warning. Firefox 157 flags in the shield panel and in Settings when the browser has been configured to record encryption keys. That means something on the machine was set up to log encrypted traffic. It has nothing to do with containers, but it appears after the same update and often gets blamed on them.
How Send.win Helps With Firefox Containers Not Working
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).
🏆 Send.win Verdict
Containers are the right tool for keeping a personal and a work login apart inside one Firefox window, and for most problems in this article the fix is a version check, a permission grant or one same-container sign-in. Where containers stop helping is at the edge of the machine: shared fingerprints and one IP address behind every tab. If your work is managing client or brand accounts that must not touch each other at that level, Sendwin Browser gives each profile its own cookies, storage, fingerprint settings and proxy on Pro and Team plans, and a profile shared with a paid teammate opens already signed in.
See Send.win plans — plans from $19/mo with residential proxies included, or try the free cloud demo first if you want to see the environment before you commit.
Frequently Asked Questions
Why don’t containers show up after installing the extension?
Two causes cover almost every case. Either your Firefox build is older than Firefox 153, where native Containers arrived, or the extension is installed but disabled — check about:addons and look for a “could not be verified” or Disabled label. On builds older than Firefox 128, the expired add-on signing certificate blocks installation entirely, so the extension never activates.
Do I still need the Multi-Account Containers add-on in Firefox 153?
Not for basic use. Native Containers handle container tabs, cookie isolation and custom names, colours and icons without an extension. You still need the add-on for automatic site assignment, container sync between devices, and Mozilla VPN or custom proxy integration, which are not part of the first-party version yet.
Can I run the add-on and native containers at the same time?
Yes. Mozilla states that the add-on can run alongside built-in containers and that there is no need to uninstall it. In practice this is the recommended setup if you rely on automatic assignment, because the native version does not include it yet.
Why do my logins still get mixed up between container tabs?
The site is almost certainly also open in a normal tab, so its session cookie lives outside any container. Close the plain tab, sign out there, then sign in again inside the correct container. If the accounts share one IP address and one browser fingerprint, a site can still link them regardless of how the tabs are separated.
Why does single sign-on fail inside a container?
SAML and OIDC flows depend on a token cookie set by your identity provider. If the provider is open in one container and the application in another, the token never reaches the app, and you get a redirect loop. Open both the identity provider and the application in the same container and the flow completes normally.
Why did containers stop working on Linux after an update?
Firefox on most Linux distributions does not auto-update, so the About screen can report that you are up to date while the bundled signing certificate is stale. Older certificates block extension installs, which makes container extensions impossible to add. Install the Mozilla build or a newer packaged release.
Do Firefox containers give me a separate fingerprint or IP address?
No. Containers separate cookies, site storage and cached state within one Firefox profile. Canvas and WebGL output, installed fonts, screen size and the IP address your traffic leaves from stay the same across every container. When accounts need different network-level identities, use separate browser profiles with their own proxies instead.
Why did Firefox crash on startup after updating to 153?
A Windows startup crash followed some incomplete updates in that release, tracked as Bug 1681745. Reinstalling Firefox over the existing installation repairs it, and the underlying fix shipped in 153.0.1. Your bookmarks and saved passwords are not affected by the repair.