Containers

Many websites and trackers try to connect your activity across different sites. If you use the same browser identity everywhere, it is easier for them to link your shopping, social media, work tools, and other browsing together.

Containers help you split that activity into separate spaces. That can mean simple tab organization, or full site-data separation if you enable Cookie Isolation for the container.

For example, you might use:

That makes it easier to stay organized, and when you turn on Cookie Isolation, it also separates cookies and site data between containers.

Some container features always work:

Other features only work when Cookie Isolation is enabled for that container:

Important: a container only keeps separate logins, cookies, and site data when Cookie Isolation is enabled for that container. A non-isolated container is still useful for organization and site assignment, but it does not get its own cookie jar.

With Cookie Isolation turned on, websites in one container cannot use the cookies or site data from another container. For example, if you sign in to a site in your Work container, that sign-in does not automatically carry over to your Personal container.

When you browse in a container, the address bar shows a subtle colored border matching the container’s theme color, and the tab bar area is tinted with the same color. This makes it easy to recognize which container you are in without checking the container menu.

Each container can also have its own icon. The icon appears in the container bar, the container list, and tab indicators. You pick it from a searchable grid of Material Design Icons in the container editor.

Container colors come in two modes:

To change either, open the container editor and tap the large icon and color preview, then choose Change Color or Change Icon.

Suppose you create these containers:

Then you can:

This does not make you invisible, but it can reduce how much different sites learn from each other.

One reliable way to manage containers is:

When creating a container, you can set:

When editing an existing container, always expect name, appearance, pinning, and assigned-site management to be available. Proxy routing, per-container data clearing, history exclusion, and strict mode only make sense for containers that already have Cookie Isolation.

Note: Proxy Connection, Clear Data on Exit, Exclude from History, and Strict Mode depend on Cookie Isolation. If cookie isolation is off, those options are not active for that container because there is no separate browsing context to route, clear, or restrict.

You can use containers in two main ways:

To select a container for new tabs:

To move an existing tab into a container:

If needed, you can also remove a tab from a container with Unassign Container.

If moving a tab changes its cookie-isolation context, WebLibre may reopen that tab in the new context so it uses the right cookies and site data.

Assigned Sites let you tell WebLibre that a site should always use a specific container. This is useful for sites you visit often and always want to keep separated.

Examples:

When possible, WebLibre will open or move that site into the assigned container automatically.

To set this up:

Helpful notes:

If you edit a container and press the back button without saving, WebLibre asks what you want to do:

This avoids accidentally losing changes when you navigate away by reflex.

Turn on Pin Container to keep a container at the top of container lists. Pinned containers show a pin icon on the container chip and a Pinned badge in the container list.

You can also reorder containers manually: long-press and drag container chips in the bottom container bar, or use the drag handles in the container list. The order persists across sessions.

If you set a Proxy Connection for a cookie-isolated container, tabs in that container route their traffic through that connection — Tor or any of your proxy profiles — while other containers keep using your normal connection.

Example:

This lets you mix regular, Tor-routed, and proxy-routed browsing in the same browser.

If global proxy routing is enabled instead, a container can opt out with Bypass Global Proxy. That container then connects directly — useful for sites that block Tor or proxy traffic. A container cannot bypass the global proxy and have its own proxy assignment at the same time.

Learn more: Tor Integration and Proxy Connections

Strict Mode turns a container into an allowlist-only space.

When enabled, only sites assigned to that container are allowed to load there. Unassigned sites are blocked instead of loading inside the strict container. Sites assigned to another container are still redirected or handled according to their assignment.

This is useful for containers that should stay clean, such as a Banking container that should only ever open your bank’s sites.

Strict Mode requires Cookie Isolation.

With Exclude from History enabled, pages opened in that container are not recorded in browsing history.

This is separate from Exclude from Search Index: it prevents the container’s visits from being recorded in browser history at all, not just from the local search index.

Exclude from History requires Cookie Isolation.

WebLibre can index the pages you visit locally so you can search their content later (see Local Search).

Turn on Exclude from Search Index to keep a container’s pages out of that index. Existing indexed entries that only come from that container are removed immediately. If you disable the option again, eligible pages that are still open can be indexed again.

This option does not require cookie isolation.

If you enable Clear Data on Exit for a cookie-isolated container, WebLibre clears that container’s cookies and site data when the app closes.

This is useful for:

It is a good choice when you want a container to start fresh the next time you use it.

When you delete a container, WebLibre can also offer to delete that container’s browsing history. If you keep the history, those visits stay in the History screen but are shown without a container label.