Browser tabs are one of those things that start as a solution and quickly become the problem themselves. You open Chrome for a short research session, one link leads to another, and twenty minutes later you’re staring at a row of tiny unlabelled rectangles trying to remember which one had the article you actually need. Chrome tab groups were built for exactly this moment. If you want the full context, see our Chrome How-To Guides.
Introduced in Chrome 83 and steadily improved since, tab groups let you gather related tabs under a named, colour-coded label that collapses, expands, saves across sessions, and syncs between devices. This guide covers every aspect: creating and naming them, collapsing to reclaim tab bar space, saving groups so they survive a browser restart, and the specific workflow patterns where they deliver the most practical value.
What Chrome tab groups actually do
A tab group clusters multiple tabs under a single labelled header in the tab bar. When a group is created, a small coloured dot and an optional text label appear at the left edge of the grouped tabs — giving each cluster a distinct visual identity that makes it immediately distinguishable from other groups and from ungrouped individual tabs.
They sit directly in the tab bar rather than in a separate sidebar or external panel, which means they work within the existing Chrome layout without any new UI to learn or any extension to install. That’s the meaningful advantage over third-party tab managers: there’s nothing to add, nothing to maintain, and the grouping survives tab reorders, page navigation, and moving tabs to a different window.
The core behaviour that makes this genuinely useful — rather than merely cosmetic — is collapsing. Clicking the group label collapses all the tabs within it into a single chip, freeing up the space those tabs occupied while keeping all the pages loaded in memory. They haven’t closed; they’re still live, still holding their state. Clicking the chip again expands the group immediately. For a session involving three or four concurrent projects, collapsing inactive groups while working on the active one produces a dramatically cleaner tab bar than leaving everything visible simultaneously.
What distinguishes this from third-party tab management extensions is the depth of native integration. Groups persist through navigation, follow tabs when they’re moved to a new window, and as of recent Chrome versions can be saved so they reopen after a browser restart. For users who previously relied on extensions like OneTab or various tab suspenders for session management, tab groups solve a different but related problem — not storage, but the visual organisation of actively open tabs in a way that keeps the current session comprehensible.
Creating, naming, and colour-coding groups
Right-click any tab at the top of Chrome → “Add tab to new group.” Chrome presents a small popup with a text field for the group name and a row of colour circles. Type a descriptive name — “Research,” “Shopping,” “Project Alpha,” “Reading queue” — or leave it blank for a colour-only group with no text label. Choose from eight colours: Grey, Blue, Red, Yellow, Green, Pink, Purple, and Cyan. Click anywhere outside the popup to confirm.
Adding more tabs to an existing group works two ways:
- Right-click → Add tab to group: shows a submenu listing all current groups — select the target and the tab moves immediately
- Drag and drop: click and drag any tab over the group’s visual block in the tab bar and release when Chrome highlights the group boundary — good when the tab and group are close together
Opening a new tab directly inside an existing group: right-click the group label chip → “New tab in group.” The new tab opens inside the group’s boundaries, which is faster than using Ctrl+T and then dragging the tab in. Renaming or recolouring is equally non-destructive: click the group label chip and the same popup reappears, fully editable. Groups can be repurposed freely as projects evolve.
Collapsing groups — the habit that changes daily browser use
This is the most impactful behaviour in the feature set. A collapsed group takes up approximately the same space as a single labelled chip regardless of how many tabs it contains. A session with four active groups — Research with twelve tabs, Shopping with four, Work with eight, Reading queue with six — becomes four labelled chips rather than thirty individual tabs. That’s the precise difference between a navigable browser session and an overwhelming one.
Click the group label chip once to collapse. Click again to expand. Chrome remembers which specific tab was active within the group before collapsing, so expanding restores focus to exactly where you left off — not the leftmost tab in the group, but the last active one. This makes collapsing and expanding feel fast rather than disruptive.
Moving a tab from one group to another: drag it over the destination group’s visible tabs and release when Chrome highlights the target boundary. For collapsed groups: drag over the chip and hold briefly — Chrome automatically expands it to allow the drop, then re-collapses. To remove a tab from a group entirely without closing it, drag it past the group’s edge until it sits in the ungrouped section, or right-click → “Remove from group.”
The habit that unlocks the full potential of tab groups is treating collapse as the default state rather than the occasional cleanup tool. Rather than collapsing reactively when the tab bar gets unmanageable, collapsing every inactive group immediately when switching context keeps the bar consistently clean. Within about a week of this habit, working in Chrome without consistent group collapse feels as disorganised as an unorganised desktop covered in overlapping windows.
Saving groups across browser sessions
The most significant addition to the feature was the ability to save groups persistently — surviving browser restarts, remaining available even when all their tabs are closed, and syncing to other devices through the Chrome account. A saved group elevates the feature from session management to persistent workspace organiser.
To save: right-click the group label chip → “Save group.” The chip gains a visual indicator confirming the save — typically a small bookmark or cloud symbol depending on the Chrome version. Saved groups appear in the Tab Search panel (click the downward arrow at the right end of Chrome’s tab bar, or press Ctrl+Shift+A) under a “Saved tab groups” section. From this panel, saved groups can be opened with a single click even when none of their tabs are currently open — functioning like structured bookmark collections that open all their URLs at once rather than individually.
Deleting a saved group: right-click the chip → “Delete group.” This removes it from the saved list on all synced devices — permanent, so bookmark any important URLs separately first. For a group that should disappear from the current tab bar but remain available to reopen later, use “Close group” instead — the saved version persists and can be reopened from Tab Search. This distinction between closing and deleting makes the feature flexible enough for both short-term session management and long-term project organisation.
Tab groups on mobile and across devices
On Android, tab groups work through the Tab Switcher rather than a desktop-style tab bar. Long-pressing a tab thumbnail and dragging it onto another tab creates a group. Chrome Android may also automatically group tabs it detects as topically related — controlled in Chrome Android Settings → Tabs.
Saved groups created on desktop sync to Android through Chrome sync, making them available for mobile reference even when built primarily as desktop session organisers. Cross-device continuity is one of the most compelling reasons to use both the save feature and Chrome sync together — a research group built during an afternoon session on a work desktop can be reopened on a personal laptop the same evening with all URLs intact.
Our Chrome sync guide covers the account and sync settings that enable this continuity in detail, including how to verify that saved groups are included in the sync scope. For keeping work and personal tab groups completely isolated, Chrome profiles maintains separate tab groups, saved groups, and sync accounts per profile. For the version history of specific tab group features including when saved groups and group sync were introduced, the Chromium project documentation covers the implementation details.
Workflow patterns where tab groups make the biggest difference
The feature delivers the most visible improvement in sessions that involve multiple concurrent research threads. A product comparison session — evaluating five laptops across eight review sites — becomes five labelled groups, one per laptop, each containing all the relevant review, specification, and pricing tabs for that model. Switching between laptops means clicking a single group chip and having all that laptop’s context immediately visible. When a purchase decision is made, closing a single group closes all eight tabs for that model in one action, leaving the rest of the comparison intact.
For project-based work where reference material needs to stay accessible for days, saved groups replace the habit of bookmarking actively-used pages. A saved group named “Q3 Report” might contain the data source tabs, the style guide, the previous report for structure reference, and the draft document — all openable with one click at the start of each work session, all closeable with one action when done. The project context is preserved not as a bookmark folder to manually reconstruct into tabs, but as a live group that restores the entire working environment in seconds.
Colour coding by priority rather than by topic is an underused pattern. Using red for time-sensitive tabs that need attention today, yellow for things in progress, green for reference material, and grey for tabs to read when time allows — the colour becomes an instant priority signal that works even when the group label isn’t fully readable in a dense tab bar. Combined with collapsing inactive colours: the visual system communicates not just what each cluster is but how urgently it needs attention.
Tab groups have a real learning curve of about a week before they feel natural. The initial reaction from most users who try them is something like “this is more clicks than just leaving tabs open.” That changes once collapsing becomes automatic — at that point, the tab bar becomes genuinely navigable rather than something you manage around. The key is committing to the collapse habit before concluding the feature isn’t worth using.
Keyboard shortcuts for tab group management
Chrome doesn’t have many dedicated keyboard shortcuts for tab groups (most operations go through right-click menus), but the adjacent shortcuts that speed up group workflow:
- Ctrl+Shift+A: opens Tab Search (where saved groups appear and can be reopened)
- Ctrl+1 through Ctrl+8: jumps to the first tab in that position number — less useful in grouped tab bars since groups compress multiple tabs into fewer visual positions
- Ctrl+W: closes the current tab — when closing the last tab in a group, the group itself disappears (unless saved)
The most practical keyboard interaction with tab groups comes through Tab Search (Ctrl+Shift+A): type the group name or the name of a tab within a group to find and switch to it without using the mouse. For users who find mouse-driven tab navigation slow, Tab Search makes the “find the right tab in a dense session” operation keyboard-accessible.
When tab groups don’t help
Being honest: tab groups aren’t the right solution for every tab management problem. They work well when you have concurrent, distinctly-different workflows running simultaneously — different projects, different research threads, different contexts. They’re less useful when you just have too many tabs open on the same topic, or when the real problem is tabs you’ve been “saving for later” for months that you’ll never actually read.
For the “too many open tabs, most of which I don’t actually need” problem: tab groups add organisation to the problem without solving the underlying accumulation. A periodic honest tab audit — close or bookmark anything you’ve had open for more than a week without visiting — combined with tab groups for active working sessions is more effective than grouping everything and hoping the organisation makes it all manageable. Tab groups work best on sessions you’re actually using, not as a way to feel better about tabs that should have been closed weeks ago.
Chrome tab groups occupy a genuinely useful space in the browser management toolkit. They’re not a replacement for bookmarks (which are for things you want to return to eventually), not a replacement for session managers (which are for restoring entire previous sessions), and not a replacement for the close button (which is still the right answer for tabs you’re done with). They’re the right tool for active, organised, multi-threaded browser sessions — which, for anyone doing research, project work, or comparison shopping, is a large portion of daily browser use. Related: Customise Chrome’s New Tab Page.
