Middle East & North Africa · Arabic (Perso-Arabic)

Persian Speech Translation Dataset

Persian speech translation sourced to your specification — no inventory, no fixed listing. This page covers what is specifically hard about this pairing, and which fields your specification needs to pin down.

Why speech translation in Persian is its own problem

Persian speech translation's source audio is in spoken form, while translators are usually trained on the written form. Translating straight from the spoken form loses some information, and interpreting it through written-form knowledge produces mistranslation. Translators need dedicated spoken-to-written support.

The field to pin down first: Provide a spoken-to-written correspondence table for translators, and state the principle for handling spoken forms.

At a glance

LanguagePersian
Primary regionMiddle East & North Africa
Writing systemArabic (Perso-Arabic)
CategorySpeech Translation
Specification field to settle firstProvide a spoken-to-written correspondence table for translators, and state the principle for handling spoken forms.
DeliverySourced to order, pilot batch before the full run

What speech translation data is

Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.

What buyers get wrong about it

Speech translation data needs all three components: audio, source-language transcription, and target-language translation. Miss one and it cannot be trained on — many suppliers deliver only two.

The specification field that decides the quote

Whether the translation is human or machine translation with human post-editing — cost and quality differ by an order of magnitude.

The language side: what Persian demands

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.

More on Persian speech data →

What we can put in this delivery

  • Read and conversational speech

    Scripted recording for TTS, and unscripted conversation for recognition. Specified separately because they need different speaker pools.

  • Transcription to your convention

    Orthographic or phonetic, with the guideline written before production and shared with you for review.

  • Speaker metadata

    Age band, gender, region and dialect background per file, so you can slice the dataset rather than take it whole.

  • Consent documentation

    Signed speaker consent covering the intended use, plus collection methodology and the annotation guideline.

  • Pilot batch

    A small batch first, which you can reject. Misalignments surface after a few hours rather than at delivery.

  • Delivery in your format

    Audio format, sampling rate, segmentation length and metadata schema set to your pipeline's requirements.

What arrives in a delivery

ComponentWhat it is
Audio filesFormat, sampling rate and segmentation length set to your pipeline. Named to a convention you specify.
TranscriptionOrthographic or phonetic, produced under a guideline you review before production starts.
Speaker metadataAge band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced.
Recording conditionsEnvironment, device and, where relevant, measured signal-to-noise ratio per file.
Annotation guidelineThe document the annotators worked from, so you can reproduce the conventions on your own data.
Consent recordsSigned speaker consent covering your intended use, with the transfer mechanism addressed where required.
Collection methodologyHow speakers were recruited, screened and scheduled — the part that tells you how biased the pool is.
Quality reportPilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them.

Questions we get about Persian Speech Translation

How many distinct speakers can you provide for Persian Speech Translation?

It depends on the specification and the timeline, and we will give a real number rather than a target. For this pairing, speaker recruitment is usually the step that sets the schedule. Provide a spoken-to-written correspondence table for translators, and state the principle for handling spoken forms.

Can you annotate to our own guideline instead of the default?

Yes, and for this pairing we would recommend it. Persian speech translation's source audio is in spoken form, while translators are usually trained on the written form. That is exactly the kind of decision a default guideline leaves open, and it is where annotators diverge. Send us your guideline, or we will draft one and you can review it before production starts.

Do you offer a sample before we commit to a full run?

Yes. Select a free sample in the request form and describe what you need. A pilot batch is the cheapest way to establish whether the quality bar is reachable for Persian Speech Translation before committing to the full volume.

Is the data licensed or owned outright?

Licensing terms are set per project, so tell us how the model will be used and whether it will be distributed. Consent documentation travels with the data either way, and we do not handle medical or clinical data or recorded telephone calls.

Other datasets in Persian

  • Persian Children Speech

    Speech data from child speakers, grouped by age band, used for children's speech recognition and children's education products.

  • Persian Audiobook

    Continuous long-form narration in audiobook style, steady in intonation and generous in duration, the main source material for high-quality TTS.

  • Persian Short Video Speech

    Speech in the talking-head style of short video — fast, emotionally strong, colloquial — used for short video subtitles and content understanding.

  • Persian Live Stream Speech

    Long-session spoken content from live streams — host monologue and responses to audience interaction — fast-paced and heavily improvised.

  • Persian Voice Assistant

    Command and dialogue data for voice assistants, usually with intent annotation, covering the full chain from wake word to understanding to response.

  • Persian Elderly Voice

    Speech data from elderly speakers, usually stratified by age band and health status, used for voice products built for older users.

All Persian data →

Speech Translation in other languages

All Speech Translation data →

Request Persian Speech Translation

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.

We reply within two business days. Your details are used only to answer this request. See our privacy policy.

Contact

Talk to a human

Send a specification and we will come back with a real number and timeline.

Submit a sourcing request

Or email hello@linguacorpus.com