Auto Containers Firefox

Auto Containers

By: Shajirr
Automatically opens tabs in either temporary or permanent containers for domain isolation.

Features & Capabilities

This addon aims to provide automatic domain isolation using Firefox containers, to reduce cross-site data tracking.

Temporary containers

By default, each new domain will be opened in a temporary self-destructing container, that will be auto-deleted after all tabs using it are closed, along with all of their saved data. This process is fully automated.

Permanent containers

For sites that you use regularly, you can define rules to open them in permanent containers instead. This will allow you to keep their data (like active logins or preferences), but still prevent other sites from accessing it.

Rules for permanent containers can be added either from the addon's Options page, or from a popup opened by clicking the addon icon on the toolbar, which also has most likely suggestions which you can select. Popup will also list all the rules associated with the current tab's container, so you can quickly edit or delete any of them. Rules support wildcards.

Rules order does matter, they will be checked in the same order as you see them, although they are also auto-sorted to prevent more generic rules blocking more specific ones, so the user shouldn't have to worry about this in most cases.

Addon is made with the ease of use in mind, to automate container management as much as possible.

Usage instructions

  • Container style section in the popup menu is collapsible, in case you don't need it
  • When adding rules, container color / icon selection applies only to new containers, color / icon of already existing containers won't be overwritten
  • If you want to change icon / color of an existing container, then open / switch to a tab that is in that container, and after selecting icon / color in the popup menu, click "Apply to current container" button.
  • last color in the color selection grid is a theme accent color, it depends on which FF theme you're using
  • If you want to convert the currently opened container to a permanent one, in case you don't want to lose the data from your temp container - check the checkbox "Convert current temp container" when adding a rule. That will rename the current temp container to the same name that you added in the rule, and you will keep all the the data from it. Note that this works only for new containers, not if you select an existing container in the rule, as container merging is not possible by design.
  • In the Options page you can set the default icon / color for the temporary containers, or to have each assigned at random
Exclusions

There are cases where maintaining the same container even when navigating to a different domain is required, for example, when the login process is handled on a different domain, or when making payments and you're being redirected through multiple payment processor / bank pages. For such cases you can temporarily exclude the tab from domain isolation, to keep the tab in the same container. Right click anywhere on the page, select "Auto Containers" -> "Exclude tab from domain isolation". If the tab is added to exclusions list, the addon badge on the toolbar should show "EX". To remove the tab from exclusion list and restore domain isolation, select "Remove tab from exclusions" in the same menu. Note that the tab excluded from domain isolation will pass this status to any tabs opened from it (child tabs) - this is useful if the process you need to complete opens the next page as a new tab.

Reserved container names / special rules

You can activate special rules by using the specific reserved container names. Warning - these options can lead to breaking domain isolation.

  • #Default - will always open the matched address in a default Firefox container, which is the same as no container
  • #Ignore - the addon does nothing with a matched address. By default Firefox will assign the same container (or no container) as the tab its opened from.

Compatibility

This addon is incompatible with other addons that can automatically assign containers to tabs, as they will be interfering with each other, some examples of which include:

  • Firefox Multi-Account Containers
  • Temporary Containers
  • Containerise
  • Facebook / Amazon / etc. container - any site-specific container addons
Known issues / bugs
Suggested ideas / Plans
  • In Exclude Current Tab mode, a way to record and examine all domains browsed in this tab and then suggest a list of rules based on them, with the the user being able to select / edit these rules.

User Growth & Download Statistics

Manifest V2 Add-on
By:
Shajirr
Daily users:
6 -1
Rating:
4.25
(4)
Version:
2026.4.3.1 Last updated: 2026-04-03
Version code:
6207067
Creation date:
2025-08-27
Risk:
Moderate risk impact Moderate risk likelihood
Permissions:
Size:
40.12KB
URLs:
Website
Full description:
See detailed description
Source:
Firefox Add-ons Store
Data ingested on:
2026-06-25
Compare stats and ranking:

Contact the developer

Chrome-Stats does not own this Firefox add-on. Please use these information below to contact the Firefox add-on developer.
Developed by:
Shajirr
Firefox Add-ons Store
https://addons.mozilla.org/firefox/addon/auto-containers/
Website:
https://github.com/Shajirr/FF-Auto-Containers/issues

Permission Change History

2025-09-22: Version 2025.9.3 → 2025.9.22
Add Permissions: contextMenus

User Reviews

Thank you so much for this extension. I especially appreciate that it respects the rules even if they change the default behavior, like having a 'catch all' * filter that puts anything thats not filtered elsewhere into a 'default' container instead of a temp container is possible as well. The only 'issue' i noticed is that on the preferences page trying to hit the save button always throws an error such as: Invalid comma format on line (whatever): "*.android.com, Google Ecosystem". Format must be: Pattern, Name (no space before comma, space after comma) This happens even if all the rules in the list were added through the GUI and no changes are made. Currently it's only 'editable' for me through the GUI. Despite this, I love the extension! Let me know if there's anything I can do/any more information I can provide.
by Fi*****, 2026-03-29

This add-on was recommended by ChatGPT. What I like about it: ① Newly visited sites are quarantined by default, ② Only frequently used sites can be saved as containers afterward. The benefits: ① Lightbeam's graphs don't get messy, ② No more hassle with Firefox's bloated container tab list. A minor annoyance is that using domain names or double-byte characters in container names causes errors. I've been using both “Multi-Account Containers” and “Temporary Containers” until now, but Auto Containers alone seems sufficient.
by Fi*****, 2026-01-21

Doesn't work for purpose of following rules and sticking to well-organized containers; might as well disable and use private mode (which is not intent). No matter what I try, I cannot get it to open new links from outside browser into my defined container. Rules like *, my_container *.*, my_container don't seem to matter. Instead, they always open in random tmp_ containers without any of my session/cookies.
by Fi*****, 2026-01-07
View all user reviews ›

Is Auto Containers Safe?

Risk impact
Risk impact measures the level of extra permissions an extension has access to. A low risk impact extension cannot do much harms, whereas a high risk impact extension can do a lot of damage like stealing your password, bypassing your security settings, and accessing your personal data. High risk impact extensions are not necessarily malicious. However, if they do turn malicious, they can be very harmful.

Auto Containers requires a few sensitive permissions. Exercise caution before installing.

Risk impact analysis details
  • Critical Grants access to browser tabs, which can be used to track user browsing habits and history, presenting a privacy concern.
  • High ****** ********* ** * ****** ******** ******** ********** * ******* ******* *****
  • Medium ******* ******* ************* ***** *** ** ******* *** **** ******* ****** ******** *******
Risk likelihood
Risk likelihood measures the probability that a Firefox add-on may turn malicious. This is determined by the publisher and the Firefox add-on reputation on Firefox Add-ons Store, the amount of time the Firefox add-on has been around, and other signals about the Firefox add-on. Our algorithms are not perfect, and are subject to change as we discover new ways to detect malicious extensions. We recommend that you always exercise caution when installing a Firefox add-on.

Auto Containers is probably trust-worthy. Prefer other publishers if available. Exercise caution when installing this add-on.

Risk likelihood analysis details
  • High This extension has low user count. Unpopular extensions may not be stable or safe.
  • Medium **** ********* *** ******* ** *** **** * ******* *** ******* *** *** ** ****** ** *****
  • Low **** ********* *** ***** **** **** * ****** **** ***** ********** *** **** ****** ** ** ****** *** *****
  • Good **** ********* *** **** **** *******
Extension Guard
Extension Guard

Discover every extension in use, analyze risks, and enforce blocking policies with Extension Guard

Secure Your Browser
Upgrade to see full risk analysis details

Best Auto Containers Alternatives

Here are some Firefox add-ons that are similar to Auto Containers: