Google Documents on the desktop: a window instead of a tab

Searching for Google Documents on the desktop rarely means searching for an installer. It usually means a document that keeps getting lost behind twenty other tabs, a document that has to be editable on a train with no signal, or a document that opens signed in to the wrong account and shows a request for access.

None of those are solved by finding an application, because there is no application to find. What exists instead is a set of official pieces that each solve one part of the problem, and knowing which piece solves which part turns a vague want into a short decision.

What Google ships for the desktop, and what it does not

There is no native Documents editor for macOS. The editing happens in a browser, and Google's own documentation for its desktop software says so plainly.

Drive for desktop is the closest thing to a desktop client, and it is a file access tool rather than an editor. Its help page describes opening the Google Drive folder in Finder and double-clicking a file, then states the outcome directly: files in Google Docs, Sheets, and Slides open in the web browser, while other files open in their default desktop applications. A Word file in that folder opens in Word. A Google document in that folder hands off to a browser.

The same page draws a second distinction that matters for anyone short on disk space. It warns that the space tracker in Drive for desktop shows the room left on the computer's hard drive, not the Google Account storage, and that streaming a file uses almost no computer space while mirroring downloads a full copy directly to the computer.

So the desktop question becomes a browser question. That is not a defeat. It narrows the options down to four, and the four differ in ways that are easy to compare.

Four setups, and what each one gives

Each row below is a real arrangement someone is using today. The columns are the three things people actually want when they type desktop.

Setup	Its own window	Works with no network	Several accounts at once
A tab in the main browser	No	Only with the offline extension	Only by switching profiles
The page installed as an app window	Yes	Only with the offline extension	One account per window, set by profile
Drive for desktop	Finder access, then the browser opens	Files can be made available offline	Yes, several accounts at the same time
A browser that keeps each web app in its own window	Yes	Follows the browser's offline support	Yes, one per workspace

Two things stand out. Offline is a property of the browser and the account, not of the window, so no amount of window arranging delivers it. And several accounts at once is the feature that separates the setups most sharply, because a single browser profile holds a single default account.

The window, and what changes when a document stops being a tab

A document in a window gets a Dock entry, a place in the application switcher, and immunity from the reflex that closes tabs. That is the whole benefit, and it is larger than it sounds for anything that takes an hour of attention.

Google itself ships one of its web apps this way, which is useful as proof that the pattern is supported rather than improvised. The help page for the Meet Progressive Web App describes installing it from the Install control in the URL bar, requires Chrome version 73 and up, and notes that the app then appears in the app dock and updates when Chrome updates. The same mechanism, an installed page running in its own window, is what any installable site gets.

What a window does not do is change the underlying engine. Notifications, permissions and sign-in state still come from the browser that installed it. A window is a container, and the container is exactly the thing that was missing when a long document sat in the middle of a tab strip.

There is one honest cost. Each window is another thing to manage, and a person who installs eight of them has traded a crowded tab strip for a crowded Dock. The arrangement pays off when the window holds something returned to many times a day, and it does not pay off for a page opened once a month.

The choice of what deserves a window is therefore worth making deliberately rather than by enthusiasm. A reasonable test is whether the thing is opened before the first meeting of the day and closed after the last one. Mail passes that test. A document being drafted over a week passes it. A document read once to check a figure does not, and putting it in a window only adds a step to closing it.

A second point is worth knowing before installing anything: links behave differently once a window exists. A link to a document clicked in chat still opens in whatever browser is set as the default, not in the installed window, so the window and the tab strip can end up holding the same document twice. This is not a fault to fix so much as a habit to form, which is to open the window first and navigate inside it.

Offline access has exact requirements

Offline is the strictest of the three wants, and the requirements are published rather than folklore. Google's page on working offline lists them before the steps:

• An internet connection is needed to set it up.
• The browser has to be Chrome or Edge. No other browser is listed.
• Private browsing cannot be used.
• The Google Docs Offline extension has to be installed and turned on.
• There has to be enough free space on the device to save the files.

The switch itself is in Drive. Open Drive, click Settings at the top right, and turn on the Offline setting. Edge users are redirected to the Chrome Web Store to get the extension. Turning offline access on for Docs, Sheets, Slides or Drive turns it on for the rest, and turning it off for one turns it off for the others.

Two details decide whether a specific document is actually available on the train. First, some recent files are saved automatically when there is enough storage, but a particular file can be chosen by hand: on the Docs, Sheets or Slides home screen, use More on the file and select Available offline, and a check mark appears to confirm. Second, and this is the one that catches people, offline access belongs to a browser profile. Google's page states that to use offline access for another Google Account, the right Chrome or Edge profile has to be signed in.

That last line is why the offline want and the multiple accounts want collide. Turning offline on for a work account does nothing for a personal account living in the same browser under a different profile.

Safari is not on the offline list

Anyone who reads mail and documents in Safari on a Mac hits a wall here that is worth stating plainly, because it is a platform fact rather than a setting to hunt for. The requirement list names Chrome and Edge. Safari and Firefox are not on it, and no extension in the Safari gallery changes that.

The practical consequence is a split browser life. Documents that have to survive a flight need Chrome or Edge, which means a second browser gets installed for that purpose alone, and then the account question starts again inside the second browser. This is the most common route by which a Mac ends up with three browsers open and a different set of signed-in accounts in each.

There are two reasonable responses. The first is to give up on offline and accept that a lost connection means a lost hour, which is a defensible choice for anyone who works in one place with reliable network. The second is to decide that the browser used for work documents is Chrome or Edge, set it up once, and stop treating browser choice as a matter of taste for that one job. Mixing the two, and discovering the requirement while boarding, is the outcome worth avoiding.

The number in the URL, and the access request that follows

Open two Google accounts in one browser and the address of a document gains a number: a segment such as /u/0/ or /u/1/ that names which signed-in account the page is being served to. Most account confusion on a Mac traces back to that segment.

The visible symptom is a request for access on a document that is genuinely shared, because it was shared with the other account. Nothing is broken, and no permission needs changing. The page is simply being opened as the wrong person.

Drive for desktop handles this more gracefully than a browser does. Its documentation lists using multiple accounts at the same time as a supported feature, which means the Finder side of the arrangement can hold work and personal Drives together. The browser side remains one default account per profile, so a link clicked from Slack or Mail lands in whichever profile is frontmost.

Three arrangements reduce the collisions, in increasing order of effort. Keep one account per browser profile and accept the switching. Keep the second account in a separate browser entirely. Or give each account its own persistent window, which is what a browser that keeps each web app in its own window is built to do, with the Workspaces page describing how that separation is held.

An hour of writing, and what tabs do to it

Documents differ from spreadsheets and slides in one practical way: the work is long and continuous. A spreadsheet is consulted, a deck is presented, a document is written for an hour with research open alongside it.

That pattern is exactly what a tab strip handles worst. The document ends up adjacent to the sources being read, which means it competes for the same row of space, and Cmd+W on a misjudged tab closes the wrong thing. Recovering the tab is possible, but the interruption has already happened.

The second issue is attention rather than layout. Comment notifications, chat and mail all arrive in the same window as the writing, and the switch away is a single click. Separating the document into its own window does not silence anything, but it removes the adjacency: getting to the inbox becomes a deliberate move rather than a glance.

The third is more mundane and more common. A browser restart, an update, or a crash takes the whole tab strip with it. A document in a window that is opened on purpose each morning is easier to bring back than tab nineteen of thirty, and the list of services that can be held in separate windows this way is on the Supported apps page.

What to change first

Decide which of the three wants is the real one before changing anything, because the fix for each is different. If the want is a window, install the page or give it a dedicated window. If the want is offline, install the Google Docs Offline extension in Chrome or Edge and mark the specific file as available offline. If the want is two accounts without confusion, separate them by profile or by workspace.

Then pick the arrangement for the account that gets used most, and leave the rest in tabs. One window for the document being written this week, one for mail, and everything else transient, is a setup that holds. Pricing and platform details for keeping each app in its own window are on the SpaceDeck page.