Browsers with tab groups, and what a group guarantees

Tab groups used to be the reason to pick one browser over another. That era ended quietly. Chrome, Safari, Firefox and Edge all ship them now, so the question is no longer which browsers with tab groups exist. It is what a group is made of in each one, because the differences that matter are invisible until something goes wrong: whether closing a group destroys it, whether deleting one on a laptop also deletes it on a phone, and whether the group survives a browser restart at all.

Those details decide whether groups become a filing system that holds for months or a habit abandoned after two weeks. Feature checklists are useless here. What follows is what each implementation actually promises.

A group is a name, a color, and a promise about persistence

Every implementation gives a set of tabs a label and a color, and lets that set collapse into a single item on the strip. That much is universal and it is also the least interesting part. The part that varies is what happens when the set is no longer on screen.

There are three distinct promises hiding behind the same word. The weakest is visual only: the group exists while the window exists, and quitting the browser takes it with everything else. The middle promise is saved: closing a group puts it somewhere retrievable, and reopening it restores the pages. The strongest is synced: the group is an object attached to an account, present on every signed in device, and changed everywhere when it is changed anywhere.

Chrome and Firefox now make the strong promise. Safari makes a strong promise of its own shape, tied to the sidebar and to devices signed in to the same Apple Account. Knowing which promise is in effect determines how a group can be used. A group that only survives while the window is open is a workspace divider. A group that persists is closer to a bookmarks folder that remembers scroll position and tab order, which is a much better container for a project that runs for three months.

What each browser actually does

Browser	Creating a group	Persistence	Cross device
Chrome	Right click a tab, Add tab to group	Closed groups are kept in the bookmarks bar or the menu	Saved and synced when history and tabs sync is on
Safari	Tab Group button in the toolbar, or New Tab Group with the current tabs	Groups live in the sidebar and persist	Follows devices signed in to the same Apple Account
Firefox	Drag one tab onto another, pause, then drop	Groups are always saved and can be reopened after closing	Available to all users from version 138
Edge	Right click a tab, add to a new or existing group	Groups can be saved and reopened	Tied to the signed in Microsoft profile

The table hides one asymmetry worth pulling out. In Chrome and Firefox a group is a first class object with its own lifecycle, separate from the window that happens to display it. In Safari a Tab Group is closer to a mode the window is in: switching groups replaces what the window shows rather than collapsing a segment of the strip.

Chrome treats a group as an account object

This is the implementation most likely to surprise people, because the group stops belonging to the computer in front of them.

When browsing history and tabs are synced with your Google Account, changes to tab groups are automatically saved and synced across all of your devices. Source: support.google.com

Sync cuts both ways, and the destructive direction is the one to internalize. Chrome's own documentation is blunt about it: deleting a tab group removes it on the current device and on other devices using the same Google Account. Ungrouping does something similar. The tabs stay open on the machine where the action happened, and the group itself is destroyed everywhere else.

Closing a group is the safe action and it is easy to confuse with the destructive ones. A closed group is not deleted. It is kept in the bookmarks bar or in the menu, and can be reopened later with its pages intact. Two settings control how visible that shelf is: Show tab groups in bookmarks bar, and Automatically pin new tab groups to the bookmarks bar, both under Appearance in Settings. With the second one on, a group created on a desktop appears on a laptop signed in to the same account.

The practical consequence is that Chrome's groups behave like a lightweight project store rather than a window arrangement. A group named for a client, closed at the end of the day and reopened on Monday, is a reasonable unit of work. A group used as a temporary divider is a poor fit, because the cleanup action for a temporary divider is the same action that erases it on every other device.

Safari treats a group as a switchable set

Apple's framing is different from the beginning.

You can organize tabs into groups that make it easy to quickly switch between groups of related websites. Source: support.apple.com

Switching is the operative verb. A Tab Group in Safari occupies the window rather than a segment of the strip, so moving between two groups swaps the entire set of visible tabs. That makes it a genuine context switch, and it is the closest thing the default browser on a Mac offers to a workspace. It also means the strip never gets long in the first place, since only one group is displayed at a time.

Two smaller behaviors are worth knowing because they change how groups get used. Control clicking a group in the sidebar offers Show Tab Overview, which previews every site in the group as thumbnails, so a group of thirty pages remains navigable without opening it. And a Tab Group can be dragged from the sidebar straight into an email message to send its links, which turns a group into a handoff format rather than a private arrangement.

Safari's Tabs settings add one more relevant control that people often miss while trying to manage volume. Automatically close tabs can be set to one day, one week, or one month, or left as Manually so that nothing closes on its own. On a machine where the strip refills faster than it empties, that setting does more real work than any grouping strategy.

Firefox arrived last and copied the folder model

Firefox began rolling tab groups out in version 137 and made them available to everyone in version 138. The interaction is the most physical of the four: drag one tab onto another, pause until a highlight appears, then drop.

Tab Groups, a new way to organize and take control of your tabs, is now available to all users worldwide. You can create a group by dragging one tab onto another, pausing, then dropping it. You can also now reposition a tab group on the tab bar by dragging it. Source: firefox.com

Two properties from the initial release still shape how they feel. Groups are always saved, so closing one is a reversible act with no separate save step to remember. And groups can be repositioned on the tab bar by dragging, which sounds cosmetic but is what allows a fixed left to right order of contexts to be maintained.

Firefox is also the browser where groups and the vertical tab layout combine best, since both live in the redesigned sidebar. A collapsed group in a horizontal strip is a colored dot with a few letters. The same group in a sidebar is a readable line of text with a count next to it, which is the difference between a feature people configure once and a feature people actually use.

Groups fail on their boundaries, not on their features

Abandoned groups almost always share one cause. The boundaries were drawn around subjects instead of around decisions, so every new tab could plausibly belong to two groups at once and the sorting cost more attention than the disorder did.

Boundaries that hold have a test attached to them. A group named for a client answers a clear question about any new tab: is this page part of that client's work. A group named research does not, because everything is research to someone. The same applies to a group named tools, which slowly absorbs every page nobody wanted to file. When sorting requires a judgment call, the sorting stops within days and the group becomes a graveyard of whatever was open when it was created.

Count matters as much as naming. Somewhere past eight or nine groups the collapsed strip becomes its own crowded list, which reproduces the problem the groups were supposed to solve one level up. Five is a comfortable working number for most people, and reaching twelve is a signal that some of those groups are really separate contexts that deserve separate windows.

The last common failure is treating a group as storage. Pages get added, nothing gets removed, and after a month the group holds forty tabs that reload on open. Groups reward a habit of removing a tab the moment its question is answered, which is easier inside a named group than in an undifferentiated strip, because a group of six with one obsolete page in it is visibly wrong in a way a strip of forty never is.

None of these failures are specific to a browser. They appear identically in every implementation described above, which is the strongest evidence that the useful comparison between browsers with tab groups is not about the feature list at all.

The boundary a group cannot draw

Every implementation above organizes pages inside one browsing session. None of them separates the session itself, and that limit is where most disappointment with tab groups originates.

Signing in to a second account for the same service does not become possible because the tabs were grouped. A group named for one employer and a group named for another still share cookies, storage, extensions and the signed in identity of the profile they sit in, so switching groups changes what is displayed without changing who the browser is. Notifications ignore group boundaries entirely: a message arriving in a collapsed group interrupts exactly as loudly as one in the active group. Memory ignores them too, since a collapsed group is a display state rather than an unload.

That is the point where the tool has to change rather than the arrangement. Giving each context its own window with its own session is a different architecture, not a different setting, and it is the model described in Workspaces. For a direct comparison of how competing applications draw that line, Compared with Shift lays the approaches side by side.

What to change first

Pick the browser already in use and find out which promise its groups make, because that single fact determines whether groups can hold a project or only a day. Then group by project rather than by topic, and see whether the boundaries hold for two weeks. If the groups keep splitting along the lines of who is signed in rather than what is being worked on, no grouping feature will close the gap and SpaceDeck solves a different problem than the one groups were built for.