Persian TTS datasets
A Persian voice reading formal written text sounds like a news bulletin, which is the wrong register for almost every conversational use. The script is written in the spoken register, and the speaker is selected for conversational delivery rather than for broadcast clarity. Getting this wrong is not a matter of polish. It decides what the voice can be used for.
What TTS work in Persian requires
Speaker consistency across sessions
A voice recorded over several days drifts in pitch and pacing. If the target is one synthetic voice, either record in fewer, longer sessions or plan to re-record segments that fall outside tolerance.
Text the speaker can read fluently
A speaker reading unfamiliar script produces disfluencies that end up baked into the synthetic voice. Script selection matters as much as recording quality.
Phonetic coverage, not just volume
A long recording can still miss phonemes that are rare in running text. Coverage has to be checked against the language's inventory, not against word count.
The mistake that costs the most
The most common mistake is buying many hours from many speakers when the goal needed a few hours from one speaker, recorded properly.
The language-specific factor
Written Persian and spoken Tehrani Persian are far apart: verb endings, pronouns, and connected speech all shift in the colloquial form. Transcribing spoken recordings against the written form produces text that does not match the audio.
Specification checklist
| Language | Persian |
|---|---|
| Writing system | Arabic (Perso-Arabic) |
| Region | Middle East & North Africa |
| Core keyword | TTS dataset |
| Must specify | Distinct speaker count, recording conditions, annotation convention, delivery format |
| Included by default | Pilot batch, speaker metadata, consent documentation, annotation guideline |
Related
-
Persian speech data
The full overview for this language, including what makes it hard to collect.
-
Multilingual speech
Running this alongside other languages in one delivery.
-
WER
How recognition quality is measured, and what the number does not tell you.
Request Persian TTS data
Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline, not a range. If we cannot source it well, we will tell you that instead.
- Pilot batch before the full run, so problems surface early.
- Consent documentation delivered with the data.
- No medical or clinical data. No recorded telephone calls.
- You send the spec Language, hours, recording conditions, and the deadline.
- We reply within two business days A real number and a real timeline, not a range.
- You approve a pilot batch A small run first, so problems surface before the full order.
- Full run, then delivery with documents Audio, transcripts, and the consent record for every speaker.