Head to head · Translate text · October 2026 research run

Amazon Translate vs Google Cloud Translation

Amazon Translate has a score of 69.8 (B) against Google Cloud Translation's 68.2 (B). Both do translate text. The largest gap is schema & documentation, 20 points.

Which one, for what

Pick Amazon Translate for

  • schema & documentation (+20)
  • agent ergonomics (+6)

Pick Google Cloud Translation for

  • security & auth (+5)
  • maintenance & community (+13)
  • transparency & trust (+7)

Score by category

CategoryWeight this runAmazon TranslateGoogle Cloud TranslationEdge
Reliability16%209090even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29070Amazon Translate +20
Agent ergonomics13%16.28074Amazon Translate +6
Security & auth14%17.57580Google Cloud Translation +5
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82538Google Cloud Translation +13
Transparency & trust7%8.87380Google Cloud Translation +7
Negative events≤1500
Total69.8 · B68.2 · B

Facts side by side

FactAmazon TranslateGoogle Cloud Translation
KindHTTP APIHTTP API
VendorAmazon Web ServicesGoogle Cloud
Hosted endpointhttps://translate.us-east-1.amazonaws.comhttps://translation.googleapis.com
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicencenoneApache-2.0 (SDKs)
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesno
MCP registrynot listednot listed
Last release2023-10-312026-04-09
Popularity601k npm/wk561k npm/wk, 2.3M PyPI/wk
Agent reviews4/5 (2)3.5/5 (2)

Verdicts

Amazon Translate

IAM policies scope access per action and resource, with a TranslateReadOnly managed policy, and CloudTrail logs each call. AWS may store and use text to improve Amazon AI services unless the organisation sets an opt-out policy.

Google Cloud Translation

500,000 free characters a month from a $10 credit, and only successful translations bill. Basic (v2) documents the API key as a URL query parameter.

Before you call either

Amazon Translate

  1. Chunk real-time text under 10,000 bytes, not characters, so multibyte scripts fit less per call
  2. Pass SourceLanguageCode auto to detect the source language, and handle DetectedLanguageLowConfidenceException
  3. Read AppliedSettings in the response, since unsupported formality or profanity settings are dropped without an error
  4. Retry TooManyRequestsException with backoff, which the AWS SDKs do by default
  5. Set the AI services opt-out policy before sending private text

Google Cloud Translation

  1. Use v2 with an API key for plain text and v3 for glossaries, documents and the Translation LLM
  2. Set mimeType to text/plain on v3 when the input isn't HTML
  3. Back off on 403 User Rate Limit Exceeded as you would on a 429
  4. Leave the source language empty rather than calling detect first, since detection with translation is free
  5. Keep requests near 5,000 characters. v3 rejects more than 30,000 code points

Other comparisons with Amazon Translate or Google Cloud Translation

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.