Chrome Workspace Download: What There Is to Install
Searching for a chrome workspace download returns a mixture of a browser installer, a productivity suite, a Chrome Web Store listing, and a handful of pages that are none of those. The reason is that the phrase points at four different things, and only one of them is an actual file.
Sorting the four takes a few minutes and saves a wasted install. What follows is what each one puts on a Mac, what it does after it lands, and which of them survives a machine change.
There is no single file with that name
Google does not ship a product called Chrome Workspace. Two separate names are being compressed into one phrase.
Google Workspace is the productivity suite: Gmail, Calendar, Drive, Docs, Meet, and the admin console behind them. It is a service, not an application, and there is nothing to download to start using it. Google's own guidance for the suite points at running it in a browser rather than at installing anything.
Chrome is the browser, and it does have a download. It comes as a universal installer for macOS, offered as either a PKG or a DMG on the enterprise download page for administrators who need to deploy it, and as a standard installer for everyone else.
The third source of the phrase has nothing to do with Google. Several browsers use the word workspace for a saved set of tabs and windows, and several Chrome extensions do the same. Anyone who has used one of those and then gone looking for the equivalent as a download ends up on the same search. That is the meaning worth the most attention, because it is the one where the choices differ.
Meaning one: installing the browser for a Workspace account
If the goal is running a work account's mail and calendar, the only required download is the browser itself. Nothing else needs installing, and the suite runs entirely in the browser window.
Two details matter on a Mac. The first is that installing the browser does not sign anything in. The account is added afterwards, and if the organisation has enabled the Chrome Enterprise policy that requires a separate profile for a managed account, the sign-in will prompt for one. Google's documentation for that policy describes the result in one line: no data or content is shared between profiles. That is a boundary worth having, and it is also the point at which one browser starts producing several windows that macOS cannot distinguish.
The second detail concerns deployment. The enterprise download page offers the browser as a PKG or a DMG universal installer covering both Intel and Apple silicon, alongside policy templates and update management templates for machines under management. For a single Mac, the ordinary installer is the right one. The enterprise packages exist so that an administrator can push the browser and its policies to many machines at once, and running one on a personal Mac gains nothing.
Meaning two: turning a Workspace app into its own window
This is the download that most people are actually looking for, and it is not a download at all. Chrome can install a page as an application, which produces a separate window with its own Dock icon and no address bar.
The route is in the browser menu, under the option for casting, saving, and sharing, where an entry installs the current page as an app. Applied to a mail or calendar page, the result behaves much closer to a desktop client than a tab does.
What the installed window inherits is the part to understand before doing it. The window is bound to the browser profile it was created in, and it carries that profile's session, including whichever account is default. Installing a mail window from a profile holding three signed-in accounts produces a window that still holds three accounts and the same ambiguity about which one answers. One account per window requires one profile per account first, and the install second.
The other limit is that this covers one page at a time. A workspace in the sense of a named set of tools, restored together, is not what installing a page produces. Six installed windows are six separate things with no relationship to each other.
Doing it in the right order
The order of the steps decides whether the installed windows are useful or just relocated tabs.
Create the profile first, one for each account that needs to stay signed in independently. Give it a name and a colour, since the colour is the only identity marker visible from across the room. Sign that one account in, and add nothing else to it.
Install the pages second, from inside that profile. Each install produces a window bound to that profile, so a mail window created from the work profile stays on the work account regardless of what happens in the personal one.
Place the results third. Installed apps appear in the applications list and can be kept in the Dock, which is what makes them reachable without going through the browser. At this point the same services should be closed in the ordinary browser window, because leaving both open means notifications arrive twice and it stops being obvious which copy is authoritative.
The residual cost is that every profile is still the same macOS application underneath, so the application switcher groups them together even when the windows are separate. That is the boundary of what this route can do.
Meaning three: downloading a workspace extension
The Chrome Web Store carries extensions that group tabs into named workspaces and restore them later. They are free to try and quick to remove, which makes them a reasonable first step. Three things are worth checking before relying on one.
Check the manifest generation. Chrome disabled Manifest V2 extensions for all users on all channels with Chrome 138 in July 2025, and the remaining Manifest V2 items were removed from the Chrome Web Store on 31 August 2026. Anything found through an older article or a mirror site may no longer install at all.
Check the last update date on the listing. Tab management is a category with a long tail of abandoned projects, and an extension untouched for two years is one that has not been tested against recent browser changes.
Check where the data is kept. Most of these extensions store their workspaces in the browser's local storage, which means the saved sets belong to that profile on that machine. Reinstalling on a new Mac does not bring them along unless the extension has its own account and sync.
Permissions are the fourth thing to look at, and the one most often skipped. A tab workspace extension has to read tab titles and addresses to do its job, which means granting access to the pages being visited. That is a reasonable ask for the function, and it is also a broad grant to hand to an unknown developer. The listing shows the requested permissions before installation, and reading them takes less time than recovering from a bad choice. An extension that asks for more than its description explains is worth skipping regardless of how good the reviews are.
There is also a quieter failure mode. Extensions that restore tabs work by closing the current set and opening a saved one, which means anything unsaved in those tabs is gone at the moment of switching. For pages being read this costs nothing. For a half-written message or a filtered dashboard it costs the work. Testing a switch on a set of throwaway tabs before trusting it with a working session is a small step that prevents an avoidable loss.
The structural point is that an extension operates inside the tab model. It can name and restore sets of tabs. It cannot give a set its own cookie store, its own Dock icon, or its own place in the application switcher, because none of those are things an extension is allowed to create.
Meaning four: downloading a browser where the workspace is the unit
The last interpretation is a browser in which workspaces are built in rather than added. Several exist, and they differ in what a workspace contains.
| Approach | What a workspace holds | Separate sessions | Reachable from macOS |
|---|---|---|---|
| Extension on top of Chrome | A named set of tabs | No, one profile session | No, all inside one window |
| Chrome profiles | Everything, per profile | Yes | One app icon for all of them |
| Browser with built-in workspaces | Tabs, and often storage | Depends on the browser | Depends on the browser |
| App aggregation browser for macOS | One service per space, with its own storage | Yes | Own window, own switcher entry |
The distinction that matters is whether a workspace is a label or a container. A label groups tabs for tidiness. A container gives the group its own cookies, so two accounts on the same service can stay signed in at once. The second is what removes account switching from the daily routine, and it is the reason the two things should not be compared on tab handling alone. The Workspaces page describes what a container-style workspace holds, and the Supported apps list shows which services run inside one without extra setup.
Before installing anything in this category, it is worth checking that the project is still maintained. Browsers in this space have changed hands and stopped development, and one well-known workspace browser now redirects its old domain to a different company's product. A download page that still exists is not evidence that the software is still being built.
What no download restores
Whichever route is taken, three things do not arrive with an installer.
Sessions do not transfer. Signing in happens after installation, once per account, on each machine.
Profile data is not portable in any supported way. Copying a profile folder between Macs is not a documented migration path, and the browser's own sync covers bookmarks, history, passwords, and settings rather than everything in the folder.
Tab groups behave differently from what people expect from a backup. Google's documentation states that deleting a tab group removes it on that device and on other devices using the same account, and that ungrouping tabs also deletes the group across devices. A synced group is not an archive.
When you delete a tab group, it'll be removed on your device and other devices that use the same Google Account. Source: support.google.com
Which install to make first
Start by deciding whether the goal is tidier tabs or separate accounts, because the two lead to different files. Tidier tabs is an extension or a layout setting and costs nothing to try. Separate accounts is a container, which means either one browser profile per account or a browser that treats each space as its own session, the arrangement SpaceDeck is built around. Installing the wrong one first is how an afternoon disappears.
Frequently asked questions
Is there an official Chrome Workspace app to download?
No. Google ships Chrome as a browser and Google Workspace as a set of web services, and there is no product combining the two names. The closest official option is installing a Workspace page as an app from the Chrome menu, which creates a standalone window rather than installing new software.
What is the difference between the normal Chrome download and the enterprise one?
The enterprise download page offers the browser as a PKG or DMG universal installer for Intel and Apple silicon, together with policy and update management templates. Those extras exist for administrators deploying the browser to many machines. On a single personal Mac the ordinary installer gives the same browser.
Do workspace extensions keep working after the Manifest V2 removal?
Only those built on Manifest V3. Chrome disabled Manifest V2 extensions for all users with Chrome 138 in July 2025, and remaining Manifest V2 items were removed from the Chrome Web Store on 31 August 2026. Checking the listing's last update date before installing avoids the problem.
Can a downloaded workspace move to a new Mac?
Usually not by itself. Most tab workspace extensions store their data in the local browser profile, so a fresh install starts empty unless the extension offers its own account and sync. Browser sync covers bookmarks, history, passwords, and settings, which is not the same as moving a saved workspace.