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

Many DeepL Pro teams want two things in the desktop app: fast, layout‑preserving document translation and glossaries that “just apply” without extra clicks. You can get very close to that workflow—especially if you understand how document translation and glossary usage are designed to work together.

Below I’ll walk through:

How to enable and use document translation in the DeepL desktop app
How glossaries interact with document translation
Practical ways to make your glossary feel “default” in day‑to‑day work—even where automatic application isn’t available yet

1. Enabling document translation in the DeepL desktop app

With DeepL Pro, document translation is available directly in the Windows and macOS desktop apps. You don’t need to “turn on” a special mode, but you do need to:

Sign in with a DeepL Pro account
Use the correct part of the interface (the document translation surface, not just copy/paste text)

The exact UI wording can evolve, but the workflow is broadly:

Open the DeepL desktop app
- Launch the DeepL app on Windows or macOS.
- Make sure you’re signed in with your DeepL Pro credentials.
Locate the document translation area
Typically, you’ll see:
- A text translation area (where you paste or type text)
- A document translation area with an upload icon or “Translate files” CTA
Look for language selectors (e.g. “Detect language” → “English”) and an upload area that accepts formats like .docx, .pptx, .pdf, etc.
Select your source and target languages
- In the document translation pane, choose:
  - Source language (or keep “Detect language” enabled)
  - Target language (for example, German → English, or Japanese → French)
Drag‑and‑drop or upload your file
- Drag your Word, PowerPoint, PDF, or other supported file into the upload area, or
- Click the upload icon and pick a file from your system.
Start translation
- Confirm the translation, if prompted.
- DeepL will translate the entire document while preserving layout and visual context, so:
  - Headings, bullet lists, and tables remain intact
  - Fonts and basic formatting are maintained
  - The result is usually ready to use “as is,” or with minimal post‑editing
Download and review the translated file
- Once processing is complete, download the translated file.
- As a DeepL Pro user, your files are deleted after translation, so you can handle sensitive documents with more confidence.

From an operations point of view, this is how many legal, finance, and customer‑support teams achieve the “no more copy/paste” goal: they drag PDFs or contracts into DeepL Translator on desktop, then review the output in Word or PowerPoint instead of rebuilding layouts manually.

2. How glossaries work in DeepL Translator

Glossaries are critical if you care about terminology governance—product names, regulatory phrases, and legal boilerplate must be consistent. DeepL’s glossary feature is built exactly for that.

2.1 Creating glossaries in DeepL

To create or manage a glossary (web or desktop):

Open DeepL Translator (desktop or web).
Look for “Glossary” in the interface:
- Either as a top‑level menu item
- Or as a panel/icon in the translation view
Create a new glossary:
- Choose the language pair (e.g., English ↔ German).
- Add term pairs:
  - Source term (e.g., “General Terms and Conditions”)
  - Target term (e.g., “Allgemeine Geschäftsbedingungen”)
- Save the glossary.

You can create multiple glossaries for different language pairs and departments (e.g., “Legal EN–DE,” “Product EN–FR,” “Support EN–ES”).

2.2 Applying glossaries to text translation

For standard text translation in the app (pasted/typed text), DeepL allows you to:

Select a specific glossary for the active language pair
Have that glossary applied automatically to the current translation
See glossary terms highlighted or incorporated in the translation output

This is ideal for:

FAQ content
Email templates
Knowledge‑base articles
Reusable product copy

Translation quality improves because the same terms are used every time, not just “best guess” equivalents.

3. Can I use my glossary by default for document translation?

This is the core of your question—and it touches a subtle but important distinction:

Text translation surface: Where you paste or type text and can actively select a glossary.
Document translation surface: Where you upload files like Word, PowerPoint, and PDF.

DeepL’s core positioning is:

“Consistency matters in translation. With DeepL, you can create and manage a personalized glossary of terms, ensuring your translations are always accurate and consistent.”

Glossaries are tightly integrated with text translation, and—as an enterprise practitioner—I strongly recommend using that surface whenever terminology is mission‑critical. For full documents, there are three realistic strategies:

3.1 Strategy A: Glossary‑first workflow with review (most controllable)

Use document translation for speed and layout, then run your critical, glossary‑sensitive passages through text translation where you explicitly apply the relevant glossary.

Workflow:

Translate the full document in the desktop app
- Drag‑and‑drop your file (contract, policy, presentation).
- Download the translated version with formatting preserved.
Identify glossary‑sensitive sections
Typical candidates:
- Definitions and key terms
- Legal provisions and disclaimers
- UX copy, product names, and feature lists
Copy those sections into text translation
- Open DeepL Translator (desktop or web).
- Select your glossary for the relevant language pair.
- Paste the critical section and retranslate.
Replace the corresponding parts in your document
- Paste the glossary‑corrected text back into your file.
- This ensures your most risk‑sensitive passages adhere to your terminology governance.

This gives you the operational speed benefits of document translation and the terminology precision of a glossary‑driven workflow without having to manually rewrite everything.

3.2 Strategy B: Pre‑standardize source text with DeepL Write

If you regularly translate from, say, internal English to multiple target languages, cleaning up the source text first reduces ambiguity and makes your glossary easier to enforce.

DeepL Write can:

Improve clarity and structure in the source text
Align tone and formality before translation
Reduce odd phrasings that might conflict with your glossary entries

Recommended flow:

Run the source document text through DeepL Write
- Focus on key sections: definitions, product names, legal language.
- Choose a consistent style (e.g. “formal,” “confident,” “diplomatic”).
Update the source document with the improved text
Translate the cleaned‑up document via the desktop app

Because your source phrasing is now more standardized, your glossary mappings can be more precise (same source string every time), and translation consistency improves—even when you’re relying on document translation for speed.

3.3 Strategy C: Use CAT tools + DeepL where glossary governance must be absolute

For teams with strict regulatory needs (finance, health, insurance), DeepL specifically supports CAT tool integration. Your Translation Management System (TMS) or CAT environment typically gives you:

Translation memories
Termbases / glossaries
QA rules for terminology consistency

DeepL Pro can be integrated with those tools so:

DeepL handles the initial MT suggestion
Your glossary and TM enforce terminology
In‑tool QA checks highlight any deviations

In other words, if you absolutely need full document + glossary + QA in one pipeline, your best option is:

Use DeepL Pro via CAT integration for high‑risk content
Use DeepL desktop document translation for lower‑risk, internal documents where speed matters more than perfect term enforcement

4. Practical ways to “default” your glossary usage

While UI behavior can change over time, several habits make it feel like your glossary is always on:

Standardize language pairs and glossaries
- For each major language pair (e.g., EN–DE, EN–FR), maintain a single, team‑approved glossary rather than many overlapping ones.
- This reduces the chance of translators picking the “wrong” glossary.
Create internal usage rules
For example:
- “All legal definitions and product naming passages must be translated via DeepL Translator with the ‘Legal EN–DE’ glossary applied.”
- “Customer‑facing UI text is always handled via CAT + DeepL integration, not straight document translation.”
Template workflows for your teams
- Record short screen‑capture videos showing:
  - How to open the glossary panel
  - How to select the correct glossary
  - How to translate key passages and paste them back into documents
- Bake these into your internal localization or content ops playbook.
Use glossaries with DeepL API for system‑driven workflows
If you integrate DeepL via API into your CMS, ticketing, or product, you can often specify glossaries in your calls. That way:
- Content flowing through your systems always respects your termbase.
- Desktop document translation is used mainly for ad‑hoc work and internal drafts.

5. Security and compliance considerations for document translation

If you’re handling confidential or regulated content, your question about DeepL Pro and glossaries usually sits alongside security requirements. DeepL Pro is built to meet these needs:

Maximum data security
- DeepL Pro uses strong encryption and privacy controls.
- Texts are never stored without your consent.
- For documents, your files are deleted after translation, so they’re not kept in long‑term storage.
Enterprise‑grade controls
- SSO/MFA and admin governance for user access (for Pro team plans).
- ISO 27001, SOC 2 Type 2, and HIPAA/GDPR positioning for regulated industries.

From a vendor‑risk perspective, this is the line I draw: if a provider can’t explain what happens to your files after you drag‑and‑drop a contract, they’re not ready for enterprise translation. DeepL’s stance—that Pro content is deleted after processing and not used for model training—is exactly the kind of policy that passes security review.

6. Decision guide: which workflow to use when

To wrap it up, here’s how I’d choose:

You want: one‑click, layout‑preserving translations of general business documents.
→ Use DeepL Translator in the desktop app for document translation.
You want: strictly enforced terminology for key passages (e.g., definitions, product names).
→ Use DeepL Translator text translation + Glossaries, then paste results into your document.
You want: full governance—translation memories, locked terminology, QA checks.
→ Use DeepL Pro via CAT tool integration, especially for legal, compliance, and product UI text.
You want: cleaner source text so your glossary behaves more predictably.
→ Use DeepL Write to standardize your source language, then translate via the desktop app.

For teams that rely on DeepL Pro every day, the most effective setup combines all three surfaces:

Desktop document translation for speed and preserved layouts
Glossary‑driven text translation for high‑risk segments
CAT + DeepL integration for large‑scale, audited localization pipelines

If you’re planning to roll this out across a department or entire company, it’s worth aligning with DeepL’s sales team on the right Pro plan, CAT integrations, and security posture for your environment.

Get Started