Firefox's container tabs feature is one of the most underused privacy and workflow tools in any browser. Here's what they actually do and when to use them.
What Are Firefox Containers?
Containers are isolated browsing contexts. Each container has its own:
- Cookies
- localStorage and sessionStorage
- IndexedDB
- Cache
- Login state
A site in Container A cannot read cookies from Container B. You can be logged into the same website as different accounts in different containers simultaneously.
Built-in Container Types
Firefox ships with four built-in containers (visible in the Multi-Account Containers extension):
- Personal
- Work
- Banking
- Shopping
These are just labels — any container can hold any type of content. You can rename them and add more.
How to Use Containers
Option 1: Firefox Multi-Account Containers extension
Available from AMO. Gives you a full interface to:
- Create and name containers
- Assign specific sites to always open in a specific container (site assignment rules)
- Open new tabs in any container from the new tab menu
Option 2: Container tabs via keyboard
Long-press the new tab button (+ icon) to get a container picker.
Option 3: Temporary Containers extension
Creates a new isolated container for each tab automatically — the most aggressive isolation approach.
Use Case 1: Multiple Accounts on the Same Site
Log into GitHub as your work account in the "Work" container and your personal account in the "Personal" container. Both windows are open simultaneously, neither interfering.
Useful for:
- GitHub personal vs work accounts
- Multiple Google accounts (no more "Switch accounts" in Gmail)
- Separate Twitter/Mastodon accounts
- Testing different user roles on your own app
Use Case 2: Cross-Site Tracking Isolation
Social media buttons, analytics, and embedded content track you across the web when you're logged into those services. If your Facebook session is in a "Social" container and you never visit other sites in that container, Facebook's trackers on other sites can't link to your logged-in identity.
Setup: Use the Multi-Account Containers extension to create a "Social" container and assign facebook.com, instagram.com, and twitter.com to always open there. Browse everything else in the default context.
This is defense-in-depth alongside Total Cookie Protection (which Firefox has enabled by default since Firefox 103).
Use Case 3: Work-Personal Separation
Assign all work tools (Slack, Jira, work email) to the "Work" container. Everything else in "Personal" or Default.
Benefits:
- Work cookies expire when you close the work container
- No accidental login mixing
- Clear mental separation
Use Case 4: Testing and Development
Web developers: open your app's staging and production environments in different containers. Test with different session states without logging in/out.
Also useful: opening a site without any existing login state by using a fresh container.
What Containers Don't Do
Containers do NOT:
- Hide your IP address
- Prevent your browser fingerprint from being detected
- Isolate network requests (DNS, WebRTC)
- Protect against JS-based fingerprinting
For IP isolation you still need a VPN or Tor. Containers are about session/storage isolation, not network anonymity.
Total Cookie Protection vs Containers:
Firefox's default Total Cookie Protection already prevents third-party cookies from leaking across sites. Containers provide an additional layer: even first-party session isolation for sites where you're actively logged in.
Site Assignment Rules (The Key Feature)
The real power of Multi-Account Containers is automatic site assignment:
- Open the extension popup
- Click "Always Open in..." for a site you're on
- Every time you navigate to that site, Firefox automatically opens it in the assigned container
Once configured, you don't think about it — your work tools always open in Work, social sites always in Social. It becomes transparent.
My Container Setup
For a reasonable balance of privacy and convenience:
- Personal: default browsing, news, general
- Work: Slack, GitHub (work), email
- Social: Twitter, Reddit, Mastodon (keeps social tracking isolated)
- Banking: Financial sites (single container = I notice if something unexpected opens here)
- Shopping: Amazon, eBay (limits purchase history profiling across other contexts)
Five containers covers most cases without becoming maintenance overhead.
Top comments (0)