MOSS-TTS
OpenMOSS
Open speech and sound generation family - nano to 8B, 31 languages, real-time streaming.
What is MOSS-TTS?
MOSS-TTS is a family of five open models from OpenMOSS/MOSI.AI: a flagship 8B with zero-shot cloning, a multi-speaker dialogue model, a voice-design-from-text model, a low-latency real-time model, and a sound-effect model. A ~100M nano variant targets CPU-only deployment. Code and weights are Apache-2.0.
MOSS-TTS in depth
Most teams that need synthetic speech end up gluing together several tools: one model for narration, another for multi-speaker dialogue, a separate service for voice cloning, and yet another for sound effects or low-latency agents. Each piece has its own license, its own deployment story, and its own quirks. MOSS-TTS, from the Chinese lab OpenMOSS and its MOSI.AI effort, tackles that fragmentation by shipping a whole family of open speech and audio models under a single Apache-2.0 repo. It spans a flagship 8B text-to-speech model with zero-shot voice cloning, a multi-speaker dialogue model, a voice-design-from-text model, a real-time streaming model, a sound-effect model, and a roughly 100M nano variant aimed at CPU-only deployment. The pitch is one coherent toolkit for the full voice-AI stack.
The family shares a common backbone. At its core sits the MOSS-Audio-Tokenizer, a transformer codec that compresses 24kHz audio down to a 12.5Hz frame rate using residual vector quantization, with selectable bitrates. On top of that, an LLM derived from Qwen3 predicts discrete audio tokens autoregressively, the same recipe many recent neural TTS systems use. What is distinctive is the spread of specialized variants on one architecture, plus fine-grained control: you can steer output with Pinyin, phonemes, duration tokens, and explicit pause markers like [pause 3.2s]. The project also offers a torch-free inference path through a llama.cpp backend with ONNX Runtime, which is what makes the nano model practical on plain CPUs. The lab reports 31-language support and stable generation over long passages.
This is for engineers and product teams who want to self-host voice generation rather than pipe every request through a paid API. Concrete fits include audiobook and long-form narration where stable multi-minute output matters, podcast or dialogue production that needs distinct speakers, and game or interactive-media voice design where you generate characters from a text description without reference audio. The real-time model, which the project reports at around 180ms time-to-first-byte, targets conversational agents, while the sound-effect model covers environmental audio for film and animation. The nano variant is the standout for edge and privacy-sensitive cases: it claims real-time synthesis on four CPU cores, which opens up offline kiosks, on-device assistants, and cost-sensitive batch jobs that cannot justify GPU rental or per-character cloud fees.
The caveats are real. The flagship 8B model and the 8B dialogue model carry heavy infrastructure requirements, so the headline quality is not free: you need capable GPUs to run them well, even if the repo lists 8GB-plus cards as workable. Almost every quality and latency figure, including the word and character error rates and the claim of beating closed models like Doubao and Gemini 2.5 Pro, is self-reported by the lab and comes from its own evaluations and subjective tests, with no independent third-party benchmarks cited yet. As a Chinese-lab project, it may also draw supply-chain and governance scrutiny in regulated environments. Voice cloning raises the usual consent and misuse questions, and a six-model family is more surface area to learn, version, and maintain than a single endpoint.
Against ElevenLabs, the obvious commercial reference, MOSS-TTS trades polish and operational simplicity for ownership and cost control. ElevenLabs gives you a managed API, mature voice library, and predictable quality with no infrastructure to run, which is hard to beat for teams that just want results. MOSS-TTS makes sense when self-hosting, data residency, Apache-2.0 licensing, or avoiding per-character pricing outweigh that convenience, and especially when the CPU-deployable nano model unlocks use cases a cloud API cannot serve economically. It is a strong choice for experimentation, internal tooling, and edge deployment today. It is too early if you need proven production reliability backed by independent benchmarks, a support contract, and guaranteed uptime, in which case the managed alternative remains the safer bet until the family matures.
Pros & Cons
Pros
- Covers the full voice-AI stack from sound effects to real-time agents in one Apache-2.0 repo
- Nano (~100M) claims real-time generation on 4 CPU cores - accessible for edge use
- 31-language support with active development
Cons
- Flagship 8B model has heavy infrastructure requirements
- Quality and latency figures are self-reported
- Chinese-lab origin may raise supply-chain scrutiny in regulated contexts
License
Apache-2.0 (OSI-open)
When it is interesting
You want an Apache-licensed, self-hostable voice toolkit spanning TTS, dialogue, voice design and real-time, including a CPU-deployable nano model.
When it is too early
You need proven production reliability with third-party benchmark comparisons.
Commercial alternative & related
- Commercial counterpart: ElevenLabs
This repo featured in the 2026-07 edition of the Open-Source AI Radar.
voicebox
jamiepine
A free, on-device alternative to ElevenLabs for TTS, voice cloning and dictation.
VoxCPM
OpenBMB
Tokenizer-free TTS from OpenBMB covering 30 languages with voice design and real-time streaming.
Chatterbox
resemble-ai
MIT-licensed open TTS with zero-shot voice cloning - 500M params, 23+ languages.