DeepL for Mac: translating without switching tabs
Most searches of this shape end in disappointment. Someone looks for the desktop version of a web tool, finds that it does not exist, and settles for a bookmark. DeepL for Mac is the opposite case. The app is real, it is published by DeepL, and it is free to download. So the interesting question is not whether to install it. It is what the app actually removes from the working day, and which browser tabs are still standing afterwards.
The app exists, and this is the rare search that ends there
DeepL's own page for the Mac application states the requirement plainly: macOS 14 or higher. The download is free, and the app combines two products in one window, the translator and DeepL Write.
Enjoy distraction-free work without browser tab clutter. Source: deepl.com
That sentence is DeepL's own framing of the problem, which is worth noting because it is unusually direct for a product page. The company is not selling the app on translation quality, which is identical to the website's. It is selling the app on not having to go and find a tab.
The translator side does what the web translator does. The DeepL Write side improves grammar and spelling and adapts text to a chosen tone or style, in the same window. For anyone whose day includes both writing in a second language and reading in one, having those two in one place rather than two tabs is the larger part of the benefit.
What the two shortcuts actually change
The feature that justifies the install is not the window. It is the pair of keyboard shortcuts, and they are documented on the same page.
The first is Cmd+C+C. Select text anywhere, press it, and the translation appears in the app. The second is Cmd+Shift+C+C, which does the same thing but asks for a target language first, which matters for anyone working across more than two languages.
Read carefully, those shortcuts do something more interesting than saving clicks. They make the translation tab unnecessary. The tab was never the destination. It was the place text had to be carried to. With a system wide shortcut, the text stays where it is: in a PDF, in a mail client, in a code comment, in a chat window. Nothing is pasted anywhere, so nothing has to be pasted back.
That is why the honest recommendation for this particular tool starts with the app rather than with a window. Anyone who currently keeps a translator tab permanently open should install the app, learn one keystroke, and close the tab for good. The window advice that follows applies to what is left over, not to the everyday case.
One detail is plan dependent and worth knowing before building a habit on it. Saving translations for later is described as a feature for DeepL Pro users, so anyone on the free version should not assume the app is keeping a history.
How many DeepL surfaces one person ends up with
DeepL publishes an unusually large number of entry points, and the download list on its own site is the fastest way to see the scale of it: Android, iPhone, iPad, Windows, Mac, a Chrome extension, a Firefox extension, an Edge extension, and add ins for Microsoft Outlook, Word and PowerPoint, plus Google Workspace, plus the API.
The consequence is not obvious until it happens. A person who translates regularly does not choose one of those. They accumulate four or five, each one appropriate to a different context, and each one signed into the same account. That is fine, and it is arguably the point of shipping so many. But it changes what the browser is for.
Once the Mac app handles selected text and the browser extension handles pages, the web interface stops being the everyday tool and becomes the occasional one. It is where longer passages get worked on, where a document gets translated, and where the account itself is managed. An occasional destination that still has to be reached quickly is exactly the case a tab serves worst, because a tab that is not used daily is never where it was left.
The plan decides what the app can save
DeepL's published limits are per user and per month, and the numbers below are taken from the price list as shown for Germany in euros. Annual billing is stated to save 16 percent against monthly.
| Plan | Price | Characters per month | File translations | Glossaries |
|---|---|---|---|---|
| Free version | 0 | 50,000 | 1, up to 5 MB | 1, with 5 entries per language pair |
| Individual | €7.49 per month, billed annually | 300,000 | 3, up to 30 MB | 1 |
| Team | €24.99 per user per month, billed annually | 1,000,000 | 20, up to 30 MB, bulk translation | 5 shared |
| Business | €49.99 per user per month, billed annually | Unlimited, under a fair usage policy | 100, up to 100 MB | Unlimited, under a fair usage policy |
| Enterprise | Custom | Customisable | Custom | Unlimited, under a fair usage policy |
Saved translations follow the same ladder: one on the free version and on Individual, ten on Team, unlimited on Business and Enterprise. DeepL Write Pro is a separate add on at €6.99 per user per month billed annually, and can be added to Individual or Team. Business plans list it as included. Team adds administration, analytics and reporting, and single sign on. Business adds translation memory, user provisioning through SCIM, domain capture and a stated 99.0 percent availability figure, which Enterprise raises to 99.9 percent.
Two rows change the daily shape more than the price does. The character allowance is what decides whether long passages go through the app at all or get broken up. And glossaries are what decide whether the same product name comes out the same way twice, which for anyone translating documentation is the difference between usable output and output that needs editing.
The tabs the app does not replace
Three things stay in a browser after the app is installed, and it is worth being clear about which.
The first is full page translation, which is listed among what the Individual plan includes. Translating a whole page is a browser operation by definition, and it is what the Chrome, Firefox and Edge extensions exist for.
The second is long form work. Selecting text and pressing a shortcut suits a sentence or a paragraph. Working through several pages with glossary terms applied is a different activity, and it happens in a full interface.
The third is the account itself: the plan, the usage against the character allowance, the glossary entries, and for a team, the administration and reporting that the Team plan adds.
None of those are daily for most people, which is exactly why they end up as a stale tab or as a search through browsing history. A window with a name, an icon and a fixed position in the Dock solves that, and it solves it whether the account is personal or shared.
A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com
Safari's route is File then Add to Dock, or the Share button then Add to Dock, and the window's settings panel allows the Application Name, Application URL and Icon to be set, along with an Extensions tab that enables Safari extensions per window. Chrome's route is the three dot menu, then Cast, save, and share, then Install page as app.
A web app is an app built for the web that you can access on any device. Source: support.google.com
The Chrome caveat is that the window inherits the profile's session and the profile's extensions, so a second account means a second Chrome profile first. What a purpose built window covers is set out on the Features page, and the build steps are in the Guide.
The routes, side by side
| Route | Setup | Selected text anywhere | Whole pages | Account and glossaries | Session per window |
|---|---|---|---|---|---|
| Browser tab | None | No | No | Yes | No |
| DeepL for Mac | Free download, macOS 14 or higher | Yes, two shortcuts | No | No | One account at a time |
| Browser extension | Install once | Within the browser | Yes | No | Follows the browser |
| Safari, Add to Dock | Two clicks | No | No | Yes | Yes |
| Chrome, install page as app | Three clicks | No | No | Yes | Follows the Chrome profile |
| Site to app tool | Pick the URL once | No | No | Yes | Yes, per app |
The combination that covers everything is the app for selections, an extension for pages, and one window for the account. Other services that end up arranged the same way are listed on the Supported services page.
The case for a separate window gets stronger with a second account, which is more common here than it looks. A translator signed into a personal plan and into a client's Team plan has two logins, and a browser profile holds one session per site. Two windows that keep their own cookies let both stay signed in, which also keeps the character allowance being spent against the right plan.
Five things worth checking in the first week
Translation sits in the middle of other work, so a setup problem shows up as a broken sentence in something already sent. A few deliberate checks are cheaper than that.
First, the shortcut against everything else already bound. Cmd+C pressed twice is an unusual combination precisely so that it does not collide, but a Mac with a clipboard manager or a text expander installed may already be watching for repeated copies. Test it in a mail client, a PDF reader and a terminal, since those three behave differently.
Second, the target language after a restart. Confirm that the pair chosen yesterday is the pair still selected today, because a silently reset default is how text comes back in the wrong language without anything looking wrong.
Third, formatting on the way out. Copy a translation into a mail client and into a chat window and check that what lands is text rather than a styled block that inherits the app's font.
Fourth, the character allowance. Translate a normal day's worth of work and then look at the usage figure, because 50,000 characters sounds generous until a few long documents have gone through it.
Fifth, any second account. Open both windows, leave them a day, and confirm neither has signed the other out. A week is the right period, since sessions can expire on a longer cycle than a single day.
What to change first
Install the Mac app, learn Cmd+C+C, and close the permanently open translator tab, because that one keystroke is what removes the tab rather than relocating it. Then give the account and glossary side a window of its own with a fixed Dock position, and if a personal plan and a client's plan are both in play, one permanently signed in Kagemusha window each keeps the usage counted against the right account.
Frequently asked questions
Is there an official DeepL app for Mac?
Yes. DeepL publishes a Mac application, the download is free, and the stated requirement is macOS 14 or higher. It contains both the translator and DeepL Write in the same window, and it adds system wide keyboard shortcuts that the web version cannot offer.
What are the DeepL keyboard shortcuts on a Mac?
Two are documented on DeepL's own page for the app. Cmd+C+C translates selected text from any application inside the app. Cmd+Shift+C+C does the same but asks for a target language first, which is the one to learn for anyone working in more than two languages.
How much can the free version translate?
The published comparison lists 50,000 characters per month for the free version, one file translation of up to 5 MB, and one glossary limited to five entries per language pair. Individual raises that to 300,000 characters and three file translations, and higher plans raise it further.
Does the Mac app replace the browser extension?
No, they cover different things. The app works on text selected in any application. Translating a whole web page is what the Chrome, Firefox and Edge extensions are for, and full page translation appears in the feature list from the Individual plan upward.
Can two DeepL accounts be used on one Mac?
Not simultaneously in one browser profile, because one profile holds a single session per site. A personal plan and a client's Team plan are best kept in two windows that each store their own cookies, which also keeps each month's character usage counted against the correct account.