How do I set formality (formal vs informal) in DeepL translations for German client emails?

Most teams writing German client emails run into the same issue: you need to switch cleanly between “Sie” and “du,” adjust tone, and still move fast. DeepL’s formality controls are built exactly for this—so you can decide, per email, whether you want a formal or informal translation and keep that consistent across your organization.

Below I’ll walk you through how to set formal vs informal formality in DeepL for German emails, how it behaves across products (DeepL Translator, DeepL Write, DeepL API, and integrations), and how to combine it with glossaries and rules for rock-solid client communication.

How formality works in DeepL for German

DeepL supports explicit formality control for German. That means you can tell the model to:

Use formal address: “Sie,” “Ihr,” more polite phrasing
Use informal address: “du,” “ihr,” more casual phrasing
Let DeepL decide automatically based on the context (default)

Formality doesn’t just switch pronouns. It also affects:

Verb conjugation (e.g., “könnten Sie…” vs “kannst du…”)
Set phrases and closings (e.g., “Mit freundlichen Grüßen” vs “Viele Grüße” depending on context)
Overall tone (more hedging/politeness in formal; more direct in informal)

For German client emails—especially in B2B or regulated contexts—you typically want consistent formal “Sie” unless you’ve explicitly agreed on “du.”

Setting formality in the DeepL web translator

If you’re drafting or translating emails in the browser, you’ll use DeepL Translator and DeepL Write from deepl.com. Here’s how to control formality for German:

1. Choose languages first

Go to deepl.com/translator.
Set your source language (e.g., English).
Set the target language to German (Deutsch).

Formality options only appear when you select a language that supports formality, like German.

2. Set formality level

Once German is the target language:

Look for the Formality or tone selector near the target-language text field.
Choose one of:
- More formal – for “Sie”-based, business-appropriate German.
- More informal – for “du”-based, casual or internal emails.
- Automatic/default – DeepL decides; fine for mixed scenarios, but I don’t recommend this for sensitive client communication where you must enforce “Sie.”

DeepL will immediately re-render the translation in line with the selected formality.

3. Review and fine-tune with DeepL Write

For client emails, I recommend a two-step flow:

Translate in DeepL Translator → set “More formal” for German.
Click into the result and open DeepL Write (or paste the German text into DeepL Write).

In DeepL Write, you can:

Ask for clearer, more concise business phrasing.
Adjust style and tone to match your brand (e.g., more “confident” or more “diplomatic”).
Fix subtle register issues without losing the “Sie” form.

This combination gives you both correct formality and polished business German.

Setting formality in DeepL desktop and mobile apps

If your team uses DeepL outside the browser (Windows/macOS app, or mobile apps), the formality controls follow the same logic.

Desktop apps (Windows, macOS)

Open the DeepL app.
Select source and target languages (target = German).
Enter or paste your email text.
Find the Formality selector near the translation output and choose:
- More formal for client-facing emails.
- More informal for colleagues you “duzen.”

The app remembers the last-used setting per language, so if you always write German client emails in formal style, set it once and keep an eye on it before sending.

Mobile apps (iOS, Android)

Open the DeepL app on your phone.
Set target language to German.
Paste or type your email.
Use the formality control (e.g., via a dropdown or settings icon near the output) to choose formal or informal.

This is useful if you’re approving quick replies from your phone and still need consistent “Sie.”

Using formality with DeepL for Outlook, Word, and other integrations

Many teams draft and send client emails directly from Outlook or Google Workspace. DeepL provides extensions and add-ins so you can translate where you work, often with formality controls built in.

Outlook / Word add-ins

In the DeepL add-in for Outlook or Word:

Highlight the source text (e.g., an English draft email).
Open the DeepL pane.
Choose German as the target language.
Look for the Formality option:
- Set to More formal for client communication.
- Confirm that the output uses “Sie” and formal verb forms.

Then you can insert the translation directly into your email without copy-paste gymnastics.

Browser extensions (Chrome, Firefox, Edge)

If you’re using webmail (e.g., Outlook Web, Gmail):

Install the DeepL browser extension.
Draft your email in your source language or paste text into the compose window.
Use the extension to translate the selection to German.
In the extension popup, set Formality: More formal before inserting the translation.

This keeps your German client emails aligned with your company’s formality standards even in browser-based workflows.

Controlling formality via DeepL API (for automated email workflows)

If you’re integrating DeepL into your CRM, ticketing system, or custom email workflow via the DeepL API, you can set formality programmatically.

Key parameter

Use the formality parameter in your API request.

Typical values include:

formality=more → more formal German (recommended for client emails)
formality=less → more informal German
formality=default or omitted → let DeepL decide

Example logic for German client emails

If your system detects:

Outbound client emails to German-speaking customers → send text to the DeepL API with:
- target_lang=DE
- formality=more
Internal communications to German-speaking colleagues → you may opt for:
- formality=less if you use “du” internally.

This way, formality is not a user decision—it’s enforced by your tooling based on audience, which is exactly what you want in regulated or brand-sensitive environments.

Best practices for German client emails with DeepL formality

To avoid inconsistent tone and accidental “duzen” in client communications, I recommend a few governance steps.

1. Decide company-wide rules for German formality

Typical patterns I see:

B2B, finance, legal, healthcare, public sector:
- Default: formal “Sie” for all external clients and partners.
- Exceptions: only when the client explicitly initiates “du.”
Tech/SaaS, startup culture:
- Marketing website may use “du,” but contracts, invoices, and support escalation emails still often rely on “Sie.”
- Decide this clearly and document it.

Once this policy is set, configure DeepL accordingly in all your main surfaces.

2. Combine formality with DeepL glossaries

Formality alone won’t protect you from inconsistent terminology. For client emails you send in volume (support, account management, onboarding), use DeepL glossaries to:

Lock in product names and feature terms (no unwanted localization).
Standardize legal and financial phrases.
Align on preferred tone expressions (e.g., “Vielen Dank für Ihre Nachricht” vs “Danke für Ihre Nachricht”).

In practice:

Set Formality: More formal for German.
Define glossary entries that match your brand’s preferred polite phrases.
Train your team to rely on these outputs instead of rewriting from scratch.

3. Use DeepL Write to polish tone (without breaking formality)

Even with the right formality setting, an email can feel:

Too stiff or old-fashioned.
Too direct for a sensitive situation.

Paste the German output into DeepL Write and:

Select an appropriate tone (e.g., “diplomatic” for complaint handling, “confident” for proposals).
Let Write propose Alternatives and show changes.
Confirm that it retains “Sie” and formal verb forms.

This is where you get from “correct” to “on-brand and empathetic.”

4. Create templates for recurring email types

For high-volume scenarios (support tickets, onboarding, renewals):

Draft master templates in German using:
- DeepL Translator with formality set to More formal.
- DeepL Write to refine phrasing.
Review once with your legal/compliance and local market owner.
Store them in your CRM or help desk.

Then your teams can send these consistently, with only minor adjustments, instead of deciding formality every time.

Common pitfalls and how to avoid them

Pitfall 1: Mixing “Sie” and “du” in the same conversation

If you translate some messages with “More formal” and others with “More informal,” you can end up addressing the same client with both “Sie” and “du.”

Fix:
For all German-language client threads:

Set and keep Formality: More formal in DeepL.
If the client explicitly switches to “du,” explicitly update the setting to “More informal” from that point on and leave a note in the CRM.

Pitfall 2: Assuming automatic formality is safe for clients

The automatic/default formality is convenient, but not strict. It may make stylistic decisions that you wouldn’t sign off on for regulated or VIP clients.

Fix:
For German client emails, especially in legal, financial, healthcare, or enterprise sales, always:

Set Formality: More formal manually (or via API).
Treat automatic formality as acceptable only for internal drafts or low-risk channels.

Pitfall 3: Over-editing and breaking consistency

Sometimes a native speaker will “improve” an email by rewriting parts and accidentally mixing formality level or voice.

Fix:

After manual edits, run the text through DeepL Write to re-harmonize tone.
Ask Write for a style that matches your guidelines (e.g., “polite and clear”) and check the final version for consistent “Sie” forms.

Using DeepL Voice for Meetings without breaking formality

If you also use DeepL Voice for Meetings (e.g., multilingual subtitles in Microsoft Teams or Zoom), remember:

Live subtitles prioritize understanding over strict register.
However, when you follow up by email, switch back to:
- DeepL Translator with Formality: More formal for German.
- DeepL Write to adjust politeness and structure.

The goal is: conversational flexibility in meetings; controlled formality in written follow-ups.

How to operationalize this across your organization

To make sure every German client email respects your formality standard:

Document your rules
- Specify when to use formal vs informal German.
- Give example phrases for openings and closings for each.
Standardize DeepL settings
- For all client-facing teams, set default target language = German (formal) in DeepL.
- In API-integrated systems, enforce formality=more for German client messages.
Train teams on formality controls
- Show where the formality switch is in:
  - DeepL web Translator
  - Desktop apps
  - Outlook/Word add-ins
  - Browser extensions
- Make “check formality before sending” a checklist item.
Review real emails periodically
- Sample outgoing German client emails.
- Validate formality, terminology, and tone.
- Update templates, glossaries, or rules if recurring issues appear.

Final recommendation

For German client emails, your safest and most consistent setup with DeepL is:

Always set Formality: More formal for target language German in DeepL Translator, desktop, and extensions.
Use the DeepL API with formality=more for any automated or integrated email flows.
Layer DeepL Glossaries for fixed terms and DeepL Write for final tone polishing.

That combination gives you fast, high-quality German translations that stay firmly in the “Sie” register—without relying on each individual sender to remember the nuances.

To explore how this can look in your environment and at your scale, you can get in touch with DeepL’s team:
Get Started