Is there a Mac app for Google Translate? Somewhere you can always call it up

Google gives the answer on its own Translate page, in the last block before the footer. Next to a QR code, the instruction is to start using Google Translate in a browser, or to scan the code and download the app for a mobile device. The two download buttons underneath are Android and iOS. Google's help pages follow the same split: the ones headed Computer describe opening Translate in a browser such as Chrome or Firefox, while the ones about camera translation, conversation mode and downloading languages for offline use are filed under Android and iPhone.

So there is no macOS installer, and that is the end of the download question. The interesting question is different. Translation is a utility, not a destination. Nobody plans to visit Translate; it is needed for eleven seconds in the middle of doing something else, several times a day. A utility that lives in a browser tab is a utility that has to be found first, and finding it is most of the cost.

What the browser version actually does

The browser version is not a cut down edition. Google's help pages for computer use describe choosing the source and target languages or letting the language be detected, entering text, listening to the translation with an adjustable speed, copying the translation, rating or suggesting an edit, and looking up details such as definitions, examples and alternative translations for selected languages.

Two capabilities are worth remembering because they save real work. The first is the limit on pasted text: Google states that up to 5,000 characters can be translated at a time when copying and pasting. That is roughly a long email or a page and a half of a contract, and it is the number that decides whether a document has to be split.

The second is that the browser version does not stop at loose text. Google documents translating whole documents by uploading a file, and translating a whole website by entering its address. Those two are frequently the right tool when the reflex is to paste paragraph after paragraph into the text box.

Two smaller features are underused and both are in Google's help pages. Look up details shows definitions, examples and other possible translations, which is the panel that turns a guess into a decision when a word has two plausible meanings. It is available for selected languages only, so it is worth checking once for the pair you work in rather than assuming it will be there. Listen plays the translation, with the speed adjustable between normal, slow and slower in the settings at the top right, which is the quickest way to check whether a sentence sounds like something a person would say. Google also documents saving translations so they can be reached again from any device, which is the closest thing the service has to a glossary.

None of those require anything to be installed. They do require the window to be available at the moment the question comes up, which is the whole argument of this article.

What only the phone app does

The features that pull people towards an app are mostly the ones that need a sensor. Google's Translate page lists pointing a camera at something and translating what is on screen, having a spoken conversation with someone in another language, running simultaneous speech translation with Transcribe, translating text copied from any other app, and handwriting characters that a keyboard cannot produce. Its offline instructions are filed under the mobile platforms as well: languages are downloaded inside the Translate app so they can be translated without a connection.

None of that arrives on a Mac by installing something, because there is nothing to install. It is worth knowing anyway, because it separates two different frustrations. If what is missing is a camera pointed at a menu, the phone is the answer and no amount of window management changes that. If what is missing is a text box that appears instantly and disappears again, that is a Mac problem with a Mac solution.

What always available means on a Mac

macOS and Chrome both offer a way to give a site its own window, and each one covers part of the problem.

In Safari, open the site, click the share control in the toolbar and choose Add to Dock. Apple documents the result: an icon in the Dock and in Spotlight Applications, an existing sign-in carried over in most cases, a simplified toolbar, and notifications available like any other app. The web app can then be adjusted from its own menu bar under Settings and General, which offers the application name, the application URL, the Dock icon, whether the Back, Forward and Share buttons appear, and whether the title bar takes the site's colour. For a translation window, turning the navigation controls off is the right choice, because there is nowhere to navigate.

In Chrome, the equivalent is in the three dot menu under Cast, save and share, as Install page as app. Google notes that installed web apps are listed at chrome://apps, that some gain extra capabilities such as notifications and icon badges, and that uninstalling offers to remove the app's data from Chrome at the same time.

What a utility needs	Browser tab	Dock web app	Configured app
Appears without hunting	No	One click or Command and Tab	One keystroke, from anywhere
Stays small and out of the way	Shares the browser window	Own window, default size	Own window, chosen size
Survives a browser restart	Lost with the session	Independent	Independent
Does not collect other tabs	Collects them	Clean	Clean

The first row is the one that matters for translation and the one the built-in routes only half solve. A Dock icon is a click, and Command and Tab is a cycle through everything else that is open. Neither is the same as a single key combination that summons a small window over whatever is on screen and dismisses it again. That is what a configured app adds, and for a tool used many times an hour it is the difference between a utility and a destination. The Features page covers which of those window behaviours can be set, and the Supported services list shows which sites are already prepared as presets.

Translating a page you are reading is a different job

Before building anything, it is worth separating two tasks that both get called translation, because one of them needs no window at all.

Reading a foreign page is handled by the browser. Apple documents that when a page can be translated into one of your preferred languages, Safari shows a Translate button in the Smart Search field. Chrome offers its own equivalent. For an article, a product page or a support document, that is faster than any separate window, because the text never leaves the page it lives on.

Holding text that needs translating is the other job: a paragraph pasted from a chat, a sentence being drafted in another language, a phrase whose nuance needs a second opinion from the Look up details panel. That is the job a dedicated window is for, and it is the job that benefits from being one keystroke away.

Keeping those two separate stops a common mistake, which is building a translation app and then using it to do work the browser was already doing for free.

A test that settles it in two days

Instead of reasoning about it, count. For two working days, note every time translation was needed and what shape the task had. Three columns are enough: pasted text, a whole page being read, or something in front of a camera.

If the camera column dominates, the phone is the tool and nothing needs changing on the Mac. If the whole page column dominates, turn on the browser's own translation and stop there. If the pasted text column dominates, and the count is more than a handful, the case for a standalone window is made, and the next decision is only about how it opens.

The count also tells you how much configuration is justified. Three times a day is a Dock icon. Twenty times a day is a global shortcut, a window sized to sit beside the work rather than cover it, and an icon distinct enough to recognise in the Dock without reading the label.

How to set the window up so it stays useful

A translation window that is set up like a document window will be resented within a week. Three details decide whether it stays out of the way.

Size and position come first. The window only has to hold a source box, a target box and a language pair, so roughly a third of the screen is enough. Set it to open at that size on the side of the screen you do not write on, and it can sit beside the work rather than covering it. A window that has to be resized every time it opens gets closed instead.

The name and icon come second, and they matter more than they sound. A Dock full of near-identical browser derived icons is a Dock nobody can aim at. Apple's web app settings allow both to be changed, so give it a one word name and an icon distinct at Dock size. The same applies to the entry that appears when cycling with Command and Tab.

Notifications come third, and the answer here is almost always off. Translate has nothing urgent to say, and Apple states that a web app can post notifications like any other app, so the default is worth changing rather than tolerating.

The privacy question, stated plainly

One point deserves a sentence, without alarm. Translation happens on Google's servers, which is why the browser version needs a connection and why the offline feature exists only inside the phone app with a downloaded language. Anything pasted into Translate is sent for translation. Google's own help pages describe the same for Tap to Translate on Android, where copied text is sent only after the Translate action is tapped.

For a marketing email that is unremarkable. For a clause from a client contract or a customer record, the relevant policy is the employer's, not the tool's, and a standalone window does not change what leaves the machine. What a standalone window changes is how easily the right window is found, which is worth being clear about so the decision is made on the correct grounds.

What to change first

Turn on the browser's built-in page translation and stop using Translate for pages you are reading. Then add Translate to the Dock from Safari and use it for a week for pasted text only. If it is being opened often enough that a click starts to feel slow, that is the point at which a global shortcut and a fixed window size are worth setting up with a tool such as Kagemusha, rather than living with a Dock icon that has to be aimed at.