Chrome tab groups disappeared? Three causes, and what each one recovers

The short version

Tab groups almost never delete themselves. Three causes cover nearly every case: the group was only ever on one machine because it was never saved to your Google Account, another device deleted or ungrouped it and sync carried that everywhere, or the group is still saved and you are looking for it in the tab strip instead of the bookmarks bar. Only the first has a version nothing recovers.

Cause 1: the group was never in your Google Account

Chrome carries tab groups between devices through sync, not through anything the group itself holds. Google's Manage tabs in Chrome page states the condition before it describes the feature: 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.

Read that sentence backwards and you have the most common failure. Signed out — or signed in with history and tabs switched off — a group exists on one machine, in one profile, and nowhere else. This is why someone can be certain a group was saved and still find nothing on the other laptop. It was saved. It was saved locally.

Check it. Open the three-dot menu, then Settings, then You and Google, then your account name, and look for History and tabs. Google documents that same path on its sync help page. If the toggle is off, nothing you did to that group ever left the device.

Recover it. Only from the machine that made the group, and only if that profile is still intact. Sign in there and Chrome offers to push local data up: the profile menu carries a Save … items in Account entry for exactly this. Read what it lists before assuming your groups are in the count — Google describes it in terms of bookmarks and other info, and does not enumerate every data type.

Prevent it. Turn History and tabs on before you build anything you would mind losing, not after. A group made while signed out is not retroactively rescued by signing in later.

Cause 2: another device deleted the group, and sync carried that everywhere

This is the one people report as a bug, and it is documented behaviour. Two ordinary actions remove a group on every device, not just the one in front of you. Google's help page says both plainly: when you delete a tab group it is removed on your device and other devices that use the same Google Account, and when you ungroup tabs it leaves the tabs open on your device but also deletes the group on your device and the others.

Ungroup is the trap. It reads like a local tidy — the tabs stay open, nothing looks destroyed — and it is the same one-way operation as delete. Do it on a desktop at lunchtime and the group is gone from the laptop you open that evening, with no event on that machine to explain it.

Recover it. You do not. There is no undo for a removed group and no bin it waits in. The pages usually survive even when the group does not: your history still has them, and on the machine where the window was closed Ctrl + Shift + T reopens tabs in the order they were closed. You are rebuilding the group by hand, which is exactly as annoying as it sounds. If the group was a working session rather than a reading list, the ways to save a set of tabs that do not depend on groups are worth knowing before the next time.

Prevent it. Learn the difference between the three right-click actions on a group's name. Close group puts it away and keeps it. Ungroup and Delete group both destroy it everywhere. Only one of the three is reversible, and it is not the one that sounds most gentle.

Cause 3: the group is closed, not deleted, and closed groups are not in the tab strip

Closing a group hides it from the tab strip, which is the only place most people ever look. The group is still there. Google is explicit: a closed group is not deleted and is saved in the bookmarks bar or in the menu.

Recover it. Two places. In the bookmarks bar, click the grid icon and pick the group by name. Or open the three-dot menu, choose Tab groups, and select it from the list. Either way it comes back as a group of live tabs, not as a folder of links.

Prevent it. In Settings, under Appearance, there are two switches that make this cause disappear for good: Show tab groups in bookmarks bar, and Automatically pin new tab groups to the bookmarks bar. The second one also pins groups you created on your other devices under the same account. Turn both on and a closed group stops being invisible.

Why don't I have "Save group" in Chrome?

Because there is nothing left to switch on. Saving is what a group does now.

The question is common because the toggle was real, people learned it, and then it stopped appearing in the menu — which reads exactly like a feature being taken away. What actually happened is that the behaviour it controlled became the default. Right-click a tab, choose Add tab to group, then New group, and the group you get is already a saved group. Nothing in the current interface asks you to opt in, because nothing has to.

You can confirm this in about twenty seconds rather than taking anyone's word for it. Make a group, right-click its name, choose Close group, and then look in the bookmarks bar or under Tab groups in the three-dot menu. If it is there, it saved itself.

One thing not to do: go hunting in chrome://flags. Flags gate features on the way in, not after they ship as default behaviour, and there is nothing to switch on there that brings back a group sync has already removed. Changing flags on the profile you work in is a reliable way to acquire a second problem while still having the first.

Tab groups not syncing between devices

If groups save fine on one machine and never show up on another, work down this list before concluding anything is broken.

• Same account, same profile. Chrome profiles are separate universes. A group made in your work profile will not appear in your personal one on the same computer.
• History and tabs, on both devices. It is a per-device setting. One machine with it off is enough to make syncing look one-directional.
• A sync passphrase. If you set one, Google notes that history stops syncing in full — only web addresses you typed into the address bar are synced. That is a deliberate privacy trade, and worth knowing before you diagnose it as a fault.
• A managed browser. Work and school profiles run under administrator policy, and sync data types can be restricted centrally. Nothing in your own settings will override that.
• The other device is a phone. Tab groups behave differently on Android and iOS builds than on desktop, and a group you expect to see may simply not be presented the same way there.

That last point is the honest answer to the "saved tab groups unsupported" wording people run into and then search for. Chrome does not document that string, so treat it as a signal, not a diagnosis: it points at a device that cannot take part — an older build, a mobile build, or a managed profile — rather than at a group that has been damaged. Check the version, the account and the policy on that device rather than re-saving the group on this one.

What none of this brings back

If the group was deleted or ungrouped, and it was never on any other device, it is gone. There is no export, no version history, no thirty-day window. Everything above is either "find where it went" or "stop it happening again", and it is worth saying plainly rather than sending you through five fixes that were never going to work.

What usually survives is the pages, scattered across your history and your other windows. What is lost is the boundary you drew around them — which is the part that took the effort.

Grouping keeps falling apart, and it isn't a bug

Here is the uncomfortable structural point underneath all three causes.

A tab group is a container you maintain by hand. The thing it is meant to represent — a project — has edges that move every day: a client picks up a new repo, a piece of research turns out to belong to two things at once, a one-off task becomes a workstream. The group does not move with it. So groups drift out of date, get pruned, get ungrouped in a tidy-up, and the pruning is exactly the operation that propagates everywhere and cannot be undone.

Chrome's own automatic grouping does not solve this, and a stronger model would not either, because it is not a quality problem: topic is a property of the page and project is a property of you. We wrote about where Chrome's built-in AI tab grouping stops in more detail, including the conditions under which it will not run at all.

The practical conclusion is smaller than "stop using tab groups". It is that a group is a good way to arrange what you are working on right now, and a bad place to store the only copy of a boundary you care about.

SideBoo is built for the other half of that: finding a page again across every window, your history, your bookmarks and your recently closed tabs from one keystroke, with no group required and nothing to maintain. It does not restore a deleted group, and it will not pretend to. It removes the reason you needed the group to survive.