A Google Sheets app for the desktop: what it takes to get one

Searching for a Google Sheets app for the desktop tends to end the same way. There is no installer that drops Sheets into the Applications folder, and the Mac App Store has no entry for it. What exists instead is a set of separate parts that, assembled, behave close enough to an application that the difference stops mattering. The useful work is figuring out which part answers which complaint, because the three complaints people bring to this search have three different fixes.

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

Google's downloadable software for macOS is Drive for desktop. It puts Drive files into the Finder and syncs them. It does not contain the Sheets editor. A Google Sheets file that appears in that mounted folder is a small pointer file, and double-clicking it hands the work straight back to a browser tab. The spreadsheet engine lives on Google's servers and renders in a web view. That is the design, not an oversight.

The clearest evidence of that design is how Google solves offline editing. It is not an application. It is a browser extension. The Google Docs Offline listing in the Chrome Web Store is published by Google Ireland, Ltd., was last updated on September 16, 2026, and weighs 157KiB. Its own description says it lets you "Edit, create, and view your documents, spreadsheets, and presentations, all without internet access", and, more plainly, that it "transforms Chrome into an offline editor". A 157KiB download is not a spreadsheet engine. It is a switch that tells the browser to keep a working cache and to service requests from it.

So the honest framing of this search is not "where is the app". It is: of the things an application would have provided, which ones are actually needed, and which parts of macOS and the browser already supply them. Storage sits underneath all of it. A personal Google Account starts at 15GB, and Google's own Drive page describes business storage as scaling from 15GB to 5TB per user, with the option to request more. None of that quota is what makes a file available on a train, which is a separate switch entirely.

The three complaints hiding inside the word "app"

Almost everyone arriving at this query wants one of three things, and they rarely say which.

The first is a window that stays where it is put. Sheets opened in a tab is one of forty tabs. It gets dragged between windows, it gets closed by a stray Command-W, and after a browser restart it comes back in a different position or not at all. This is a window management complaint, not a Google complaint.

The second is offline access. A train, a flight, a conference venue with a captive portal that keeps dropping. This one genuinely needs Google's cache layer, and that layer only exists inside Chromium browsers with the extension installed and offline access switched on in Drive settings.

The third is accounts. A work Google Account and a personal one, or three client accounts, and the account switcher inside Google's own interface that keeps sending the wrong identity to a shared file. This is a cookie isolation problem. No amount of window wrapping fixes it, because a wrapper that borrows the default browser profile inherits the default browser's signed-in state.

Naming which of the three applies is worth doing before installing anything, because two of them are solved by macOS and the browser already on the machine, and one is not.

The reason the three get conflated is that a native application would have delivered all three at once. A real Sheets application would have its own window, its own local file store and its own account list, the way a mail client does. Because the editor is a web application, those three properties come from three different layers: the window from the operating system, the local store from the browser engine, and the account from the cookie jar. Any setup that treats them as one thing ends up half working, and the half that fails is usually whichever one was never actually configured.

Offline is the part only the browser can give you

Offline editing in Sheets is not a file format feature. There is no local document that a generic viewer can open. The browser holds a cached copy of the editor and of the documents flagged for offline use, and reconciles changes when the connection returns. That is why the requirements are narrow.

It needs a Chromium browser, because the extension is distributed through the Chrome Web Store. It needs offline access turned on in Drive's settings, not just the extension installed. And it needs the specific files pinned, because, as the listing puts it, only "hundreds of your most relevant documents are automatically made available for offline viewing and editing" unless you mark more.

The failure mode matters here. A plain window wrapper built on a web view that is not Chromium, or one that does not carry the extension, will show a network error page the moment the connection drops. It will look like an app right up until the point where being an app would have helped. If offline is the real reason for this search, the answer is a Chromium browser with the extension, and everything else is decoration.

Four ways to put Sheets in its own window

Approach	Own window	Offline editing	Separate accounts	Cost
Safari profile window	Window, but with tabs	No	Yes, per profile	Included with macOS
Chromium browser, page installed as an app	Yes, one window per app	Yes, with the extension	Only by switching profile	Free
Drive for desktop plus a browser tab	No	No	Follows the browser	Free
A browser that keeps each web app in its own window	Yes, one window per app	Depends on the engine	Yes, per workspace	Varies

Safari's approach is profiles. The steps are short: open Safari settings, click Profiles, click the add button, name it, pick an icon and colour, choose a bookmarks folder, then click Create Profile. Switching is File, then New Window, then the profile's own window command. Extensions are selected per profile. Passwords stored in iCloud Keychain stay available across all of them, which is convenient and also means profiles separate browsing state rather than identity wholesale. Deleting a profile erases its tabs, history and website data.

Chromium browsers can install a page as an app, producing a standalone window with its own Dock icon and no address bar. That removal is more useful than it sounds. With no address bar, Command-L stops stealing focus and reaches the page instead, and the window has no tab strip for a spreadsheet to get lost in. The limit is account isolation: an installed app window belongs to the browser profile that installed it, so two accounts means two profiles and two sets of installed windows to keep straight.

A dedicated app aggregation browser takes the third position, treating each web app as a first-class window with its own persistent session. That is the same trade the browser profile makes, with the bookkeeping moved out of your head. Whether that is worth anything depends entirely on how many accounts are in play. For one Google Account, it is not.

The account problem, stated precisely

Google's account switcher works at the application layer. The browser still sends one cookie jar per profile, and Google reconciles which identity you meant. This is why a link pasted from a work chat opens under the personal account, and why "you need access" appears for a file you demonstrably own under a different identity.

Profiles fix it because they change the cookie jar rather than the label on it. Two profiles means two independent signed-in states, and a link opened in the work profile's window is a work request from the first byte. The cost is that the profile is now a thing you have to choose correctly before clicking, and macOS will happily open a link in whichever browser window was frontmost.

That last detail is where most setups quietly fail. The isolation is correct and the routing is not. If a link from a work channel lands in the personal profile, no amount of isolation helps, because the wrong window received it. Tools that bind a specific site to a specific workspace solve the routing rather than the isolation, which is the part macOS does not do on its own.

What tends to break after a few weeks

Window position is the first thing to go. A browser restores tabs; an installed app window restores less reliably, and a macOS update or a forced quit resets the geometry. Anyone who has arranged a spreadsheet on a second display and found it back on the laptop screen after an update knows the pattern.

Notifications are the second. Permission is granted per origin, and the origin here is Google's, shared with every other Google property. Granting notifications to a calendar and denying them to a spreadsheet is not a distinction the web platform offers at that level.

The third is printing and export. Exporting to PDF or XLSX runs through the browser's download path, and an installed app window with no visible downloads tray makes a finished export feel like it vanished. It did not. It went to the Downloads folder, which is why Option-Command-L in the Finder is worth keeping in reach.

The fourth is shortcut collisions. In a tab, Command-W closes the tab and the sheet survives in another. In an app window, Command-W closes the only window holding it. Nothing is lost, since the document lives on the server, but the muscle memory built in a tabbed browser produces a jarring result in a single-window app.

None of these four are reasons to avoid the app-window approach. They are the reasons a setup that felt right in week one feels wrong in week six, and each has a small fix. Pin the window to a display and leave it there. Decide once whether Google notifications are wanted at all, since the choice is made for the whole domain. Keep a Finder window or a Downloads stack visible so exports are never in doubt. And accept that a single-window app rewards a slightly different set of keys than a tab strip does.

What to change first

Decide which of the three complaints is actually yours. If it is offline, install the Chrome extension and turn on offline access in Drive settings, and stop there. If it is one window that stays put with a single account, install the page as an app in the Chromium browser already on the Mac. If it is two or more Google Accounts colliding daily, the fix is isolation plus routing, which is what SpaceDeck is built around.