Chrome workspaces like Edge, and what maps across

Switching to Chrome after living in Edge produces one specific moment of confusion. The Workspaces button is not in the toolbar, the menus have nothing under that word, and searching Chrome settings for it returns nothing. The feature is not hidden. Chrome has never shipped anything called workspaces, and the closest things it does ship are split across three unrelated parts of the browser.

That matters more than it sounds, because Edge Workspaces bundles together several capabilities that Chrome keeps separate. Deciding what to build in Chrome starts with knowing which of those capabilities was actually being used.

What Edge Workspaces is, in the vendor's own description

Microsoft's documentation for administrators states that each workspace contains its own set of tabs and favorites, created and curated by the user and their collaborators, and that workspaces are automatically saved and kept up to date. The same page lists prerequisites that get skipped in most write-ups: a Microsoft Entra tenant, Edge version 114 or later, and access to a OneDrive for Business license in order to create a workspace. Workspaces for personal use arrived later, in Edge stable version 120.

The sharing model is the part that defines the feature. A workspace shares its browser tabs, favorites, and history with the team in real time, along with the active tab each group member is currently on. It explicitly does not share logins, passwords, downloads, extensions, or cookies. Closing a tab in a workspace closes it for everyone using that workspace, and a workspace can only be shared inside the same Entra tenant.

Read that list carefully and the shape of the feature changes. Edge Workspaces is a collaboration surface built on a cloud identity, not a session separator. Two workspaces on one machine still run inside the same profile, so the same Gmail account is signed in to both. Someone who used workspaces purely to keep a client project apart from internal work was using a filing feature. Someone who used them to onboard a colleague in one link was using the collaboration feature. Chrome answers those two needs very differently.

Chrome splits the same territory across three mechanisms

None of these is called a workspace, and no menu presents them as related.

Tab groups

A tab group is a named, colored, collapsible run of tabs in the strip. Collapsing one takes a project out of view without closing anything, which is the closest single behavior to switching workspaces in Edge. Groups live inside a profile, so every tab in every group shares one cookie jar and one set of logins.

Profiles

A profile is the boundary that holds cookies, history, saved passwords, extensions, and settings. On a Mac each profile is a folder inside ~/Library/Application Support/Google/Chrome, named Default or Profile 1, Profile 2 and so on, each with its own Cookies, History, Login Data, and Extensions. The friendly name shown in the profile menu is recorded separately in the Local State file, which is why the folder name and the display name almost never match. Each profile opens in its own window, and that window is the only real workspace-shaped container Chrome offers.

Vertical tabs

Current Chrome builds include a vertical tab strip, toggled from the tab strip context menu. It does not change any boundary, but it changes what a large project looks like. Twenty tabs in a vertical list stay readable at a glance in a way that twenty tabs in a horizontal strip do not, and for anyone whose Edge habit was really about seeing the shape of a project, this is the piece that carries most of the value.

Mapping the feature, row by row

Edge Workspaces behavior	Chrome equivalent	What is lost
Its own set of tabs	Tab group, or a separate profile window	Nothing, if one project fits one group
Its own set of favorites	Bookmarks folder per profile	Bookmarks are per profile, not per group
Saved automatically and restored	Saved tab groups, profile session restore	Restore is per window, not per project
Reachable from another machine	Chrome sign-in and sync	Tabs sync as a list, not as a live set
Separate logins per workspace	A second profile	Requires a whole profile, not a group
Shared tabs updating in real time	No equivalent	This is the actual gap
Locked tabs a colleague cannot close	No equivalent	Pinned tabs are per person, not shared

The table has one honest conclusion. Everything on the organizing side has a Chrome answer, some of it better than Edge's, and everything on the shared side has none.

Why the sharing half has no Chrome answer

The reason is architectural rather than a missing checkbox. Edge Workspaces stores its data in the user's OneDrive for Business and is scoped to a Microsoft Entra tenant, which is why an administrator can turn it on or off with a policy and why it cannot be shared outside the organization. Chrome sync has no equivalent shared container. It syncs one person's data to that same person's other devices.

For a team that relied on the shared part, the practical replacement is not a browser feature at all. It is whatever the team already uses to hold links, moved from being an afterthought to being the real surface: a pinned channel message, a shared document of live links, or a project page. That sounds like a downgrade and it is, for exactly one workflow, which is onboarding someone into a set of in-progress tabs. For every other workflow the difference is smaller than expected, because a shared workspace that everyone edits at once has its own failure mode. A tab someone closes disappears for everybody.

The extension route closed in 2025

The usual next move is to search the Chrome Web Store for something that adds workspaces, and that search now behaves differently than it did a few years ago. Google published a timeline for retiring Manifest V2, the older extension platform, and two dates on it matter to anyone shopping for a tab organizer today. On July 24th, 2025, with Chrome 138, Manifest V2 extensions were disabled for all users on all channels with no way to re-enable them, and the enterprise policy that had allowed an exception was removed in Chrome 139. On August 31st, 2026, all remaining Manifest V2 extensions were removed from the Chrome Web Store entirely.

The practical effect is that a highly rated tab manager recommended in a 2023 article may simply not exist at its old address, and one that does still exist may have been rewritten. Manifest V3 also changed what an extension is allowed to do in the background, which is exactly the area a session or workspace extension depends on. Before installing anything found through an older recommendation, check the store listing's last update date and read the recent reviews rather than the average rating, because a five year old average says nothing about whether the extension survived the migration.

There is a second reason to be cautious here that has nothing to do with the platform version. Any extension that manages tab sets can read and write across every tab in the profile it runs in, which is a wider permission than most people picture when they install something to tidy a tab strip. That is a reasonable trade for a tool that is genuinely maintained, and a poor one for an abandoned project that happens to still load.

Where a Chrome setup starts to leak

Two limits are worth knowing before building anything.

The first is that a profile separates without protecting. Chrome's own help page is direct about this.

Profiles let you separate all your Chrome information, like bookmarks, history, passwords, and other settings. If someone has your device, they can switch to any other Chrome profile on it.

That is the correct model to plan around. Profiles keep a work Google account and a personal one from colliding in the same window. They are not a lock, and they are not a substitute for logging out on a shared machine.

The second is that tab groups postpone the count problem rather than solving it. A collapsed group holds its tabs in memory and in the session, and a browser with eight collapsed groups is still a browser with a hundred tabs. Chrome's Memory Saver reduces the cost by making inactive tabs release memory, with three levels named Moderate, Balanced, and Maximum. It also keeps a documented list of tabs it will not deactivate, including tabs playing audio or video, tabs sharing a screen, tabs with a partially filled form, tabs with an active download, and pinned tabs. Anyone who pins the six apps they use all day has, without meaning to, told Chrome to hold all six in memory permanently.

Building the Edge habit inside Chrome

The sequence that produces the fewest surprises is boring and works.

Start by deciding which of the Edge workspaces were really identities and which were really projects. An identity is anything defined by who is signed in: a client's Google Workspace, a second Slack account, a personal Gmail. Each of those becomes a profile, named after the identity rather than the project, because identities outlive projects. A project is anything defined by what is being worked on, and each of those becomes a tab group inside the right profile.

Then turn on the vertical tab strip in the profiles that carry real work, and leave it off in the profile used for quick lookups. Pin only the applications that must never be reloaded, and accept the memory cost knowingly rather than by accident.

Name the groups after outcomes rather than topics. A group called "Q3 pricing review" tells the reader when it can be closed, while a group called "pricing" never can be, and groups that can never be closed accumulate until the collapsed strip is as unreadable as the expanded one was. Give each profile a distinct color in the profile menu as well, since the colored ring on the profile icon is the only thing in the window that says which identity is active, and every other pixel of Chrome looks the same in all of them.

One more habit transfers badly and is worth naming. Edge Workspaces kept everything, so nothing ever had to be closed, and that is a comfortable arrangement that quietly turns the browser into an archive. Chrome's saved tab groups can reproduce it, and reproducing it is usually a mistake. A weekly pass that closes finished groups rather than saving them keeps the arrangement usable, and anything genuinely worth keeping belongs in bookmarks or in the project's own document, where the rest of the team can find it too.

The place this arrangement breaks down is switching cost. Chrome opens each profile in a separate window with its own menu bar state, and moving between four profiles all day means four windows competing in the window switcher, four Dock behaviors, and notifications arriving from a browser that gives no clue which identity they belong to. A browser designed around one window per web app takes a different route, giving each app a fixed place and its own session rather than making the window the unit of separation. The Workspaces page describes how that grouping is arranged, and the Features page covers what the individual app containers hold.

What to change first

Split the old Edge workspaces into identities and projects on paper before touching Chrome, because the two need different mechanisms and mixing them is what makes the rebuild feel broken. Set up profiles for the identities, tab groups for the projects, and check after a week whether the window switching is the thing costing time. If it is, SpaceDeck is built around the opposite arrangement, with each app in its own container rather than each account in its own browser window.