Product - Aug 13, 2026

How to Use DeepL: Translator, Write, Documents, and API

Answer First

Start with the smallest DeepL surface that matches the job: Translator for text, document translation for layout-bearing files, Write for revising prose, or the API for a product workflow. Test one representative sample, compare it with the original, and verify current limits on the official DeepL product and API documentation before paying or automating.

Choose the Right Starting Surface

Job	Start here	Acceptance check
Translate a paragraph	DeepL Translator	Meaning, tone, terminology, names, numbers, and negation
Improve existing prose	DeepL Write	Intended meaning remains unchanged; edits match audience and style
Translate a document	Document translation	Text, tables, footnotes, links, page order, and formatting survive review
Reuse approved terminology	Glossary-capable workflow	Required terms are applied consistently in context
Add translation to a product	DeepL API	Language support, latency, error handling, billing, privacy, and human review

First Translation Workflow

Choose a short but representative sample containing a name, number, product term, and ambiguous sentence.
Paste only content you are authorized to process.
Select source and target languages explicitly when that reduces ambiguity.
Review the output sentence by sentence against the source.
Correct key terminology and save the approved pair for later comparison.
Test the same sample in the exact app, extension, document, or API path you plan to use.

Fluent output can still be wrong. For legal, medical, safety, contractual, or publication-critical text, use a qualified human reviewer.

Document Translation Checklist

Before uploading, confirm the file contains no data that the current account and organization policy prohibit. After translation, inspect:

headings, tables, footnotes, captions, and links;
names, dates, currency, units, and decimal separators;
untranslated text inside images or diagrams;
line breaks, overflow, and page order;
clauses whose meaning depends on jurisdiction or defined terms.

Do not call a document complete because the file exported successfully.

API Pilot

Use the current DeepL API documentation rather than copying an old endpoint, quota, or price. A production pilot should record:

exact endpoint and authentication method;
supported source and target languages;
glossary and document requirements;
retry, timeout, and idempotency behavior;
usage and cost alerts;
data handling and log retention;
human-review rules for high-impact content.

Consumer product access and API billing are separate boundaries until official account documentation proves otherwise.

Current API plan map

DeepL’s official API-plan help was rechecked on August 13, 2026. It says the former API Free and API Pro plans can no longer be purchased and describes three current paths:

Current path	Official boundary	First check
API Developer	A bounded developer entry plan with a total character allowance	Whether the total allowance, supported resources, and upgrade path fit the pilot
API Growth	A recurring plan with included usage, overage billing, cost controls, and API-key limits	Current monthly or yearly terms, included usage, overage, and resource access
Enterprise API	Custom commitments for large-scale or long-term programs	Contracted capacity, security, administration, support, and data requirements

Older API Free or API Pro accounts can still appear in help content, but a legacy account description is not a current purchase path. Likewise, DeepL’s current plan overview says Translator subscriptions do not grant translation API access and a Write Pro add-on does not grant Write API access.

For language support, avoid one static checklist. DeepL’s developer docs expose resource-specific language data because Translate, document translation, Voice, Write, glossaries, formality, and style rules can support different combinations.

Frequently Asked Questions

Do I need a DeepL account to get started?

Begin on the current DeepL product surface and follow the live sign-in requirement for the task. Account, file, language, and plan requirements can differ by product and region.

Should I use DeepL Translator or DeepL Write?

Use Translator to change languages and Write to revise wording within a supported language. For important work, review meaning, terminology, names, numbers, and formatting after either workflow.

Does a DeepL Translator plan include API usage?

No. DeepL’s current plan help says Translator plans do not include translation API access, and a Write Pro add-on does not include the Write API. Choose and verify an API plan separately.

Can a new customer buy DeepL API Free or API Pro?

DeepL’s current API-plan help says API Free and API Pro can no longer be purchased. New API evaluation should start from the live Developer, Growth, or Enterprise offering shown for the account and region.

How should I check DeepL API language support?

Use the current language endpoints or documentation for the exact resource instead of hardcoding one language list across Translate, Documents, Voice, Write, glossaries, and style rules.

Next Decision

Use Grammarly vs. DeepL Write for a writing-assistant comparison.
Use the English-to-French translator or English-to-Japanese translator for a prompt-and-review workflow.
Use the Felo AI pricing guide when multilingual research, rather than translation alone, is the main job.

Sources and Review Date

Official links were checked on August 13, 2026. Reconfirm supported languages, files, limits, prices, and data terms in the live product before scaling.