Persian data for AI training, collected to your brief
Persian data from IndecalAI is collected or reviewed by a native Persian speaker, not pulled from an existing archive. We work with speakers across the Middle East and Central Asia, where a formal written register and everyday speech can diverge sharply, matched to your brief and checked before delivery.
What Persian data can we produce?
Persian data from IndecalAI is speech, text, conversational and translation data collected or reviewed by a Persian speaker for your brief, not pulled from an existing archive.
A formal written register and everyday spoken language can differ sharply in this region, so we ask upfront whether you need the standard written form, a regional spoken variety, or both.
This sits across several of our services depending on what you need: data collection for raw speech or text, conversational AI data for dialogue, and translation and localization for converting between Persian and another language.
Translation projects often pair this language with English or another regional language. See translation and localization for that scope.
Persian data at a glance
- Data types
- Speech, text, conversational, translation
- Services
- Data collection, Translation
- Who works on it
- Contributors from our network of 30,000+ people worldwide, matched to your brief.
- Review
- A review pass before anything is delivered.
- Your data
- NDA first, used only for the agreed scope, returned or deleted when you ask.
- First step
- A small free sample before you commit.
What to know about Persian before you brief it
Persian, called Farsi in Iran, Dari in Afghanistan and Tajik in Tajikistan, is a language with a rich classical literature that is still read and recited today.
Everyday Tehran speech differs a great deal from the formal written language, with shortened verb forms and different pronunciation, so spoken data should be transcribed with a clear rule about whether to write speech as heard or to standardize it. Persian spelling also depends on a zero-width non-joiner that stops letters from joining, and text that loses it looks wrong. Iranian and Afghan usage differ, so name the audience.
Languages that sit close to Persian in script, family or region: Tajik data, Pashto data, Kurdish data, Urdu data, Arabic data and Azerbaijani data.
Deciding what to specify for any language? The guide to speech data collection covers the choices that apply across languages, and the one on transcription for AI and for people covers how speech becomes text.
Persian at a glance
- Language family
- Indo-European (Iranian)
- Script
- Perso-Arabic script, right to left
- Spoken mainly in
- Iran, Afghanistan (as Dari) and Tajikistan (as Tajik)
- Name it in a brief
- Iranian Persian (Farsi), Dari in Afghanistan, Tehran colloquial speech
- Its own name
- فارسی
Four ways to request Persian data
Each links to the service that runs it, with its full scope and process.
Persian speech data
Recorded speech in Persian: calls, prompts and voice bot utterances, in either the standard written register or a regional spoken variety, to your brief.
Persian text data
Written Persian: messages, reviews, tickets or chat logs, written or labeled by people who read it natively.
Persian conversational data
Scripted or spontaneous Persian dialogue for voice bots and support agents, in the formal or everyday register your brief calls for.
Persian translation
Human-verified translation between Persian and another language, covering both formal and everyday registers.
What to put in a Persian brief
Four things worth deciding before contributors start, so the first sample already looks right.
Region or dialect
Persian is spoken mainly in Iran, Afghanistan (as Dari) and Tajikistan (as Tajik). Worth naming in a brief: Iranian Persian (Farsi), Dari in Afghanistan, Tehran colloquial speech. Tell us the region or community you're targeting so contributors are matched to the right one.
Script or transliteration
Script for Persian: Perso-Arabic script, right to left. Say whether you want the native script, a transliterated version, or both, especially if your downstream system only reads one.
Data type mix
Speech, text, conversational and translation can be requested together or on their own. Tell us the mix your model needs.
Volume and timeline
A rough sense of how much data and how soon lets us staff the right number of contributors from the start.
From your brief to reviewed Persian data
One named contact owns the project from scoping to the last file.
Brief
You tell us the data type, the Persian variety or region and roughly how much you need.
NDA and scope
We sign an NDA before any data moves, then agree the scope with you.
Free sample
We produce a small sample free, so you can check it before you commit.
Production
Contributors from our network work in our own tools, to the brief you set.
Review
A review pass runs before anything is delivered.
Delivery
The data comes to you, or moves on to another service with us.
Where Persian data ends up
Common jobs for Persian data. They're examples of the work, not a client list.
Voice bots and IVR
Recorded Persian prompts and calls teach a voice bot to recognize how people actually speak, not just how a script reads.
Support chat and tickets
Everyday Persian messages, written in the domain you work in, give a chat assistant real phrasing to learn from.
Content moderation and sentiment
Labeled Persian posts, reviews and messages teach a model to read tone and intent correctly in this language.
Localizing a product
Translating prompts, UI copy and training data into Persian so a product reads like it was written for that market, not machine-translated.
Off-the-shelf Persian data, or built to your brief?
We hold around 35,000 hours of off-the-shelf speech, prompts and conversations already collected across our network, and roughly 500 hours of it is Persian: see the Persian speech dataset. Here's how the two paths compare.
| Topic | A typical off-the-shelf dataset | Persian data with us |
|---|---|---|
| Already collected? | No way to know until you've already paid for it | Yes: roughly 500 hours of Persian speech are already recorded, and we tell you what they cover before you buy |
| Fit to your brief | Built for whoever bought it first, not your exact region, register or use case | Collected or reviewed to the region, script and format you specify |
| Who else has it | The same files can be sold to more than one buyer | Custom collections are scoped to your engagement. For stock data, who else can license it is set in your licence |
| Checking the fit | You find out after you've already paid for it | A small free sample first, so you check it before committing to volume |
Persian data terms, in plain words
General definitions. They describe the field, not a claim about us.
Where Persian data fits
Persian is one of 100 languages on our languages directory. You can also browse every category on the datasets hub.
Questions about Persian data
The datasets FAQ covers questions that apply across every category.
Do you support Persian?
Yes. Persian is one of 100 languages in this directory, part of our wider language coverage worldwide, including deep Indian language coverage. Tell us the regional variety you need.
Do you already have any Persian data collected?
Yes. Roughly 500 hours of Persian speech, prompts and conversations are already recorded and ready to license. The Persian speech dataset page has the details, and anything it doesn't cover we collect to your brief.
Can you mix regional varieties of Persian in one project?
Yes. Tell us the mix of regions or dialects you need and we'll match contributors from our network to that brief.
Which data types are available in Persian?
Speech, text, conversational data and translation to or from Persian. Image and video categories don't depend on language, so Persian speakers can also appear in those briefs on request.
Is a sample available before we commit?
Yes, a small free sample first.
Can this run alongside other languages in the same project?
Yes. Many engagements mix languages, domains and data types under one brief and one named contact, using our network of 30,000+ people across 150+ projects delivered so far.
What counts as a regional variety of Persian?
A version of the language tied to a place or community, which can differ in vocabulary, pronunciation, formality or script from another region's variety. Name the region in your brief if it matters for your use case.
Can you handle Persian in its native script?
Yes. Contributors work in the native script by default, with transliteration available if your project needs it instead.
Which variety of Persian should I ask for?
Ask for the one your users actually speak. Persian is spoken mainly in Iran, Afghanistan (as Dari) and Tajikistan (as Tajik), and the forms most worth naming in a brief are Iranian Persian (Farsi), Dari in Afghanistan, Tehran colloquial speech. If you are unsure, describe your users and where they live, and your named contact will help you decide before collection starts.
How is Persian written, and does it matter for the data?
Persian data uses Perso-Arabic script, right to left. The script and its encoding affect how a model reads the data, so say in the brief which one you need and whether a romanized or transliterated version is also required.
Request Persian data
Pick the data type, confirm Persian as the language and a rough volume, and send it. We'll produce a small sample free before you commit.
- Your named contact replies within one business day.
- We sign an NDA before any data changes hands.
- We produce your free sample, then agree the full scope.
This opens your email app with the brief filled in. Nothing is sent until you press send. You can also use the contact page.