Putting Google Photos in the Dock, out of the browser

The results for a Google Photos desktop app tell the story before any of them are opened. A Microsoft community thread asking how to install it. A Reddit thread asking whether there is a way to reach the library from a desktop. A third-party listing offering a wrapped version. And Google's own page for Photos, which has an App Store button, a Play Store button, and a link to photos.google.com.

That last one is the fact that settles it. Google distributes Photos as an iPhone app, an Android app and a website. On macOS there is nothing to install. The library is reachable, fully featured, and permanently a browser tab, which is exactly the part that grates when the library is opened several times a day.

What Google actually ships for a Mac

Nothing labelled Google Photos. The macOS software Google publishes for files is Drive for desktop, which puts Drive into Finder and syncs files. It is not a photo library, it does not show albums, and it does not give the search, the face grouping or the editing that make Photos worth using.

Apple Photos is also on the Mac already, but it is a different library, not a viewer for the Google one. Pointing it at a Google account is not something either company supports. Treating it as a substitute means maintaining two libraries, which is usually worse than the problem being solved.

The honest inventory for macOS is therefore short. There is photos.google.com in a browser, there is Google Takeout for pulling copies of the originals down as an archive, and there is whatever can be done to make the browser feel less like a browser. The third item is where the remaining gain is.

The browser choice is not cosmetic here

One line in Google's own documentation decides more than any preference about browsers. In the instructions for backing up photos and videos from a computer, Google states plainly: to automatically back up folders, a Chromium-based browser such as Chrome or Edge must be used.

That single sentence splits the options in two.

Someone who only views, searches, shares and occasionally edits can use any browser, and Safari is a perfectly good choice. Someone who wants a folder on the Mac to keep itself backed up to Photos has to be in Chrome or Edge, and a Safari window will never do it no matter how it is packaged.

Manual uploading works anywhere. From photos.google.com the flow is Create, then Add photos, then Import photos, and dragging files from Finder onto an album uploads them into that album. Google's backup and upload page documents both paths, along with the limits worth knowing before a big import: photos up to 200 MB or 200 MP, videos up to 10 GB, and items must be larger than 256 by 256 pixels.

What a tab costs when the tab is a photo library

Photo libraries stress a browser tab in ways a document does not.

Uploads are long and fragile. A few hundred photos dragged into a tab is a transfer that runs for minutes. That tab now cannot be closed, and the browser cannot be quit, and if the browser is restarted for an unrelated reason the transfer goes with it. A window that exists on its own is far less likely to be closed by accident during a tab cleanup.

Viewing wants the whole screen. Photos is a grid that rewards space, and a browser adds a tab strip, a bookmarks bar and an address bar above it. Full screen in a browser hides those, but it also hides every other tab, which is rarely what is wanted mid-task.

The library is also personal while the browser is usually work. Screen sharing a browser window with a personal photo library one tab away is a small risk that repeats every meeting. Moving it to its own window and its own icon removes the class of accident entirely.

Memory is a factor too, though not in the direction people assume. A web app runs on the same engine as the tab it replaces, so it does not use less memory by itself. What it does is keep a heavy, image-filled page out of the window that holds twenty other tabs, which makes it easier to quit one without disturbing the other.

And a library gets opened impulsively. Looking up a photo from last summer is a ten-second task that currently starts with finding the browser, then the tab. That is the friction that a Dock icon removes.

Giving photos.google.com its own window

Both browsers can do this without any extra software, and both can be undone in seconds.

Safari, Add to Dock

From macOS Sonoma 14 onward, Safari can save any page as a web app. Open photos.google.com, choose File, then Add to Dock, name it, and click Add. The app is stored in the Applications folder inside the home folder and shows up in the Dock and in Spotlight. Apple's Use Safari web apps on Mac page covers the rest, including changing the name and icon from the app's own Settings.

The behaviour to expect: a Safari web app shares no browsing history, cookies, website data or settings with Safari, so the Google sign-in happens again inside it, once. After that the window holds its own session, which is the property that makes a second account possible.

Chrome, Install page as app

In Chrome, open photos.google.com, then More at the top right, then Cast, save, and share, then Install page as app. Google's Use web apps page covers installing and removing them.

This route inherits the session of the Chrome profile it was created from, so no second sign-in is needed. More importantly for Photos, it stays Chromium, which is the requirement for automatic folder backup. For anyone who backs up a folder from the Mac, this is the route to take.

The routes side by side

Route	Own Dock icon	Automatic folder backup	Signed in separately	Notes
Browser tab	No	Only in Chrome or Edge	Shares the browser session	The default, and the thing being fixed
Safari, Add to Dock	Yes	No	Yes, its own session	Needs macOS Sonoma 14 or later
Chrome, Install page as app	Yes	Yes, it stays Chromium	No, shares the Chrome profile	Best fit if a folder is backed up
Drive for desktop	Finder integration	Not a photo library	Up to four accounts for files	Syncs Drive files, not the Photos library
Site to app tool	Yes	Depends on the engine used	Yes, one session per app	Sensible once several sites need this

The choice is mostly settled by one question. If a folder on the Mac has to back itself up, stay in Chrome. If the Mac is only used to view and share what the phone already uploaded, Safari gives the cleaner separation.

Getting the originals onto the Mac

A window makes the library pleasant to use. It does not put a single file on the disk, and for some people that is the actual requirement: a copy of the originals that exists without a Google account, for editing in another application or for an offline backup.

That job belongs to Google Takeout rather than to any app. From the Takeout page, products in use are selected by default, so the first step is unchecking everything except Google Photos. Individual albums can be chosen instead of the whole library where that option is offered. Delivery can be a download link sent by email, or the archive can be dropped straight into Drive or Dropbox, which is easier for a large library than babysitting a browser download. Google's download your data page lists the steps and the delivery options.

Two details save trouble. The archive reflects the library at the moment it is built, and Google notes that changes made between requesting the download and the archive being created may not be included, so a Takeout is a snapshot rather than a sync. And an archive delivered to Drive counts against the same account storage as the library it came from, which can push a nearly full account over the line.

Takeout is also the honest answer to the question sitting underneath a lot of searches for a desktop app. People often want the app because they want the files. The files are available, they just arrive as an export rather than as a folder that stays in step. Anyone who wants the folder to stay in step is describing a sync client, and for Google Photos on macOS that does not exist.

Once the originals are down, the ordinary Mac tools apply. They can be imported into Apple Photos, left in a folder, opened in an editor, or copied to an external drive. None of that requires the browser window to change, which is why this is a separate decision from the one about the Dock icon.

Two accounts, and the one that backs up

A lot of people have a personal library and a work or school account, and Photos handles this less gracefully than Drive does.

Google is explicit that photos and videos can be backed up to only one Google Account at a time. That is an account-level rule, not a browser one, and no window arrangement changes it. What a separate window changes is viewing: two Safari web apps built from photos.google.com each keep their own cookies, so one can stay signed in to each account without the account switcher in between.

Naming matters more than usual here. Two identical Photos icons in the Dock, one personal and one work, is a mistake waiting to be made when dragging a folder of photos in. Renaming each app and giving them different icons takes a minute from the app's Settings and prevents an upload landing in the wrong library.

For someone already doing this with Gmail, Calendar and Drive, the pattern repeats often enough that a dedicated site to app tool is less work than maintaining a set of hand-built web apps. Every app gets its own session and its own icon by design, which is the whole difficulty here. The supported services list is the quick way to check what is already covered, and the guide walks through the naming and icon step that keeps two accounts apart.

What to change first

Answer one question before touching anything: does a folder on this Mac need to upload itself to Photos automatically? If yes, install Photos as an app from Chrome and turn folder backup on there, because that feature does not exist outside Chromium.

If the Mac is only for viewing, searching and sharing, use Safari's Add to Dock instead and get a cleaner, separately signed-in window in under a minute. Either way, rename the app and change the icon straight away so that a second Google account can be added later without confusion. Once the same treatment is wanted for three or four more sites, Kagemusha does it per site without stacking browser profiles.