There is no Gmail installer for macOS, so what goes in the Dock

Searching for Gmail desktop for Mac produces plenty of download buttons and not one of them belongs to Google. Some lead to third party mail clients, some to instructions for adding a Google account to Apple Mail, and some to App Store listings that turn out to be for iPhone. The pattern is consistent because the premise is wrong. Google has never published a Gmail application for macOS. Gmail exists as a mobile app and as a web application, and Google's own documentation treats the browser as the desktop client.

The closest thing Google offers is offline mode, which is a browser feature rather than an application. Google's help page is explicit about its limits: Gmail offline works only in a Chrome browser window that is not in Incognito mode, and a message sent while offline is saved in an Outbox folder and sent automatically once a connection returns. Useful on a train, but it installs nothing and puts no icon anywhere.

So the real question is not how to install Gmail. It is what should occupy that spot in the Dock, and there are four honest answers.

What the search results are actually offering

Each kind of result promises something different from what it delivers, which is why the search feels unproductive.

App Store listings are often iPhone and iPad applications. Apple Silicon Macs can run some of them, but only where the developer left them available on the Mac, and the listing rarely says so before the click.

Third party mail clients are real Mac applications. They are covered below, and they fall into two very different groups depending on how they connect to Gmail.

Browser extensions install into Chrome rather than onto the Mac. They add features to the Gmail page and disappear along with the browser profile that holds them.

Export tools produce a copy of the mail rather than access to the account. That is the right object for an archive and the wrong one for daily use.

None of the four is an installer for Gmail, because no such installer exists. What follows is a choice between substitutes, and the substitutes differ mainly in whether they keep Gmail's own interface.

Route one: add the account to Apple Mail

Every Mac ships with Mail, and Google supports this arrangement directly. Google's documentation states that Gmail can be added to other email clients such as Microsoft Outlook, Apple Mail, or Mozilla Thunderbird, and that messages and labels are synced with the client.

Setup happens in System Settings, under Internet Accounts. Sign in to Google, enable Mail, and messages start arriving. Nothing is installed, nothing is bought, and the application is native, which means it is lighter on memory than a browser window kept open all day.

Two limits are worth knowing before committing.

The first is the model. Gmail organises mail with labels, and one message can carry several. Standard mail clients organise mail with folders, and one message sits in one place. The sync works, but the shape of a heavily labelled mailbox does not survive the translation intact, and features built on Gmail's model tend to be missing or approximated. Categories and the tabbed inbox, snooze, and Gmail's search operators are the ones people notice first.

The second is scale. Google warns that adding Gmail to too many clients at once produces a too many simultaneous connections error, with a limit of 15 clients per account, and recommends not syncing folders containing more than 10,000 messages. A large archive is where this route gets slow.

For a mailbox that is mostly a stream of messages to read and answer, Apple Mail is free, fast, and already installed. For a mailbox that is a filing system built on labels and filters, it is a downgrade.

Route two: a native client built specifically for Gmail

There is a middle category that many people never find: Mac applications written specifically around Gmail rather than around generic mail standards.

Mimestream is the clearest example. It is a native macOS email client for Gmail that uses the Gmail API rather than IMAP, which is what lets it keep labels, categories, and Gmail search behaving the way they do on the web. It requires macOS 12 Monterey or newer, costs $4.99 per month or $49.99 per year, and offers a 14 day free trial that does not require a credit card. Subscription is the only purchase option.

The trade-off here is different from route one. Much less of Gmail's model is lost, because the application was designed around it. What is still lost is whatever Google adds to the web interface and does not expose through its API, and anything a Workspace administrator configures centrally that lives only in the browser.

Route	Cost	Interface	Gmail model kept	Runs without a browser
Apple Mail	Free, pre-installed	Apple's	Partly, labels become folders	Yes
Mimestream	$4.99 per month or $49.99 per year	Its own	Largely	Yes
Gmail in a browser tab	Free	Google's	Completely	No
Gmail as a standalone app	Free or one time	Google's	Completely	Yes

The table splits on one question. The first two change the interface. The last two keep it and change where it lives.

Signing in is where old instructions go wrong

One detail catches out anyone following a guide written more than a few years ago. Google states that Gmail no longer supports third party apps or devices that require sharing a Google username and password, and points to Sign in with Google instead.

In practice this means any instruction that involves typing the Google password directly into a mail application, or generating an app password to paste into one, is either obsolete or an unusual exception. Current clients open a Google sign in window, complete two factor there, and receive a token. Apple Mail does this through Internet Accounts, and applications built around the Gmail API do it as part of their own setup.

Two consequences follow. The first is that access can be revoked from the Google account's security settings without changing the password, which is the correct way to remove an old machine or an application that is no longer used. The second is that a client which stops receiving mail has often had its token expire rather than its password change, and the fix is to sign in again rather than to rebuild the account.

This also quietly settles an old argument about security between the routes. A mail client holding a revocable token and a browser holding a signed in session are closer to each other than they used to be. The meaningful difference is no longer how the credential is stored, it is how many places hold one, and how easy it is to see and revoke them from one screen.

Route three: keep Gmail's page, give it a window

If the complaint was never the interface, changing clients solves nothing. Someone who likes Gmail and simply loses it among thirty tabs does not want different mail software. They want the same mail, in a place they can find.

macOS includes a route for this. Starting with macOS Sonoma 14, Safari can save any webpage as a web app through Add to Dock. Apple's documentation describes the result precisely: the web app is saved to the Applications folder of your home folder, it shares no browsing history, cookies, website data, or settings with Safari, and the number of unread notifications appears as a red badge on the app's icon in the Dock. For a single Gmail account, that badge is very close to what the search was looking for.

Chrome offers a similar result through the More menu at Cast, save, and share, then Create shortcut.

Both share a weakness that appears with the second account. A Chrome shortcut belongs to the browser profile it was created from, so a work address and a personal address created from one profile are both signed into whichever account that profile holds. Signing out of one signs out of both. Anything tied to a browser profile also disappears when that profile is reset or removed, typically leaving a dead icon behind.

Route four: a standalone app built from the Gmail page

The fourth route uses a tool that turns a website into a standalone Mac app. What comes out is an ordinary application bundle in the Applications folder, with its own name, its own icon, and its own isolated session, showing Gmail exactly as the web shows it, because it is the web.

The difference from route three is ownership. The app belongs to itself rather than to a browser, so resetting Chrome or Safari does not disturb it. Each app carries its own cookies, which means a work inbox and a personal inbox can sit side by side in the Dock, both permanently signed in, with no account switching and no profile juggling. Notifications come from the app, so new mail can announce itself when no browser is open.

Nothing is reimplemented, so nothing from Gmail is missing. Labels, filters, categories, search operators, keyboard shortcuts, and anything an administrator configured all behave as they do on the web, because they are the web. The cost is that it is one more application to install and update, and that it is a browser engine underneath, so rendering and printing behave exactly as they do in a browser. The Features page covers what a separate profile and icon per app involves, and the Supported services list includes Gmail among the prepared configurations, so the address and icon do not have to be assembled by hand.

Choosing in one question

Ask what was wrong with Gmail in a browser tab.

If the answer is Gmail itself, that it is slow, cluttered, or unpleasant to work in all day, then the fix is a different client. Apple Mail is the free place to test that theory, and if the verdict is that the interface was fine but the label handling was wrong, a Gmail specific client such as Mimestream is the narrower fix.

If the answer is that Gmail was fine and the tab was the problem, that mail only announced itself when the browser happened to be open, or that two accounts were one too many for a single browser profile, then swapping clients makes things worse. The interface was never the complaint. The fix is to give that same interface its own window, its own icon, and its own session. The Guide walks through what that looks like in practice.

What to change first

Add the Google account to Apple Mail in System Settings today. It takes two minutes, costs nothing, and within a week it is obvious whether the interface or the location was the real problem. If it was the location, build Gmail into a standalone application with a site to app tool such as Kagemusha rather than replacing a mailbox that was working.