Brave Just Got Multi-Account Containers: How to Use Them for Better Privacy

Brave has added built-in support for multi-account containers, a feature that previously required add-ons in other browsers. If you manage several online identities—work, personal, shopping, or social media—containers let you keep each one isolated from the others. This means separate cookies, local storage, and cache per container, which prevents login mix-ups and reduces tracking across different sites. Here’s what changed and how to put it to work.

What happened

In a recent update, Brave rolled out multi-account container tabs as a native feature. The idea isn’t new: Firefox introduced a similar concept years ago through its Multi-Account Containers add-on. But Brave’s version is baked directly into the browser, no extension needed. You can create containers, assign a color and label, and open tabs within that container. Each container acts like its own browsing environment.

Brave’s implementation is straightforward. You right-click a tab, choose “Open in container,” and either select an existing container or create a new one. Tabs in different containers don’t share cookies, so you can be logged into the same site with different accounts without one session overwriting the other.

Why it matters

For anyone juggling multiple accounts, containers are a practical step up from using separate browsers or private windows. They give you organized separation without the overhead. More important, they improve privacy in a few concrete ways:

  • Isolation prevents cross-site tracking. Advertisers and analytics scripts that try to follow you across sites via third-party cookies can’t easily connect your activity in one container to another. Each container has its own cookie jar.

  • Accidental exposure is less likely. If you’re logged into Google with your personal account in one container and open a work document in another, the browser won’t mix the sessions. That alone avoids many awkward logouts or “wrong account” errors.

  • Storage compartmentalization also helps with fingerprinting. Because cache, localStorage, and session data are separate per container, scripts have a harder time building a consistent profile of your browser across different tasks.

That said, containers are not a silver bullet. They don’t block trackers that operate within the same container—Brave’s built-in Shields still handle that. And containers don’t anonymize your IP address or encrypt traffic. They simply isolate session data.

What readers can do

Enabling and using multi-account containers in Brave is simple:

  1. Open Brave and make sure it’s up to date (Settings → About Brave → check for updates).
  2. Right-click any tab and select “Open in container” → “New container”.
  3. Give your container a name (e.g., “Work,” “Personal,” “Shopping”) and pick a color to identify it quickly.
  4. Assign a default site if you’d like—Brave will ask you. This is optional.
  5. Repeat for each identity you need.

Once containers are created, you can open any link or bookmark in a specific container by right-clicking and choosing the right one. Brave also lets you move an existing tab into a container.

Tips for organizing:

  • Use one container per major context: work email, personal social accounts, streaming services, banking.
  • For shopping, a separate container can help limit price tracking and retargeting ads.
  • Keep a “default” container (no label) for one-off browsing that you don’t need to isolate.

A note on limitations: Container isolation applies only within Brave. If you switch to another browser or use a different device, those sessions are separate. Also, some sites use login methods that link your identity across browser profiles (e.g., “Sign in with Google”). Those cross-container logins may still connect your accounts if you authenticate the same provider in multiple containers. To fully separate identities, consider using different browser profiles (Brave Profile) on top of containers.

Sources

  • Brave’s official release notes and help documentation (available at brave.com)
  • Mozilla’s Multi-Account Containers extension page for reference on the original feature
  • Consumer reports and privacy guides (e.g., EFF, PrivacyTools) discussing container-based isolation

No new data was collected for this article. The feature is publicly documented and confirmed by Brave’s download page and changelogs. Use at your own discretion—test with a few accounts before fully migrating your workflow.