Get an audit

Head to head · Translate text · October 2026 research run

Azure Translator vs Google Cloud Translation

Azure Translator has a score of 72.2 (BB) against Google Cloud Translation's 68.2 (B). Both do translate text. The largest gap is maintenance & community, 32 points.

Azure TranslatorMicrosoft Azure · HTTP API BB72.2/100#73 of 452 Google Cloud TranslationGoogle Cloud · HTTP API B68.2/100#130 of 452

Which one, for what

Pick Azure Translator for

  • schema & documentation (+13)
  • agent ergonomics (+8)
  • maintenance & community (+32)

Pick Google Cloud Translation for

  • reliability (+7)
  • security & auth (+5)

Score by category

CategoryWeight this runAzure TranslatorGoogle Cloud TranslationEdge
Reliability16%208390Google Cloud Translation +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28370Azure Translator +13
Agent ergonomics13%16.28274Azure Translator +8
Security & auth14%17.57580Google Cloud Translation +5
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87038Azure Translator +32
Transparency & trust7%8.88080even
Negative events≤1500
Total72.2 · BB68.2 · B

Facts side by side

FactAzure TranslatorGoogle Cloud Translation
KindHTTP APIHTTP API
VendorMicrosoft AzureGoogle Cloud
Hosted endpointhttps://api.cognitive.microsofttranslator.comhttps://translation.googleapis.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs)Apache-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.txtnono
MCP registrynot listednot listed
Last release2026-06-062026-04-09
Popularity156k npm/wk, 40k PyPI/wk561k npm/wk, 2.3M PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

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. Basic (v2) documents the API key as a URL query parameter.

Before you call either

Azure Translator

  1. Send Ocp-Apim-Subscription-Region with the key for a regional resource
  2. Pin api-version=3.0 until your client handles the 2026-06-06 inputs and value shape
  3. Batch up to 1,000 strings a call rather than one call per string
  4. Spread load across the hour, since the character caps are hourly and bursts get 429
  5. Treat 403001 as the free quota running out, not a permissions error

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 Azure Translator 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.

Get an auditSee a sample report