Head to head · Translation · October 2026 research run

Amazon Translate vs Google Cloud Translation

Amazon Translate scores 76.9 (BB) on agent readiness against Google Cloud Translation's 71.1 (BB), and leads in 4 of 7 scored categories. Google Cloud Translation leads on security & auth and transparency & trust. Both do translation. Amazon Translate is cheaper for translation, $15 against $20 per 1M characters.

Best machine translation APIs for AI agents · All 105 translation comparisons

Which one, for what

Amazon Translate BB

Best for Operators already on AWS who want translation inside IAM and CloudTrail, with S3 batch jobs and terminology files.

Ahead on

  • Schema & documentation, 90 against 70
  • Agent ergonomics, 80 against 74
  • Payments & pricing, 45 against 30
  • Maintenance & community, 65 against 38

Also in its favour

  • Cheaper for translation, $15 against $20 per 1M characters
  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

AWS may store and use text to improve Amazon AI services unless the organisation sets an opt-out policy

Google Cloud Translation BB

Best for Agents on Google Cloud that want high quotas, clear data terms and a choice of NMT, LLM or adaptive translation with glossaries.

Ahead on

  • Security & auth, 87 against 78
  • Transparency & trust, 85 against 72

Watch for

Basic (v2) documents the API key as a URL query parameter, and both versions accept an OAuth token as ?access_token=

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Amazon Translate +27

Amazon Translate 65

Read as a closed service from its own service model, as this run reads every AWS listing. The translate model in aws/api-models-aws changed on 8 October 2026 (commit 11f19c6), adding Smithy RPC v2 CBOR as a second protocol beside AWS JSON 1.1, 24 days before 1 November (30). In the 90 days from 3 August that is one model change. @aws-sdk/client-translate shipped 60 versions in the same window, to 3.1161.0 on 30 October, and every one but 3.1148.0 (8 October, the same CBOR change) is a version bump that doesn't change the service, so they count at half, as amazon-sns's client versions were read (10 of 20). The document history's newest entry is still brevity on 2023-10-31. AWS re:Post and paid support plans exist, SDK issue trackers not checked (5 of 15). Official SDKs current, @aws-sdk/client-translate 3.1161.0 and boto3 (15). SDKs regenerate from the model on AWS's release train, CI not checked (5 of 10). 30 + 10 + 5 + 15 + 5 = 65.

Google Cloud Translation 38

Read as a closed service with official SDKs. The last change to the API we found is still the adaptive mime_type field, in Node.js client 9.4.0 on 8 April 2026 and Python client 3.26.0 on 9 April, 206 days before 1 November, and the newest release note is 24 February 2026 (0). In the 90 days from 3 August there are seven client releases and no release note. Node.js @google-cloud/translate 10.0.0 (4 August, Node.js 22 floor), 10.0.1 (12 August, dependencies), 10.1.0 (8 September, a generator upgrade that only reformats the client code), 10.1.1 (28 September, package.json), 10.2.0 (7 October, a test script) and 10.3.0 (8 October, no change to the package beyond its version), and Python google-cloud-translate 3.28.0 (1 October, declares Python 3.15 support). None changes the service or the client's behaviour, so none can set the recency line. Releases that don't change the service count half on the 90-day line, and with no change to the service in the window that is half the line, as the Amazon SNS listing reads its version bumps and the AgentCore Code Interpreter listing its SDK releases (10 of 20). Release notes, Google Cloud support and the public issue tracker exist, but the notes have had one entry in the past year (8 of 15). Official client libraries current, Python for 3.10 to 3.15 and Node.js 22 or later (15). Libraries regenerate in the googleapis monorepos, CI not checked (5 of 10). 0 + 10 + 8 + 15 + 5 = 38.

Schema & documentation Amazon Translate +20

Amazon Translate 90

The service model (API version 2017-07-01) is public in every AWS SDK and in the aws/api-models-aws repository, a machine-readable contract in the role OpenAPI plays. Since 8 October 2026 it declares Smithy RPC v2 CBOR beside AWS JSON 1.1 (25). llms.txt for the developer guide (139 lines on 1 November), a Markdown contents page with a link to the whole guide as one Markdown file (10). The guide separates real-time text, real-time documents and S3 batch jobs and says when each fits (15). Inputs typed with enums for formality, profanity and brevity, byte limits and required fields marked (15). Each action lists its errors with HTTP codes, but the API reference has syntax templates and no worked examples (10 of 15). Versioned API and a dated document history (15).

Google Cloud Translation 70

A public Discovery document for v3 (revision 20260901, unchanged on 1 November) and the protos behind the SDKs form the machine-readable contract (25). No llms.txt at docs.cloud.google.com/translate (0). The docs explain Basic against Advanced and NMT against the Translation LLM and adaptive translation, but not when to avoid each (15 of 20). Types and required fields in the Discovery document, but model is a resource path string and mimeType a free string rather than enums (10 of 15). REST pages carry examples and the quotas page documents the 403 messages, with errors otherwise in Google's generic error model (10 of 15). Versioned v2 and v3 and a release notes page, but the notes skip changes the SDK changelog shows, such as RefineText in November 2025 and an adaptive mime_type field in April 2026 (10 of 15).

Payments & pricing Amazon Translate +15

Amazon Translate 45

No x402, MPP or L402 (0). Per-million-character prices for every mode published without a login, re-read on 1 November (20). The pricing page lists 2 million characters a month free for 12 months for standard text and batch translation, and none for real-time documents. New AWS customers get up to $200 in Free Tier credits on a free plan of up to 6 months, and the Free Tier FAQ (Q4) says a payment method isn't required for most new customers, but AWS's account docs read on 1 November say AWS might request payment information and holds USD $1 to verify, so half, as on the Polly, Transcribe, S3, SES and Secrets Manager listings (10). A person signs up in a browser. IAM can mint keys by API only after a human has an account (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Google Cloud Translation 30

No x402, MPP or L402 (0). Per-million-character and per-page prices for every model published without a login, re-read on 1 November (20). A $10 monthly credit covers 500,000 NMT characters, but a billing account needs a card (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Google Cloud Translation +13

Amazon Translate 72

Closed service under the AWS Service Terms (15). The FAQ, service terms and opt-out guide agree that AWS may use content by default and that an organisation policy stops it, and a DPA and sub-processor list exist. The same FAQ, re-read on 1 November, says AWS will only use content with your consent, which sits awkwardly beside a default you have to switch off (20 of 30). No deprecation policy or dated deprecation notices found for Translate (0). Sub-processors listed and the region chosen per request, but the FAQ allows some content to be stored in another region (15 of 20).

Google Cloud Translation 85

Closed service under the Google Cloud terms, client libraries under Apache-2.0 (15). The data usage FAQ (last updated 27 October) agrees with the terms on in-memory processing, no training and no sharing, but doesn't cover the Translation LLM or adaptive translation (25 of 30). The Translation docs carry a deprecation page that applies the Google Cloud terms' discontinuation section and gives Translation Hub a deprecation date of 30 June 2025 and a shutdown date of 20 September 2026, and the release notes date the PBMT removal of 2021. The notice is for a neighbouring product rather than the API, and there is no per-version lifecycle page like Document AI's (16 of 20). Regional endpoints on Advanced for data location, global-only on Basic. Google Cloud's sub-processor list wasn't re-checked (15 of 20). 15 + 25 + 16 + 15 = 71.

Security & auth Google Cloud Translation +9

Amazon Translate 78

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. SigV4 with IAM users, roles and temporary credentials, scoped per action and resource, and a TranslateReadOnly managed policy (30). Section 50.3 of the AWS Service Terms (last updated 30 October 2026, re-read on 1 November) still names Amazon Translate among the services whose content AWS may store and use to improve the service and other Amazon AI technologies by default. Any customer can opt out with an AI services opt-out policy in AWS Organizations (10 of 20). The FAQ, re-read on 1 November, says content is stored at rest in the region in use and that some may be stored in another region for service improvement. No zero-retention mode without the opt-out (5 of 15). CloudTrail logs API calls per caller (15). Vulnerability reporting policy at vdp.aws.security, SOC and ISO reports in AWS Artifact and public security bulletins, none of the 39 in the feed on 1 November naming Translate. The security.txt on aws.amazon.com, expired from 24 September 2026, was renewed and, re-read on 1 November, expires on 16 October 2027. We found no paid public bug bounty, so 2 points stay held back, as on the Polly, Transcribe, S3 and Secrets Manager listings (18 of 20). 30 + 10 + 5 + 15 + 18 = 78.

Google Cloud Translation 87

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines, as the other translation listings are read. Advanced (v3) uses OAuth 2.0 from service accounts or Application Default Credentials, with a cloud-translation scope and IAM roles (30), less 10 because Basic (v2) documents the API key as a key query parameter. The OAuth token can travel in the URL as well. The v3 Discovery document (revision 20260901) lists access_token, oauth_token and key as query parameters, and on 1 November a v3 translateText request with no token answered 401 'Request is missing required authentication credential' while one with a made-up ?access_token= answered 401 'Request had invalid authentication credentials', the test every Google API listing takes in this run. The checklist takes the 10 off once for a secret in a URL, so this adds no second deduction (20). The data usage FAQ (last updated 27 October) says Google doesn't use content sent to the API to train or improve Google Translation and won't share it with third parties (20). Text is held briefly in memory for the request. Glossaries are stored in your project, and Basic's global endpoint can't keep processing in one region (15). The audit logging page lists every v3 method by permission type, and translation calls write Data Access logs, which Google Cloud leaves off until the owner enables them. Basic (v2) isn't audit-logged, and calls to AutoML models aren't logged (12 of 15). google.com security.txt valid to 1 April 2030 and pointing to the vulnerability reward programme, and Google Cloud's ISO 27001 page names Cloud Translation in scope, both read on 1 November. That is the reading most Google Cloud listings take on this line (20). 20 + 20 + 15 + 12 + 20 = 87.

Agent ergonomics Amazon Translate +6

Amazon Translate 80

API reading of the checklist. Responses carry the translation plus AppliedSettings and AppliedTerminologies and nothing else, and brevity can shorten output, but there's no field selection (20 of 25). List calls page with NextToken and MaxResults, and request limits are published, but TranslateText takes one string, so batching small strings means S3 jobs or many calls (15 of 20). Typed errors an agent can act on, such as UnsupportedLanguagePairException, DetectedLanguageLowConfidenceException and TextSizeLimitExceededException (20). TranslateText is stateless and batch jobs take a ClientToken. No read-only hints apply to a plain API (15 of 20). Three required fields, auto for detection, but SigV4 signing is hard without an SDK. SDKs in every major language (10 of 15).

Google Cloud Translation 74

API reading of the checklist. Responses hold the translations and detected language, and a glossary call returns both the glossary and plain translations, which doubles the output (20 of 25). Many strings per request (128 on v2), glossary listing with page size, token and filter, batch jobs to Cloud Storage (18 of 20). Errors use Google's status and message format, but quota errors arrive as 403, so generic 429 retry logic misses them (12 of 20). Stateless translation and long-running batch operations, with no retry guidance on the quotas page (12 of 20). v3 needs a project and location path and treats input as HTML unless mimeType says otherwise. Client libraries in seven or more languages (12 of 15).

Score by category

CategoryWeightAmazon TranslateGoogle Cloud TranslationEdge
Reliability16%9090even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9070Amazon Translate +20
Agent ergonomics13%8074Amazon Translate +6
Security & auth14%7887Google Cloud Translation +9
Payments & pricing10%4530Amazon Translate +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6538Amazon Translate +27
Transparency & trust7%7285Google Cloud Translation +13
Negative events≤1500
TotalBB 76.9/100BB 71.1/100

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
Price for translation$15 per 1M characters$20 per 1M characters
x402nono
LicencenoneApache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesno
Last release2026-10-082026-10-08
Terms last updated2026-10-012026-09-02
Privacy policy last updated2026-05-182026-10-01
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity601k npm/wk561k npm/wk, 2.3M PyPI/wk
Agent reviews4/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Amazon Translate higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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, and the document history has no new capability since October 2023.

Google Cloud Translation

500,000 free characters a month from a $10 credit, and only successful translations bill. Advanced has per-method audit logs and regional endpoints. Basic (v2) documents the API key as a URL query parameter, quota errors arrive as 403 rather than 429, and the API itself hasn't changed since April 2026.

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. Send keys and tokens in headers, never as key or access_token in the URL, so they stay out of logs

Questions

Which is better for AI agents, Amazon Translate or Google Cloud Translation?

Amazon Translate scores 76.9 (BB) on agent readiness against Google Cloud Translation's 71.1 (BB), and leads in 4 of 7 scored categories. Google Cloud Translation leads on security & auth and transparency & trust.

Which is cheaper for translation, Amazon Translate or Google Cloud Translation?

Amazon Translate, at $15 per 1M characters against $20 per 1M characters for Google Cloud Translation. These are the vendors' published prices for the job.

Do Amazon Translate and Google Cloud Translation need an API key?

Amazon Translate needs an API key. Google Cloud Translation takes an API key or an OAuth sign-in.

Can an agent call Amazon Translate and Google Cloud Translation without installing anything?

Yes. Amazon Translate has a hosted endpoint at https://translate.us-east-1.amazonaws.com and Google Cloud Translation at https://translation.googleapis.com.

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.