Browsers with Edge style workspaces on a Mac

Someone who lived in Edge Workspaces on a Windows machine and then moved to a Mac usually arrives at this search with a specific picture in mind: a named button that opens the eleven tabs belonging to one project, and nothing else. The picture is reasonable. What complicates the search is that every browser now ships something called workspaces, spaces, or tab groups, and the four features are not interchangeable. One of them syncs tabs between people. One of them separates logins. One of them does neither and just colors the tab strip.

Sorting that out first saves an install. What follows is what Edge Workspaces actually is, which macOS browsers offer the closest match, and how to tell which of the three underlying problems is the one in play.

What Edge Workspaces is, precisely

An Edge workspace is a named set of tabs that lives with the signed in account rather than with the window. Opening one launches a separate browser window containing that set. Closing it puts the tabs back in storage. The set can be shared with other people, and when it is shared, tabs open and close live for everyone in it, which makes it closer to a collaborative document than to a bookmark folder.

Two properties matter more than the rest.

A workspace does not separate logins. It belongs to a browser profile and uses that profile's cookies. Two workspaces in the same profile are signed in to the same accounts, which means a workspace cannot hold a second Slack account or a second Gmail account on its own.

Signing in is required. Workspaces are tied to a Microsoft account or a work account, because syncing and sharing are the point of the feature. That also means availability has depended on the account type and the release channel, so the honest instruction for a Mac is to open the Edge menu and look rather than to trust a general statement about platform support.

Edge for macOS exists and is actively maintained, so for a reader whose only requirement is the exact Edge feature, staying in Edge is the shortest path. The rest of this article is for readers who cannot or would rather not.

Three different problems wear the same name

The search term covers at least three distinct complaints. The right tool depends entirely on which one applies.

The first is grouping. Eleven tabs belong together and should open and close as a unit. This is a tab management problem, and every major browser now solves it.

The second is isolation. The same service has two accounts and both need to be usable without signing out. This is a cookie problem, and tab groups never solve it.

The third is switching. The tabs are already grouped, the accounts are already separate, and finding the right window still costs attention forty times a day. This is a window management problem, and it lives at the operating system level rather than inside the browser.

Most people searching for a workspace feature have the first problem and discover the second within a month. The third one is the one that survives every browser change, because it was never a browser feature to begin with.

The macOS options, one by one

Chrome tab groups

Chrome groups tabs under a colored, named label. Groups can be collapsed to a single chip, and saved groups persist after the window closes and sync to the same account on other devices. This is the closest functional match to the solo use of an Edge workspace. It shares the profile's cookies, so it does nothing for isolation. Chrome's own documentation on grouping and on profiles is the reference worth reading before building anything, and it is available in the Chrome Help centre.

Safari tab groups and profiles

Safari has both halves in separate features. Tab groups hold named sets of tabs and sync through iCloud. Profiles, added in macOS Sonoma, keep separate cookies, history, extensions, and their own tab groups. Combining them gets a reader closer to the full picture than any single feature in any other browser: grouped tabs inside an isolated identity. The cost is that switching between profiles is a menu, and macOS still treats it all as one application named Safari.

Vivaldi Workspaces

Vivaldi uses the word workspace for a named set of tabs inside a window, switchable from the tab bar. It is the most literal match to the Edge vocabulary and it is available on macOS. Like the others, it groups without isolating, since the cookie jar belongs to the profile.

Arc Spaces

Arc splits the sidebar into named Spaces, and a Space can be assigned to a specific profile. That assignment is the part most reviews skip, and it is the part that makes Spaces capable of holding two accounts of the same service. Arc stopped receiving new features in 2025, so the feature set is now fixed. For a reader who only needs what already exists, that is a stable target rather than a problem.

Firefox Multi-Account Containers

Mozilla's free extension gives each container tab its own cookie jar inside one window, with a colored underline and the option to pin a site to a container permanently.

Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs.

Source: support.mozilla.org

This is the only free way to put two accounts of the same service side by side in one window. It solves isolation and grouping at the tab level, and leaves the switching problem exactly where it was.

A second browser, used deliberately

The oldest answer in this category is still the cheapest. Running one browser for work and a different one for everything else gives two dock icons, two application switcher targets, and two completely separate cookie jars, with no configuration at all. It is worth mentioning because it beats several paid options on the switching problem specifically.

It stops working at three. A third and fourth browser means remembering which application holds which account, and the memory cost grows faster than the benefit. The technique is excellent for a hard two way split and poor for anything more granular.

Comparison by what the reader actually needs

Option	Named set of tabs	Separate logins	Shared with other people	Window per context
Edge Workspaces	Yes	No	Yes	Yes, one window per workspace
Chrome saved tab groups	Yes	No	No	No
Safari tab groups	Yes	No	No	No
Safari profiles	Through tab groups	Yes	No	Yes
Vivaldi Workspaces	Yes	No	No	No
Arc Spaces with a profile each	Yes	Yes	No	No
Firefox containers	Per tab	Yes	No	No
A browser that keeps each web app in its own window	Per app	Yes	No	Yes

The right hand column is the one that gets ignored during a comparison and then decides how the day feels. A named tab set inside one window still requires the reader to be looking at that window. A separate window per context puts the switch on Command Tab or on a dock icon, which is a different motion entirely.

Where the sharing part goes missing

The feature people miss most after leaving Edge is not the grouping. It is the live shared workspace, where a colleague opens a tab and it appears for everyone in the set. Nothing else in this list reproduces that, because the rest of these features are personal rather than collaborative.

The practical substitute is to stop asking the browser to do it. A shared set of links belongs in the tool the team already uses for shared things: a pinned message, a page in the team wiki, a shared bookmark folder. What made the Edge version pleasant was that it was one click away, and that convenience can be rebuilt by giving the shared page a permanent home rather than by finding a browser that syncs tabs.

Rebuilding a workspace setup without recreating the mess

A move between browsers is the cheapest moment of the year to drop things, and the moment most people waste by importing everything.

Start from the list of projects rather than the list of tabs. An Edge workspace usually accumulates around a project, and a fair number of those projects have ended. Writing down the projects that are genuinely active this month produces a shorter list than the browser suggests, and every tab that does not belong to one of them is a bookmark rather than a workspace member.

Then separate permanent tools from temporary reading. A service opened every hour deserves a fixed slot. A documentation page opened twice deserves nothing. Setups get heavy because both were pinned with equal ceremony, and heavy setups are what push readers to search for a new browser in the first place.

Finally, decide the boundary before choosing the tool. Grouping by service produces a tidy list that solves nothing when two services each have two accounts. Grouping by identity, meaning the company self, the personal self, and one entry per client, survives the addition of a new service later. The order matters: pick the boundary, then pick the mechanism that draws it.

Deciding by frequency, not by feature list

Count how many times a day the context actually changes. That number picks the tool more reliably than any table.

A handful of switches a day means tab groups are enough, in whichever browser is already installed. There is no reason to migrate for this.

Several switches a day involving two accounts of the same service means the constraint is cookies. Safari profiles, Arc Spaces with profiles assigned, or Firefox containers all solve it, and the choice comes down to whether the two accounts need to be visible at the same time.

Dozens of switches a day across many services means the constraint is neither grouping nor cookies. It is that everything lives inside one application, so the fast path through macOS leads to a browser rather than to a task. That is the case where giving each service its own window and its own dock presence changes the shape of the day. The Workspaces page describes how those windows are arranged by project rather than by service, and the Features page sets out which browser behaviors are kept in that model and which are deliberately left out.

Before installing anything in that last category, it is worth reading a direct comparison rather than a feature list. The Compared with Wavebox page covers the closest tool in terms of scope, and the Compared with Ferdium page covers the free and open source end of the same idea.

What to change first

Open the current browser and check whether the tab sets in use share one profile, because that answer decides whether the problem is grouping or isolation. If they already sit in separate profiles and switching still costs attention, the remaining constraint is window management, and SpaceDeck is built around that boundary rather than around the tab strip.