Putting Gemini in the Dock, out of the browser

The answer to whether a Gemini Mac app exists changed in April 2026, and a lot of the advice still circulating online was written before it did. Google now publishes a native Mac application, it is free, and it is downloaded from a Google address rather than the App Store. Anyone searching for it should start there and stop reading advice about browser tricks.

The complication is that the official app comes with one hard requirement and one design decision, and both of them send a sizeable group of people back to the website. The requirement is a macOS version floor. The design decision is that the app is an assistant summoned over other applications, not a window that holds the Gemini chat page. Neither is a flaw, but neither is what everybody searching for this was picturing.

What the official app is and what it needs

Google introduced the Mac application on 15 April 2026 as a native desktop experience, summoned with a keyboard shortcut so that it appears alongside whatever is already open. The release note states the requirement plainly:

The new desktop app is available to users on macOS versions 15 and up, globally, for free. Source: gemini.google

The download lives at gemini.google/mac, which redirects to the desktop page carrying separate buttons for macOS and Windows. Windows arrived later, on 10 September 2026, which is why the Mac version has picked up features first.

Three capabilities have shipped since launch and they describe the shape of the product better than any feature list. The summon shortcut is Option and Space, which brings Gemini up over the active application. Window sharing lets the app see what is on screen so that a question can refer to the thing being looked at rather than being described from scratch. And since 29 July 2026, holding the Fn key dictates into the active window, with the transcribed text landing at the cursor in whatever application has focus.

Gemini Spark, described by Google as a personal AI agent that works on tasks autonomously and under direction, reached the Mac app on 30 June 2026. It handles multi-step work across Google Workspace and local files.

What sits inside the desktop workspace

Beyond the summon shortcut, the app carries a dedicated workspace of its own, and Google's desktop page describes what is reachable from it. Connections to everyday Google applications are the headline: Gmail, Google Drive, Docs and Calendar can be pulled into a desktop session, so a request to find a detail buried in an email thread or to summarise a shared document is answered without opening those services separately.

Image and video generation are present in the same workspace, with Nano Banana named for custom images and Gemini Omni for video. Deep Research and Canvas, both available in the web version, carry across as well.

This is the part that tends to settle the argument for people whose Mac qualifies. A browser window pointed at gemini.google.com reaches the same model and most of the same tools, because the web version is the product that everything else is built around. What it does not reach is the surrounding system: the key combination that works from inside any application, the screen context, and the dictation that writes into a document in another program.

So the choice is not really about capability inside the conversation. It is about whether the assistant needs to reach outside its own window, and that question has a different answer for someone drafting all day in one long thread than it does for someone asking quick questions between other tasks.

The floor that sends people back to the browser

macOS 15 is a real barrier. A Mac that cannot be upgraded past macOS 14 or earlier, whether because of hardware age or because an administrator controls updates, cannot run the official app at all. That is the single most common reason a person lands on a page like this one after already finding Google's download button.

There is a second group, smaller but consistent. Some people do not want a system-wide overlay with a global keyboard shortcut and screen access. They want gemini.google.com in an ordinary window with a Dock icon, sitting in Cmd+Tab next to everything else, with nothing listening for a key combination and nothing reading the screen. The official app is not built for that, and installing it to get it would be the wrong tool.

The third group has a Mac that qualifies and wants the official app, but also needs a second Google account open at the same time. A desktop application signs in to one account and switching means signing out and back in.

The routes, side by side

Route	What it gives	Requirement	Second account
Official Gemini app	Overlay summoned with Option and Space, screen sharing, dictation	macOS 15 or later	Sign out and back in
Browser tab	Nothing beyond the page	None	Second browser profile
Chrome, install page as app	A window tied to the Chrome profile	Chrome	Second Chrome profile
Safari, Add to Dock	An independent window with its own store	macOS Sonoma 14 or later	Not supported
Site to app tool	A built application with its own data store	A one-time setup	Separate app per account

Read the requirement column first. It produces a clean decision on most machines without any need to weigh features. On macOS 15 or later, the official app is the answer unless one of the two objections above applies. On macOS 14, Safari's Add to Dock is available even though the official app is not. Below macOS 14, neither built-in route exists.

Safari's Add to Dock, in practice

Apple added web apps in macOS Sonoma 14. The command is File then Add to Dock in the menu bar, or the Share button in the Safari toolbar then Add to Dock. A name is typed, the app is created, and it lands in the Applications folder inside the home folder, reachable from the Dock and from Spotlight.

The separation is the part that surprises people on first launch:

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

So the new app asks for a Google sign-in even on a Mac where Safari is signed in already. That happens once. Afterwards the session belongs to the app, and clearing Safari's browsing data has no effect on it, which is the behaviour most people actually want from something they keep open all day.

The settings panel, reached by clicking the app's name in the menu bar, is where the window gets tuned. The application name can be changed, the URL it opens can be edited or set to the current page, the icon can be replaced with any image, and the navigation controls can be switched off so that the back, forward and Share buttons disappear. For a chat page that never needs a back button, switching them off produces a window that reads as a plain application.

One rule catches everyone. Apple is explicit that a notification permission has to be answered inside the web app rather than in Safari, and only then does the app appear in Notifications settings under its own name. A permission granted earlier in a browser tab does not transfer.

Where a built window keeps its data

Anything installed raises the question of how to undo it, and for Safari web apps Apple answers it directly. The app is saved to the Applications folder inside the home folder, and removing it means opening that folder and dragging the app to the Trash. Nothing is scattered into system directories and no uninstaller is involved.

The same settings panel that renames the app also carries a Privacy tab, and that tab is the repair kit. It clears the website's data for that app alone, cookies and caches included, which resets a sign-in that has got itself stuck without disturbing Safari or any other web app on the machine. An Extensions tab sits next to it, where Safari extensions can be enabled or disabled for that app individually, so an extension that is useful while browsing can be kept out of a window meant only for one site.

Knowing that both exist changes how much weight to put on the route. A session that breaks stops being a reason to abandon the arrangement and becomes a short repair in a panel that is two clicks away. It also means a web app can be pointed somewhere else later, since the application URL field accepts a new address or can be set to whatever page is currently open, turning an app built for one part of a site into an app for another without rebuilding it.

Chrome's install command

Chrome offers the same idea through a different mechanism. The command sits under the three dot menu: More, then Cast, save, and share, then Install page as app. An install icon sometimes appears at the right of the address bar instead.

What matters is what the installed app is attached to. It keeps using the Chrome profile it was created from, so it is signed in from the first launch with no second sign-in required. The trade is the mirror image of Safari's: clearing Chrome's browsing data signs the app out too, because one cookie store sits behind both, and a second account needs a whole second Chrome profile rather than just a second window.

There is one detail specific to this route that is easy to miss. The shape of the installed window is decided by the site rather than by Chrome, through a small file called a web app manifest that declares a display mode. Google's services do not agree with each other on that value. Google Chat asks for a plain standalone window, while Gmail and Google Calendar ask for a browser display. The practical consequence is that installing two Google services the same way in the same browser does not reliably produce two windows that look and behave alike.

Running the official app and a plain window together

These routes are not mutually exclusive, and on a Mac running macOS 15 or later the combination is often better than either alone. The official app covers the case of wanting an answer about whatever is on screen right now, which is exactly what a global shortcut and window sharing are for. A standalone window covers the case of a long working session in one conversation, where the value is a stable place in the Dock and a window that does not vanish when the browser is quit.

They also solve the account problem between them. The official app holds one account. A separate built application can hold another, with its own data store, so a personal account and a work account can both be open without either one being signed out. For anyone who keeps several sites arranged this way, the supported services list shows which sites already have a preset, and the guide covers how notifications and window behaviour work in a built app.

What to change first

Check the macOS version before anything else. On macOS 15 or later, download the official app from Google and use it for a week before deciding anything else is needed. On macOS 14 or older, or when a second account or a plain window without a global shortcut is the actual requirement, build gemini.google.com into a standalone application with Kagemusha and keep the browser out of it entirely.