T5Gemma TTS

T5Gemma TTS

Free open TTS model with zero-shot voice cloning and explicit duration control in English, Chinese, and Japanese.

70/100Safe BetFreeFree

Duration control is the reason to care. Most open TTS releases give you nothing but a speed slider; here you name a target and get 3.0s, 5.0s, and 7.0s renders of the same sentence. Quality judgement is still by ear, because the model card explicitly says there are no WER/CER or SIM-O metrics yet, and three layers of non-commercial licensing (Gemma Terms, CC-BY-NC 4.0, XCodec2's own terms) close the door on shipping it. It is also not optimized for real-time inference, since autoregressive audio token generation is slow. Worth a Colab session for speech-timing research; if you need a hosted, commercially licensed speech API, look at ElevenLabs, Azure Speech, or Google Cloud TTS instead.

Verified 23h ago · liveness 70/100 · cite: rightaichoice.com/tools/t5gemma-tts

Best for
  • Speech researchers studying length-controllable TTS and PM-RoPE duration steering
  • Non-commercial multilingual projects needing zero-shot voice cloning in EN/ZH/JA
  • Hobbyists auditioning voice cloning for free on Colab or Kaggle notebooks
  • Audio work where generated speech has to hit a target duration
Not ideal for
  • Any commercial product — Gemma Terms of Use, CC-BY-NC 4.0, and XCodec2's non-commercial terms all apply
  • Real-time or low-latency TTS, since autoregressive audio token generation takes significant time
  • Buyers who need published WER/CER or SIM-O benchmarks before choosing a model
Visit Website

IntermediateResearcher with a GPU box: under an hour to a first render, mostly spent on the gated license acceptance, pip install of transformers and accelerate, and the ~5B-parameter download. Hobbyist on Colab or Kaggle: 15-30 minutes using the linked notebooks, plus session limits to work around. Anyone without a GPU should budget an hour or more of queueing before hearing output.WebNo public APIVerified 23h ago
Pricing
Free
FreeFree tier4 hidden costs
Learning curve
Intermediate
Researcher with a GPU box: under an hour to a first render, mostly spent on the gated license acceptance, pip install of transformers and accelerate, and the ~5B-parameter download. Hobbyist on Colab or Kaggle: 15-30 minutes using the linked notebooks, plus session limits to work around. Anyone without a GPU should budget an hour or more of queueing before hearing output.
Runs on
Web
No public API · 5 integrations
Who it's for
Speech synthesis researcherNon-commercial dubbing hobbyistGrad student writing a TTS survey
Live sentiment
Is T5Gemma TTS actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip T5Gemma-TTS if you need commercially licensable speech or published WER/CER and SIM-O benchmarks before committing, since the CC-BY-NC 4.0 and Gemma terms bar commercial use and the developer publishes no objective metrics.

The 30-second take
Biggest gripe

Because the weights are gated, you cannot pull them in an automated CI job without first accepting the license through a logged-in Hugging Face account.

Price reality

The model itself is $0 to download and run — you pay in GPU time. That puts it in a different bracket from hosted speech APIs such as ElevenLabs, Azure Speech, or Google Cloud TTS, which charge per character and carry commercial rights. For a non-commercial research project on a single GPU or a free Colab/Kaggle session, T5Gemma-TTS costs nothing but your compute; if you need commercial rights or low-latency production output, the hosted APIs are the realistic line item.

In short

T5Gemma TTS — Free open TTS model with zero-shot voice cloning and explicit duration control in English, Chinese, and Japanese. Best for Speech researchers studying length-controllable TTS and PM-RoPE duration steering, Non-commercial multilingual projects needing zero-shot voice cloning in EN/ZH/JA, Hobbyists auditioning voice cloning for free on Colab or Kaggle notebooks. Free to use.

What people actually say about T5Gemma TTS — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

8 mentions across 3 sources (Hacker News, Bluesky, GitHub) · researched Jul 5, 2026.

33% positive67% critical

Average across the 3 sources that answered — each source counts once, not each post.

Recurring strengths
  • +Free, open-source with CC-BY-NC 4.0 license.
  • +Multilingual: English, Chinese, Japanese trained on 170k hours.
  • +Zero-shot voice cloning from reference audio (claimed).
  • +Explicit duration control via P-RoPE for speed/length adjustment.
  • +Hugging Face Spaces demo available for quick try.
Recurring frustrations
  • −Voice cloning reportedly non-functional in comparison to alternatives.
  • −No formal evaluation metrics (WER, SIM-O) provided.
  • −Multiple GitHub issues: 401 errors, multi-GPU failures.
  • −Lacks ONNX/TorchScript export for deployment on C++/Java.
  • −No AMD GPU support via ROCm.
Patterns worth knowing
Core feature (voice cloning) disputed
Seen on Hacker News
Setup and compatibility issues
Seen on GitHub
Lack of documentation and evaluation
Seen on GitHub
Learning curve
advancedProductive in ~A few hours
Hidden costs people mention
  • • Requires GPU with sufficient VRAM (2B model)
  • • May incur cloud compute costs

Viability Score

70/100
Safe Bet

How well maintained and how widely used is T5Gemma TTS? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
90
Traction
87
Site health
95
User sentiment
33
What the vendor publishes
40

Last calculated: October 2026

How we score →

Key Features

  • Zero-shot voice cloning from a short reference audio clip
  • Explicit duration control via PM-RoPE, with 3.0s, 5.0s, and 7.0s sample renders
  • Multilingual TTS in English, Chinese, and Japanese
  • Encoder-decoder LLM initialized from google/t5gemma-2b-2b-ul2
  • XCodec2 audio codec for audio tokenization
  • Autoregressive audio token generation
  • Transformers text-to-speech pipeline with trust_remote_code
  • AutoModelForSeq2SeqLM loading with device_map="auto"
  • Interactive demo hosted on Hugging Face Spaces
  • Open training code and inference scripts on GitHub
  • Google Colab and Kaggle notebook walkthroughs
  • Roughly 5B parameters in BF16 precision
  • Trained on ~170,000 hours of public speech (Emilia, libriheavy)
  • Technical report on arXiv (2604.01760, 2026/04/03)
  • Gated download requiring login and license acceptance

About T5Gemma TTS

FreeIntermediateNo APIWeb

T5Gemma-TTS-2b-2b is a multilingual text-to-speech model published on Hugging Face by Chihiro Arata as a personal project. It speaks English, Chinese, and Japanese, clones a voice from a short reference clip with no fine-tuning, and — unusually for an open release — accepts an explicit target duration for the generated audio. The model card shows the same English sentence rendered at 3.0s (fast), 5.0s (normal), and 7.0s (slow), with matching Japanese samples. The build is an encoder-decoder LLM initialized from google/t5gemma-2b-2b-ul2, with the audio half trained from scratch on roughly 170,000 hours of public speech (about 100k English, 50k Chinese, 20k Japanese, drawn mainly from Emilia and libriheavy) using 8 AMD MI300X GPUs on the AMD Developer Cloud for about two weeks. Audio is tokenized with the XCodec2 codec, the checkpoint lands around 5B parameters in BF16, and the architecture follows VoiceStar (arXiv 2505.19462), including PM-RoPE for length control. A technical report arrived on arXiv (2604.01760) on 2026/04/03. You run it through the Transformers text-to-speech pipeline or AutoModelForSeq2SeqLM with trust_remote_code and device_map="auto", or test it in the Hugging Face Spaces demo; training code and inference scripts live on GitHub with Colab and Kaggle notebooks. The download is gated behind login and license acceptance. This is research tooling, not infrastructure: the dual license (Gemma Terms of Use plus CC-BY-NC 4.0, with XCodec2 carrying its own non-commercial terms) rules out commercial deployment, and the developer states plainly that no formal WER/CER or SIM-O numbers exist yet.

Behind the Verdict

T5Gemma-TTS is a hobby project that happens to solve a real problem. If you have ever tried to fit synthesized speech to a fixed slot — a dubbing cue, a dialogue beat, a slide narration that must end when the slide ends — you know most TTS tools give you a speed multiplier and hope. T5Gemma-TTS takes a target duration directly, implemented through PM-RoPE in an architecture the model card credits to VoiceStar (arXiv 2505.19462), and demonstrates it on the same English and Japanese sentences at 3.0s, 5.0s, and 7.0s. The engineering is more substantial than a prompt wrapper. The base is google/t5gemma-2b-2b-ul2 with the audio half trained from scratch, roughly 5B parameters in BF16, trained on about 170,000 hours of public speech (English ~100k, Chinese ~50k, Japanese ~20k, mainly Emilia and libriheavy) across 8 AMD MI300X GPUs for about two weeks. Audio is tokenized with XCodec2. Zero-shot voice cloning works from a reference clip with no fine-tuning, and the card shows three cloning examples (its reference clips were themselves generated with NandemoGHS/Anime-Llasa-3B and gemini-2.5-pro-preview-tts, which is worth knowing when you judge the samples). A technical report landed on arXiv (2604.01760) on 2026/04/03, so you can cite it. The honest weaknesses are the ones the developer states. There are no formal objective metrics — no WER/CER, no SIM-O — so quality assessment is by ear. Duration control is not perfect: generated audio may differ from the duration you specify. Inference is not optimized for real-time use, because autoregressive audio token generation takes significant time. And the licensing stack is the hard wall: CC-BY-NC 4.0, the Gemma Terms of Use, and XCodec2's separate non-commercial terms. Malicious use including impersonation is explicitly prohibited, and the weights are gated behind login and license acceptance. Where it fits: a speech researcher or grad student studying length-controllable generation, someone who needs English/Chinese/Japanese voice cloning for a non-commercial demo, or an audio hobbyist who wants to hear duration-conditioned pacing without paying for a hosted API. Where it does not: any product you intend to sell, any latency-sensitive pipeline, and any procurement that requires benchmark numbers before adoption.

Researching T5Gemma TTS? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Real-world workflow fit

Concrete scenarios for the personas T5Gemma TTS actually fits — and what changes day-one when you adopt it.

Speech synthesis researcher

You want to test whether duration-conditioned generation beats a speed-slider baseline on the same sentence, so you clone a container environment, load the model with AutoModelForSeq2SeqLM and trust_remote_code, and render the same English text at 3.0s, 5.0s, and 7.0s.

Outcome: You get three comparable renders plus a citable paper (arXiv 2604.01760) and the VoiceStar lineage to write against, with no licence fee and no vendor account beyond the gated download.

Non-commercial dubbing hobbyist

You are timing subtitles for a fan project in Japanese and need a line of narration to land inside a fixed eight-second slot, so you feed a short reference clip for voice and specify a target duration.

Outcome: You get speech in a cloned voice aimed at your slot, knowing the model card warns the control is not perfect, so you re-render or trim rather than assume an exact match.

Grad student writing a TTS survey

You need a multilingual open checkpoint in English, Chinese, and Japanese to compare against length-controllable baselines, and you run it from the Kaggle notebook linked on the model card.

Outcome: You have reproducible inference on free compute and an explicit caveat to report: the developer publishes no WER/CER or SIM-O scores, so your evaluation is the first objective number on the model.

Use Cases

Models Under the Hood

google/t5gemma-2b-2b-ul2XCodec2gemini-2.5-pro-preview-ttsNandemoGHS/Anime-Llasa-3B

as of 2026-10-14

Limitations

  • Licensing blocks commercial use: the model is CC-BY-NC 4.0 and follows the Gemma Terms of Use, and the XCodec2 codec carries its own non-commercial terms.
  • Malicious use, including impersonation, is strictly prohibited.
  • The model is gated, so you must log in and accept the license before accessing the content.
  • The developer states there are no formal objective evaluation metrics (WER/CER, SIM-O, etc.) available, so you judge quality by ear.
  • Duration control is not perfect: generated audio may differ from the specified duration.
  • Inference is not optimized for real-time TTS — autoregressive generation of audio tokens takes significant time and is unsuitable for low-latency use cases.
  • This is described on the model card as a hobby project.

as of 2026-10-17

Verification history

We have re-verified T5Gemma TTS 8 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  2. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  3. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  4. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  5. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  6. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it

Showing the 6 most recent of 8 verification passes.

Free to cite with attribution — this page re-verifies continuously.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly
—
—

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Plans compared

For each published T5Gemma TTS tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.

Public Model (non-commercial)

$0

Ideal for

Speech researchers, students, and hobbyists who need multilingual zero-shot voice cloning with duration control and can work inside a non-commercial license

What this tier adds

Starting (and only) tier: $0 for gated weights on Hugging Face, Transformers inference, a Spaces demo, GitHub training code, and Colab/Kaggle notebooks, under CC-BY-NC 4.0 plus the Gemma Terms of Use

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • Because the weights are gated, you cannot pull them in an automated CI job without first accepting the license through a logged-in Hugging Face account.
  • Running the ~5B-parameter BF16 checkpoint needs a GPU with real VRAM; free Colab or Kaggle tiers cap session length and GPU class, so long inference runs can get cut off.
  • Autoregressive audio token generation is slow by design, so the effective cost of a batch of samples is GPU hours rather than an API line item.
  • The XCodec2 codec brings its own non-commercial terms on top of CC-BY-NC 4.0 and the Gemma Terms, so a legal review has three licenses to clear, not one.

Where the pricing makes sense

The company stage and team size where T5Gemma TTS's pricing actually pencils out — and where peers do it cheaper.

The model itself is $0 to download and run — you pay in GPU time. That puts it in a different bracket from hosted speech APIs such as ElevenLabs, Azure Speech, or Google Cloud TTS, which charge per character and carry commercial rights. For a non-commercial research project on a single GPU or a free Colab/Kaggle session, T5Gemma-TTS costs nothing but your compute; if you need commercial rights or low-latency production output, the hosted APIs are the realistic line item.

Setup time & first value

How long it actually takes to get something useful out of T5Gemma TTS — broken out by persona, not the marketing-page minute.

Researcher with a GPU box: under an hour to a first render, mostly spent on the gated license acceptance, pip install of transformers and accelerate, and the ~5B-parameter download. Hobbyist on Colab or Kaggle: 15-30 minutes using the linked notebooks, plus session limits to work around. Anyone without a GPU should budget an hour or more of queueing before hearing output.

Switching to or from T5Gemma TTS

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From a hosted TTS API (ElevenLabs, Azure Speech, Google Cloud TTS): port your texts and reference clips into the Transformers pipeline with trust_remote_code, and drop per-character billing for GPU time.
  • →From a baseline open TTS model: swap the checkpoint for Aratako/T5Gemma-TTS-2b-2b and add a target-duration argument where you previously used a speed multiplier.
  • →From VoiceStar: reuse your length-control evaluation harness and point it at the t5gemma-2b-2b-ul2-initialized checkpoint.
Migrating out
  • ↗To a hosted commercial API (ElevenLabs, Azure Speech, Google Cloud TTS): required if you need to ship commercially, since CC-BY-NC 4.0 and the Gemma Terms bar commercial use here.
  • ↗To a real-time TTS engine: necessary if latency matters, because autoregressive audio token generation here is not optimized for low-latency use.
  • ↗To a benchmarked open model: choose one with published WER/CER and SIM-O figures if you need objective quality evidence before adoption.

Integrations

Hugging Face TransformersHugging Face SpacesGoogle ColabKaggleGitHub

Resources & Guides

Tutorials & Learning

YouTube returned 6 videos for “T5Gemma TTS”, and we withheld 6: 6 did not mention T5Gemma TTS. We are showing none, because we could not prove any of them are about T5Gemma TTS.

Tools that pair well with T5Gemma TTS

Common stack mates teams adopt alongside T5Gemma TTS, with the specific reason each pairing earns its keep.

Featured Head-to-Head Comparisons

Alternatives to T5Gemma TTS

View all
VoxCPM

VoxCPM

VoxCPM2 is a tokenizer-free open-source TTS model for 30-language speech synthesis, Voice Design, and 48kHz voice cloning on your own GPU.

FreeTry
OpenVoice

OpenVoice

Open-source instant voice cloning from a 10-second clip, with separate control knobs for emotion, accent, rhythm, pauses, and intonation.

FreeTry
Inworld

Inworld

Inworld delivers realtime text-to-speech, speech-to-text, and open-model inference on one API for consumer voice apps.

FreemiumTry

Frequently Asked Questions

Used T5Gemma TTS? Help shape our editorial sentiment research.