Set of π with π to improve the voice - natural and intelligible
See the code
A curated, developer-friendly path through text-to-speech, organized around the one decision that shapes every other: real-time streaming synthesis for agents versus high-fidelity offline synthesis for media.
Text-to-speech split into two fields wearing one name. One is real-time synthesis, judged by time-to-first-byte and measured in milliseconds, where a voice agent has to start speaking before the caller notices a gap. The other is offline synthesis, judged by naturalness and expressive range, where an audiobook or a dub can take all the compute it wants. A model that wins one loses the other, and almost every mistake in a TTS build traces back to picking a tool tuned for the wrong side of that line.
This list is organized so that split stays visible everywhere. Providers, models, and benchmarks each carry a real-time or offline lean, and the sections that matter most to agent builders, streaming, cancellation, and codecs, are the ones the rest of the field explains worst.
Learning resources are tagged π’ Beginner, π‘ Intermediate, or π΄ Advanced. Prefer free official docs and vendor-neutral guides; where an author has a commercial interest, it is flagged.
Read top-to-bottom if you are new to synthesis. The recommended path:
In scope. Everything that turns text into a waveform: the front-end (text normalization, grapheme-to-phoneme, prosody prediction), acoustic models, neural vocoders and audio codecs, streaming and cancellation, voice cloning and voice design, expressive and multilingual control, and the evaluation and ethics that any serious deployment now requires.
Out of scope. Speech-to-text, voice activity detection, turn detection and endpointing, transport (WebRTC), and telephony (SIP) all belong to the pipeline, not to synthesis. Where a TTS decision depends on one of them, this list explains just enough to make that decision and no more. Turn detection is the clearest case: cancelling synthesis on a barge-in is a TTS concern and lives in Section 4, but deciding that a barge-in happened is a turn-taking concern that sits outside this list.
The boundary cases, and how they are handled. Voice cloning and voice conversion are treated as core TTS and included, scoped to synthesis rather than to speaker verification. Watermarking and cloning ethics stay in, because in 2026 they are inseparable from shipping a synthetic voice. Music and general audio generation stay out.
The inclusion bar. A resource earns a place if it is active within the last 12 months, accessible to a working developer, and either vendor-neutral or clearly labeled when authored by a commercial party. A provider earns a row if you can send it text and get back audio today, not on a waitlist.
Classical neural TTS is a three-stage pipeline: a text front-end (normalization, grapheme-to-phoneme, prosody prediction) feeds an acoustic model that predicts a mel-spectrogram, which a neural vocoder turns into a waveform. The central design choice is real-time versus offline: streaming and end-to-end architectures collapse or reorder these stages to emit audio within a couple hundred milliseconds for voice agents, whereas offline synthesis keeps the stages separate to maximize naturalness. Start here to build the mental model before comparing models or providers.
Every provider here is generally available today: send text, get audio back, no waitlist. The split that matters for a builder is architectural: providers built for turn-by-turn conversation now hit roughly 40 ms to 200 ms time-to-first-audio, while media and dubbing providers trade that latency for expressive range and long-form control. Pick from the first group for voice agents and the second for narration, dubbing, and produced content.
| Provider | Lean | Best for |
|---|---|---|
| ElevenLabs | both | Expressive Eleven v3 voices, dubbing, and a mature agent stack. |
| Cartesia Sonic 3.5 | real-time | Lowest-latency conversational TTS (40 ms Turbo, vendor). |
| Deepgram Aura-2 | real-time | Enterprise contact-center agents with on-prem option. |
| OpenAI TTS | both | Steerable delivery via instructions inside the OpenAI stack. |
| Rime | real-time | High-volume IVR with deterministic pronunciation control. |
| Hume Octave 2 | both | LLM-driven emotional prosody from text semantics. |
| Inworld TTS | real-time | Natural-language voice steering across 200+ languages. |
| Soniox TTS | real-time | Low-cost real-time synthesis paired with Soniox STT. |
| LMNT | real-time | Fast streaming plus voice cloning for agents and games. |
| Neuphonic | real-time | WebSocket-first low-latency TTS plus open-source on-device NeuTTS. |
| PlayAI | both | Multi-speaker conversational dialogue synthesis (PlayDialog). |
| Amazon Polly | both | AWS-native generative and neural voices with streaming. |
| Google Cloud TTS | both | Chirp 3 HD voices across 50+ locales on GCP. |
| Azure Neural TTS | both | 600+ voices, Dragon HD, SSML, and batch synthesis. |
| Murf | offline | Studio-grade voiceover with style and pacing control. |
| WellSaid Labs | offline | Enterprise narration for e-learning and corporate video. |
| Speechify | both | Large voice library and cloning for reading and media apps. |
| Resemble AI | both | Voice cloning plus the open-source Chatterbox model. |
Self-hostable TTS in 2026 spans two poles: tiny CPU-friendly models that stream in under a second, and large LLM-backbone models that clone a voice from a few seconds of reference audio. The single most important gating factor is the weight license, not audio quality, since several top open-weight models ship non-commercial or capped-usage terms that block production shipping. Read the per-model license note before you build, because permissive code often sits next to restrictively licensed checkpoints.
| Model | License | Best for |
|---|---|---|
| Chatterbox (Multilingual v3, Turbo) | MIT (code and weights) | Production voice agents needing low latency (vendor), 23 languages, and built-in watermarking. |
| Kokoro 82M | Apache 2.0 | Cheapest realtime TTS: 82M params, runs fast on CPU, 8 languages. |
| Piper | GPL v3 | Fully offline embedded and Raspberry Pi devices. |
| Coqui XTTS v2 (idiap fork) | Coqui Public ML License (non-commercial weights) | Zero-shot cloning across 17 languages from a maintained fork. |
| MeloTTS | MIT | Realtime CPU inference with multiple English accents. |
| Kitten TTS | Apache 2.0 | Ultra-light 15M to 80M ONNX models for edge and browser deploys. |
| Orpheus-TTS | Apache 2.0 | Emotive Llama-3B TTS with token-streaming for agents. |
| Sesame CSM-1B | Apache 2.0 | Context-aware conversational speech that conditions on dialogue history. |
| CosyVoice 2 / 3 | Apache 2.0 | Streaming LLM TTS with about 150 ms first-chunk latency (vendor) and strong Chinese and English. |
| Dia (Nari Labs, Dia 2 family) | Apache 2.0 | One-pass multi-speaker dialogue with laughs, sighs, and turns. |
| Fish Speech / OpenAudio S1-mini | Apache 2.0 code, CC-BY-NC-SA-4.0 weights | Low-WER multilingual cloning from a 10 to 30 s sample. |
| GPT-SoVITS | MIT | Best-similarity few-shot cloning from about 1 minute of audio. |
| F5-TTS | MIT code, CC-BY-NC-4.0 weights | Research and non-commercial flow-matching cloning; retrain to ship. |
| StyleTTS 2 | MIT | Human-level single and multi-speaker quality via style diffusion. |
| Parler-TTS | Apache 2.0 | Prompt-controllable voice attributes and a full open training stack. |
| Zonos / Zonos2 | Apache 2.0 | High-fidelity cloning; Zonos2 is a low-latency 8B-total MoE. |
| IndexTTS-2 | Bilibili Model License (commercial use needs separate grant) | Autoregressive TTS with precise duration and emotion-timbre control. |
| Higgs Audio v2 | Boson community license (commercial cap at 100k annual active users) | Expressive multi-speaker and speech-plus-music from a Llama-3.2-3B base. |
| MaskGCT (Amphion) | Amphion / research (CC-BY-NC weights) | Non-autoregressive masked-codec zero-shot TTS with no forced alignment. |
This is the section the rest of the field explains worst, and the one an agent builder needs most. For a voice agent, naturalness you cannot start playing in under 200 ms is naturalness the caller never hears. The metric that governs this section is time-to-first-byte (TTFB), the delay between sending text and receiving the first chunk of playable audio, not the total time to synthesize the full utterance. A model with beautiful output and a 900 ms first byte loses to a plainer model that starts speaking at 90 ms, every time, on a live call.
Read this section as three questions in order: how does streaming TTS actually work, how do you stop it mid-word when the caller interrupts, and how do you measure any of it honestly.
Not all streaming is the same, and the differences decide whether your agent can interrupt cleanly. There are three levels, and providers rarely tell you which one they ship.
The moment a caller interrupts, the audio already buffered has to stop within roughly 60 ms or the agent sounds like it talked over them. This is a TTS capability, not a turn-taking one: your provider either supports killing an in-flight synthesis stream or it does not, and you cannot know from the marketing page. Deciding that an interruption happened is a separate turn-detection problem; this subsection is only about stopping the sound once that decision is made.
A comparison table is the fastest way for a reader to pick. Keep the columns honest and measurable: real published TTFB, streaming mode from the taxonomy above, cancellation support, and transport. Do not reprint vendor latency claims without noting they are vendor claims.
| Provider | Streaming mode | Published TTFB | Mid-stream cancel | Transport |
|---|---|---|---|---|
| Cartesia Sonic | Dual-streaming | Sub-100 ms (vendor) | Yes | WebSocket |
| ElevenLabs Flash | Output-streaming | Sub-150 ms (vendor) | Yes | WebSocket |
| Deepgram Aura-2 | Output-streaming | Low (vendor) | Yes | WebSocket |
| Rime (Mist v3) | Output-streaming | ~37 ms TTFA (vendor) | Yes | WebSocket |
| OpenAI Speech API | Output-streaming | Unpublished | No (close connection) | HTTP |
| OpenAI Realtime API | Dual-streaming | Unpublished | Yes | WebRTC / WS |
Every latency figure above is a vendor claim until you measure it on your own traffic and your own network path. Treat this table as a starting shortlist, not a verdict. The methodology to replace these numbers with your own is in the next subsection.
The through-line of this whole list is that vendor benchmarks are tuned to flatter the vendor, and TTFB is where that distortion is worst, because it is measured under ideal network conditions the vendor controls. The only number you can trust is the one you produce against your own text, from your own region, over your real transport.
Voice cloning turns a short reference sample into a speaker, and voice design turns a text description into one, spanning open-source zero-shot models (as little as 5 seconds of reference) and commercial APIs with instant versus fine-tuned tiers. Cloning a voice without the speaker's consent is the ethical fault line for this entire section, so pair any tool here with the consent, watermarking, and disclosure practices in Section 14: Ethics, consent, and regulation. Each entry is marked open (self-hostable weights) or commercial (hosted API).
Expressive synthesis is where 2026 TTS diverges most sharply from the phoneme-and-pitch era: the field has shifted from hand-authoring SSML prosody tags toward natural-language style prompts and inline emotion tags that a language-model-based TTS interprets semantically. For builders this means less markup engineering and more prompt design, but SSML still matters for deterministic pauses, pronunciation, and rate control that free-text prompts cannot pin down. The resources below cover markup standards, prosody control, inline emotion and audio tags, and description-driven style prompting.
Multilingual TTS has converged on single models that speak dozens of languages from one checkpoint, but most open models still require you to declare one language_id per request, so true mid-utterance code-switching remains the exception rather than the default. The hard part is per-language phonemization (G2P): a model can share acoustics across languages while pronunciation quality tracks how good the grapheme-to-phoneme frontend is for each one. For the training corpora behind these models, see Section 10: Datasets.
Modern TTS is a story of one architectural choice repeated at every layer: generate the waveform one step at a time, or generate it all at once. Autoregressive models buy natural prosody with sequential latency, while non-autoregressive models (duration-predicted, diffusion, or flow-matching) buy parallel speed and now match them on quality. This section is explainer-first; the canonical papers themselves live in Section 9.
These are the papers behind the models developers actually run in production, from the autoregressive waveform era through today's codec language models and flow-matching systems. The field's center of gravity has shifted from mel-spectrogram pipelines to codec-LM and flow-matching architectures that deliver zero-shot voice cloning from a few seconds of reference audio. Read the Foundations first if you want to understand why modern systems are built the way they are.
Speech corpora are the raw material for training and fine-tuning TTS, and the license attached to a dataset matters as much as its hours. For a legally clean fine-tune, start with a permissive single-speaker or multi-speaker English corpus like LJSpeech (public domain) or LibriTTS-R (CC BY 4.0), then scale to large in-the-wild data like Emilia once your pipeline is proven.
Honest TTS evaluation pairs subjective listening tests (MOS, CMOS) with objective proxies (UTMOS for naturalness, ASR-derived WER for intelligibility, speaker-similarity SIM for cloning fidelity), then sanity-checks against public arena leaderboards. A vendor's own benchmark almost always flatters the vendor, and no published latency number substitutes for measuring time-to-first-byte on your own traffic, region, and text lengths (see Section 4).
The final synthesis stage turns acoustic features (mel spectrograms) or discrete tokens back into a waveform: GAN vocoders do this for feature-based TTS, while neural audio codecs supply the discrete token space that modern codec-LM TTS predicts over. Codec choice sets the latency and quality floor for codec-LM TTS, because frame rate fixes how many autoregressive steps per second the LM must run and the codec's reconstruction quality caps how good the output can ever sound.
Two jobs live here: marking synthetic speech at generation time so it stays attributable, and detecting synthetic or manipulated speech after the fact when no watermark survives. In 2026 the practical split is proactive watermarking (SynthID, AudioSeal, PerTh) for content you generate versus passive deepfake detectors for content you receive, and neither alone closes the gap. Watermarks are cheap to embed but removable by a motivated attacker, while detectors generalize poorly to unseen generators, so serious deployments run both and log provenance; consent and disclosure obligations are covered in Section 14.
Shipping a synthetic voice in 2026 is a legal question before it is a product question: disclosure and consent are no longer optional. The EU AI Act Article 50 transparency duties apply from 2 August 2026, the FCC has ruled that AI-generated voices in robocalls are artificial voices under the TCPA (so they need prior express consent), and the FTC plus new US likeness laws (the ELVIS Act, the pending NO FAKES Act) give people a direct cause of action over their cloned voice. These resources cover the specific obligations and the practical consent frameworks a builder needs before deploying a cloned or generated voice.
These are runnable, end-to-end guides for building one TTS system at a time, from your first synthesized clip to a fully fine-tuned custom voice. The fastest path to a working custom voice in 2026 is fine-tuning an existing checkpoint (VITS, XTTS, Piper, or Parler-TTS) on 20 minutes to a few hours of clean audio, not training from scratch. Finish one build before starting another: pick the model whose training story matches your data volume and deployment target, then follow its guide to completion.
Before you wire a TTS vendor into a voice agent, audition it: a blind arena or a vendor playground tells you more in five minutes than a datasheet does in an hour. Once you commit, the boring utilities (phonemizers, G2P, and text normalization) decide whether "$4.99 on 07/21" reads correctly, so treat them as first-class parts of the pipeline.
Vendors and researchers ship faster than any static list can track, so the people building TTS in 2026 stay current through blogs, Discords, and conference proceedings rather than documentation alone. The most useful signal for a working TTS developer comes from vendor engineering blogs and the open Discords where their engineers answer latency and cancellation questions directly. Every entry here carries an empty tag by convention, since currency matters more than difficulty for this section.
Pull requests welcome. Resources must be active in the last 12 months, accessible to developers, and vendor-neutral or clearly labeled when authored by a commercial party. A provider earns a row only if you can send it text and get audio back today, not from a waitlist. Open an issue to suggest additions or removals.
MIT. Fork it, ship it.
2 commits
Set of π with π to improve the voice - natural and intelligible
See the code
A curated, developer-friendly path through text-to-speech, organized around the one decision that shapes every other: real-time streaming synthesis for agents versus high-fidelity offline synthesis for media.
Text-to-speech split into two fields wearing one name. One is real-time synthesis, judged by time-to-first-byte and measured in milliseconds, where a voice agent has to start speaking before the caller notices a gap. The other is offline synthesis, judged by naturalness and expressive range, where an audiobook or a dub can take all the compute it wants. A model that wins one loses the other, and almost every mistake in a TTS build traces back to picking a tool tuned for the wrong side of that line.
This list is organized so that split stays visible everywhere. Providers, models, and benchmarks each carry a real-time or offline lean, and the sections that matter most to agent builders, streaming, cancellation, and codecs, are the ones the rest of the field explains worst.
Learning resources are tagged π’ Beginner, π‘ Intermediate, or π΄ Advanced. Prefer free official docs and vendor-neutral guides; where an author has a commercial interest, it is flagged.
Read top-to-bottom if you are new to synthesis. The recommended path:
In scope. Everything that turns text into a waveform: the front-end (text normalization, grapheme-to-phoneme, prosody prediction), acoustic models, neural vocoders and audio codecs, streaming and cancellation, voice cloning and voice design, expressive and multilingual control, and the evaluation and ethics that any serious deployment now requires.
Out of scope. Speech-to-text, voice activity detection, turn detection and endpointing, transport (WebRTC), and telephony (SIP) all belong to the pipeline, not to synthesis. Where a TTS decision depends on one of them, this list explains just enough to make that decision and no more. Turn detection is the clearest case: cancelling synthesis on a barge-in is a TTS concern and lives in Section 4, but deciding that a barge-in happened is a turn-taking concern that sits outside this list.
The boundary cases, and how they are handled. Voice cloning and voice conversion are treated as core TTS and included, scoped to synthesis rather than to speaker verification. Watermarking and cloning ethics stay in, because in 2026 they are inseparable from shipping a synthetic voice. Music and general audio generation stay out.
The inclusion bar. A resource earns a place if it is active within the last 12 months, accessible to a working developer, and either vendor-neutral or clearly labeled when authored by a commercial party. A provider earns a row if you can send it text and get back audio today, not on a waitlist.
Classical neural TTS is a three-stage pipeline: a text front-end (normalization, grapheme-to-phoneme, prosody prediction) feeds an acoustic model that predicts a mel-spectrogram, which a neural vocoder turns into a waveform. The central design choice is real-time versus offline: streaming and end-to-end architectures collapse or reorder these stages to emit audio within a couple hundred milliseconds for voice agents, whereas offline synthesis keeps the stages separate to maximize naturalness. Start here to build the mental model before comparing models or providers.
Every provider here is generally available today: send text, get audio back, no waitlist. The split that matters for a builder is architectural: providers built for turn-by-turn conversation now hit roughly 40 ms to 200 ms time-to-first-audio, while media and dubbing providers trade that latency for expressive range and long-form control. Pick from the first group for voice agents and the second for narration, dubbing, and produced content.
| Provider | Lean | Best for |
|---|---|---|
| ElevenLabs | both | Expressive Eleven v3 voices, dubbing, and a mature agent stack. |
| Cartesia Sonic 3.5 | real-time | Lowest-latency conversational TTS (40 ms Turbo, vendor). |
| Deepgram Aura-2 | real-time | Enterprise contact-center agents with on-prem option. |
| OpenAI TTS | both | Steerable delivery via instructions inside the OpenAI stack. |
| Rime | real-time | High-volume IVR with deterministic pronunciation control. |
| Hume Octave 2 | both | LLM-driven emotional prosody from text semantics. |
| Inworld TTS | real-time | Natural-language voice steering across 200+ languages. |
| Soniox TTS | real-time | Low-cost real-time synthesis paired with Soniox STT. |
| LMNT | real-time | Fast streaming plus voice cloning for agents and games. |
| Neuphonic | real-time | WebSocket-first low-latency TTS plus open-source on-device NeuTTS. |
| PlayAI | both | Multi-speaker conversational dialogue synthesis (PlayDialog). |
| Amazon Polly | both | AWS-native generative and neural voices with streaming. |
| Google Cloud TTS | both | Chirp 3 HD voices across 50+ locales on GCP. |
| Azure Neural TTS | both | 600+ voices, Dragon HD, SSML, and batch synthesis. |
| Murf | offline | Studio-grade voiceover with style and pacing control. |
| WellSaid Labs | offline | Enterprise narration for e-learning and corporate video. |
| Speechify | both | Large voice library and cloning for reading and media apps. |
| Resemble AI | both | Voice cloning plus the open-source Chatterbox model. |
Self-hostable TTS in 2026 spans two poles: tiny CPU-friendly models that stream in under a second, and large LLM-backbone models that clone a voice from a few seconds of reference audio. The single most important gating factor is the weight license, not audio quality, since several top open-weight models ship non-commercial or capped-usage terms that block production shipping. Read the per-model license note before you build, because permissive code often sits next to restrictively licensed checkpoints.
| Model | License | Best for |
|---|---|---|
| Chatterbox (Multilingual v3, Turbo) | MIT (code and weights) | Production voice agents needing low latency (vendor), 23 languages, and built-in watermarking. |
| Kokoro 82M | Apache 2.0 | Cheapest realtime TTS: 82M params, runs fast on CPU, 8 languages. |
| Piper | GPL v3 | Fully offline embedded and Raspberry Pi devices. |
| Coqui XTTS v2 (idiap fork) | Coqui Public ML License (non-commercial weights) | Zero-shot cloning across 17 languages from a maintained fork. |
| MeloTTS | MIT | Realtime CPU inference with multiple English accents. |
| Kitten TTS | Apache 2.0 | Ultra-light 15M to 80M ONNX models for edge and browser deploys. |
| Orpheus-TTS | Apache 2.0 | Emotive Llama-3B TTS with token-streaming for agents. |
| Sesame CSM-1B | Apache 2.0 | Context-aware conversational speech that conditions on dialogue history. |
| CosyVoice 2 / 3 | Apache 2.0 | Streaming LLM TTS with about 150 ms first-chunk latency (vendor) and strong Chinese and English. |
| Dia (Nari Labs, Dia 2 family) | Apache 2.0 | One-pass multi-speaker dialogue with laughs, sighs, and turns. |
| Fish Speech / OpenAudio S1-mini | Apache 2.0 code, CC-BY-NC-SA-4.0 weights | Low-WER multilingual cloning from a 10 to 30 s sample. |
| GPT-SoVITS | MIT | Best-similarity few-shot cloning from about 1 minute of audio. |
| F5-TTS | MIT code, CC-BY-NC-4.0 weights | Research and non-commercial flow-matching cloning; retrain to ship. |
| StyleTTS 2 | MIT | Human-level single and multi-speaker quality via style diffusion. |
| Parler-TTS | Apache 2.0 | Prompt-controllable voice attributes and a full open training stack. |
| Zonos / Zonos2 | Apache 2.0 | High-fidelity cloning; Zonos2 is a low-latency 8B-total MoE. |
| IndexTTS-2 | Bilibili Model License (commercial use needs separate grant) | Autoregressive TTS with precise duration and emotion-timbre control. |
| Higgs Audio v2 | Boson community license (commercial cap at 100k annual active users) | Expressive multi-speaker and speech-plus-music from a Llama-3.2-3B base. |
| MaskGCT (Amphion) | Amphion / research (CC-BY-NC weights) | Non-autoregressive masked-codec zero-shot TTS with no forced alignment. |
This is the section the rest of the field explains worst, and the one an agent builder needs most. For a voice agent, naturalness you cannot start playing in under 200 ms is naturalness the caller never hears. The metric that governs this section is time-to-first-byte (TTFB), the delay between sending text and receiving the first chunk of playable audio, not the total time to synthesize the full utterance. A model with beautiful output and a 900 ms first byte loses to a plainer model that starts speaking at 90 ms, every time, on a live call.
Read this section as three questions in order: how does streaming TTS actually work, how do you stop it mid-word when the caller interrupts, and how do you measure any of it honestly.
Not all streaming is the same, and the differences decide whether your agent can interrupt cleanly. There are three levels, and providers rarely tell you which one they ship.
The moment a caller interrupts, the audio already buffered has to stop within roughly 60 ms or the agent sounds like it talked over them. This is a TTS capability, not a turn-taking one: your provider either supports killing an in-flight synthesis stream or it does not, and you cannot know from the marketing page. Deciding that an interruption happened is a separate turn-detection problem; this subsection is only about stopping the sound once that decision is made.
A comparison table is the fastest way for a reader to pick. Keep the columns honest and measurable: real published TTFB, streaming mode from the taxonomy above, cancellation support, and transport. Do not reprint vendor latency claims without noting they are vendor claims.
| Provider | Streaming mode | Published TTFB | Mid-stream cancel | Transport |
|---|---|---|---|---|
| Cartesia Sonic | Dual-streaming | Sub-100 ms (vendor) | Yes | WebSocket |
| ElevenLabs Flash | Output-streaming | Sub-150 ms (vendor) | Yes | WebSocket |
| Deepgram Aura-2 | Output-streaming | Low (vendor) | Yes | WebSocket |
| Rime (Mist v3) | Output-streaming | ~37 ms TTFA (vendor) | Yes | WebSocket |
| OpenAI Speech API | Output-streaming | Unpublished | No (close connection) | HTTP |
| OpenAI Realtime API | Dual-streaming | Unpublished | Yes | WebRTC / WS |
Every latency figure above is a vendor claim until you measure it on your own traffic and your own network path. Treat this table as a starting shortlist, not a verdict. The methodology to replace these numbers with your own is in the next subsection.
The through-line of this whole list is that vendor benchmarks are tuned to flatter the vendor, and TTFB is where that distortion is worst, because it is measured under ideal network conditions the vendor controls. The only number you can trust is the one you produce against your own text, from your own region, over your real transport.
Voice cloning turns a short reference sample into a speaker, and voice design turns a text description into one, spanning open-source zero-shot models (as little as 5 seconds of reference) and commercial APIs with instant versus fine-tuned tiers. Cloning a voice without the speaker's consent is the ethical fault line for this entire section, so pair any tool here with the consent, watermarking, and disclosure practices in Section 14: Ethics, consent, and regulation. Each entry is marked open (self-hostable weights) or commercial (hosted API).
Expressive synthesis is where 2026 TTS diverges most sharply from the phoneme-and-pitch era: the field has shifted from hand-authoring SSML prosody tags toward natural-language style prompts and inline emotion tags that a language-model-based TTS interprets semantically. For builders this means less markup engineering and more prompt design, but SSML still matters for deterministic pauses, pronunciation, and rate control that free-text prompts cannot pin down. The resources below cover markup standards, prosody control, inline emotion and audio tags, and description-driven style prompting.
Multilingual TTS has converged on single models that speak dozens of languages from one checkpoint, but most open models still require you to declare one language_id per request, so true mid-utterance code-switching remains the exception rather than the default. The hard part is per-language phonemization (G2P): a model can share acoustics across languages while pronunciation quality tracks how good the grapheme-to-phoneme frontend is for each one. For the training corpora behind these models, see Section 10: Datasets.
Modern TTS is a story of one architectural choice repeated at every layer: generate the waveform one step at a time, or generate it all at once. Autoregressive models buy natural prosody with sequential latency, while non-autoregressive models (duration-predicted, diffusion, or flow-matching) buy parallel speed and now match them on quality. This section is explainer-first; the canonical papers themselves live in Section 9.
These are the papers behind the models developers actually run in production, from the autoregressive waveform era through today's codec language models and flow-matching systems. The field's center of gravity has shifted from mel-spectrogram pipelines to codec-LM and flow-matching architectures that deliver zero-shot voice cloning from a few seconds of reference audio. Read the Foundations first if you want to understand why modern systems are built the way they are.
Speech corpora are the raw material for training and fine-tuning TTS, and the license attached to a dataset matters as much as its hours. For a legally clean fine-tune, start with a permissive single-speaker or multi-speaker English corpus like LJSpeech (public domain) or LibriTTS-R (CC BY 4.0), then scale to large in-the-wild data like Emilia once your pipeline is proven.
Honest TTS evaluation pairs subjective listening tests (MOS, CMOS) with objective proxies (UTMOS for naturalness, ASR-derived WER for intelligibility, speaker-similarity SIM for cloning fidelity), then sanity-checks against public arena leaderboards. A vendor's own benchmark almost always flatters the vendor, and no published latency number substitutes for measuring time-to-first-byte on your own traffic, region, and text lengths (see Section 4).
The final synthesis stage turns acoustic features (mel spectrograms) or discrete tokens back into a waveform: GAN vocoders do this for feature-based TTS, while neural audio codecs supply the discrete token space that modern codec-LM TTS predicts over. Codec choice sets the latency and quality floor for codec-LM TTS, because frame rate fixes how many autoregressive steps per second the LM must run and the codec's reconstruction quality caps how good the output can ever sound.
Two jobs live here: marking synthetic speech at generation time so it stays attributable, and detecting synthetic or manipulated speech after the fact when no watermark survives. In 2026 the practical split is proactive watermarking (SynthID, AudioSeal, PerTh) for content you generate versus passive deepfake detectors for content you receive, and neither alone closes the gap. Watermarks are cheap to embed but removable by a motivated attacker, while detectors generalize poorly to unseen generators, so serious deployments run both and log provenance; consent and disclosure obligations are covered in Section 14.
Shipping a synthetic voice in 2026 is a legal question before it is a product question: disclosure and consent are no longer optional. The EU AI Act Article 50 transparency duties apply from 2 August 2026, the FCC has ruled that AI-generated voices in robocalls are artificial voices under the TCPA (so they need prior express consent), and the FTC plus new US likeness laws (the ELVIS Act, the pending NO FAKES Act) give people a direct cause of action over their cloned voice. These resources cover the specific obligations and the practical consent frameworks a builder needs before deploying a cloned or generated voice.
These are runnable, end-to-end guides for building one TTS system at a time, from your first synthesized clip to a fully fine-tuned custom voice. The fastest path to a working custom voice in 2026 is fine-tuning an existing checkpoint (VITS, XTTS, Piper, or Parler-TTS) on 20 minutes to a few hours of clean audio, not training from scratch. Finish one build before starting another: pick the model whose training story matches your data volume and deployment target, then follow its guide to completion.
Before you wire a TTS vendor into a voice agent, audition it: a blind arena or a vendor playground tells you more in five minutes than a datasheet does in an hour. Once you commit, the boring utilities (phonemizers, G2P, and text normalization) decide whether "$4.99 on 07/21" reads correctly, so treat them as first-class parts of the pipeline.
Vendors and researchers ship faster than any static list can track, so the people building TTS in 2026 stay current through blogs, Discords, and conference proceedings rather than documentation alone. The most useful signal for a working TTS developer comes from vendor engineering blogs and the open Discords where their engineers answer latency and cancellation questions directly. Every entry here carries an empty tag by convention, since currency matters more than difficulty for this section.
Pull requests welcome. Resources must be active in the last 12 months, accessible to developers, and vendor-neutral or clearly labeled when authored by a commercial party. A provider earns a row only if you can send it text and get audio back today, not from a waitlist. Open an issue to suggest additions or removals.
MIT. Fork it, ship it.
2 commits