Open API PricingOpen API Pricing

Amazon Translate vs DeepL API pricing

Both are in translation apis. Amazon Translate is billed per million chars; DeepL API is billed per million chars. Numbers below are copied from each vendor's pricing page.

Amazon Translate vs DeepL API pricing side by side
Amazon TranslateFree tier or trial
Free tier
2M chars/mo for 12 months
Billed
Per million chars
Best for
MT inside the AWS stack
Verified
Jun 27, 2026
DeepL APIFree tier or trial
Free tier
500k chars/mo (API Free)
Billed
Per million chars
Best for
High-quality MT API for developers
Verified
Jun 27, 2026

Amazon Translate plans

PlanPriceWhat it covers
Standard Text Translation$15.00 / 1M charactersReal-time and asynchronous batch text translation; billed per character including whitespace, pay-as-you-go.
Batch Document Translation$15.00 / 1M charactersAsynchronous translation of documents stored in Amazon S3.
Real-Time Document Translation (Text & HTML)$15.00 / 1M charactersSynchronous document translation preserving formatting; no free tier.
Real-Time Document Translation (Docx)$30.00 / 1M charactersSynchronous Word .docx translation; no free tier.
Active Custom Translation (ACT)$60.00 / 1M charactersDomain-customized output using parallel data; includes 200 GB free parallel-data storage ($0.023/GB/mo overage).
Free Tier$02M characters/month free for first 12 months (standard & batch); ACT 500K characters/month free for 2 months.

Source: https://aws.amazon.com/translate/pricing/

DeepL API plans

PlanPriceWhat it covers
API Free$0/monthUp to 500,000 characters per month; full text and document translation API access, no cost.
API Growth~$26/month (annual)Includes ~12M characters/year (~1M/month) with overage billed around $27.50 per additional million characters.
Enterprise APICustomUp-front custom commitments for characters, speech-to-text and speech-to-speech; pay-as-you-go above commitment; includes 99.9% uptime SLA.

Source: https://www.eesel.ai/blog/deepl-pricing

Amazon Translate pricing guideDeepL API pricing guideQuality scores on APIbenchmarks →