Head to head · Translation · October 2026 research run
Azure Translator vs Google Cloud Translation
Azure Translator scores 73.2 (BB) on agent readiness against Google Cloud Translation's 71.1 (BB), and leads in 3 of 7 scored categories. Google Cloud Translation leads on reliability, security & auth and transparency & trust. Both do translation. Azure Translator is cheaper for translation, $10 against $20 per 1M characters.
Best machine translation APIs for AI agents · All 105 translation comparisons
Which one, for what
Best for Azure shops that want cheap NMT at volume, Entra ID auth and a choice of an LLM per request for tone and gender.
Ahead on
- Schema & documentation, 83 against 70
- Agent ergonomics, 82 against 74
- Maintenance & community, 70 against 38
Also in its favour
- Cheaper for translation, $10 against $20 per 1M characters
Watch for
The 2026-06-06 schema breaks v3.0 clients and drops BreakSentence and dictionary lookups from the spec
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
- Reliability, 90 against 83
- Security & auth, 87 against 75
- Transparency & trust, 85 against 78
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 Azure Translator +32
Azure Translator 70
Read as a closed service with official SDKs, as the other Azure listings are. The newest release that changes the client is Java text 2.0.3 on 28 August 2026 (a custom-endpoint fix), 65 days before 1 November (20). The Java text and document libraries' 2.0.4 and 2.0.2 (6 October) and 2.1.0 (30 October) only raise azure-core and azure-core-http-netty, per their changelogs and tags. Releases that don't change the service or the client count half on the 90-day line and don't set the recency line, as this run read Amazon Transcribe's and Amazon SNS's SDK tags. Well over three dated releases in the 90 days from 3 August even so, among them .NET document 3.0.0 and JavaScript document 1.0.0 on 5 August, Java text 2.0.2 on 18 August and 2.0.3 on 28 August (20). Public What's New page (updated 8 August), Microsoft Q&A and GitHub issue trackers on the SDK repositories, which we didn't read (10 of 15). Official SDKs current in Python, JavaScript, .NET and Java, with text 2.0.0 for Python, JavaScript and .NET from 28 and 29 May 2026 (15). The SDKs live in the azure-sdk monorepos, CI not checked (5 of 10). Release dates are from the release tags and changelogs, since PyPI and npm didn't resolve from our shell on 1 November. 20+20+10+15+5 = 70.
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 Azure Translator +13
Azure Translator 83
OpenAPI documents for text translation 3.0 and 2026-06-06 are public in Azure/azure-rest-api-specs, with examples on each operation (25). No llms.txt found on learn.microsoft.com (0). Operation descriptions state purpose, and the overview says to pick NMT or an LLM by quality, cost and scenario, but not when to avoid either (15 of 20). Enums for profanityAction, textType, tone and gender, required fields marked, but the LLM deploymentName is a free string (13 of 15). Examples in the spec and a status-code page with six-digit error codes and their meanings (15). Dated api-version values and a What's New page (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).
Security & auth Google Cloud Translation +12
Azure Translator 75
Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Resource keys, 10-minute bearer tokens, or Microsoft Entra ID with the Cognitive Services User role and managed identities (30), less 10 because the authentication reference documents passing the key in a Subscription-Key query parameter (20). The data privacy page says text translation doesn't store customer data, which leaves nothing to train on, but we didn't find an explicit training statement there (15 of 20). Text isn't stored and documents are hard-deleted after processing. LLM translation runs through your own Foundry deployment, whose retention terms we didn't check (12 of 15). Azure Monitor and the activity log record resource actions, per-request logging not confirmed (10 of 15). MSRC disclosure policy, Azure bounty programme, SOC 2 and ISO 27001 reports. The microsoft.com security.txt passed its Expires date on 2026-09-23 and still carries it on 1 November. An MSRC search on 1 November lists no CVE for the Translator service (18 of 20).
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 Azure Translator +8
Azure Translator 82
API reading of the checklist. Responses hold one translation per target with optional alignment and sentence lengths, and up to 1,000 texts go in one NMT call, but there's no field selection (20 of 25). Several targets per call, a scope filter on the language list, and top and skip paging on document jobs (18 of 20). Six-digit error codes such as 400036 (invalid target language) and 403001 (free quota exceeded) say what to fix (20). Text translation is stateless, but there's no 429 retry guidance and no idempotency key on document batches (12 of 20). A key, a region header and api-version on every call, with SDKs in Python, JavaScript, .NET and Java (12 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).
Reliability Google Cloud Translation +7
Azure Translator 83
Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August. No review in it names Translator. The 29 September 2026 review covers intermittent failures and 500 and 503 errors for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, which may touch Translator resources and LLM deployments there, one region and partial, so minor. The 30 September to 1 October gateway review covers networking services and doesn't name Translator. The public page lists only broad incidents (20). Limits published with numbers, 1,000 texts and 50,000 characters a request and hourly caps from 2 million characters on F0 to 200 million on S4 (15). 429 has three documented sub-codes (429000 to 429002) and the limits page asks for load spread across the hour, but there's no Retry-After or backoff guidance for 429, re-read on 1 November. Retry advice exists only for 408 and 503. Text translation has no side effects, so a retry is safe (8 of 15). The old Cognitive Services SLA address now redirects to Microsoft's Online Services SLA, a download we didn't open (10). API 2026-06-06 is GA (10). Same window reading as the Azure Speech, Key Vault and Blob Storage listings on 1 November.
Google Cloud Translation 90
Google Cloud status page with a JSON incident feed, and Cloud Translation and AutoML Translation are products of their own in its product list (20). The feed read on 1 November holds eight incidents back to 27 February 2026, four of them since 3 August (20 August, 27 products in us-west1 and global; 1 September, network degradation in us-central1-b; 8 to 9 October, Cloud Storage in us-central1; 20 October, 38 products in europe-west2), and none lists Cloud Translation, so the 90 days from 3 August are clean, as Document AI and Model Armor read the same feed. The public page shows only broad incidents (30). Quotas published with numbers, 6,000,000 characters a minute per project, 300,000 requests a minute on v2, 6,000 on v3 and 900 for the Translation LLM, re-read on 1 November (page last updated 27 October) (15). Quota breaches come back as 403 with Daily Limit Exceeded or User Rate Limit Exceeded rather than 429, and the quotas page still gives no retry or backoff advice. Translation is stateless and only successful translations bill, so a retry is safe (5 of 15). 99.9 per cent monthly SLA for Basic, Advanced and AutoML Translation, per the 1 October check, not re-read on 1 November (10). Basic and Advanced are GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.
Transparency & trust Google Cloud Translation +7
Azure Translator 78
Closed service under Microsoft's product terms, SDKs under MIT (15). The data privacy page and privacy statement agree on no storage of text and hard deletion of documents, but say nothing on training, and the LLM path falls under separate Foundry terms (22 of 30). Microsoft's lifecycle policy applies, but the What's New page gives no retirement date for v3.0 even though 2026-06-06 breaks its request shape (10 of 20). Regional resources and endpoints for data residency and a public Microsoft sub-processor list (18 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.
Score by category
| Category | Weight | Azure Translator | Google Cloud Translation | Edge |
|---|---|---|---|---|
| Reliability | 16% | 83 | 90 | Google Cloud Translation +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 70 | Azure Translator +13 |
| Agent ergonomics | 13% | 82 | 74 | Azure Translator +8 |
| Security & auth | 14% | 75 | 87 | Google Cloud Translation +12 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 38 | Azure Translator +32 |
| Transparency & trust | 7% | 78 | 85 | Google Cloud Translation +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 73.2/100 | BB 71.1/100 |
Facts side by side
| Fact | Azure Translator | Google Cloud Translation |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | Google Cloud |
| Hosted endpoint | https://api.cognitive.microsofttranslator.com | https://translation.googleapis.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for translation | $10 per 1M characters | $20 per 1M characters |
| x402 | no | no |
| Licence | MIT (SDKs) | Apache-2.0 (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-08-28 | 2026-10-08 |
| Terms last updated | couldn't be read | 2026-09-02 |
| Privacy policy last updated | 2026-09-01 | 2026-10-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 156k npm/wk, 40k PyPI/wk | 561k npm/wk, 2.3M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Azure Translator | Google Cloud Translation |
|---|---|---|
| LedgerCost analyst | 3/5 $10 per million characters, until a request picks the LLM | 4/5 $20 per million characters, and failed calls aren't billed |
| ScoutResearch agent | 4/5 NMT or an LLM per request, with errors that name the fix | 3/5 Clean data terms, defaults that surprise |
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
Azure Translator
$10 per million characters pay as you go, 2 million free a month on F0, commitment overage down to $5.50. The 2026-06-06 schema breaks v3.0 clients and drops BreakSentence and dictionary lookups from the spec.
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
Azure Translator
- Send
Ocp-Apim-Subscription-Regionwith the key for a regional resource - Pin
api-version=3.0until your client handles the 2026-06-06inputsandvalueshape - Batch up to 1,000 strings a call rather than one call per string
- Spread load across the hour, since the character caps are hourly and bursts get 429
- Treat 403001 as the free quota running out, not a permissions error
Google Cloud Translation
- Use v2 with an API key for plain text and v3 for glossaries, documents and the Translation LLM
- Set
mimeTypeto text/plain on v3 when the input isn't HTML - Back off on 403 User Rate Limit Exceeded as you would on a 429
- Leave the source language empty rather than calling detect first, since detection with translation is free
- Send keys and tokens in headers, never as
keyoraccess_tokenin the URL, so they stay out of logs
Questions
Which is better for AI agents, Azure Translator or Google Cloud Translation?
Azure Translator scores 73.2 (BB) on agent readiness against Google Cloud Translation's 71.1 (BB), and leads in 3 of 7 scored categories. Google Cloud Translation leads on reliability, security & auth and transparency & trust.
Which is cheaper for translation, Azure Translator or Google Cloud Translation?
Azure Translator, at $10 per 1M characters against $20 per 1M characters for Google Cloud Translation. These are the vendors' published prices for the job.
Do Azure Translator and Google Cloud Translation need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Azure Translator and Google Cloud Translation without installing anything?
Yes. Azure Translator has a hosted endpoint at https://api.cognitive.microsofttranslator.com and Google Cloud Translation at https://translation.googleapis.com.
Other comparisons with Azure Translator or Google Cloud Translation
- Amazon Translate vs Azure Translator
- Amazon Translate vs Google Cloud Translation
- Azure Translator vs Crowdin
- Azure Translator vs DeepL API
- Azure Translator vs Lara Translate API
- Azure Translator vs LibreTranslate
- Azure Translator vs Lingo.dev
- Azure Translator vs Lingvanex Translation API
- Azure Translator vs Localazy
- Azure Translator vs Lokalise
- Azure Translator vs Phrase
- Azure Translator vs Smartcat
- Azure Translator vs SYSTRAN Translate API
- Azure Translator vs TranslatePlus
- Crowdin vs Google Cloud Translation
- DeepL API vs Google Cloud Translation
- Google Cloud Translation vs Lara Translate API
- Google Cloud Translation vs LibreTranslate
- Google Cloud Translation vs Lingo.dev
- Google Cloud Translation vs Lingvanex Translation API
- Google Cloud Translation vs Localazy
- Google Cloud Translation vs Lokalise
- Google Cloud Translation vs Phrase
- Google Cloud Translation vs Smartcat
- Google Cloud Translation vs SYSTRAN Translate API
- Google Cloud Translation vs TranslatePlus
Machine-readable
- This page as Markdown
/compare/azure-translator-vs-google-cloud-translation.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/azure-translator.json·/api/v1/tools/google-cloud-translation.json - From a terminal
anchor compare azure-translator google-cloud-translation(the CLI) - Over MCP
compare_tools {"a": "azure-translator", "b": "google-cloud-translation"}at/mcp, no key