Firefox's Multi-Account Containers feature is one of the most underrated browser privacy and productivity tools available. After using it for two years, here's everything I know about it.
What Containers Actually Do
Containers isolate your browser sessions. Each container has its own:
- Cookie storage (sites can't see cookies from other containers)
- localStorage and sessionStorage
- IndexedDB
- Service Workers
Practical meaning: you can be logged into different accounts on the same service in different containers simultaneously. You can browse news sites in a container that doesn't share cookies with your work container.
The Privacy Case
Without containers, tracking pixels and cookies from one site can follow you across the web via cookie syncing and fingerprinting. Advertisers build profiles of your browsing behavior across many sites.
With containers:
- Work browsing and personal browsing are isolated from each other
- Sites in a "personal" container can't see your work session cookies
- You can put high-tracking sites (social media) in isolated containers that never touch your work or banking sessions
The Facebook Container extension (by Mozilla) does this automatically for Meta properties — it isolates every Facebook/Instagram/WhatsApp site into a dedicated container automatically.
The Productivity Case
For anyone managing multiple accounts:
- Two Gmail accounts simultaneously (work and personal)
- Multiple Slack workspaces without constantly logging in and out
- Two AWS console accounts without browser profiles
- Testing your own web app while staying logged into your personal accounts
The container color coding in tab bar makes it visually obvious which context you're in.
Setup That Actually Works
The setup I'd recommend:
- Install Multi-Account Containers
- Create: Work (one color), Personal (another color), one per long-term project if needed
- Set specific sites to always open in a specific container (right-click a link → "Open in Container")
- Install Facebook Container (by Mozilla) if you use Meta services
Don't over-engineer the container structure. Two or three containers handles most use cases. More than five becomes overhead.
The Shutdown Ritual
The most underrated use of containers: ending your workday. When I'm done working, I close all Work container tabs as a group.
This is a deliberate signal: work session is over. The container close has the same function as leaving the office — a defined end point. Without it, work bleeds into personal time because there's no clear separation.
What Containers Don't Do
- They don't prevent browser fingerprinting (your browser's fingerprint is the same across containers)
- They don't anonymize your IP address
- They don't encrypt your traffic
- They're not a substitute for a VPN or Tor if you need real anonymity
For most privacy use cases — keeping work and personal separated, preventing ad tracking across contexts — containers are sufficient. For high-stakes privacy (journalists, activists), you need stronger tools.
Pairing with a New Tab Extension
One interesting interaction: your new tab page loads in whatever your "default" container is (usually no container). Extensions like Weather & Clock Dashboard load outside of containers — they're browser extension pages, not regular web pages. This means your new tab weather/clock display is always available regardless of which container you're browsing in.
Top comments (0)