Google Sheets on the desktop: one window per spreadsheet

Searching for Google Sheets on the desktop usually comes from one of three frustrations, and they need different answers. Either a spreadsheet keeps getting lost among thirty tabs, or a spreadsheet needs to be usable on a train with no signal, or the file opens signed in to the wrong account. The word desktop covers all three, which is why generic advice about installing it as an app satisfies only one of them.

The place to start is the fact that shapes every option: there is nothing to install in the ordinary sense.

There is no Google Sheets application for macOS

The App Store listing for Google Sheets is a mobile listing. Its compatibility section requires iOS 17.0 or later on iPhone and iPadOS 17.0 or later on iPad, and Mac is not listed. Google does not ship a native Sheets client for macOS the way Microsoft ships Excel.

Google Drive for desktop does not close that gap either, and its own documentation is explicit about why. It syncs files to the Mac, but as it puts it, files in Google Docs, Sheets and Slides open in the web browser while other files open in their default desktop applications. So installing Drive for desktop gives a Finder folder full of spreadsheets that each hand off to a browser when double-clicked.

Everything that follows is therefore a way of making a browser behave more like an application. That is not a workaround imposed by a missing product. It is the only shape the product has on a Mac, and once that is accepted the choices get much clearer.

Separating the three wants

A window means the spreadsheet stops being tab number nineteen. It gets its own entry in the Dock and in Cmd+Tab, and closing a tab by reflex cannot take it away.

Offline means the spreadsheet opens and edits with no network, and the edits sync when the network returns. This has the strictest requirements of the three, and they are not negotiable.

The right account means the spreadsheet opens as the identity that has access to it, first time, without a request-access screen. This is the one that wastes the most time and gets the least attention.

Any of the three can be solved on its own. Solving all three at once narrows the options to two, which is worth knowing before spending an hour on the wrong one.

Giving a spreadsheet its own window

Safari, from macOS Sonoma 14 onward

Open the spreadsheet in Safari, then choose File, then Add to Dock. Name it something specific, because the default name will be the spreadsheet title as it was on that day, and a renamed sheet leaves a stale label in the Dock.

Two properties of the result matter for spreadsheets in particular. The first is that Apple documents the web app as sharing no browsing history, cookies, website data or settings with Safari, so it starts with an empty session and asks for a sign-in. That is an advantage here, because it means the window belongs to one account permanently. The second is that these apps are saved to the Applications folder of the home folder, ~/Applications, and deleting one from there removes its stored data with it.

The limitation is offline, covered below, and it is a hard one.

Chrome, and the two menu items that are not the same

In Chrome the option is More, then Cast, save and share, then Install page as app. The result is a windowed application that runs in the Chrome profile that installed it.

The neighbouring item, Create shortcut, does something else. From Chrome 128 onward it produces a bookmark that launches the page in a new tab rather than in a window. Both sit in roughly the same part of the menu and only one of them produces a window, which accounts for a good share of the reports that installing a page as an app did nothing.

Because a Chrome installed app inherits the profile that installed it, the account is decided by which Chrome profile was in front at install time. There is no prompt and no visible indicator afterwards.

Offline has rules, and they are specific

This is where most plans collapse, so it is worth reading Google's requirements as written rather than as remembered. Google's documentation for using Docs, Sheets and Slides offline states that offline files work in the Google Chrome or Microsoft Edge browsers, that the Google Docs Offline extension has to be installed and enabled, that setup requires an internet connection, that private or incognito browsing will not do, and that only one account per browser profile can have offline enabled.

Four consequences follow, and each one kills a popular idea.

Safari cannot do it. A Safari web app for a spreadsheet is an elegant online-only window, which is fine for a shared tracker on an office network and useless on a flight.

A single Chrome profile cannot serve two accounts offline. The one-account-per-profile rule means a consultant with a personal Google account and two client accounts needs three browser profiles, or three separate sessions, to have offline access for all three.

Offline has to be arranged in advance, while connected. Turning it on at the airport does not work, and neither does marking a specific file as available offline after the signal has gone.

Storage matters. Google notes that recent files are saved offline automatically if there is space, and that individual files can be marked as available offline. On a Mac with a nearly full disk, the automatic part quietly stops being reliable, so mark the spreadsheets that matter by hand rather than trusting the automatic selection.

What offline does not cover

Offline access applies to the spreadsheet document, not to everything a spreadsheet touches. A sheet that pulls data with IMPORTRANGE, IMPORTHTML, GOOGLEFINANCE or a connected data source needs the network for those cells, and offline they hold their last cached value or an error. A sheet driven by an Apps Script trigger does not run that script offline either.

This changes what should be prepared before going offline. Copying the live values into a static column, or duplicating the sheet and converting the imported ranges to plain values, is the step that makes an offline copy genuinely usable. Marking the file as available offline and assuming the numbers will be current is the version that fails quietly, because the cells look like numbers rather than like errors.

The account problem, and the number in the URL

A Google URL carries the account position in it, as the /u/0/ or /u/1/ segment. That number is an index into the order in which accounts were added to that browser profile, not a stable identifier for a person.

This causes two specific failures. A bookmark or an installed app that captured /u/1/ will point at whatever account is now in position one, which changes when an account is removed and re-added. And a link pasted from a colleague usually carries their index, which on the receiving machine resolves to a different account entirely and produces a request-access screen for a file the reader already has access to.

The practical rule is that the account belongs to the window, not to the URL. One session per account, with the spreadsheet windows for that account living inside it, removes the whole class of problem. That is what browser profiles do in Chrome, what separate web apps do in Safari, and what a browser that keeps each app in its own workspace does by design.

Route	Own window	Offline editing	Account fixed to the window	Effort
Tab in the main browser window	No	Only if that profile is set up for it	No	None
Safari, Add to Dock	Yes	No	Yes	Under a minute per sheet
Chrome, Install page as app	Yes	Yes, with the offline extension in that profile	Yes, the installing profile	Under a minute per sheet
Drive for desktop	No, it opens the browser	No, Google files need the browser	No	An install
A browser with one window per app	Yes	Depends on the engine	Yes, per space	A download

What actually goes wrong when spreadsheets live in tabs

Three failures repeat, and none of them is about features.

Cmd+W is the first. In a spreadsheet, the reflex that closes a finished tab also closes a half-finished piece of work, and while Sheets saves continuously so nothing is lost, the state is: which cell was selected, which filter view was active, which tab of the workbook was open. Restoring that takes a minute each time and it happens several times a day.

The second is that a spreadsheet is the heaviest thing in the window. A large sheet with volatile formulas recalculates on every edit, and it is competing for the same renderer resources as everything else in that browser. Splitting it into its own window does not make the machine faster, but it does stop a slow spreadsheet from making the rest of the browser feel broken, and it makes the cause obvious rather than mysterious.

The third is find. Cmd+F in a spreadsheet is the sheet's own search, and Cmd+F in a browser is the browser's search, and which one gets the keystroke depends on where focus is. In a dedicated window with no browser chrome the ambiguity mostly disappears. In a tab it never fully does.

There is a fourth that only shows up in shared work. A spreadsheet open in a background tab keeps its presence indicator alive, so colleagues see an avatar sitting in the file all day. That is harmless until someone waits before editing a shared range because it looks occupied, or until a comment goes unanswered because the notification arrived in a window nobody was looking at. Closing the sheet when the work is done is easier to remember when the sheet is a window that has to be quit than when it is one of thirty tabs.

For anyone running several spreadsheets across more than one Google account all day, the per-sheet setup stops scaling at around five windows, because each one has to be created, named, given an icon and maintained. The features page sets out what a browser built around per-app windows handles instead, and the supported apps list shows which services are already configured that way.

What to change first

Pick the one spreadsheet that gets opened first every morning and give it its own window, using Chrome's Install page as app if offline access is needed and Safari's Add to Dock if it is not. Then, before the next trip, turn on offline access while connected and mark that sheet as available offline, since that step cannot be done later. If the count of windows to maintain is already past five, or if two Google accounts are in play, a browser that gives every app its own space such as SpaceDeck is the setup that does not need rebuilding each time.