Amazon Translate Pricing Calculator
Estimate Amazon Translate character and parallel-data storage costs for real-time text, batch, document, Office, and Active Custom Translation workloads by AWS Region.
Frequently Asked Questions
What counts as a billable Amazon Translate character?
AWS counts text characters processed, including whitespace. For multiple target languages, each translated output processes the source text again; use direct character mode when an AWS billing or job record already provides the final total.
Why does real-time DOCX translation cost more?
AWS exposes a separate Office file-type meter for the TranslateDocument operation. It is distinct from the Basic text and HTML meter, so the calculator keeps those modes separate.
Does custom terminology change the translation price?
Not in the current AWS Price List. Custom terminology does not expose a separate rate, while parallel data changes a batch job into the higher-priced Active Custom Translation mode and can add storage cost.
Why are translation modes priced separately?
AWS publishes separate meters for TranslateText, batch translation, Basic document files, Office documents, and Active Custom Translation. Batch jobs support text, HTML, DOCX, PPTX, XLSX, and XLIFF files, with up to 10 target languages per job. The calculator uses the selected meter without substituting another mode.
How is parallel-data storage priced?
AWS includes 200 GB of parallel-data storage per account. Active Custom Translation estimates charge only for storage above that amount. AWS documents this mode in US East (N. Virginia), US West (Oregon), and Europe (Ireland).
What does this estimate exclude?
It excludes negotiated volume pricing, credits, taxes, AWS Support, S3, KMS, CloudWatch, application compute, data transfer, and human translation or review. AWS asks customers processing more than 1 billion characters per month to request volume pricing.
How can I reduce Amazon Translate costs?
Use billing exports for the final character count, choose text or HTML when Office formatting is not needed, and remove stale parallel-data resources above the included 200 GB. Custom terminology is enough when you only need term-level control.
Related tools
CloudBurn
Catch AWS cost mistakes before they ship.
scan against Terraform and CloudFormation before deploy, then run discover against live AWS to find the waste that is already burning.Read the docs to learn how it works.