Translation API Free Tiers 2026: DeepL, Google Cloud, Azure Compared¶
Building an MVP and trying to figure out how many translations actually fit in the free tier - and whether you’ll get a surprise bill after week one. Here are the exact numbers for all three major APIs, including the gotchas that don’t make it onto the official landing pages.
Quick comparison: all three free tiers at a glance¶
| DeepL API Free | Google Cloud Translation | Azure Translator F0 | |
|---|---|---|---|
| Characters/month | 500,000 | 500K (Basic) + 500K (Advanced) | 2,000,000 |
| Credit card required | No | Yes (won’t charge) | No |
| Duration | Permanent | Permanent | Permanent |
| Document translation | Yes | No | No |
| Glossaries | No | No | No |
| Custom models | No | No | No |
| LLM translation mode | No | No | No |
| DPA / GDPR | No | No | No |
| Price after limit | $25/1M + $5.49/mo | $20/1M | $10/1M |
The key takeaway: Azure gives you 4x more characters for free - but no document translation. DeepL is the only one of the three that lets you translate files (DOCX, PDF, PPTX) on the free tier. Google wins on language coverage - 189+ languages vs 36 for DeepL.
DeepL API Free: what’s actually included¶
500,000 characters per month is the headline limit. But the real difference from API Pro isn’t the character count - it’s the missing features and data handling terms.
What you get on the free tier:
- Text translation via
/v2/translate(all supported languages, ~36 currently) - Document translation via
/v2/document- DOCX, PDF, PPTX, XLSX, HTML, TXT with formatting preserved - Automatic language detection
- No credit card required to sign up
- Same API endpoints as paid plans
What’s missing or limited:
Glossaries - not available on the free tier. If you need consistent terminology (same term always translates the same way) - you need a paid plan.
Formality control (formal/informal) - Pro only. For German, French, Portuguese, and other languages where register matters, this is a significant missing feature.
Data Processing Agreement - DeepL doesn’t offer DPA on the free tier. Your data can be used to improve the service. If you’re processing client personal data (names, addresses, IDs) through the API, that’s a GDPR problem.
Rate limiting - DeepL doesn’t publish rate limits for the free tier, but they’re tighter than Pro. A developer on Stack Overflow described it this way:
On the free tier I kept hitting 429 errors even with just 5 concurrent requests. Switched to Pro and the same code worked perfectly. DeepL doesn’t document rate limits for free, but they’re definitely tighter.
So if your service fires multiple parallel translation requests, you may hit rate limits well before you reach 500K characters.
For a detailed quality comparison of DeepL vs Google vs Azure - including benchmarks for European language pairs - see DeepL vs Google Cloud vs Azure Translator: 2026 Comparison.
Google Cloud Translation: two separate free tiers¶
There’s a nuance not everyone knows: Google Cloud Translation has two separate free allowances - 500K characters each:
- 500K/month for Cloud Translation Basic (v2)
- 500K/month for Cloud Translation Advanced (v3)
That’s effectively 1M characters free if you use both API versions. But there’s a meaningful difference in what each one does.
Cloud Translation Basic (v2):
Simple text translation, minimal options. 189+ languages - the widest coverage of the three APIs. No glossaries, no adaptive translation, no batch translation. Good for basic tasks: translate a string, detect a language.
Cloud Translation Advanced (v3):
Glossaries, batch translation, and Adaptive Translation (LLM mode) are available here - but those features require a paid account. The free 500K allowance doesn’t cover them. Document translation is also paid-only ($0.08/page or via character-based billing for Advanced).
Per Google Cloud’s official pricing page:
Document translation falls under Advanced services and uses the same per-character billing. The free tier does not apply to document translation, Adaptive Translation, or the TextTranslation LLM model.
Billing setup is mandatory - even for the free tier, Google requires you to create a billing account and attach a card. Without it, you can’t access the 500K free allowance. Google won’t charge you until you exceed the limit, but you need to set up budget alerts in GCP Console yourself to avoid surprises.
If you’re just experimenting and don’t want to attach a card yet - DeepL and Azure are easier entry points.
For more on data privacy differences across paid and free tiers, including Google Cloud - see AI Translation and Data Privacy.
Azure Translator F0: the biggest limit with a significant catch¶
Azure gives you 2 million characters per month on the free F0 tier - and it’s permanent, not just the first 12 months like some AWS free tiers.
That’s 4x more than DeepL and Google. For a startup or MVP this can mean running for months without any payment even under real load.
What F0 includes:
- Text translation (100+ languages)
- Automatic language detection
- Transliteration (alphabet conversion)
- Dictionary lookup
- No credit card required to sign up
What F0 doesn’t include:
Document translation - this is a separate service in Azure and it’s not available on F0 at all. Only Standard (S1) and D3 Volume plans support document translation via Blob Storage.
Custom Translator - training custom models on your own parallel corpora - also not available on F0.
What happens when you hit 2M characters:
Azure doesn’t automatically switch to a paid tier. After hitting the limit you just get HTTP 429 or 403 errors until the next month resets. As the official Microsoft Learn Q&A confirms:
Once you reach the monthly quota, you will just receive an error until a new month begins.
No surprise charges - but your translation service stops working. For a production service that relies on real-time translation, this matters: if the limit runs out mid-month, translations just fail silently unless you’ve built in proper error handling.
What 500K and 2M characters actually means¶
Abstract numbers don’t tell you much - let’s calculate against real use cases.
500,000 characters (DeepL Free or Google Cloud Free) is roughly:
- 300-350 pages of A4 dense text (~1,500 chars/page)
- 2,000-3,000 short email messages (200-250 chars each)
- 100-250 standard documents (contract, statement, certificate - 2,000-5,000 chars each)
- About one full average-length novel
2,000,000 characters (Azure F0) - 4x that:
- 1,200-1,400 pages of A4 text
- 8,000-10,000 email messages
- 400-1,000 standard documents
| Content type | Average size | 500K chars | 2M chars |
|---|---|---|---|
| Short chat message | ~200 chars | ~2,500 messages | ~10,000 messages |
| ~1,000 chars | ~500 emails | ~2,000 emails | |
| Web article | ~3,000 chars | ~167 articles | ~667 articles |
| Standard document | ~3,500 chars | ~143 documents | ~571 documents |
| Legal contract | ~15,000 chars | ~33 contracts | ~133 contracts |
| Book (~300 pages) | ~500,000 chars | 1 book | 4 books |
Concrete example: if your service translates online chat messages, 500K covers roughly 2,500 messages per month, Azure F0 covers 10,000. For e-commerce product descriptions at 1,000 chars each - 500K is 500 new listings, 2M is 2,000.
What happens after the free limit runs out¶
This is where the three APIs differ most - especially if you care about financial risk.
DeepL API Free → Pro:
If a card is attached and billing is enabled, exceeding 500K automatically triggers Pro pricing: $25.00 per million characters plus a mandatory minimum subscription of $5.49/month. Even translating 501K characters means a minimum charge of $5.49 + a small overage amount. If you signed up without a card, the API just blocks instead - no charges, but also no translations.
Google Cloud Translation:
After 500K characters, Google starts charging $20.00 per million characters for both Basic and Advanced text translation. With billing enabled, it charges automatically without warning. Set up budget alerts in GCP Console - without them, it’s easy to run up a bill you didn’t expect.
Azure Translator F0:
No automatic transition. Just errors until the next month. To switch to paid, you manually change the tier from F0 to S1 in the Azure Portal.
| DeepL API Free | Google Cloud | Azure F0 | |
|---|---|---|---|
| After limit | Auto-charges (if card) or blocks | Auto-charges | Blocks (error 429) |
| Price after limit | $25/1M + $5.49/mo | $20/1M | $10/1M |
| Warning system | None | Budget alerts (manual setup) | None |
| Risk of surprise bill | Medium | Medium-high | Minimal |
Data privacy on free tiers¶
This is something developers often skip when evaluating free APIs - and it matters.
None of the three free tiers include a Data Processing Agreement (DPA). That means: no contractual obligation to delete data after translation, and the provider may use your requests to improve their models. If you’re passing client personal data (names, addresses, ID numbers) through the API, this is a direct GDPR issue.
DeepL: the free tier explicitly states data may be used to improve the service. DPA is available on paid plans only.
Google Cloud: the free tier falls under standard Google Terms of Service. For a DPA and Data Residency guarantees, you need a paid plan.
Azure: F0 also has no DPA. Microsoft’s Data Protection Agreement kicks in when you move to a paid tier.
If you’re building a B2B service where clients trust you with their documents, using a free API tier in production isn’t compliant under GDPR. For more on compliance requirements when working with AI translation - see DeepL DPA and GDPR: what you need to know.
Which API to choose for your use case¶
Testing and prototyping without documents - Azure F0. 2M characters free, no card required, straightforward REST API. Perfect for quickly integrating and checking if translation quality works for your use case. If you hit the limit, you just wait for the next month - no surprise charges.
MVP with document translation (DOCX/PDF) - DeepL API Free. The only one of the three that allows document translation on the free tier. 500K characters without a card, and quality for European language pairs (EN/DE/FR) is among the best in machine translation.
Maximum language coverage (50+ languages) - Google Cloud Basic. 189 languages vs 36 for DeepL and 100+ for Azure. If you need rare language pairs, Asian or African languages - Google is the only choice.
Production with zero financial risk - Azure F0 until the limit, then manual upgrade. Biggest free allowance, and after it runs out you just get errors instead of charges. But text translation only.
Once the free tier runs out and you’re choosing a paid plan, Azure is cheapest ($10/1M), Google is middle ground ($20/1M), DeepL is most expensive ($25/1M + subscription). But price isn’t the only factor: for European language pairs, DeepL quality typically cuts post-editing time by 2-3x compared to the others.
FAQ¶
Which translation API free tier has the highest character limit?¶
Azure Translator F0 - 2 million characters per month, permanently. That’s 4x more than DeepL API Free (500K) and Google Cloud Translation (500K). The downside: no document translation and no custom models on the free tier.
Does DeepL API Free require a credit card?¶
No. DeepL API Free signs up without any payment details. To move to API Pro (unlimited + glossaries + DPA) you need a card and a minimum $5.49/month subscription.
Does Google Cloud Translation free tier require a credit card?¶
Yes. Google requires you to set up billing (attach a card) even to access the free tier - though it won’t charge you until you exceed the limit. If you don’t want to attach a card, use DeepL or Azure instead.
Can I translate documents (DOCX, PDF) for free via API?¶
Of the three APIs, only DeepL API Free supports document translation on the free tier via the /v2/document endpoint. Google Cloud and Azure both restrict document translation to paid plans only.
What happens when the free tier limit runs out?¶
DeepL: if a card is attached, automatically switches to paid ($25/1M + $5.49/mo). Google: same, charges $20/1M characters. Azure F0: returns a 429/403 error until the next month resets - no charges, but translations stop working.
Are free API tiers suitable for production use?¶
Technically yes - but three issues: limits can run out unexpectedly mid-month, no DPA on free tiers (GDPR problem if processing client personal data), and DeepL Free throttles under concurrent load. For serious projects with real clients, upgrade to a paid plan after testing.
How many characters does a standard document have?¶
A typical A4 page of dense text is 1,500-2,000 characters. A standard contract (5-10 pages) is 7,500-20,000 characters. An official certificate or statement is 1,000-3,000 characters. A thesis (60 pages) is 90,000-120,000 characters.