Lightning v3.1 Pro
lightning_v3.1_pro_10_26 is in preview for English, Spanish and Hindi until 2026-11-28.
Premium 44.1 kHz text to speech on dedicated capacity: curated Indian, British and American voices, Hindi code-switching, 31 languages. Same latency and limits as Lightning v3.1. Start with the quickstart.
Who it’s for
- Voice agents and IVR where voice quality is the differentiator and the caller hears the brand.
- Products serving Indian, British and American English customers from one catalog, with Hindi code-switching.
Model Overview
Checkpoints
How checkpoints work
lightning_v3.1_pro always serves the current stable checkpoint. A dated ID such as lightning_v3.1_pro_10_26 lets you try a new checkpoint during its 30-day preview, and the checkpoint may receive updates during that time; the changelog lists them. When a preview is promoted, it becomes the stable lightning_v3.1_pro and the dated ID stays available for 30 more days. A new checkpoint can cover only some languages, and when it is promoted only those languages change. Enterprise customers who need more time can contact their account team to pin their current checkpoint.
For English (en), Spanish (es) and Hindi (hi) only, the lightning_v3.1_pro_10_26 preview becomes the stable lightning_v3.1_pro. From then on, use "model": "lightning_v3.1_pro" for these languages. Requests that omit language default to en + hi, so they move too. lightning_v3.1_pro_10_26 remains available for 30 more days, until 2026-12-28. The other 28 languages and auto stay on their current checkpoints, so their audio does not change and you don’t need to do anything for them.
lightning_v3.1_pro vs lightning_v3.1_pro_10_26
For any language other than English, Spanish or Hindi, use lightning_v3.1_pro.
Try the preview
Key Capabilities
Ultra-low latency architecture designed for conversational AI and live streaming.
HTTP, SSE, and WebSocket transports for real-time playback.
language: en → UK + American accented English. language: hi → Indian accented English + Hindi (code-switching). Omit → defaults to en + hi. Plus 29 additional languages via dedicated Pro voices - pass the ISO 639-1 code (e.g. ta, de, ja), or use auto for cross-language routing.
Broadcast-quality 44.1 kHz audio with natural prosody, intonation, and conversational rhythm.
Premium voices across American, British, and Indian accents.
Custom pronunciation dictionaries for specialized vocabulary, brand names, and domain-specific terms.
Performance & Benchmarks
Pro improves on standard Lightning v3.1 across accuracy, expressiveness, delivery, and MOS quality. Tables below pair Pro with the same competitor set documented on the Lightning v3.1 model card; refer to that card for Pro-vs-Standard comparisons. Open the accordion under each category to see what each metric measures.
Where 200 ms TTFB comes from. Measured from a client in the same AWS region as the inference pool (India ap-south-1, USA us-west-2, geo-routed by client location). Client-to-server round-trip time adds on top. A naive test from a laptop far from either region typically reports 500-800 ms because RTT dominates synthesis time. For a production-realistic number, measure from your production network position, not your dev machine.
Naturalness - higher is better
What each Naturalness metric measures
- Overall - Holistic listener rating of how natural the voice sounds end-to-end.
- Naturalness - How human-like the voice sounds; penalizes robotic or synthetic quality.
- Intonation - Whether pitch rises and falls appropriately for the sentence type (question, statement, exclamation).
- Prosody - The broader umbrella of rhythm, stress, and melody, how well the voice “reads” the sentence as a human would.
Expressiveness - higher is better
What each Expressiveness metric measures
- Overall - Holistic listener rating of how expressive the voice sounds given the context of the sentence.
- Paralinguistics - Non-verbal vocal elements like laughter, sighs, or filler sounds (“um”, “uh”) and whether they’re rendered appropriately.
- Emotions - How accurately the voice conveys the intended emotional tone (neutral, warm, urgent, etc.).
Delivery - higher is better
What each Delivery metric measures
- Boundary Consistency - Whether phrase and sentence boundaries are marked consistently with pauses or pitch shifts, without arbitrary breaks mid-phrase.
- Pronunciation Style - Not just correctness, but stylistic choices i.e., formal vs. casual register, regional accent consistency, honorific handling.
- Natural Pace - Whether the speaking rate feels comfortable and appropriate for the content type, neither rushed nor dragging.
- Pause Placement - Whether silences appear at semantically correct points (after commas, between clauses) rather than mid-word or mid-phrase.
- Breathing Naturalness - Whether breath sounds occur at realistic points and with realistic frequency, not absent entirely or inserted randomly.
Accuracy
Mixed direction - WER, CER, Hallucination, and Deletion are lower is better; Pronunciation % is higher is better.
Whisper jiwer
Whisper LLM
What each Accuracy metric measures
- WER (Word Error Rate) - Percentage of words in the transcript that differ from the reference; measures how faithfully the TTS renders the input text.
- CER (Character Error Rate) - Like WER but at the character level.
- Hallucination - Words or sounds the TTS generates that have no basis in the input text. Insertions, substitutions, or fabricated content.
- Deletion - Words from the reference text that the TTS dropped entirely.
- Pronunciation % - The proportion of words pronounced correctly out of total words.
- Whisper jiwer vs Whisper LLM - Two judging methodologies.
jiweruses raw Whisper-decoded transcripts; LLM-judged uses a follow-on LLM to normalize transcription noise. Both report the same metric family; LLM-judged tends to give lower error rates by reducing false positives from punctuation/casing.
MOS v2 - higher is better
Per-language head-to-head vs MiniMax speech-2.8-hd
Per-language advantage of Lightning v3.1 Pro over MiniMax speech-2.8-hd, male/female voices averaged per language. Emergent Win % is the share of samples where at least one AI judge preferred Lightning; the Advantage columns are the score margin above zero (higher is better; a negative value means MiniMax won that metric on that language).
What each column measures
- Emergent Win % - How often listeners preferred Lightning v3.1 Pro over MiniMax speech-2.8-hd when hearing both say the same thing. Above 50 = Lightning won more often than not. Scores averaged over a male and a female voice per language.
- Acc-LLM Advantage - How many fewer word mistakes per hundred words compared to MiniMax, judged with a language-aware LLM. Positive = ours is more accurate.
- Acc-jiwer Advantage - Same as Acc-LLM, but the word mistakes are counted automatically by software (
jiwer) rather than an LLM. Positive = ours is more accurate. - WV-MOS Advantage - Difference in overall sound quality, rated automatically by a quality-prediction model (WV-MOS). Positive = ours sounds cleaner.
- Audiobox-CE Advantage - Difference in how pleasant and enjoyable the audio is to listen to (Content Enjoyment score). This score matches human opinions best in our testing. Positive = ours is more enjoyable.
- Audiobox-PQ Advantage - Difference in recording/production quality (e.g. how clean and professional the audio sounds). Positive = ours is cleaner.
On Norwegian, Swedish, and Malay, MiniMax does not have native voices for these languages, so its English voices were used to speak them. The test sentences for these three languages were also machine-translated from English.
What each MOS metric measures
- Mean MOS - Mean Opinion Score: average listener rating on a 1–5 scale across the test set; the canonical aggregate quality metric in TTS evaluation.
- UTMOS - A predicted MOS from the UTMOS reference model - an automated proxy for subjective quality.
- WV-MOS - A predicted MOS from the WavLM-based WV-MOS reference model - another automated proxy commonly reported alongside UTMOS for cross-validation.
Want to reproduce these results? See the TTS evaluation script to measure TTFB and synthesis quality in your own environment.
lightning_v3.1_pro_10_26 vs other providers
Each value is the share of judged comparisons that the lightning_v3.1_pro_10_26 preview checkpoint won against that provider, with male and female voices combined. 50% is on par and higher favours Lightning; N/A means that provider has no voice for the language.
† OpenAI US English: clean sentences only.
Supported Languages
Pass the language body parameter to steer the Pro pool’s output:
Additional Pro languages
29 additional languages have dedicated Pro voices. Pass the ISO 639-1 code in the language body parameter and pick a voice_id from the matching Voice Catalog section. Pass auto to route across all supported languages using any English or Hindi voice.
Indic - 9 languages
Asian & Middle Eastern - 8 languages
European - 12 languages
Dutch and Swedish accept the codes on Pro; voice-count data pending as new Pro voice trains for those roll out.
For other languages, use the standard Lightning v3.1 model (20 accepted codes; 12 with a trained voice catalog).
Voice Catalog
The Pro voice catalog is distinct from standard Lightning v3.1. Voices below are listed in recommended ranking per accent group.
Recommended voices for lightning_v3.1_pro_10_26
Every Pro voice works on the preview checkpoint. These give the best results, listed best first.
Indian - Female
Indian - Male
British - Female
British - Male
American - Female
American - Male
Indian Languages - 67 voices
Pair each voice with its matching language code (e.g. "language": "ta" with a Tamil voice).
Asian & Middle Eastern Languages - 21 voices
European Languages - 61 voices
Need a voice not in this list? Use the standard Lightning v3.1 catalog (217 voices, more languages). Pass "model": "lightning_v3.1" (or omit the field) instead of lightning_v3.1_pro. Both pools support voice cloning.
API Reference
Endpoints
See Synthesize Speech for the full request/response schema, supported parameters, and error codes. To route to the Pro pool you must set model to lightning_v3.1_pro (or lightning_v3.1_pro_10_26 for the preview checkpoint: English, Spanish, Hindi) explicitly - the field is optional but defaults to standard Lightning v3.1.
Best Practices
Voice ID + model pairing
Pair Pro voice IDs above with "model": "lightning_v3.1_pro" (or "model": "lightning_v3.1_pro_10_26" for the preview checkpoint). The API does not currently reject mismatched pairings, but pairing a Pro voice with "model": "lightning_v3.1" (or omitting model) can produce wrong or hallucinated audio. Server-side validation is on the roadmap.
Language selection
language: en→ UK + American accented English. Pair with British or American Pro voices for best results.language: hi→ Indian accented English + Hindi with native code-switching mid-utterance. Pair with Indian Pro voices.- Any additional Pro language (e.g.
language: ta,language: de,language: ja) → native synthesis in that language. Always pair with a Pro voice from that language’s Voice Catalog section. - Omit
language→ defaults toen + hi. Sensible when you don’t know the input language ahead of time.
Per-voice metadata still lives in tags.language on the voice catalog (GET /waves/v1/lightning-v3.1/get_voices). The body parameter sets the target language for the synthesis pass; the voice ID controls the timbre and accent of the speaker.
Text Formatting
- Chunk boundaries. Segment input at natural prosodic boundaries (
.!?,). Maximum chunk size is 250 characters; optimal throughput at 140 characters per request. - Script integrity. Use native script for each language. Mixed-script input within a single language token produces unpredictable phoneme mappings.
- Lexicon overrides. Use pronunciation dictionaries for domain-specific terms, brand names, and acronyms where default grapheme-to-phoneme conversion is insufficient.
For comprehensive text formatting rules (numeric handling, date/time, symbols, chunking logic), see TTS Best Practices.
Use Cases
FAQ
How is Lightning v3.1 Pro different from standard Lightning v3.1?
Pro runs on dedicated inference capacity, isolated from general Lightning traffic, and ships a curated premium voice catalog with improved naturalness. Concurrency, latency, and rate-limit ceilings are identical to standard Lightning v3.1 - the difference is voice quality and the catalog.
How do I route requests to the Pro pool?
Set model to lightning_v3.1_pro explicitly. The field is optional, but it defaults to standard Lightning v3.1 - for Pro you must pass it on every request.
Can I pair any voice with the Pro model?
Pair Pro voice IDs with "model": "lightning_v3.1_pro". The API does not currently reject mismatched pairings, but pairing a Pro voice with "model": "lightning_v3.1" (or omitting model) can produce wrong or hallucinated audio. Server-side validation is on the roadmap.
Does Lightning v3.1 Pro support voice cloning?
Yes. Pass model: lightning-v3.1-pro to the voice-cloning API to clone onto the Pro pool, then use the resulting voice_id with TTS model: lightning_v3.1_pro. The default is lightning-v3.1.
Which languages does Lightning v3.1 Pro support?
Set language: en for UK + American accented English, or language: hi for Indian accented English + Hindi with native code-switching. Omitting language defaults to en + hi.
Are word-level timestamps supported on Pro voices?
Pro shares the Lightning v3.1 base-queue voices for English + Hindi (meher, devansh, kartik, maithili, liam, avery), so word events emit on those. Other Pro-only voices fall back to silent graceful degradation - audio is normal, but no word events are emitted.
What is lightning_v3.1_pro_10_26?
It is a new Lightning v3.1 Pro checkpoint for English (en), Spanish with English code-switching (es) and Hindi with English code-switching (hi), in preview until 2026-11-28. Try it by passing "model": "lightning_v3.1_pro_10_26" with one of those language values. Every Pro voice works on it; the recommended voices give the best results. On 2026-11-28, it becomes the stable lightning_v3.1_pro for English, Spanish and Hindi only, including requests that omit language, so use "model": "lightning_v3.1_pro" from then on. lightning_v3.1_pro_10_26 remains available for 30 more days, until 2026-12-28. See Checkpoints.
Will my integration change on 2026-11-28?
Only if you call lightning_v3.1_pro with language set to en, es or hi, or without language. On 2026-11-28, the lightning_v3.1_pro_10_26 preview becomes the stable lightning_v3.1_pro for English, Spanish and Hindi, and those requests start using it, so test lightning_v3.1_pro_10_26 before then. You don’t need to change the model value. If you are already calling lightning_v3.1_pro_10_26, switch to lightning_v3.1_pro by 2026-12-28; the preview ID remains available for 30 days after promotion. Enterprise customers who need more time can contact their account team to pin their current checkpoint.
I use other languages or auto on lightning_v3.1_pro. Does anything change?
No. Only English, Spanish and Hindi move to the new checkpoint. All other languages and auto stay on their current checkpoints, and no action is needed.
Safety & Compliance
Known Limitations
- Larger, curated catalog on standard v3.1. The Pro catalog is intentionally smaller. For the widest voice selection and more languages, use standard Lightning v3.1.
Lightning v3.1 Pro must not be used for impersonation or fraud, generating deceptive audio content (deepfakes), creating content that violates consent or privacy, harassment or abuse, or any illegal or unethical purposes.
Compliance
- No retention of synthesized audio
- Usage monitoring for policy compliance
- Enterprise plans can stop input text being stored, expire it after a window, or expire a single request with the
x-expire-contentheader. See Zero Data Retention
For compliance documentation (GDPR, SOC2, HIPAA), contact support@smallest.ai.