← Back to Blog

TTS & STT Landscape in Spring–Summer 2026: On-Device Breakthroughs, API Consolidation, and Open-Source Acceleration

  • tts
  • stt
  • offline
  • open-source
  • supertonic
  • kokoro
  • grok
  • gemini
  • realtime-api
  • on-device
  • whisper
  • voice-cloning
  • browser
  • arena

If 2025 was the year TTS became “usable,” the first half of 2026 is when it hit an inflection point. On-device engines are approaching cloud quality faster than most predicted. Cloud APIs are collapsing the three-stage STT→LLM→TTS pipeline into a single call. Open-source models are covering capabilities — emotion control, multi-speaker dialogue, zero-shot voice cloning — that were exclusive to commercial APIs just months ago. And all of this is happening simultaneously.

Here is the TTS/STT landscape as of mid-2026, based on offlinetts.com’s blog coverage.


1. On-Device TTS: Two Flagship Releases and a Steady Workhorse

1.1 Supertonic — 99M Parameters, 31 Languages, 167× Real-Time

Supertonic (by Supertone Inc.) is the most technically impressive on-device TTS release of the season. It runs on ONNX Runtime for fully local inference.

DimensionSpec
Model size~99 million parameters (99M)
Inference speed167× real-time — 1 hour of audio in ~22 seconds
Languages31
Run targetsRaspberry Pi, phone, browser (WebGPU / WASM)
Latest versionSupertonic 3: improved accuracy and language coverage
Custom voicesVoice Builder tool from short reference clips

OfflineTTS integrated Supertonic on May 13, initially supporting 5 languages (English, Spanish, Portuguese, French, Korean) with 10 preset voice styles. Two core knobs control the quality/speed trade-off — Steps (denoising passes) and Speed (speech rate):

StepsBest ForTrade-off
4–8Quick drafts and previewsFastest, less refined
8 (default)Everyday useBalanced quality and latency
12–20Final exportsSmoother but slower

Model assets are cached in IndexedDB after first load, so repeat visits skip re-downloads.

Bottom line: For any use case where privacy, latency, or offline operation is a requirement, Supertonic has become the benchmark that other on-device solutions are measured against.

1.2 ToBe SAID — Fully Offline Android TTS Engine

Unlike Supertonic’s developer focus, ToBe SAID delivers a polished end-user experience as a system-level Android TTS engine. It runs entirely on-device and is built around ebook-to-audiobook conversion. Recent updates significantly improved voice stability and naturalness. The free tier covers one voice slot; Pro unlocks unlimited slots.

1.3 Kokoro TTS — The On-Device Workhorse

Kokoro is built on StyleTTS 2 architecture — 82M parameters, 82MB ONNX model, and the most mature ecosystem among browser-runnable TTS engines:

  • 88 voices, graded A–D by quality
  • 9 languages: English (US/UK), Japanese, Chinese, French, Spanish, Hindi, Italian, Portuguese, Korean
  • Run modes: browser (WebGPU / WASM), Python CLI, API ($0.65/1M chars)
  • License: Apache 2.0

Top English A-grade voices:

VoiceAccentBest For
HeartAmericanAudiobook narration, YouTube voiceovers
BellaAmericanConversational content, podcasts
NovaAmericanProfessional presentations, e-learning
NicoleBritishBritish narration, formal content

TTS Arena performance:

Kokoro ranks 32nd overall (Elo 1056) out of 74 models — but it is #1 among browser-runnable models. It excels at knowledge-sharing content (articles, docs, education) with Elo 1066, outperforming Google WaveNet (873) and Amazon Polly Neural (868).

CategoryAccentEloWin Rate
Knowledge sharingAll1065.857.1%
AssistantsAll1065.850.9%
Customer serviceUS1135.446.0%

For anyone who wants TTS without cloud APIs or GPU servers, Kokoro is the most pragmatic choice available.


2. Cloud APIs: Consolidation, Speed, Emotion

xAI Grok TTS & STT — A New Contender

xAI entered the voice API market in May with Grok TTS and STT, emphasizing speed, multilingual accuracy, and easy integration (already available through Telnyx for telephony apps). The message is clear: major AI platform companies now treat voice I/O as a core capability, not an add-on.

OpenAI Realtime API — Single-Call Architecture

This is the most architecturally significant shift this year. The traditional voice agent pipeline:

STT (speech→text) → LLM (reasoning+generation) → TTS (text→speech)

Each hop adds latency and integration overhead. The Realtime API compresses this into one call: speech in, speech out.

DimensionTraditional PipelineOpenAI Realtime API
API calls3+1
LatencyCumulative per hopEnd-to-end optimized
OrchestrationHigh (WebSocket management)Low
Best fitWhen cloud is acceptablePrivacy-sensitive still needs on-device

Gemini 3.1 Flash TTS — Emotional Control at Scale

Google’s Gemini 3.1 Flash TTS brings two breakthroughs:

  1. 70+ languages — one of the broadest cloud TTS coverages available
  2. Fine-grained emotional control — adjusts tone, emphasis, and affect to match content context

This upgrades TTS from “listenable” to “engaging.” In the Artificial Analysis TTS Arena it ranks #2 with 1205.8 Elo, just 4 points behind Inworld Realtime TTS 1.5 Max (1209.6).

Other Commercial API Notes

  • ElevenLabs v3: Quality benchmark (1178 Elo), but $100/1M chars — most expensive
  • MiniMax Speech 2.8 HD / Turbo: Solid top-10 performers (1163.7 / 1146.7 Elo)
  • Azure Speech Service: Expanding language coverage, enterprise SLAs

3. TTS Arena Leaderboard Deep Dive

The Artificial Analysis Speech Arena ranks 74 models by Elo through blind A/B listening tests — the most objective TTS quality benchmark available.

Top 10 (All Closed-Source Commercial)

RankModelCreatorEloWin RatePrice/1M chars
1Realtime TTS 1.5 MaxInworld1209.673.3%$35
2Gemini 3.1 Flash TTSGoogle1205.872.4%$36.61
3Eleven v3ElevenLabs1178.068.9%$100
4Inworld TTS 1 MaxInworld1165.466.1%$35
5Speech 2.8 HDMiniMax1163.765.2%$100
6Realtime TTS 1.5 MiniInworld1158.466.2%$25
7Step TTS 2StepFun1149.164.6%$40
8Speech 2.8 TurboMiniMax1146.764.0%$60
9Speech 2.6 HDMiniMax1133.562.1%$100
10Speech 2.6 TurboMiniMax1128.761.3%$60

Open-Weight Model Standings

Overall RankModelCreatorEloWin RateNotes
11Fish Audio S2 ProFish Audio1128.761.0%Best open-weight; needs GPU
32Kokoro 82M v1.0Kokoro1056.254.4%Browser-runnable, 82MB
33Voxtral TTSMistral1055.952.3%Released March 2026
35Maya1Maya Research1050.650.5%
51Fish Speech 1.5Fish Audio1011.949.1%
52ChatterboxResemble AI1006.447.9%
55Zonos v0.1Zyphra1000.047.1%
60OpenVoice v2OpenVoice949.944.0%
66XTTS v2Coqui885.936.4%
67StyleTTS 2StyleTTS878.837.4%
74MetaVoice v1MetaVoice765.221.5%

The Gap Is Shrinking — Fast

EraBest Open-Weight EloBest Commercial EloGap
2023879 (StyleTTS 2)1102 (OpenAI TTS-1)223
2024950 (OpenVoice v2)1107 (ElevenLabs v2)157
Early 20251006 (Chatterbox)1134 (MiniMax Speech 2.6 HD)128
Mid 20251056 (Kokoro)1170 (Eleven v3 pre)114
Early 20261129 (Fish Audio S2 Pro)1210 (Inworld RT 1.5 Max)81

From 223 to 81 — a 64% reduction in under 3 years. At the current trajectory, an open-weight model could crack the top 10 within a year.

⚠️ Caveat: Elo measures listener preference, not objective quality. It does not capture latency, privacy, cost at scale, language coverage, or browser-deployability — factors that matter enormously in production.


4. Open-Source Model Ecosystem: MOSS-TTS and Beyond

MOSS-TTS Family (OpenMOSS / MOSI.AI)

The most ambitious open-source speech generation effort today — not a single model but a family:

VariantCore Capabilities
MOSS-TTSHigh-fidelity long-form speech, multi-speaker dialogue, real-time streaming TTS, sound design
MOSS-TTS-NanoLightweight variant for mobile and embedded devices

Key capabilities:

  • Long-form fidelity — sustained quality across extended passages, solving the “starts good, degrades after a few sentences” problem
  • Multi-speaker dialogue — distinct voices within a single generation, no stitching needed
  • Real-time streaming — chunk-by-chunk output with minimal buffering
  • Sound effects — non-speech audio generation for games and media production

Also active: Chatterbox, Fish Audio S2 Pro, Kokoro, and Zonos all continue to receive community updates.


5. Browser-Based STT: The Technical Landscape

Browser-based speech recognition has moved from demo-grade to production-ready in 2026.

How It Works

Three stages:

  1. Audio capture & decoding — microphone or file → mono 16kHz PCM (Whisper’s expected format), WebCodecs for hardware acceleration
  2. Neural inference — Whisper encoder-decoder via ONNX Runtime Web, WebGPU preferred, WASM fallback
  3. Post-processing — raw tokens → text, timestamp tokens → segment boundaries, long audio via 30s sliding windows

Model Family Comparison

LibraryModelsLanguagesModel SizeWebGPUStreamingWorker-Based
transformers.jstiny/base/small/large9940–3000 MB
browser-whispertiny/base/small9940–240 MB
Whisper.cpptiny~large-v39939–3000 MBNative
Moonshinetiny/baseEnglish only6–61 MB
Distil-Whispersmall/mediumEnglish only185–760 MB

Model Size vs. Accuracy

ModelParametersDownload (hybrid quant)Relative AccuracyWebGPU RT Factor
Whisper Tiny39M~40 MBAdequate for clear speech10–15×
Whisper Base74M~76 MBBest balance for most use cases5–8×
Whisper Small244M~240 MBHandles accents/noise best2–4×

Why Quantization Matters More Than You Think

ONNX models can be quantized to reduce size, but not all parts should be quantized equally:

  • Encoder (feature extractor): Quantization-sensitive — fp32 recommended. Quantizing to q8 degrades feature quality, producing garbled output on accented or noisy audio.
  • Decoder (text generator): Quantization-tolerant — q4 or q8 both work; q4 is significantly smaller.

This is why browser-whisper defaults to hybrid quantization (fp32 encoder + q4 decoder). A full q8 model at ~300 MB is not just larger — it can produce worse transcriptions than the 76 MB hybrid version, because encoder quantization noise propagates through the entire decoder stack.

WebGPU vs WebAssembly

WebGPU provides 5–10× speedup over WASM for Whisper, but browser support is uneven:

BrowserWebGPU Support
Chrome 113+ / Edge 113+✅ Best performance
Safari 17.4+✅ macOS and iOS
Firefox❌ Behind a flag
Linux Chrome⚠️ Needs --enable-unsafe-webgpu

A robust production implementation must fall back to WASM gracefully.

Two Common Issues with Long Audio

  1. Hallucination: Whisper can generate repetitive nonsense text at chunk boundaries or in silent regions. In transformers.js v3.8.1, SuppressTokensLogitsProcessor is commented out, leaving 90 hallucination-prone tokens unsuppressed. browser-whisper applies correct pipeline configuration to mitigate this.

  2. Timestamp drift: At chunk boundaries, timestamps can drift or overlap, requiring post-processing for subtitle formats (SRT/VTT).

Production Architecture Recommendations

  • Most use cases: browser-whisper + whisper-base + hybrid quantization
  • Maximum accuracy: browser-whisper + whisper-small
  • Slow connections / fastest first load: whisper-tiny
  • Real-time streaming (live captions): Moonshine
  • Server-side deployment: Whisper.cpp

6. Voice Cloning: Three Engines Compared

Voice cloning is now fully achievable offline. OfflineTTS compared three leading engines in detail.

At a Glance

DimensionKokoCloneKitten Fine-TunePiper Express Clone
MethodZero-shot (speaker encoder)Full fine-tuningSynthetic data + fine-tune
Reference audio3–10 seconds5–30 min (transcribed)3–10 seconds
Training needed?❌ No✅ 6–12 hours✅ 2–4 hours
GPU needed?❌ CPU works✅ 8–40GB VRAM✅ Recommended 8–12GB VRAM
Clone qualityGoodGood (with enough data)Best
Inference speed~150ms/10s text (CPU)Very fast (tiny model)Real-time on CPU
Model size~84MB20–30MB~75MB
Multi-language✅ 9 languages❌ Single

Detailed Breakdown

KokoClone — Zero-Shot Instant Cloning

KokoClone uses an ECAPA-TDNN speaker encoder to extract acoustic features from a short audio sample, producing a speaker embedding that plugs directly into Kokoro’s existing decoder. No retraining needed.

from kokoclone import KokoClone

clone = KokoClone(device="cpu")
audio = clone.text_to_speech(
    text="Hello, this is my cloned voice.",
    ref_wav="my_voice.wav",
    language="en"
)

Best for: Rapid prototyping, personal assistants, IoT devices. Clone quality depends heavily on reference audio quality.

Kitten TTS — Fine-Tuning for Tiny Footprints

Kitten is a lightweight VITS architecture (15M params, 15–80MB). No zero-shot mechanism — you need 5–30 minutes of transcribed audio and 6–12 hours of GPU training. The output is a 20–30MB model that runs extremely fast on CPU.

Best for: Embedded systems, mobile apps, Raspberry Pi Zero — where size and speed matter more than setup convenience.

Piper Training Suite — Express Clone

Two-stage pipeline:

  1. Chatterbox generates 1,500+ synthetic training clips from 3–10 seconds of reference audio
  2. Piper fine-tuning runs 300–500 epochs, exports a standard ONNX model
# One-command clone
python cloneToPiper.py MyVoice ./reference.wav \
    --samples 200 --epochs 500 --quality high --language en-us

# Use the cloned voice
piper -m ./exports/MyVoice.onnx -t "This is my cloned voice"

Highest quality among the three, but requires 2–4 hours of training.

Best for: Audiobook production, customer service voice bots, game character voiceovers.

Decision Framework

  • Need the voice now? → KokoClone (seconds, no GPU)
  • Highest possible quality? → Piper Express Clone (fine-tuning > zero-shot)
  • CPU only? → KokoClone (only option)
  • Embedded / smallest footprint? → Kitten (20–30MB)

7. Developer Decision Guide

Combined across all the trends above, here’s how to choose your stack in mid-2026:

Your ScenarioTTS PickSTT PickRationale
Offline / privacy non-negotiableSupertonic / KokoroWhisper variant (browser-whisper)Quality is production-grade; data never leaves the device
Highest quality, cloud OKGemini 3.1 Flash / ElevenLabs v3OpenAI Whisper APIBest emotional expressiveness or overall naturalness
Building a voice agent, fastOpenAI Realtime API (single call)Built-inEliminates 3-service orchestration
Browser-first user experienceKokoro / Supertonic (both WebGPU)browser-whisperZero install, zero config, fully offline
Low-cost at scaleKokoro self-hosted ($0.65/1M chars)Whisper.cpp100×+ cost reduction vs commercial APIs
Voice cloning (quick)Kokoro + KokoClone3–10 seconds of reference audio
Voice cloning (high quality)Piper Training SuiteTrain once, deploy everywhere
Embedded / IoTKitten TTS / MOSS-TTS-NanoMoonshineTiny models, extremely fast inference

8. Summary

The most important trend of H1 2026 is not any single release — it’s convergence:

On-device quality is catching up to cloud. The Elo gap has shrunk from 223 to 81 — a 64% reduction — and open-weight models could crack the top 10 within a year.

Cloud APIs are simplifying architectures. The three-stage pipeline is becoming a single call, making voice agent development dramatically easier.

Open-source models now cover formerly commercial-only capabilities. Emotion control, multi-speaker dialogue, zero-shot voice cloning — all achievable locally.

The browser is becoming a viable runtime. WebGPU enables 82MB TTS and 76MB STT models to run in a browser tab in real-time, offline, with zero installation.

The result is a TTS/STT ecosystem that offers better options at every point on the quality–cost–privacy spectrum. Whether you are building a voice assistant, an audiobook platform, a video dubbing tool, game characters, or an accessibility feature:

If you haven’t put voice in your product yet, 2026 is the year to start.


Based on offlinetts.com blog coverage (April–May 2026). Sources include official announcements from xAI, OpenAI, Google, and Supertone; the Artificial Analysis Speech Arena leaderboard; GitHub repository activity; and community discussions.

Reference Articles (from offlinetts.com)

TitleDate
TTS & STT Landscape in May 20262026-05-08
Supertonic TTS Is Now Available on OfflineTTS2026-05-13
Kokoro TTS: Complete Guide2026-05-07
TTS Arena Leaderboard 20262026-05-06
Browser Speech Recognition in 2026: Whisper and the STT Landscape2026-04-28
Voice Cloning with Offline TTS: Kokoro, Kitten, and Piper Compared2026-04-25

Share this article

Frequently Asked Questions

What is the best on-device TTS engine in mid-2026?
Supertonic (99M params, 167x real-time, 31 languages) is the most technically impressive on-device TTS engine as of mid-2026. It runs on ONNX Runtime, supports WebGPU/WASM in browsers, and can run on a Raspberry Pi. For a more mature ecosystem with the widest voice selection, Kokoro (82M params, 88 voices, 9 languages) is the most pragmatic choice.
How does open-source TTS compare to commercial APIs in 2026?
The gap is shrinking fast. In 2023, the best open-weight model (StyleTTS 2, 879 Elo) trailed the best commercial model by 223 Elo points. By early 2026, Fish Audio S2 Pro (1129 Elo) is only 81 points behind Inworld Realtime TTS 1.5 Max (1210 Elo) — a 64% reduction in the gap. Open-weight models could crack the TTS Arena top 10 within a year.
What is the OpenAI Realtime API and why does it matter?
It replaces the traditional three-stage pipeline (STT → LLM → TTS) with a single API call that takes speech in and returns speech out. This eliminates orchestration complexity, reduces latency, and dramatically simplifies voice agent development — though it requires cloud connectivity.
Which Whisper variant should I use for browser-based STT?
browser-whisper with the whisper-base model and hybrid quantization (fp32 encoder + q4 decoder) is the recommended default. It runs in Web Workers, supports streaming output, and the 76MB model transcribes at 5-8x real-time on WebGPU. For maximum accuracy, use whisper-small.
What offline voice cloning options are available in 2026?
Three main options: (1) KokoClone — zero-shot, instant, CPU-only, 3-10 seconds reference audio, good quality; (2) Piper Express Clone — synthetic data + fine-tuning, highest quality, 2-4 hours training, requires GPU; (3) Kitten TTS fine-tuning — 20-30MB output, best for embedded/IoT, 6-12 hours training.

Try OfflineTTS

Free. Private. Works offline. 54 voices in 9 languages.

Open TTS Tool

Sponsored

Ads help keep OfflineTTS free to use.