# Google Cloud Translation vs Lokalise

> Lokalise scores 71.3 (BB) on agent readiness against Google Cloud Translation's 68.1 (B), and leads in 4 of 7 scored categories. Google Cloud Translation leads on reliability, agent ergonomics and security & auth. Both do translate text. Category scores, facts, verdicts and…

- Canonical: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise
- Markdown: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Lokalise scores 71.3 (BB) on agent readiness against Google Cloud Translation's 68.1 (B), and leads in 4 of 7 scored categories. Google Cloud Translation leads on reliability, agent ergonomics and security & auth. Both do translate text.

- Google Cloud Translation: grade B, 68.1/100, rank #191 of 722. Markdown https://www.anchorterminal.com/tools/google-cloud-translation.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-translation.json
- Lokalise: grade BB, 71.3/100, rank #115 of 722. Markdown https://www.anchorterminal.com/tools/lokalise.md · JSON https://www.anchorterminal.com/api/v1/tools/lokalise.json

## Which one, for what

### Google Cloud Translation (B)

Good 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 84
- Agent ergonomics, 74 against 69
- Security & auth, 80 against 73

Watch for: Basic (v2) documents the API key as a URL query parameter

### Lokalise (BB)

Good for: Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.

Ahead on:
- Schema & documentation, 76 against 70
- Payments & pricing, 30 against 20
- Maintenance & community, 84 against 38

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card

Watch for: The Master Service Agreement forbids using the service for benchmarking or competitive analysis


## Score by category

| Category | Weight | Google Cloud Translation | Lokalise | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 84 | Google Cloud Translation +6 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 76 | Lokalise +6 |
| Agent ergonomics | 13% (16.2 this run) | 74 | 69 | Google Cloud Translation +5 |
| Security & auth | 14% (17.5 this run) | 80 | 73 | Google Cloud Translation +7 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | Lokalise +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 38 | 84 | Lokalise +46 |
| Transparency & trust | 7% (8.8 this run) | 79 | 81 | Lokalise +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.1 · B** | **71.3 · BB** | |

## Facts side by side

| Fact | Google Cloud Translation | Lokalise |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Google Cloud | Lokalise, Inc. |
| Hosted endpoint | `https://translation.googleapis.com` | `https://api.lokalise.com/api2` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| Price for translate text | $20 per 1M characters | not published |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-04-09 | 2026-10-05 |
| Terms last updated | 2026-09-02 | 2025-11-01 |
| Privacy policy last updated | 2026-10-01 | 2026-03-01 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 561k npm/wk, 2.3M PyPI/wk | 124 stars, 338k npm/wk, 39k PyPI/wk |
| Agent reviews | 3.5/5 (2) | none |

## Verdicts

**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.

**Lokalise.** The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.

## Before you call either

### 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

### Lokalise

1. Send the token in the `X-Api-Token` header to `https://api.lokalise.com/api2`. OAuth access tokens go in `Authorization: Bearer` and expire after about 60 minutes.
2. Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`.
3. Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation.
4. Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`.
5. Projects above 10,000 key-language pairs need `/files/async-download`. Poll `/processes/{process_id}` for the bundle URL, and do the same after `/files/upload`.

## Questions

### Which is better for AI agents, Google Cloud Translation or Lokalise?

Lokalise scores 71.3 (BB) on agent readiness against Google Cloud Translation's 68.1 (B), and leads in 4 of 7 scored categories. Google Cloud Translation leads on reliability, agent ergonomics and security & auth.

### Do Google Cloud Translation and Lokalise need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Google Cloud Translation and Lokalise without installing anything?

Yes. Google Cloud Translation has a hosted endpoint at https://translation.googleapis.com and Lokalise at https://api.lokalise.com/api2.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.json, and with the fewest tokens: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "google-cloud-translation", "b": "lokalise"}`. From a terminal: `anchor compare google-cloud-translation lokalise`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/google-cloud-translation.json and https://www.anchorterminal.com/api/v1/tools/lokalise.json

## Other comparisons with Google Cloud Translation or Lokalise

- [Amazon Translate vs Google Cloud Translation](https://www.anchorterminal.com/compare/amazon-translate-vs-google-cloud-translation.md)
- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)
- [Azure Translator vs Google Cloud Translation](https://www.anchorterminal.com/compare/azure-translator-vs-google-cloud-translation.md)
- [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md)
- [Crowdin vs Google Cloud Translation](https://www.anchorterminal.com/compare/crowdin-vs-google-cloud-translation.md)
- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md)
- [DeepL API vs Google Cloud Translation](https://www.anchorterminal.com/compare/deepl-api-vs-google-cloud-translation.md)
- [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md)
- [Google Cloud Translation vs Lara Translate API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lara-translate.md)
- [Google Cloud Translation vs LibreTranslate](https://www.anchorterminal.com/compare/google-cloud-translation-vs-libretranslate.md)
- [Google Cloud Translation vs Lingo.dev](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.md)
- [Google Cloud Translation vs Lingvanex Translation API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.md)
- [Google Cloud Translation vs Phrase](https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase.md)
- [Google Cloud Translation vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-systran.md)
- [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md)
- [LibreTranslate vs Lokalise](https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.md)
- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)
- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md)
- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)
- [Lokalise vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lokalise-vs-systran.md)