What is TabIdent? Firefox-style containers for Chrome
Chrome users often ask for a Firefox Multi-Account Containers equivalent. TabIdent is that idea for Chromium: colored container identities in one window so work and personal accounts can stay signed in side by side.
The problem
Chrome profiles isolate everything—bookmarks, extensions, history. That is heavy when you only need two logins on the same site. Logging out and back in wastes time and breaks flows like customer-support tenants or QA roles.
What TabIdent does
- Create named, colored containers (identities).
- Assign a tab to a container so its cookies and common site storage are namespaced.
- Keep bookmarks and extensions shared across containers.
- Optionally bind a site so it always opens in a chosen container.
- Persist definitions and sessions on this computer—no TabIdent account.
What it deliberately is not
TabIdent is not a fingerprint browser, not a proxy farm, and not “one account per tab forever.” Tabs in the same container share a session on purpose. If you need a disposable identity every time, that is a different product (and outside the current MVP).
Local-only trust model
The extension requests cookie and related permissions so it can isolate identities. It does not upload cookies or credentials. See the Privacy Policy for the full statement.
Getting started (once installed)
- Open the toolbar popup and create containers (for example Work and Personal).
- Assign the current tab to a container; the page reloads into that identity.
- Sign in. Open another tab, assign the other container, sign in to the second account.
- Optional: enable “always open this site” for mail or dashboards you always want in Work.
Honest limits
Some browser APIs (Shared Workers, Cache Storage, BroadcastChannel) can still cross containers. Large SSO providers can be fragile—use pause rules instead of permanently binding login hosts like accounts.google.com. We publish a compatibility stance rather than claiming every site isolates perfectly.