Google has shipped a striking new experiment in Chrome Canary that lets users convert a tab group into a standard bookmark folder with one click—and optionally clear the entire group from the tab strip in the process. The move transforms tab groups from temporary visual clusters into first-class, archivable objects that sync across devices, marking a major step in Chrome's long-running effort to bridge ephemeral browsing with durable workspace management.

The feature, spotted by Windows Report in a recent Canary build, adds a "Convert group to bookmark folder" option to the tab group context menu. After saving, Chrome prompts whether to delete the original group, making the action a move-and-archive operation rather than a simple duplication. The resulting bookmark folder behaves exactly like any other folder in Chrome's bookmark system: it appears in the bookmarks bar, side panel, and manager, and instantly syncs via Chrome Sync to all signed-in devices.

This isn't a surprise feature drop. Chromium commit logs show engineers have been working on tab group persistence for years, and recent additions like the SavedTabGroupSyncBridge laid the groundwork for the UI experiments now visible in Canary. Google's strategy is clear: reuse existing bookmark infrastructure instead of inventing a new storage system. Bookmarks are durable, searchable, and already synced—so why rebuild that wheel for tab groups?

What exactly does the new flow look like?

When the experimental flag is enabled, right-clicking a tab group's colored bubble or using the group menu reveals the new conversion entry. The flow proceeds as follows:

  • Right-click the tab group bubble (or use the group menu) and select Convert group to bookmark folder.
  • The familiar Bookmark all tabs dialog opens, prompting you to name the folder and choose a destination.
  • After saving, Chrome asks: "Delete the tab group?" If you confirm, the entire group—all open tabs and the visual bubble—is removed from the window.
  • The saved folder appears in your bookmarks and syncs to other devices signed into the same Chrome profile.

Because the feature lives behind an experimental flag, the exact wording and prompts will likely change before any stable release. Early reports confirm the bookmarks created are plain bookmark folders, not a new "saved group" object. That means they inherit all existing bookmark behaviors: search, export, and compatibility with bookmark manager extensions.

The flags driving the experiment

The conversion feature isn't a lone experimental toggle; it's part of a cluster of related flags that point toward a broader rethinking of tab group management. In Canary builds referenced by reports, the key flags include:

  • Bookmark and tab group conversion — described as "Enable conversion between bookmark and tab group." This flag surfaces the conversion action itself.
  • Add context menu when left-clicking a tab group — turns a left click on a tab group in the bookmarks bar into a contextual menu, matching the existing right-click menu. This increases discoverability.
  • Make options menus include more tab group actions — populates menus with additional group management actions, giving power users direct access without hidden workarounds.

These flags are experimental by nature. Their names can change, merge, or vanish between Canary builds. The feature set has appeared in build logs and user reports, not in an official Chrome release note, so anyone relying on them should treat them as provisional.

Why "move" instead of "copy"?

One of the most debated details in community discussions is the delete-after-save prompt. Google has chosen a move semantic: convert the group to a bookmark folder and then offer to remove the original tabs. This aligns with an archival mindset—finish a project, stash it, and clear your workspace. But it may surprise users who expected a non-destructive copy.

Forum members quickly noted that this behavior could become a pitfall if the prompt isn't explicit. Accidentally confirming deletion would tear down a live tab group, leaving only the bookmark folder. Power users and admins are already crafting workarounds: some suggest keeping a backup group, while others hope Google will add a straight "copy" option in the final UI.

Real-world power and pitfalls

For anyone managing dozens of tabs across multiple projects, the archival conversion is a major quality‑of‑life improvement. Instead of manually bookmarking each tab one at a time, you can wrap an entire research session, shopping cart, or documentation set into a single bookmark folder. That folder then appears on your laptop, desktop, and phone—a true "save and resume" workflow.

But the feature isn't without drawbacks:

  • Synced everywhere means exposed everywhere. Because the folder is a standard bookmark, it becomes part of Chrome Sync. If you use a shared or managed Google account, those archived tabs appear on every device signed into that profile. Sensitive URLs saved into bookmarks could leak across personal and work boundaries.
  • Canary instability. Canary builds are bleeding edge; experimental flags can crash the browser, corrupt profiles, or cause data loss. Testing should be done on a secondary profile with regular bookmark exports.
  • No mobile parity yet. Chrome on Android and iOS still lacks the rich tab group UI of desktop. While the resulting bookmark folder is cross-platform, the conversion UX and the ability to restore a bookmark folder as a tab group may lag or look different on mobile.

Security and enterprise considerations

Bookmarks have long been a blind spot in many organizations' data loss prevention (DLP) strategies. Converting a tab group to bookmarks effectively writes live browsing state into a synced storage layer. That has immediate implications:

  • Compliance: Enterprises subject to strict DLP rules may need to block or audit the feature. Chrome's enterprise policies already include controls over bookmark sync and desktop shortcuts; admins should evaluate whether to allow tab group conversion on managed devices.
  • Accidental data leakage: A user might archive a group containing internal tool URLs, then later sign into a personal device where those bookmarks sync. The result is an unintentional exfiltration path.
  • AI and telemetry overlap: Chrome's growing use of on-device AI and cloud protections (like Enhanced Safe Browsing) means some browsing signals may be sent to Google. When AI features are active, archived groups become part of a larger privacy surface, even if the bookmarks themselves are local.

Enterprises should treat tab group archiving the same as any other bookmark operation: verify sync policies, train users on the move-vs-copy behavior, and consider audit logging where feasible.

How to test the feature safely right now

If you're comfortable with experimental software, you can try the conversion flow today in Chrome Canary. Follow these conservative steps to avoid breaking your main browsing setup:

  1. Install Chrome Canary as a separate browser alongside your stable Chrome. Canary runs completely independently.
  2. Create a fresh, throwaway Chrome profile—do not sign in with your primary Google account if you want to avoid unexpected sync events.
  3. Navigate to chrome://flags and search for terms like tab group, save, or bookmark and tab group conversion. Enable only the flags you recognize, and document exactly which ones you toggle. The flag names may differ slightly from builds; current Canary observations point to Enable conversion between bookmark and tab group as the primary switch.
  4. Relaunch Canary, then create a small tab group with a few non-sensitive pages (e.g., Wikipedia articles).
  5. Right-click the tab group bubble and select the conversion action. Observe the flow: name the bookmark folder, choose a location, and note whether the post-save prompt offers to delete the group or simply duplicates it.
  6. Check the resulting bookmark folder in the bookmarks manager (Ctrl+Shift+O) or side panel. Verify that the folder syncs to another device only after you've confirmed the save behavior.
  7. Before making any big changes, export your existing bookmarks as an HTML file from the bookmarks manager as a safety net.

Critical safety notes: Canary can crash and lose tabs without warning. Never test experimental flags on your primary profile or with irreplaceable tabs. Keep regular bookmark exports.

The bigger picture: from ephemeral bubbles to permanent workspaces

The conversion experiment is the latest milestone in Google's multi-year journey to make tab groups persistent. Chrome first introduced tab groups as a simple visual candy: colored labels that helped you spot related tabs. Since then, the browser has added:

  • Saved tab groups that appear as buttons in the bookmarks bar.
  • Tab group sync across devices in recent releases.
  • Open bookmark folders as tab groups, a complementary feature that closes the loop.

These changes reflect a consistent design philosophy: reuse Chrome's mature bookmark and sync infrastructure rather than build a parallel, siloed "workspace" system. Bookmarks are already indexed, searchable, exportable, and supported by countless extensions. By layering tab group archival onto that foundation, Google gets cross-device persistence and tooling compatibility with minimal new code—and users get a unified mental model where a "workspace" is just a bookmark folder with a tab group's UX.

Community reactions and lingering concerns

On forums and social media, the response has been cautiously optimistic. Power users appreciate the reduced friction, but many voice the same reservations:

  • "Is it really a move, not a copy?" The delete prompt remains the top concern. A mis-click could vaporize a live group, and Chrome doesn't offer an undo. Users want a clear "copy" option or an undo buffer.
  • "Bookmark clutter is real." Without better folder management tools—auto-tagging, deduplication, or bulk health checks—archived groups could simply trade tab clutter for bookmark clutter. Chrome's built-in bookmark manager hasn't seen major upgrades in years.
  • "What about mobile?" While the bookmark folder will sync to Android and iOS, the ability to reopen it as a tab group isn't guaranteed. Google has yet to show how the entire archive-and-restore loop will work on mobile platforms.

These open questions are where user feedback becomes crucial. Canary builds are a testing ground; Google engineers monitor Chromium issue trackers and usage metrics to decide which experiments graduate to stable.

Alternatives for the impatient

If you don't want to wait for a stable release or mess with experimental flags, several third-party extensions already approximate the feature:

  • Bookmark Tab Group – adds keyboard shortcuts and one-click folder creation from existing tab groups.
  • Bookmarks to Tab Groups – specializes in reconstructing tab groups from bookmark folders, giving you a two-way pipeline.
  • Workflow-focused extensions (Toby, Session Buddy, OneTab) – provide session management and lightweight workspace archiving, though they use their own storage rather than native bookmarks.

These extensions work today in stable Chrome, but they depend on extension APIs and developer maintenance. Google's native implementation, once stable, will be more tightly integrated and benefit from Chrome Sync's reliability and cross-platform reach.

What to expect next

Google rarely flips experimental flags directly into stable. Based on past feature rollouts, the likely path looks like this:

  1. The conversion flag spends several weeks or months in Canary, during which UI strings and behavior are refined based on telemetry and bug reports.
  2. A refined version lands in Chrome Beta, possibly behind a flag or as a gradual rollout.
  3. When the feature reaches stable, it will probably launch as a default-off flag first, then become a standard menu item once Google is confident in its stability and usability.

The companion flags—left-click context menus and expanded group actions—suggest a broader tab group overhaul is in the works. When all three land together, tab groups will feel less like a cosmetic add-on and more like a central, archivable building block of Chrome's browsing model.

Bottom line

Chrome Canary's new tab-group-to-bookmark-folder converter is a deceptively simple feature with deep implications. It signals that Google is committed to breaking down the wall between what you're working on right now and what you want to save for later. By mapping tab groups onto existing bookmark primitives, Chrome avoids adding yet another sync pipeline and gives users a powerful archival tool that works everywhere bookmarks do.

The experiment isn't ready for daily driving yet. The move semantics need clearer messaging, and enterprises must weigh the privacy and compliance risks. But for anyone who has ever stared at a dozen open tabs and wished they could just stash them away with a single click, the direction is clear: Chrome is building a future where your workspace is never more than a bookmark folder away.