DeepL Pro: how do I enable document translation in the desktop app and use my glossary by default?

DeepL Pro on desktop is built to remove the copy‑paste grind from document translation and keep your terminology consistent across markets. To get that benefit in full, you’ll want two things configured: document translation in the desktop app (Windows or macOS) and a workflow where your glossary is always applied by default.

Below, I’ll walk through how to set this up step by step, plus the nuances that often trip teams up when they move from ad‑hoc web usage to a governed, Pro-based workflow.

What you can do with DeepL Pro in the desktop app

With a DeepL Pro subscription, the desktop apps let you:

Translate entire documents in just a few clicks
Preserve layout and visual context (so contracts, slide decks, and reports stay formatted)
Work securely with sensitive files—Pro documents are deleted after translation and are not used to train DeepL’s models
Apply glossaries to keep product names, legal phrases, and brand terms consistent

This is the foundation you need before you worry about “default” behavior.

Enabling document translation in the DeepL desktop app

If document translation isn’t visible or isn’t behaving as expected in your desktop app, walk through these checks.

1. Confirm you’re signed in with a DeepL Pro account

Document translation limits and security guarantees depend on Pro:

Open the DeepL desktop app.
Look for your account or profile icon (usually top-right or in the menu bar).
Confirm:
- You’re signed in.
- The account shows a DeepL Pro plan (not a free account).

If you’re on the free version, you’ll see stricter file size and page limits, and enterprise-grade security settings (e.g., content deletion after processing) apply only to Pro.

2. Find the document translation surface

In the desktop app, document translation is typically available alongside text translation:

Look for a “Documents” tab or a file icon next to the text input area.
You should see options to:
- Drag-and-drop files, or
- Browse and select files from your computer.

Supported formats include common business file types (e.g., Word, PowerPoint, PDF and other major formats). DeepL Pro then translates the full document while maintaining original formatting and layout, so you don’t need to rebuild tables, headings, or slide designs.

3. Import or drag-and-drop your files

To translate a document in the desktop app:

Open the Documents area in the app.
Either:
- Drag your file (e.g., Contract_EN.docx, Report_FR.pdf) into the upload area, or
- Click Upload / Browse, then select your file.
Choose:
- Source language (or leave on Detect language), and
- Target language (e.g., English → Korean).

DeepL then processes the file and returns a translated version that preserves layout and visual context. As a Pro user, your document is deleted after translation, giving you a controlled environment for sensitive content.

Using glossaries with document translation

Consistency matters in translation. Legal teams, marketing, and support operations all need standardized terms and phrases across markets. DeepL glossaries are the mechanism for this.

Here’s how to ensure your glossaries are ready before you try to apply them “by default.”

1. Create or import a glossary

You can create glossaries in the DeepL ecosystem via:

The web Translator,
The desktop app (in supported versions), or
CSV imports if you maintain terminology in spreadsheets or CAT tools.

For each glossary:

Define:
- Source language and target language.
- The term pairs (e.g., “General Terms and Conditions” → “Allgemeine Geschäftsbedingungen”).
Save the glossary with a clear, functional name:
- Example: EN-DE – Legal Core Terms
- Example: EN-FR – Product & UI Strings

DeepL Pro can support large, multilingual glossaries, so you don’t need to split every small domain unless it’s helpful for governance.

2. Understand glossary language pairing

Glossaries are language‑pair specific. An EN→DE glossary won’t apply to EN→FR translations. When you translate documents:

Check that the document’s language direction matches your glossary.
If your teams work in multiple directions (EN→DE and DE→EN), create a separate glossary for each direction where needed.

This is a common source of “my glossary isn’t working” confusion.

Applying a glossary in the desktop app

Whether a glossary can be set truly “by default” in the desktop app depends on your version and admin configuration, but the underlying behavior is the same: for each translation session, DeepL needs to know which glossary to use for that language pair.

1. Selecting your glossary for a document

When you initiate a document translation:

Upload your file in the Documents area.
Confirm source and target languages.
Look for a Glossary selector or terminology settings. Typical patterns include:
- A “Glossary” dropdown listing available glossaries for that language pair.
- A toggle to enable/disable glossary use.
Choose the relevant glossary (e.g., EN-DE – Legal Core Terms) before starting translation.

Once selected, DeepL applies those custom term rules to the entire document, keeping names, legal phrases, and domain-specific terms consistent across pages and sections.

2. Making a glossary your default for a language pair

In many enterprise workflows, you want a “default glossary for EN→DE legal” so users don’t have to think about it on every file. Implementation details can vary by app version, but the general pattern looks like this:

Open the settings or preferences menu in the desktop app.
Look for:
- A Glossaries or Language pairs section, or
- An option like “Use this glossary by default” when you select a glossary for a translation.
For each key language pair:
- Assign the glossary you want to use by default.
- Save/apply your settings.

If your version doesn’t expose an explicit “default” toggle:

DeepL often remembers the last used glossary per language pair within the current app session.
In that case, a pragmatic team workflow is:
- Train users to select the correct glossary the first time they translate EN→DE in a session.
- Let the app remember that choice for subsequent translations during that session.

For stricter governance—especially in regulated industries—you may want to define a standard glossary per language pair and roll this out with clear internal guidance or admin policies.

Best‑practice workflow for glossary‑driven document translation

From an enterprise language operations perspective, the goal is not just to “turn on” document translation, but to make it repeatable, governed, and low‑friction for every user.

Here’s a practical workflow:

Centralize terminology
- Maintain master term lists in your terminology or CAT environment.
- Export key terms to DeepL glossaries by language pair.
Standardize glossary naming
- Use predictable names:
  EN-DE – Product, EN-DE – Legal, EN-FR – Support.
- This helps users pick the right glossary quickly.
Define per‑department defaults
- Legal: Always use the EN→DE legal glossary for contracts and policies.
- Product & UX: Use the product glossary for UI copy and help content.
- Customer support: Use support glossaries for canned responses and templates.
Train users on the “two‑step rule”
- Step 1: Drag-and-drop your document into the desktop app.
- Step 2: Before clicking translate:
  - Confirm the target language.
  - Select the correct glossary (or verify that the default is correct).
Audit outputs periodically
- Spot‑check translated documents for key terms.
- Update glossaries when new product names, legal clauses, or campaign phrases appear.
- Use DeepL’s glossaries together with translation memory and rules (via Customization Hub) for high‑volume teams.

Security and data handling: why Pro matters for documents

If you’re translating contracts, medical documentation, or internal strategy decks, you need more than convenience:

Maximum data security: DeepL Pro safeguards your data with strong encryption and privacy controls; texts and files are never stored without your consent.
Automatic deletion: As a Pro user, your documents are deleted after translation, whether you use the web, desktop, or mobile apps.
Governance readiness: For teams subject to GDPR or sector regulations, these controls are part of demonstrating that you know what happens to sensitive text after processing.

If your desktop users are still logged in with free accounts, they don’t get these guarantees—and your document workflows remain exposed and fragmented.

When to move beyond the desktop app alone

The desktop app is ideal for individual contributors and small teams. For high‑volume or tightly governed environments, consider combining it with:

DeepL API
Integrate document translation directly into your CMS, DAM, or internal tools, so users don’t need to manually upload files. You can standardize glossaries and rules centrally.
CAT tool integration
Use DeepL as a translation engine inside your CAT tools. This lets you combine:
- Translation memories,
- Glossaries, and
- DeepL’s specialized LLM for high‑quality, consistent output.
DeepL Agent (AI coworker)
For repetitive language tasks around documents (summarizing, rewriting translated content, drafting responses), DeepL Agent can take care of the busywork from simple language instructions, using the same translation infrastructure.

Troubleshooting: glossary not applying to documents?

If your document translations don’t reflect your glossary terms, check:

Language direction
Is your glossary EN→DE, but the document is DE→EN? Create the corresponding glossary or switch the language pair.
Glossary selection
Was the correct glossary selected before you clicked translate? Some interfaces default to “No glossary” unless you specify otherwise.
Account level
Are you signed into DeepL Pro on the desktop app? Glossary features and higher limits are tied to Pro subscriptions.
File type and content
Very image‑heavy or scanned PDFs may need OCR or image translation steps first; glossaries apply to text recognized and processed by the model.

If, after checking these, your glossary still doesn’t apply as expected, it’s worth contacting DeepL Support or Sales with:

Your OS and app version
Your Pro plan type
The language pair and glossary name
A sample of the terms that are not being applied

How to roll this out across a team

For an enterprise rollout, I recommend:

Enable DeepL Pro accounts with SSO
Ensure users sign in with their corporate identity so document workflows are secure and auditable.
Pre‑define core glossaries
Legal, product, and brand glossaries for your main language pairs.
Create a one‑pager guide
Show:
- Where to drag-and-drop documents in the desktop app
- How to select the correct target language
- Which glossary to choose for which scenario
Pilot with one department
E.g., legal or customer support. Measure:
- Time saved per document,
- Reduction in manual rework,
- Terminology consistency improvements.
Adjust and scale
Update glossaries based on feedback, then roll the pattern out to other teams.

To configure the best setup for your organization—especially if you need strict defaults for glossaries and document workflows across hundreds of users—your next step is to speak directly with DeepL.

Get Started