Brave’s New Container Tabs: What They Do and How to Use Them

Intro

If you manage multiple online accounts or want to keep your work browsing separate from personal browsing, you’ve probably wished your browser could do this natively without a separate profile. Brave has recently added a built-in container feature that addresses exactly that. It isolates your sessions so that cookies and site data from one container don’t leak into another. This is not just about reducing clutter – it’s a meaningful privacy gain.

What Happened

Brave introduced container tabs as a built-in feature in a recent update (likely version 1.70 or later; check your browser’s “About Brave” for the exact version). The feature was previously available through extensions or in competing browsers like Firefox, where Mozilla’s Multi-Account Containers have been popular for years. Brave’s implementation works similarly but integrates directly with the browser’s privacy tools such as Shields and its built-in ad blocker.

Why It Matters

Container tabs prevent cross-site tracking and data leakage on a fundamental level. When you visit a website inside one container, it cannot access cookies or storage from another container. This means you can be logged into your work Google account in one container and your personal Google account in another without them interfering. It also reduces the ability of third-party trackers to build a unified profile of your activity across contexts.

For workflow flexibility, containers let you assign different color labels and names (e.g., “Work,” “Shopping,” “Social”). You can keep your shopping session from influencing the ads you see while reading news, and you can open the same site in multiple containers simultaneously with different logins.

Compared to Firefox Containers, Brave’s version is still maturing. Firefox offers per-site container rules and the ability to always open a specific site in a specific container. Brave, at launch, allows you to manually assign tabs to containers but does not yet support automatic site-to-container rules. Firefox also has a richer ecosystem of extension-based containers. However, Brave’s advantage is that containers are part of the core browser and work seamlessly with Shields and Tor mode (when enabled). You don’t need an extra extension to manage them.

What Readers Can Do

Enable container tabs in Brave

  1. Open Brave and type brave://settings in the address bar.
  2. Go to Privacy and security → Container tabs.
  3. Toggle on “Enable container tabs.”

Once enabled, you’ll see a container icon (a small box) next to the address bar. Opening a new tab will give you the option to create a new container or choose an existing one. You can name each container and pick a color for easier visual identification.

Practical use cases

  • Work vs. personal: Create a “Work” container where you log into email, project management tools, and internal sites. Switch to a “Personal” container for email, social media, and forums. No risk that a work tracker sees your personal browsing.
  • Shopping and comparison: Use a “Shopping” container when comparing prices. Sites like Amazon or eBay won’t see your search history from other containers.
  • Multiple social accounts: Stay logged into two Twitter or Instagram accounts at the same time by opening each account in a different container.

Tips for managing containers

  • Rename containers immediately after creating them – otherwise you’ll forget what each one is for.
  • Use color coding to quickly distinguish containers in your tab bar.
  • Container sessions persist across browser restarts by default. If you close Brave and reopen, each container’s cookies remain separate. (This is worth verifying on your version – early releases may have differed.)
  • You can also open a link from outside the browser into a specific container by right-clicking and selecting “Open in container tab.”

Limitations to keep in mind

  • Container tabs do not prevent tracking that happens via fingerprinting or network-level identifiers. They only isolate cookie-based data. For best results, keep Shields enabled in each container.
  • Memory usage increases when you have multiple containers open, since each container maintains its own storage partition. If you run many tabs in separate containers, your system might slow down.
  • Some sites (e.g., banking portals) may detect multiple logged-in sessions from the same IP and require additional verification. This isn’t a container issue per se, but something to be aware of.
  • For now, you cannot set permanent rules to always open a specific site in a given container (as you can in Firefox). You must manually assign the container each time unless you use an option to “Always open links from [site] in this container,” which Brave may add later.

Sources

  • The Futurum Group article (July 3, 2026): “Brave’s Browser Containers Raise the Bar for Privacy and Workflow Flexibility”
  • Brave’s official release notes and support pages (check brave://settings/help for your version)