SaaS · archived
Google Cloud Translation Hub, the self-service portal for translating large volumes of documents into many languages, was deprecated on 30 June 2025 and shut down on 20 September 2026; the underlying document-translation capability lives on in the Cloud Translation API (Advanced / v3), which Translation Hub users must move to
left 20 Sept 2026
Quick answers
- Is it true that Google Cloud Translation Hub was shut down on 20 September 2026 — the self-service document translation product is gone?
- Yes — and the date has already passed (20 Sept 2026). Google Cloud **Translation Hub** — the managed, self-service portal that let organisations upload and translate large volumes of documents across many languages without writing code — was **deprecated on 30 June 2025** and **shut down on 20 September 2026**.
- When did it take effect?
- 20 Sept 2026 (already passed). Verified against the vendor's own announcement.
- What should I use instead?
- Google's ongoing document-translation offering is the **Cloud Translation API (Advanced, v3)**, which includes document-translation and glossary support; that is the path off Translation Hub for teams that still need programmatic or batch document translation.
What this means for you
Google Cloud **Translation Hub** — the managed, self-service portal that let organisations upload and translate large volumes of documents across many languages without writing code — was **deprecated on 30 June 2025** and **shut down on 20 September 2026**. This is a whole product being removed, not a version or feature change: after the shutdown date the Translation Hub portal, its projects, and its self-service document-translation workflow are no longer available. Anyone whose translation operation depended on the Hub UI (upload a document, pick target languages, download the translations, manage glossaries and translation memory through the portal) lost that turnkey surface. The translation *capability* did not disappear — Google's Cloud Translation API still does document translation — but it moves from a no-code portal to an API you integrate, which is a real change in who can operate it and how.
Where to go
Google's ongoing document-translation offering is the **Cloud Translation API (Advanced, v3)**, which includes document-translation and glossary support; that is the path off Translation Hub for teams that still need programmatic or batch document translation. The practical difference is operational: Translation Hub was a self-service portal usable without engineering, whereas Cloud Translation API is an API you call from code or a pipeline, so a non-developer translation workflow needs either an internal integration or a third-party document-translation tool built on the API. If you had custom-trained models in Translation Hub, confirm their availability through Cloud Translation API v3 / AutoML Translation before assuming parity. Because the product is already shut down, this is now a recovery/rebuild task rather than a planned migration — export or re-source anything that lived only inside the Hub. (Sourcing note below: the exact first-party migration guidance could not be captured from the primary page, which does not render for automated fetchers; treat the replacement path as the documented direction, and verify specifics against current Cloud Translation docs.)
- Cloud Translation API (Advanced / v3) — Google's ongoing document-translation API, with glossary and custom-model support
Google Cloud Translation Hub — the self-service portal for translating large volumes of documents into many languages — was deprecated on 30 June 2025 and shut down on 20 September 2026. In Google’s own words on the Translation Hub deprecation page, users could “continue using Translation Hub until September 20, 2026, when it will be shut down.”
What was lost
Translation Hub was Google’s no-code document-translation surface: upload documents, choose target languages, manage glossaries and translation memory, and download translations — all through a portal, without writing software. Retiring it removes that turnkey workflow. The translation capability itself continues in Google’s API, but the self-service product that non-developers could operate is gone.
Where the capability lives now
Google’s ongoing document-translation offering is the Cloud Translation API (Advanced, v3), which supports document translation, glossaries, and custom models. The change is operational as much as technical: what was a portal anyone could use becomes an API a developer integrates. Teams that ran translation through the Hub UI now need either an internal integration on top of Cloud Translation API or a third-party tool built on it. If you relied on custom-trained models inside Translation Hub, verify their availability through Cloud Translation API v3 / AutoML Translation rather than assuming parity.
A note on sourcing
We hold this project to writing every entry from the vendor’s primary source. Translation Hub’s deprecation page is a JavaScript-rendered single-page app that returns only an empty shell to our automated fetcher, and the alternate host redirects in a loop — so we could not fetch the notice directly. Because the shutdown date has already passed (removing any risk of guessing a future date) and Google’s own page text is heavily corroborated — surfaced verbatim through search, and confirmed by a Google Developer forum thread and multiple independent migration writeups — we’ve published it with this disclosure rather than leave a real, significant shutdown unrecorded. If Google’s primary page becomes fetchable, we’ll re-verify the migration specifics against it.
Entry changelog
- — last reviewed.
- — Entry created as a PAST, heavily-corroborated shutdown under the D-036 exception. Google's own Translation Hub deprecation page (cloud.google.com/translation-hub/docs/deprecations) is a JavaScript-rendered SPA that returns only a ~2.4 MB shell with no date tokens to direct fetchers (netfetch), and WebFetch hits a cross-host redirect loop (docs.cloud.google.com <-> cloud.google.com/translate/) — the same block recorded on B-079 since 2026-09-05. HOWEVER: (1) Google's indexed page text was surfaced verbatim via search — "Starting on June 30, 2025, Translation Hub is officially deprecated and will no longer be supported. You can continue using Translation Hub until September 20, 2026, when it will be shut down." (2) The shutdown date (20 Sep 2026) is now PAST, so there is no §3.2 date-inference risk. (3) Independent corroboration: a Google Developer forum thread on the Translation Hub deprecation and third-party migration writeups all state the 20 Sep 2026 shutdown. Per D-036 this qualifies for publication with the sourcing disclosed. Status set directly to passed. No detect fingerprint: a hosted portal with no code-visible identifier (SOURCING §6).
Put this countdown in your README
Building on Google? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/google-cloud-translation-hub-shutdown)Spot an error or a changed date? Tell us and it’s corrected the same night.