Translation & Localization
Google Cloud Translation
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Google Cloud EMEA Limited · cloud.google.com
Compare with DeepL Pro & API → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Google Cloud Translation at a glance
- Vendor
- Google Cloud EMEA Limited
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates Google Cloud Translation 2.5/5, the mean of 6 judges. Google Cloud Translation scores as a translation engine you build on, not a platform. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Google Cloud Translation alternatives, European ones first →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Google Cloud Translation scores as a translation engine you build on, not a platform. Machine translation scored 7 with no spread: 189 published languages, NMT, Translation LLM and adaptive models, glossaries in TSV, CSV or TMX applied during translation, and document translation that preserves layout for Office and PDF. Pricing transparency scored 8 with no spread — $20 per million characters for NMT, the first 500,000 characters per month free, $300 in new-customer credits, "no automatic charges, no commitment." Workflow and review and integrations and formats both scored 4 with no spread: a REST API and Office/PDF formats are documented; we found no public information on review stages, translator roles, or CMS, Git and shop connectors. Splits are narrow: content confidentiality 6-7 (the localization manager found no stated encryption in transit and at rest), portability and exit 3-4 (no public information on translation memory export or data return at contract end), and sovereignty 4-5 — an Irish contracting entity and Advanced API regional endpoints against global endpoints where data "cannot be configured to remain in a specific region for processing."
Speaks for it
- Machine translation scored 7 with no spread — 189 published languages, NMT, Translation LLM and adaptive translation from your own small datasets, with glossaries applied during translation.
- Pricing transparency scored 8 with no spread: per-character prices by model, $0.08 per page document translation, the first 500,000 characters per month free, $300 in new-customer credits, 'no automatic charges, no commitment.'
- Content confidentiality ran 6-7 on unusually concrete statements: sent text is held briefly in-memory only, not stored on servers, not used to train Google's translation features, and not shared with third parties.
- Document translation preserves the original formatting and layout for Google Workspace, Microsoft Office and PDF files, including scanned PDFs.
- Google Ireland Limited in Dublin is the named service provider (register number 368047) and the Cloud Data Processing Addendum is published and incorporated into the agreement.
Held against it
- Workflow and review scored 4 with no spread: we found no public information on review stages, automated QA checks, translator roles or an in-context editor, with human review named only on Translation Hub pricing lines.
- Integrations and formats scored 4 with no spread: we found no public information on CMS, shop, Git or CI connectors, webhooks, or software formats such as XLIFF, PO or JSON, and the documented document inputs are DOC, DOCX, PDF, PPT, PPTX, XLS and XLSX.
- Portability and exit ran 3-4: we found no public information on translation memory export, complete project export, or return and deletion of data when the contract ends.
- Sovereignty ran 4-5: global endpoints mean data 'cannot be configured to remain in a specific region for processing', only the Advanced API offers regionalized endpoints, the parent is Google LLC of California, and we found no public information on subprocessor locations.
- Glossary version control is explicitly not supported, and we found no public information on ISO 27001 or SOC 2 certification with its scope, audit logs or single sign-on.
Best for
- You have engineers to build on the documented REST API, client libraries and Cloud Storage batch jobs, and you want the translation engine rather than a managed platform.
- You translate high volumes of plain text or Office and PDF documents and want to compute the bill in advance from public per-character and per-page prices.
- You need broad coverage — 189 languages — with terminology control through glossaries and, optionally, AutoML custom models on 53 language pairs to and from English.
- Your compliance review weighs written commitments: in-memory-only processing, no training use, no third-party sharing, under a published Cloud Data Processing Addendum.
Avoid if
- You need a managed review process — configurable stages, roles per language, in-context editing — rather than building the workflow yourself.
- You have no developers on staff and need out-of-the-box connectors to your shop, CMS or Git repositories.
- You must keep processing in a specific region on every endpoint: the terms state global endpoints mean data 'cannot be configured to remain in a specific region for processing', with regionalized endpoints on the Advanced API only.
- You plan to resell the service: the terms state resale of the Cloud Translation API service is not permitted.
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3.5 of 5 |
| Translation memory, terminology & review workflow | 2 of 5 |
| Integrations, file formats & developer tools | 2 of 5 |
| Confidentiality of translated content | 3.5 of 5 |
| Data export, portability & self-hosting | 2 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 4 of 5 |
Machine translation & AI quality
Show reasoningHide reasoning
How this is scored
What the machine translation does and how well it is controlled: the languages and language pairs covered, the engine (own neural or LLM model, or a choice of third-party engines such as DeepL, Google, Microsoft or an LLM), glossaries and formality applied during translation, document translation that keeps the layout (Word, PowerPoint, PDF, InDesign), custom or adaptive models trained on the customer's own translations, automatic quality estimation or scoring, and published evaluations of translation quality.
0 — No machine translation of any kind, and no way to connect an engine.
3 — Machine translation is offered or one engine can be connected; languages, glossary use and quality controls are basic or not described.
5 — Machine translation for the major European and world languages with the list published, glossaries applied during translation, a formality or tone setting, document translation that keeps formatting for common office formats, and either an own engine or a choice of several named engines.
8 — Custom or adaptive models that learn from the customer's translation memory or corrections, automatic quality estimation per segment with a threshold that routes weak segments to human review, LLM-based translation with style guides and context, engine selection per language pair stated, and a published quality evaluation with its method.
10 — Translation quality that an organisation can measure and steer: evaluations against named benchmarks or blind human review published with their method, quality estimation calibrated and explained, custom models with their training data and isolation documented, and every machine-translated segment traceable to the engine, model version and glossary that produced it.
The Localization Manager
Three engines to choose from — Google's neural model, a translation large language model with contextual glossary support, and adaptive translation that learns from our own small datasets without training — covering 189 published languages, plus AutoML custom models for 53 language pairs to and from English, and document translation that preserves the layout for Word, PowerPoint and PDF. Glossaries are applied during translation with case handling, term-set types and TMX import, which is what my termbase needs. We found no public information on a published quality evaluation with its method, and quality prediction appears only as a Translation Hub tier feature without routing of weak segments into review. 1 3 4 5
The App Developer
This is the engine itself and it is a serious one: 189 languages with published lists, glossaries in TSV, CSV and TMX applied during translation, document translation that preserves formatting for Word, PowerPoint, PDF and Google Workspace, plus Adaptive Translation that works from my own small datasets without a training job and AutoML custom models on 53 language pairs to English. What keeps it off the top band: I found no published quality evaluation with its method, no formality or tone setting, and quality prediction scores appear only in the Translation Hub advanced tier rather than as per-segment routing of weak output to human review. 1 3 4 5
The In-House Document Translator
For my desk this covers the essentials: 189 languages with any-to-any pairs, glossaries enforced during translation (TSV, CSV or TMX import, with case handling and fine-grained permissions), and document translation that preserves the original formatting and layout for Word, PowerPoint and PDF, including scanned PDFs — though the documentation warns that content inside text boxes is not translated. Custom AutoML models and LLM-based Adaptive Translation that works from our own datasets are available, but custom models cover only 53 language pairs via English, and we found no published quality evaluation with its method and no formality or tone setting. 1 3 4 5
The Data Protection Officer
The engine side is strong: 189 languages with published language lists, glossaries in TSV, CSV or TMX applied during translation with case handling, an own NMT plus a Gemini-based Translation LLM and adaptive translation that uses the customer's own small datasets, custom AutoML models, and document translation for Word, PowerPoint, PDF and Excel that preserves the original layout. We found no published quality evaluation with its method, no per-segment quality estimation that routes weak output to review, and no public information on a formality or tone setting; machine translation quality prediction scores are only named on the Translation Hub pricing line. 1 3 4 5
The E-Commerce Marketer
Adaptive translation that works from my own small datasets without training, an LLM model alongside the NMT one, glossaries in TSV, CSV or TMX with case handling, and document translation that keeps the layout for Word, PowerPoint and PDF — that covers my six shop languages easily, with 189 languages on the published list. What I did not find is a formality or tone setting, published quality evaluations, or quality scoring outside the enterprise Translation Hub tier. 1 3 4 5
The Skeptic
189 languages with a published list, glossaries applied at request time from TSV, CSV or TMX files, document translation that preserves layout for Office and PDF, AutoML custom models and an LLM-based adaptive mode that learns from your own datasets, plus quality prediction scores in the Translation Hub tiers. We found no public information on a published quality evaluation with its method, nor a stated rule that routes weak segments to human review, so it stays below the top band. 1 3 4 5
Translation memory, terminology & review workflow
Show reasoningHide reasoning
How this is scored
How translation is managed as an ongoing process: translation memory with fuzzy matches, a termbase or glossary managed centrally, style guides, review and approval stages, automated QA checks (placeholders, tags, length, terminology, punctuation), an in-context or visual editor, screenshots and context for translators, tasks and deadlines, roles per language, and ordering or inviting human translators and agencies inside the product.
0 — No management of translations at all; text goes in and comes out with nothing stored or reviewed.
3 — Translations can be edited or a glossary kept; translation memory, review stages and QA checks are basic or not described.
5 — A translation memory reused across projects, a central glossary, at least one review or approval stage, automated QA checks for placeholders and terminology, comments and screenshots for context, and roles that limit translators to their languages.
8 — Configurable multi-step workflows with automation rules, an in-context or visual editor for apps or websites, QA checks configurable per project with blocking rules, style guides applied by the AI, translation memory and termbase shared across projects with penalties and priorities, vendor or agency management with ordering inside the product, and progress and cost reporting per language.
10 — A translation process an enterprise runs on: workflows per content type with conditional routing on quality scores, linguistic quality assessment with a named framework (MQM or similar), termbase with approval workflow and forbidden terms, full revision history per segment, and productivity and quality metrics per translator and vendor.
The Localization Manager
Glossaries are managed centrally with create, list, get, update and delete operations, and the separately priced Translation Hub advertises translation memory, human review and machine translation quality prediction scores in its advanced tier — but glossary version control is explicitly not supported. We found no public information on automated checks for placeholders and tags, per-language reviewer roles, an in-context editor, or inviting agencies and freelancers into the product, so I could not run a fourteen-language release review on it. A terminology store plus one review stage for documents, not a managed process. 1 3
The App Developer
The management layer is thin for someone living in JSON and xcstrings: glossaries get real central handling — create, update, delete, entry-level operations, IAM permissions, multiple glossaries per project — and Translation Hub's advanced tier lists translation memory, human review and quality prediction scores. But the pages state plainly that glossaries have no version control, and I found no public information on automated QA checks for placeholders or tags, comments and screenshots, an in-context editor, review stages, or roles that limit translators to their languages. 1 3 6
The In-House Document Translator
The glossary side is genuinely manageable — glossaries and their entries can be created, updated, listed and deleted through the API, though without version control — and the managed Translation Hub adds translation memory, human review and machine translation quality prediction scores on its advanced tier. Beyond those one-line feature mentions we found no description of configurable review stages, automated checks for placeholders or terminology, comments, or translator roles per language. As someone who wants documents back rather than a project platform that suits me, but the review machinery is thin on the documented pages. 1 3
The Data Protection Officer
This is a translation engine rather than a managed workflow: glossaries are kept centrally with create, update, list and delete over the API, multiple glossaries per project, and Translation Hub's pricing line names translation memory, human review and quality-prediction scores. We found no public information on review or approval stages, automated QA checks, roles per language, an in-context editor, or inviting translators and agencies. 1 3
The E-Commerce Marketer
Glossaries can be created, updated and deleted entry by entry, which is exactly how I would force the right product name, and the Translation Hub paid tier lists translation memory, human review and quality prediction scores. But nothing on the captured pages describes review stages, automated checks, an in-context editor or translator roles, and glossary version control is explicitly not supported. 1 3
The Skeptic
The Translation Hub tiers are named with translation memory, human review and machine translation quality prediction, and glossaries get full create-read-update-delete through the API. We found no public information on QA checks, review stages, roles per language, in-context editing or inviting translators, so what is documented reads as a review flag on a machine translation pipeline rather than a managed process. 1 3
Integrations, file formats & developer tools
Show reasoningHide reasoning
How this is scored
How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
0 — No documented way to get content in or out except typing or pasting by hand.
3 — File upload and download or a basic API; formats, repository sync and connectors are basic or not described.
5 — A documented REST API, a list of supported file formats covering the common software and document formats, sync with at least one Git host or CI, and connectors or plugins for several named CMS, shop or design tools.
8 — A CLI and SDKs for named platforms, over-the-air updates for mobile or web apps, Git sync with branching, webhooks, connectors for the main CMS, shop, design and support tools, office or browser add-ins, a public status page, and API limits documented.
10 — Integration that scales across an organisation: an API covering every function of the product with versioning and SDKs, an app or connector framework third parties build on, continuous localization in CI with pull requests opened automatically, and every connector documented with its limits and the fields it syncs.
The Localization Manager
A documented REST API with client libraries, batch jobs reading from and writing to Cloud Storage, published quotas and limits, and document translation for Word, PowerPoint, Excel and PDF give my engineers everything for custom pipelines. We found no public information on the software localization formats I ship in — XLIFF, PO, JSON, iOS and Android strings — nor on Git or CI synchronisation, CMS, shop or design connectors, or over-the-air delivery. A strong API to build on, but nothing that plugs into our repositories and CMS. 2 4
The App Developer
The API surface is solid — documented REST endpoints including full glossary operations, client libraries, published quotas and limits, batch jobs reading from and writing to Cloud Storage buckets, release notes and troubleshooting docs. But for an app developer the gap is glaring: the documented document formats are DOC/DOCX, PDF, PPT/PPTX and XLS/XLSX only, and I found no public information on JSON, iOS strings or xcstrings, Android XML, XLIFF or PO handling, nor on a CLI, Git repository sync with pull requests, over-the-air updates, webhooks or CMS connectors. 2 3 4
The In-House Document Translator
A fully documented REST API with client libraries for both editions, published quotas and limits, batch jobs of up to 100 files, and input and output through Cloud Storage; the document formats are listed precisely, from DOC and DOCX through PDF, PPT and PPTX to XLS and XLSX. We found no documented sync with Git repositories or CI pipelines, no connectors or plugins for CMS, shop or design tools, and no software formats such as XLIFF, PO or JSON for the content itself. 2 3 4
The Data Protection Officer
There is a documented REST API with client libraries for both editions, glossary endpoints, document formats from DOC to XLSX, batch requests reading from and writing to the customer's Cloud Storage, and documented quotas and limits. We found no public information on Git repository sync, CI pipelines, CMS or design-tool connectors, webhooks, a CLI or over-the-air delivery on the captured pages. 2 3 4
The E-Commerce Marketer
There is a documented REST API with client libraries, published quotas, and document translation in and out of Cloud Storage for Word, PowerPoint, Excel and PDF files. For me the gap is decisive: on the captured pages I found no Shopify or other shop connector, no Git sync, no website JavaScript snippet and no software formats like XLIFF or JSON, so with no developer on staff I could not wire this to my store myself. 2 4
The Skeptic
A documented REST API with client libraries, published quotas and limits, batch jobs reading and writing through Cloud Storage, and document formats from DOC and DOCX to PDF, PPT, PPTX, XLS and XLSX. We found no public information on Git or CI sync, CMS or design connectors, webhooks, or software localization formats such as XLIFF or JSON. 2 3 4
Confidentiality of translated content
Show reasoningHide reasoning
How this is scored
What happens to the text a customer translates: whether source and target texts are stored and for how long, deletion after translation, whether customer content is used to train the vendor's or a third party's models, which machine translation and LLM providers a TMS sends text to and whether that can be restricted or switched off, encryption in transit and at rest, single sign-on, roles and audit logs, and certifications (ISO 27001, SOC 2) with their scope. Where the text is processed is scored under sovereignty.
0 — Customer texts are stored indefinitely and used for the vendor's own purposes, or no statement on data handling exists at all.
3 — The product is described as secure or GDPR-compliant and a privacy policy exists; retention of translated texts, model training and third-party engines are basic or not described.
5 — A documented statement that customer texts are not used to train models, retention or deletion of translated texts stated, the third-party engines or LLM providers named, encryption in transit and at rest, single sign-on on a business tier, and a data processing agreement offered.
8 — Texts deleted immediately after translation or after a retention period the customer sets, third-party AI processing switchable per project or account, zero-retention terms with the named LLM providers, audit logs, granular roles, ISO 27001 or SOC 2 certification stated with its scope, and a private or dedicated deployment option.
10 — Confidentiality that can be verified: an on-premise or customer-controlled deployment, customer-managed encryption keys, every subprocessor that sees content listed with its role, independent audit reports available, and every data flow of a translation request documented end to end.
The Localization Manager
The data usage statements are unusually firm: sent text is held briefly in-memory only and not stored on servers, is not used to train Google's translation features, is never shared with third parties or made public, Google claims no ownership, and the service complies with the Cloud Data Processing Addendum, with glossaries encrypted and guarded by fine-grained IAM permissions. We found no public information on ISO 27001 or SOC 2 certification with its scope, audit logs, or single sign-on, and encryption in transit and at rest is not stated for translated content. Contractually clean, but nothing on the pages lets me verify it independently. 6 8
The App Developer
The data-usage documentation is unusually concrete: sent text is held briefly in-memory to perform the translation and is not stored on servers, Google states it does not use content to train or improve its translation features, will not share it with third parties or make it public, claims no ownership, and keeps glossaries encrypted under fine-grained IAM in my own project, with a published Cloud Data Processing Addendum. What is missing for the top band: I found no public information on audit logs, certification scope, or a dedicated deployment option in the captured pages. 6 8
The In-House Document Translator
This is the written promise I need before sending a draft contract out: Google states it does not use any sent content except to provide the service and does not use it to train or improve its translation features, that text is held briefly in-memory only and is not stored on servers, and that content is neither shared with third parties nor made public. Glossaries are encrypted with fine-grained access permissions, and a Cloud Data Processing Addendum with GDPR commitments is incorporated into the agreement. We found no statement on audit logs or ISO 27001/SOC 2 certification for this product, which keeps it a notch below the top. 6 8
The Data Protection Officer
The data-usage statements are unusually specific and are what I would put before the board: sent text is held briefly in-memory to perform the translation and return the result, is not used to train or improve translation features, is not shared with any third party or made public, no ownership is claimed in the content, glossaries are encrypted under fine-grained IAM permissions, and the Cloud Data Processing Addendum applies. The only AI provider in the chain is Google's own Gemini, so there is no third-party engine chain to restrict; we found no public information on audit logs, single sign-on, certifications with their scope, customer-managed keys or a dedicated deployment option. 1 6 8
The E-Commerce Marketer
The data usage page states plainly that text is held briefly in memory only and not stored, is not used to train Google's translation features, is not shared with any third party, and that Google claims no ownership in my content, while glossaries are encrypted with fine-grained access control under the Cloud Data Processing Addendum. I found no statement of certifications, audit logs or customer-set retention on the pages I read, and the Gemini-based service carries an 18-and-over restriction. 6 8 1
The Skeptic
The data-usage statements are unusually concrete: text is 'held briefly in-memory' and not stored on servers, is not used to train Google's translation features, is not shared with third parties, and Google claims no ownership of it; glossaries are encrypted in your own Cloud project behind fine-grained IAM, under a published Cloud Data Processing Addendum. We found no public information on ISO 27001 or SOC 2 certification with its scope, audit logs, or a dedicated deployment option, which keeps this below the top band. 6 8
Data export, portability & self-hosting
Show reasoningHide reasoning
How this is scored
Whether translation assets stay the customer's and can leave with them: export of translation memory and termbase in open formats (TMX, TBX, XLIFF, CSV), export of all projects and files, import from another TMS, an API that can read every asset, the return or deletion of data on termination, open-source code and a self-hosted or on-premise edition.
0 — Translations cannot be exported; they exist only in the vendor's interface or engine.
3 — Translated files can be downloaded; export of translation memory and glossary, import and termination terms are basic or not described.
5 — Translation memory exportable as TMX and glossary as TBX or CSV, all project files downloadable, import of translation memory and glossaries from another tool, and an API that reads translations and keys.
8 — Complete export of every asset (memory, termbase, files, comments, history) in open formats, a documented migration path from named competitors, the data returned or deleted on termination under stated terms, and a self-hosted or on-premise edition with its own documentation.
10 — The customer owns the assets end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete export another tool can import without loss, and the deletion of every copy on termination documented.
The Localization Manager
My terminology can leave: glossaries import as TSV, CSV or TMX from my own Cloud Storage bucket, every entry can be listed back through the API, and translated documents are returned to me or written to a bucket. We found no public information on exporting a translation memory as TMX, a complete project export, a migration path from another TMS, data return or deletion on termination, or a self-hosted edition. Assets are recoverable one by one, not as a documented exit package. 3 4
The App Developer
The raw assets stay mine: translated documents land in my own Cloud Storage bucket, glossaries import from TSV, CSV or TMX and every entry is readable through the API, and Google claims no ownership in transmitted content. But there is no documented translation memory export, no complete project export in open formats, no migration path from another tool, and I found no public information on a self-hosted or open-source edition or on termination terms. 3 4 6
The In-House Document Translator
Google claims no ownership in the content, translated documents come back through the API or into my own Cloud Storage bucket, and glossaries can be loaded and replaced from TSV, CSV or TMX files with entries listable via the API. We found no documented export of translation memory in an open format, no migration path from another tool, and no stated terms for returning or deleting data when a contract ends. 3 4 6
The Data Protection Officer
Glossaries import in TSV, CSV or TMX and every entry can be listed and retrieved through the API, and document translation outputs land in the customer's own Cloud Storage bucket. We found no public information on translation-memory export formats, a documented migration path, return or deletion of data on termination, or a self-hosted edition. 3 4
The E-Commerce Marketer
Translated documents come back as downloadable files, and glossaries can be imported in the open TMX, CSV or TSV formats. I found no documented export of translation memory or glossaries, no migration path from another tool, and nothing about what happens to my content on termination. 3 4
The Skeptic
Glossaries import as TSV, CSV or TMX 1.4, their entries can be listed back through the API, and the glossary input file lives in your own Cloud Storage bucket. We found no public information on translation memory export, a complete project export, or the return and deletion of data when the contract ends — the assets and terms that decide what leaving costs. 3 6
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where texts are translated, stored and processed, and who the subprocessors are (hosting, machine translation engines, LLM providers, CDN for over-the-air delivery, support and payment tools). Independently sourced by the sovereignty pipeline; translated texts often hold personal data and trade secrets, so the whole chain counts, including the engines a TMS calls. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (machine translation or LLM providers, CDN, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the engines and LLM providers, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every text on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, engine and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Localization Manager
Google Ireland Limited in Dublin is the named service provider with an Irish registration and VAT number, the Cloud Data Processing Addendum is published with GDPR commitments described, and the Advanced API offers regionalized endpoints configurable for data location — though the Basic endpoints are explicitly global and cannot be region-locked. The parent company is in the USA, and we found no public information on hosting regions, subprocessors with their locations, or security certifications. Enough EU entity and contractual footing for procurement, not enough to show my data protection officer the full chain. 6 8 10
The App Developer
The contracting side looks European: Google Ireland Limited is registered in Dublin with a published register number and VAT ID, and a Cloud Data Processing Addendum is published and incorporated into the agreement. But the captured pages do not confirm where texts are hosted — global endpoints mean data "cannot be configured to remain in a specific region for processing", with only the Advanced API offering regionalized endpoints for data location — and although a subprocessor list page was captured, it yields no named subprocessors here, while the parent is Google LLC in California. 6 8 9 10
The In-House Document Translator
There is an Irish entity with a named managing board in the legal notice, a published Cloud Data Processing Addendum with GDPR commitments, and the Advanced API offers regionalized endpoints configurable for data location under the AI/ML Data Location terms. However, the default global endpoints cannot be configured to keep data in a specific region, the parent company sits in California, and we found no published subprocessor locations or named hosting infrastructure for this service. 6 8 10
The Data Protection Officer
EU customers contract through Google Cloud EMEA Limited in Dublin, Google Ireland Limited appears as service provider in the legal notice with an Irish registration number, and a Cloud Data Processing Addendum is published and incorporated into the agreement. Against that, the Basic API and the default endpoints are global and data cannot be configured to remain in a specific region — only the Advanced API offers regionalized endpoints configurable for data location — the parent is Google LLC in California, and we found no public information on hosting locations or the subprocessor list from the captured facts. 6 8 10
The E-Commerce Marketer
The legal notice names Google Ireland Limited in Dublin with an Irish register number and VAT ID, and a published Cloud Data Processing Addendum covers the service. The Advanced API can pin data location with regional endpoints, but global endpoints process data with no region guarantee, the parent is Google LLC in California, and I found nothing on the captured pages about the hosting infrastructure or where the engines and subprocessors sit. 6 8 10
The Skeptic
A published data processing addendum and an Irish contracting and service entity are evidenced, and the Advanced API offers regionalized endpoints configurable for data location. But the Basic and AutoML endpoints are global, where the terms say 'data cannot be configured to remain in a specific region for processing', the parent is Google LLC of California, and we found no subprocessor locations among the captured facts — so sovereignty is partial and depends on choosing the right endpoint. 6 8 10
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by characters, words, keys, hosted words or seats, what happens when the volume exceeds the tier, the number of users, projects and languages included, which features (machine translation volume, AI credits, SSO, integrations, API access) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with volume, seats or features is unclear.
5 — Tiers are public with their price per volume band and main inclusions, but at least one commonly needed piece (overage, extra seats, machine translation or AI volume, SSO, connectors) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (characters, words, keys, seats), overage handling stated, add-ons and AI credits priced, the self-hosted edition's cost or licence stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given volume, seat count and feature set, with every add-on, setup, support and overage fee and the cancellation and data-return terms published.
The Localization Manager
From the public pages alone I can compute the annual bill: $20 per million characters for the neural model with the first 500,000 characters per month free, $10 per million for the LLM, $25 per million for adaptive, custom translation at $80 per million with volume bands down to $30, document translation at $0.08 or $0.25 per page, Translation Hub at $0.15 or $0.50 per page per target language, custom model training at $45 per hour capped at $300 per job, optional one- and three-year commitment prices, and $300 in free credits with no commitment. We found no public information on VAT treatment, and no self-hosted edition to price. This is the most computable price list I have graded. 1 2 7
The App Developer
I can genuinely compute the annual bill from public pages: text translation at $20 per million characters above a free 500,000 per month, document translation at $0.08 per page and $0.25 per page, Translation Hub at $0.15 and $0.50 per page per target language, adaptive and LLM translation at $25 and $10 per million characters, custom-model volume bands down to $30.00, training at $45 per hour capped at $300 per job, one- and three-year committed-use prices, $300 in new-customer credits, and "No automatic charges, no commitment." What keeps it from the top: VAT treatment beyond the USD note is not stated, and cancellation and data-return terms are not on the pricing pages. 1 2 7
The In-House Document Translator
Every model is priced publicly by unit: $20 per million characters for the general model with the first 500,000 characters per month free, $10 per million characters for the LLM model, $25 per million characters for adaptive, volume bands for custom models descending to $30, $0.08 per page and $0.25 per page for document translation, $0.15 and $0.50 per page per target language on the managed Hub, plus one- and three-year discount plans and $300 in new-customer credits under the stated terms "no automatic charges, no commitment". VAT treatment is not stated, and we found no self-hosted edition or its cost on the captured pages. 1 2 7
The Data Protection Officer
Usage pricing is published to the cent with its scaling rules: first 500,000 characters per month free then $20 per million characters for NMT (with one- and three-year rates of $18.00 and $16.00), $10 per million input and output characters for the Translation LLM, $25 per million for adaptive translation, document translation from $0.08 per page, Translation Hub from $0.15 per page per target language, custom-model training at $45 per hour capped at $300 per job, volume bands for custom translation down to $30.00, $300 in free credits for new customers, and a stated basis of no automatic charges and no commitment. What remains unstated is VAT treatment and any support or setup costs. 1 2 7
The E-Commerce Marketer
I can genuinely compute a monthly bill from the public pages: the first 500,000 characters are free, then $20 per million characters for the NMT model, $10 per million characters in and out for the LLM model, $25 per million characters for adaptive translation, and $0.08 per page for document translation, plus $300 in free credits for new customers and no automatic charges. What stayed unclear is VAT treatment, the price beyond the top published character bands, and what the one- and three-year discounted plans commit me to. 1 7 2
The Skeptic
Per-character prices by model are public — $20 per million for NMT, $10 for the LLM, $25 for adaptive, $80 for custom with volume bands down to $30 — alongside per-page document and Translation Hub prices, $45-per-hour custom training capped at $300 per job, 500,000 free characters a month, $300 in new-customer credits, and one- and three-year committed discounts. A buyer can compute an annual bill from public pages; we found no public information on VAT treatment or support fees, so it stops just short of full computability. 1 2 7
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Google Cloud Translation
Is Google Cloud Translation European?
No. whats-best.ai classifies Google Cloud Translation as Rest of world.
Where does Google Cloud Translation store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Google Cloud Translation have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to Google Cloud Translation?
As of 2 Nov 2026, the panel rates SimpleLocalize (3.5/5), LILT (3.5/5) and Phrase Localization Platform (3.5/5) highest among the other 12 Translation & Localization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is SimpleLocalize (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Google Cloud Translation alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Legal entity, Hosting location, Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 4 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage cloud.google.com Checked 1 Nov 2026 Details →
- 2 Documentation docs.cloud.google.com Checked 1 Nov 2026 Details →
- 3 Documentation (glossaries) docs.cloud.google.com Checked 1 Nov 2026 Details →
- 4 Documentation (document translation) docs.cloud.google.com Checked 1 Nov 2026 Details →
- 5 Documentation (supported languages) docs.cloud.google.com Checked 1 Nov 2026 Details →
- 6 Documentation (data usage) docs.cloud.google.com Checked 1 Nov 2026 Details →
- 7 Pricing page cloud.google.com Checked 1 Nov 2026 Details →
- 8 Data processing agreement (dpa) cloud.google.com Checked 1 Nov 2026 Details →
- 9 Subprocessor list cloud.google.com Checked 1 Nov 2026 Details →
- 10 Legal notice www.google.de Checked 1 Nov 2026 Details →
- 11 Security / trust page (compliance) cloud.google.com Checked 1 Nov 2026 Details →
- 12 Privacy policy — found from the homepage cloud.google.com Checked 1 Nov 2026 Details →
- 13 Self-hosting / on-premises installation docs — found from the homepage cloud.google.com Checked 1 Nov 2026 Details →