DeepL

Where DeepL sits

DeepL is the translation product I reach for when the actual words matter more than the language count. It is a German-built machine translation service — web translator, desktop and mobile apps, document translation, a writing assistant (DeepL Write), a voice product, and a REST API — that has spent nearly a decade competing on output quality rather than breadth. The company claims more than 200,000 business customers, and at time of writing the Translate API is advertised with over 100 supported languages after a 2025 expansion that added more than 70 in one go. That expansion changes the usual critique of DeepL: for years the trade-off was "better sentences, fewer languages," and while Google Translate still covers more low-resource pairs, the gap is far narrower than it was when DeepL shipped only 30-odd languages.

Pricing is freemium. At time of writing (deepl.com/en/pro, German storefront, EUR with VAT included), the free web translator allows 50,000 characters per month and one glossary. Individual costs EUR 7.49 per month billed annually (16% cheaper than monthly), which buys 300,000 characters per month, three file translations per month, files up to 30 MB, one glossary, and 30 minutes of DeepL Voice per user. Team is EUR 24.99 per user per month billed annually: 1,000,000 characters per user per month, 20 file translations, bulk file translation, five glossaries, SSO, team administration, and reporting. Business lifts the character cap to "unlimited" under a fair-use policy, includes translation memory and unlimited glossaries, 100 MB files, and a 99.0% availability commitment; Enterprise is quote-based with a 99.9% availability target, bring-your-own-key, and premium support. The Write Pro add-on runs EUR 6.99 per user per month billed annually on top of Individual and Team.

Developers get their own metering. The DeepL API Free tier allows 500,000 characters per month at no cost, while the newer DeepL API Developer plan is a one-time pot of 1,000,000 characters that never resets — a detail that trips people up, because "free API" now means two different things depending on which signup path you take (support.deepl.com articles on API plans and usage counting). The paid DeepL API Growth plan includes roughly 1M characters per month (12M per year on annual billing) with usage-based overage; third-party pricing trackers put the Growth base fee at about $26/month billed annually or $32.50/month billed monthly on the US checkout, and character overage around EUR 22 per million source characters. Treat those numbers as "at time of writing" figures from third-party trackers rather than a quote — DeepL's own API tab shows regional pricing. The old DeepL API Pro plan can no longer be purchased.

What it actually does

Under the hood this is text, HTML, and document translation with a small set of controls that professional users actually use: glossaries for forced terminology, a formality setting for languages that support it (German, French, Japanese and others), source-language auto-detection, and tag handling so HTML and XML markup survives translation. The Document API covers 15+ formats — DOCX, PPTX, PDF, XLSX and more — preserving layout, and accepts files up to 100 MB on the API side. The Voice product does speech-to-text and speech-to-speech translation across 40+ languages. Pro-tier content is not used for model training, and DeepL advertises ISO 27001 and SOC 2 Type II certified infrastructure with immediate deletion for API Pro processing.

My testing notes

Three things I watch for in translation tools, and DeepL's behavior on them is consistent enough that I'll describe it plainly. First, markup handling: with tag handling enabled, HTML tags are not billed as translatable characters and come back in place, which makes cost prediction on web content much saner than raw character counting. I have fed it product-description HTML and got back translated copy where the structure survived intact — links, spans, entities all in the right slots.

Second, glossaries. The glossary is the feature that separates "demo" from "workflow" in this category, and DeepL's version is per-language-pair and enforced: if I pin a product name so it is never translated, it stays untranslated in output. The limits scale with the plan (one glossary on free and Individual, five on Team, unlimited on Business and Enterprise), and the plan comparison table on deepl.com/en/pro shows glossary entries capped per language pair on lower tiers. In my testing the enforcement held across document translation as well as the text box.

Third, document fidelity. A translated DOCX with tables and heading styles came back with styles and table structure intact, which sounds like table stakes until you have watched other engines flatten a table into paragraphs. The 30 MB per-file ceiling on Individual and 100 MB on Business are the practical constraints, plus the per-month file counts (3 on Individual, 20 on Team).

On quality itself, my long-running comparison set is business correspondence and product copy between English, German, French, Spanish and Dutch. DeepL's output is the one I edit least — sentence rhythm and register come through, and the formal/informal tone switch for German does what it says. The 2025 language expansion added many new pairs via a next-generation model; the newer languages I spot-checked are usable but, unsurprisingly, less polished than the core European set.

Where it falls short

The limitations are mostly about scope and metering, not translation quality. This is not a translation management system: there is no translation memory below the Business tier, no vendor management, no project workflows. If you run a localization program you will still want a TMS around it.

The free tier is genuinely small — 50,000 characters per month is a couple of documents — and file translation is metered separately from characters, so heavy document users can hit a wall even with characters left. The Voice allocation of 30 minutes per user per month on Individual and Team is a taste, not a telephony solution. Write Pro, the AI writing assistant, is a paid add-on on Individual and Team rather than included, which I find annoying given that competitors bundle writing tools.

On the API, the Developer plan's non-resetting 1M-character pot is easy to mistake for a recurring free tier; it is not. And the per-million-character rate (around EUR 22 for overage on Growth at time of writing, per third-party trackers) is meaningfully higher than Google's basic translation tier, so at very high volumes the quality premium is a real budget line. Language coverage, while much improved, still trails Google for genuinely low-resource pairs.

Finally, pricing display is regional — the storefront flips currency and VAT treatment by detected country, so the numbers you see may differ from the EUR figures I quoted.

Verdict

DeepL is the translation engine I recommend when a human will read the result and care. It rated 4.3 in my rubric — 40% core functionality (glossaries, formality, document fidelity, a real API), 20% value (a usable free tier and honest per-seat pricing, offset by metered files and add-ons), 20% usability (the apps stay out of the way), 10% support and ecosystem (CAT plug-ins, integrations, certified infrastructure), and 10% reliability signals (long uptime record, security certifications). Buy Individual if you translate personally, Team if terminology consistency matters to your group, and evaluate the API on the Growth plan rather than the free tiers the moment you ship anything real.

Sources

• https://www.deepl.com/en/pro
• https://www.deepl.com/en/pro?tab=pricing
• https://www.deepl.com/en/developers
• https://support.deepl.com/hc/en-us/articles/360021200939-DeepL-API-Free
• https://support.deepl.com/hc/en-us/articles/360020685720-Usage-count-and-billing-in-DeepL-API
• https://support.deepl.com/hc/en-us/articles/360019925219-DeepL-Translator-languages
• https://developers.deepl.com/docs/resources/supported-languages
• https://developers.deepl.com/docs/de/resources/usage-limits
• https://www.deepl.com/en/blog/how-we-launched-70-new-languages-on-deepl
• https://www.deepl.com/en/press-release/deepl-translator-adds-korean-and-norwegian-bokml
• https://usagepricing.com/blueprint/deepl
• https://flexprice.io/pricing-index/deepl-translator
• https://wisepim.com/blog/deepl-vs-google-translate
• https://g2.com/products/deepl-api/pricing