Firefox 153 adds native containers: separate work, shopping and accounts without an extension

Firefox 153 turns a feature familiar to advanced users into a native browser option. Containers place work, personal life, shopping and banking in separate tabs, each with its own cookies and site data. Two accounts on the same service can remain signed in side by side without requiring two browsers.

The feature arrives as a preview and brings the core of Mozilla's long-running Multi-Account Containers extension into Firefox. It makes isolation more visible and easier to enable, while the extension retains additional capabilities. A container is not a virtual machine, VPN or complete defense against tracking.

The short answer

The clearest use case is multiple accounts. A work mailbox can remain open in Work while a personal mailbox uses Personal, with no repeated sign-out process or temporary private window.

How the isolation works

A website normally stores a session identifier, preferences, a shopping cart and other local information in the browser. Tabs in the same profile can retrieve those values. A container creates a distinct storage area: cookies created in Work are unavailable in Personal.

This boundary supports sessions that would otherwise conflict. A developer can test an administrator and regular-user role. A contractor can separate customer accounts. Someone can keep a social network in a limited context instead of carrying its signed-in identity through normal browsing.

Color and icon identify the selected context. They do not create security by themselves; they help users notice that a banking tab opened under Shopping or a professional link escaped Work.

Enabling native containers

On eligible versions, the control appears in general settings under tabs and browsing. After container tabs are enabled, right-clicking a tab or holding the new-tab button opens the context selector.

Firefox allows containers to be named and assigned a color and icon. A small system is easier to maintain than a long list: Personal, Work, Shopping and Banking cover many needs. Names should describe a boundary rather than one website unless a specific service deserves its own space.

The first time a site opens in a new container, it requires a fresh login. That is expected evidence of separate storage. Data already present in the default session is not silently copied into every context.

The preview may not appear in every version or account at the same time. Update Firefox through an official source and check settings rather than installing an unknown extension that claims to unlock it.

What the extension still adds

Mozilla says the native preview does not yet reproduce every Multi-Account Containers feature. The extension can automatically assign a site to a container, synchronize configuration between devices and integrate Mozilla VPN or a separate proxy with individual spaces.

Existing users do not need to uninstall it. Mozilla supports using the extension alongside built-in containers while the preview evolves. Removing it too soon could eliminate an important rule, such as always opening a work application under Work.

Before migrating, inventory the rules, containers and integrations in actual use. If four manually selected spaces are sufficient, native mode may cover the workflow. If dozens of sites depend on automatic assignment or separate VPN routes, the extension still has a purpose.

Containers do not hide the IP address

All spaces normally share the same IP address, device, operating system and many browser characteristics. A site can therefore associate visits through other signals even when it cannot read another container's cookie.

Isolation reduces direct site-data sharing; it does not guarantee anonymity. Signing into the same account in two containers obviously tells the service that the same identity is involved. A shared email address, phone number or payment method can create the same link.

A VPN serves another function by changing the visible network address and protecting a connection path within its scope. Firefox profiles separate extensions, preferences and sometimes history more broadly. Private windows discard part of their data when closed. These tools address related problems but are not interchangeable.

Another layer against tracking

A social network opened only in its own container cannot directly read cookies stored in Personal. This may reduce tracking tied to a logged-in session when buttons or scripts from the same service appear on other websites.

Firefox also provides Enhanced Tracking Protection and Total Cookie Protection, which already isolate third-party cookies according to the site being visited. Containers add user-selected separation between identities or activities.

The mechanisms complement one another. Automatic protection operates broadly against known trackers and cross-site tracking. Containers organize explicitly distinct contexts, including cases where the same domain needs multiple legitimate logins.

A useful work boundary

On a personal computer occasionally used for work, a container can prevent a link from a professional message from picking up a personal session on the same service. It also reduces mistakes caused by publishing from the wrong account.

This separation may not satisfy an employer's security policy. Downloaded files remain on the same machine, extensions may retain broad permissions and local malware does not respect browser boundaries. Regulated data or sensitive administration may require a dedicated profile, operating-system account or managed device.

Administrators should treat containers as an organization and risk-reduction tool, not a boundary equivalent to an isolated environment. A browser or operating-system compromise may reach multiple contexts.

Container, profile or private window?

Containers suit identities that should persist and remain readily available. A private window handles temporary activity. A profile provides broader organization at the cost of separate windows and settings.

A setup method that stays manageable

1. begin with only three or four containers;
2. choose a stable color for each context;
3. sign into accounts again from the correct space;
4. close older sessions running in the default context;
5. check the indicator before publishing, paying or administering an account;
6. keep the extension when a native feature is missing;
7. test links opened from external applications;
8. avoid saving a work password in the wrong context;
9. keep Firefox and extensions updated;
10. review unused spaces and erase their data.

The first few days require manual discipline. A link can open in the wrong space when no rule assigns it automatically. Color should act as a warning before an action, not decoration that users stop noticing.

What Firefox 153 actually changes

By integrating containers, Mozilla makes a practical idea more accessible: multiple web identities can coexist without sharing one cookie jar. The feature reduces repeated logins, organizes browsing and adds a useful barrier against some account-based tracking.

Its value depends on defining the boundary accurately. Containers separate site data, not the entire computer. They do not hide the IP address, neutralize a malicious extension or replace a managed work device. Used for their intended purpose, however, they are one of Firefox 153's most practical improvements.