DEV Community

Cover image for Sub-10M TTS Models Are Everywhere. One Number Is Fake.
Dishant Sharma
Dishant Sharma

Posted on Edited on Originally published at dishantsharma.dev

Sub-10M TTS Models Are Everywhere. One Number Is Fake.

i spent an hour hunting a number that does not exist.

The number was 13.7ms. Time to first audio for Zyphra's ZONOS3-Mini, on an A100, down from 80ms. It appeared in a few paraphrases and it read like the kind of number that ends an argument.

So i opened the technical report. arXiv 2611.16525, submitted 12 November. Section 9, Inference.

On one H100 with embedding prompts, the first audio arrives 85 ms after a single request and 80 ms (p50) at 8 concurrent requests.

H100, not A100. Eighty-five, not 13.7. And 80 was never "before." It was the number at eight concurrent requests.

Here's the part that stuck with me.

The real number is still absurd. 85ms to first audio, from a model that clones a voice and also runs in a browser tab. But somebody inflated it sixfold, and the inflated version is the one that traveled.

That mismatch is the whole month in small text-to-speech. The engineering is better than the marketing, and the marketing is faster than the engineering.

Why they all shipped at once

Four small TTS releases landed between 9 and 16 November. Inflect v3 on the 13th, tiny-voca on the 14th, sanoTTS hours later, ZONOS3-Mini's paper on the 12th.

But that is not a race. It is a supply chain getting cheap enough to notice.

tiny-voca's card says it plainly. Both voices were designed from text descriptions with Qwen3-TTS VoiceDesign.

All 16,018 clips came from Qwen3-TTS 1.7B. No human was recorded at any point.

So the tiny model is a student. The big model is the teacher. And the teacher is now free enough that you can manufacture a clean dataset for a voice in an afternoon.

That flips the economics. You used to need consent forms, a studio, and a pile of transcripts. Now you need one 4090 and a weekend.

The lab that ships the teacher is quietly shipping the curriculum for everyone else.

What four million parameters buys

What actually happens is that small stops meaning bad at reading out loud.

tiny-voca sits at rank 8 with 0.733% average word error rate on the Open TTS Leaderboard v1.6.3, against 50 full-coverage English models. A 4.5M model, trained only on machine audio, beats most of the field on the metric that decides whether a person understands you.

Inflect Mini is 34.31M and reports 0.739% average WER across 10,128 clips, self-run over six voices. Pooled, it lands at 0.875% over 127,308 words.

Model Size Avg WER UTMOS22
Ming-3.0-tts 0.5B 0.657 4.28
Kokoro 82M 0.690 4.51
Paradee 8M 0.693 4.38
phonon-31m 31M 0.730 4.45
Inflect Mini 34M 0.739 4.48†
tiny-voca M2 4.5M 0.733 4.34

Read the asterisks that aren't there. Inflect and tiny-voca are self-run on different panels. None of this is a matched comparison.

† Inflect reports UTMOS22Strong, which is a different predictor from UTMOS22. So even that cell is not the same measurement.

But read the sizes. An 8M model at 0.693%. That was a 500M model's job two years ago.

The numbers that hold up

i used to think "real time" was a single thing. It is not. It is a different number on every device, and the papers and the landing pages do not always agree.

  • ZONOS3-Mini: 886M total, 100M active. 80ms p50 to first audio on an H100 at 8 concurrent. 187 seconds of audio per second of compute.
  • tiny-voca: $9.56 of GPU time. 7.7 hours on one RTX 4090. 70x real time on four CPU threads.
  • Inflect Mini: 34.31M core params, 24kHz, CPU or CUDA.
  • sanoTTS heart: 2.27M params. heart-nano is 294K and runs on numpy alone.

Now the browser numbers, which reframe the whole thing. Zyphra's paper says under 800ms to first audio on a Pixel 9 and 450ms on an M3 MacBook Air.

Their marketing page says 570ms and 150ms.

Same model. Same week. Same company.

i don't think that is deception. i think it is a paper measured on one build and a landing page measured on another.

It tells you what "on device" really means. It means whatever hardware was on the desk that day.

Where the small class breaks

The problem isn't what you think. Quality is fine. The failure is in the boring front end and the missing randomness.

Every card admits the same three things. English only, or a narrow slice. A handful of fixed voices, no cloning.

And every one of them was trained on synthetic speech, so it can never outgrow the teacher.

tiny-voca's author is blunt about the last one. The same text always reads the same way, because there is no prosody sampling. Say a sentence twice and you get the identical sentence.

For a kiosk that is fine. For an audiobook you hear it by paragraph three.

Then there is the phonemizer. Numbers, dates, foreign names, homographs. tiny-voca's release notes ask you to try hard text and post what breaks.

That is a polite way of saying the weak link is the text front end, not the network.

And the community noticed. The reaction split in a way i did not expect.

  • r/LocalLLaMA gave Inflect v3 105 points and 29 comments, and tiny-voca 70 points and 32 comments.
  • Hacker News gave ZONOS3-Mini 2 points and zero comments.
  • A separate small-TTS thread on r/LocalLLaMA pulled 287 points while the biggest name in the space sat unread.

Nazeem, the tiny-voca author, was almost apologetic about the leaderboard.

I never created Voca to compete with other models or top a benchmark.

That is either humility or a very smart frame. Either way it is the correct one.


A tangent about saying things out loud

This has nothing to do with the models, but it is why i care.

My grandfather used to read the newspaper aloud, and he never read it the same way twice. Same column, different pauses. He would laugh at a line he had already read that morning.

i tried to replace that once with the Mac's say command, back when it was the only free option. It got every word right and every sentence wrong.

Flat, cheerful, faintly threatening. Like being read to by a form.

What surprised me in this research is that the new models still have that problem, just quieter. They fixed the voice and left the performance alone.

A deterministic read is still a read. It is not a person deciding, mid sentence, that this part is funny.

Who should actually care

Most apps do not need a local TTS model, and i wish launch posts said so.

If you run a phone agent, you are not inferring on the customer's handset. You need a server, a fallback, and someone awake at 2am.

ZONOS3-Mini is the real option there. It is 886M params and it wants a GPU.

If you want narration inside a web app, you want the browser build, and you accept that it is 570 to 800ms depending on which document you trust.

The honest split:

  • Bundle voice into an app with no server and no per-word bill: tiny-voca or Inflect Micro.
  • Real cloning across 43 languages: ZONOS3-Mini, and budget for hardware.
  • A long tail of names, numbers, and languages: pay somebody.

The sub-10M class is not fighting ElevenLabs. It is fighting the say command and the silence of having no voice at all.

The number i couldn't find

i never found where 13.7ms came from. Somebody typed it, somebody repeated it, and now it lives in my notes as the thing i chased on a Tuesday afternoon.

The real model was fast enough that the fake number was pointless.

Eighty-five milliseconds is not a marketing figure. It is just true, and it is the better story.

Top comments (0)