What a Chrome workspace can and cannot keep separate

No. Google Chrome does not have a user feature called workspaces. What Chrome ships instead is a set of smaller tools that each cover part of the idea: profiles keep accounts and passwords apart, tab groups keep sets of tabs together and can be saved and reopened, and named windows let a window carry a label. The only thing inside Chrome actually named "Workspace" is a developer tool in DevTools that saves code edits back to files on disk. Microsoft Edge, which is built on the same engine, does have a feature called Workspaces, and the Chrome Web Store has several extensions that add something similar. The rest of this page lays out what each option separates, checked against the official help pages on October 18, 2026, so the choice comes down to which layer of the problem is unsolved.

This site is published by the maker of SpaceDeck, a multi-account browser for macOS. The comparison below sticks to what each vendor documents.

Why the search returns three different "workspaces"

The phrase points at three unrelated things, which is why the results look scattered.

Google Workspace is the paid suite of Gmail, Drive, Docs and Meet for organizations. It has nothing to do with how Chrome arranges tabs. Its connection to Chrome is only that its apps run in a browser.

Chrome DevTools Workspace is a developer feature. According to the Chrome for Developers documentation, connecting a workspace folder lets changes made in the Sources panel to CSS, HTML and JavaScript be saved to the local source files. It is set up under Sources, then Workspace, and it only makes sense for someone running a site from a local server. It does not organize browsing.

Workspaces in the productivity sense means a named set of tabs, and often accounts, for one project or client, which can be closed and reopened as a unit. This is what most people searching the question want, and it is the meaning used for the rest of this article.

Keeping those three apart matters because advice written for one does not transfer to the others. A guide that says "set up a workspace in Chrome" may be talking about DevTools, and following it will not change the tab strip at all.

What Chrome offers today: three partial answers

Chrome covers the productivity meaning through three features that were designed separately and do not know about each other.

Profiles: the account layer

The Chrome Help page on profiles says profiles separate Chrome information such as bookmarks, history and passwords, and lists using different accounts for work and personal use as a reason to create one. A new profile is added from the profile icon at the top right, then Add Chrome profile, and it can be given its own name, photo and theme color. Each profile opens in its own window with its own cookies, so two Google accounts in two profiles stay signed in at the same time without interfering.

Tab groups: the task layer

The Chrome Help page on managing tabs describes tab groups in detail. Right-click a tab, choose Add tab to group, then New group, and the group can be named and colored. A group can be collapsed so only its name shows. Closing a group from the tab strip with Close group does not delete it. It is saved and can be reopened from the bookmarks bar or from the Tab groups menu. When history and tabs are synced to a Google Account, changes to groups are saved and synced across devices.

That save and reopen behavior is the closest thing Chrome has to a workspace. A group called "Client A" can hold six tabs, be closed at the end of the day and come back tomorrow intact.

Named windows and vertical tabs: the layout layer

The same help page covers two more pieces. A window can be named by right-clicking the empty space next to the New tab button and choosing Name window, and the name appears when switching windows. Tabs can also be shown vertically, from the View menu on a Mac with Show Tabs Vertically, which keeps full page titles visible down the side of the window.

Where the partial answers stop

Each tool works on its own layer, and the gaps sit where the layers meet.

Tab groups share one account. All groups inside a profile use the same cookies. A group labeled "Client A" and a group labeled "Client B" cannot be signed in to two different accounts of the same service. If both clients use Google Workspace and give out separate addresses, the groups will fight over which account Google treats as current.

Profiles do not organize tasks. A profile separates accounts but has no idea which tabs belong to which project. A person with three clients and two personal accounts ends up with five profile windows, each holding its own tab strip, and the work of remembering which window is which falls back on the person.

Moving work between them is manual. The help page notes that moving a tab to another window requires both windows to be signed in to the same profile. A tab cannot be dragged from one profile into another. Opening a link from email or chat sends it to whichever profile Chrome considers the default, not to the profile that holds the right account.

Saved groups are tied to sync. Deleting a group removes it from every device using the same Google Account. Ungrouping does the same to the group while leaving the tabs open. That is useful for consistency, but it means a cleanup on one machine changes every other machine.

Incognito is not a second workspace. Opening an Incognito window is a common workaround for a second login, but the Chrome Help page on Incognito explains why it does not last. Chrome starts a separate browsing session, does not sign in to the Google Account or other sites automatically, and removes cookies and site data when every Incognito window is closed. Opening a second Incognito window continues the same session rather than starting a new one. That makes it fine for a one-off check of another account and useless for keeping a client signed in from one day to the next.

None of this is a defect. Each feature does what its help page says. The gap only appears when someone expects one of them to be a complete workspace.

Microsoft Edge Workspaces and Chrome extensions

Two other routes come up in the results.

Microsoft Edge has a feature that is actually called Workspaces. The official Edge Workspaces page describes it as organizing browser tabs by project, with tabs and favorites saved and kept up to date. It lists the requirements as a desktop running Windows 10, Windows 11 or macOS, Edge version 144 or later, and being signed in to Edge with a Microsoft account or a Microsoft Entra ID account. Workspaces are opened from the workspaces menu or from Search tabs, and a new workspace can start blank or from the tabs already open. The same page states that sharing and joining workspaces are not supported in the new Edge Workspaces experience. Workspaces sync through the Workspaces and Tab Groups option in Edge's Sync settings.

So Edge answers the task layer more directly than Chrome does. It still runs inside one Edge profile, so the account question is handled the same way as in Chrome: through separate profiles.

The Chrome Web Store lists several extensions with "workspace" in the name. They generally save sets of tabs and restore them on demand. Because they run inside a profile, they inherit the same cookie jar as everything else in it. They help with the task layer and leave the account layer where it was. Before installing one, the store listing's Privacy section shows what data the developer declares it handles, which is worth reading since a tab manager can see every URL that is open.

How the options compare

Option	Keeps accounts apart	Saves and reopens a set of tabs	Needs a sign-in	Cost
Chrome profiles	Yes, one profile per account	No	No	Free
Chrome tab groups	No	Yes, from the bookmarks bar or Tab groups menu	Only for sync across devices	Free
Edge Workspaces	No, uses the current profile	Yes	Yes, Microsoft account or Entra ID	Free
Tab manager extensions	No	Yes	Depends on the extension	Varies
App aggregation browser	Yes, one container per app	Yes, apps grouped into spaces	Varies by product	Varies

The table makes the pattern plain. The free built-in tools split into two camps: one keeps accounts apart, the other keeps tasks together. Getting both at once in Chrome means stacking profiles and tab groups and accepting the window juggling that comes with it.

An app aggregation browser takes a different shape. Instead of tabs inside profiles, each web app gets its own container for cookies and storage, and apps are grouped into spaces. The Workspaces page for one such browser describes Gmail, Slack and Notion accounts staying signed in at the same time in separate containers, with nothing signed out when switching spaces. Its pricing page lists a free plan limited to 1 workspace with up to 3 apps after a 14-day trial, and a Pro plan from $5 a month billed yearly or a one-time $129, which unlocks unlimited workspaces and apps and multiple accounts per service. That is a different trade from Chrome's free tools: it costs money past a small setup, and it only runs on a Mac.

Picking by which layer is missing

The fastest way to choose is to name the layer that is actually causing trouble.

The tab strip is the problem, accounts are fine. One Google account, too many tabs, and a need to put a project away at night. Chrome tab groups already do this. Name a group per project, close it with Close group, and reopen it from the bookmarks bar. If the full page titles matter, turn on vertical tabs. No extension is required.

Accounts are the problem, tabs are fine. Two Gmail addresses or two Slack workspaces that keep signing each other out. Chrome profiles solve this. One profile per account, each with a distinct theme color so the windows can be told apart at a glance. The cost is more windows, not money.

Both layers are the problem. Several clients, each with its own accounts, each with its own set of tools, and links arriving from chat that need to land in the right account. This is where stacking profiles and tab groups starts to cost real time each day, because every link and every switch requires choosing a window by hand. Edge Workspaces does not change the account side. This is the case where a tool built around per-app containers, such as the ones covered in the comparison with Wavebox, is worth evaluating.

The search was about code. If the goal is saving CSS edits from DevTools back to a project folder, the DevTools Workspace feature is the answer and none of the above applies.

What to change first

Start with the built-in tools: one Chrome profile per account, and a named tab group per project inside each profile. Use that for a week and count how often a link opens in the wrong account or a window has to be hunted for. If that count is near zero, the setup is done; if it is several times a day, an app browser with separate containers per app, such as SpaceDeck, removes the window choice from each switch.