🍪 What are Browser Containers (and What is a Container-first Browser)?

Last updated on 31 Jul 2026

What is a browser container?

A browser container is a sealed compartment for a website's cookies and storage. Normally, a browser keeps one shared pot of cookies, so a site can only see one signed-in account at a time. Put a tab in its own container and it gets its own cookie jar, which means you can be signed in to several accounts of the same service at once, side by side, without them clashing. The classic example is running three Gmail accounts at the same time, with no logging in and out.

Container tabs began as a browser add-on and have since started appearing natively in more browsers. They're especially loved by people who juggle work and personal accounts, or many clients.

The problem containers solve

Most of us don't have just one account. We have a personal email and two work ones, a chat workspace per client, separate logins for staging and production. A normal browser is built for one of you. The moment you need two accounts of the same service, it makes you log out, log back in, or open a separate window. Containers fix that by giving each account its own isolated space to live in.

Profiles vs containers vs container-first — three approaches

It helps to picture three rungs on a ladder:

Profiles. Most browsers (including Chrome) let you create separate profiles, each with its own cookies. They work, but each profile opens in a separate window, so you're constantly switching between windows to move between accounts.
Containers. A container isolates an account inside a single window, which is much smoother. You can have several accounts of the same site open as separate tabs, each in its own compartment. This is the building block, and it's a good one.
Container-first. Here the whole browser is organized around containers. Each container is a complete, organized workspace, which makes your workday so much easier!

The first two isolate an account. The third transforms that isolation into a place to work.

What a container-first browser looks like

This is the idea Wavebox is built around. Each container is a Space, and a Space holds an entire workflow on top of the isolation:

Apps: the tools for that context, such as Gmail, Slack, Notion, etc.
Groups: those apps organized by the job they do (comms, admin, a client's toolkit). Groups appear in the sidebar (webdock).
Saved items: the specific web resources for that account, one click away in each app's menu (like pinned tabs or bookmarks, but superpowered).
Layout, colors, and icons that are yours to customize.

Because the isolation runs through the whole browser, links route themselves into the right Space automatically, you switch context in a click, and your whole setup can sync across your computers. Each client gets a self-contained workspace you step into.

Who benefits most?

If you occasionally need two accounts of the same site, a simple container is plenty. But if your day is accounts (a virtual assistant running ten clients, an agency switching between brands, a founder running several companies from one window), the difference between "isolated tabs" and "an organized workspace per context" is the difference between coping and flying. That's who container-first is built for.

How Wavebox does it

In Wavebox, containers are called Spaces. Each Space keeps its own cookies, so multiple accounts of the same service stay signed in together. Groups organize the apps inside your Spaces, and a small Spaces indicator in the address bar always shows which Space you're working in. It's the outcome people really need from profiles, every account live at once and one click apart, without the separate windows. See how Spaces work →

Try Wavebox free →

Frequently asked questions

What is a browser container?
A container is an isolated compartment for a site's cookies and storage. It lets you stay signed in to multiple accounts of the same website at once, in one window, without them conflicting. You may also know them as "Workspaces" or "Spaces" depending on which browser you're using.

Can I be logged into two accounts of the same site at the same time?
Yes, that's exactly what containers are for. Each account lives in its own container (in Wavebox, a Space) with its own cookies, so two Gmail accounts (or two of anything) stay signed in together and you switch between them in a click.

Is a container the same as a browser profile?
Not quite. Profiles also isolate accounts, but each profile opens in a separate window, so you switch between windows. A container isolates an account inside one window, which is far smoother for working across several accounts at once. Note that in Wavebox, a Profile is a completely independent version of Wavebox, with its own settings, Spaces, and data.

Do all browsers have containers?
More and more do, some as a built-in feature, some via an add-on. What varies is the depth: most treat a container as an isolated tab, whereas a container-first browser turns each one into an organized workspace with its own apps, layout, and links.

What is a "container-first" browser?
One that's built around containers from the start, so each container is a whole workspace. Wavebox is container-first: each Space holds its own apps, Groups, layout, and saved items, with the cookie isolation underneath.