Middle East & North Africa · Arabic / Latin
Kurdish In-the-Wild Speech Dataset
Kurdish in-the-wild speech 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 in-the-wild speech in Kurdish is its own problem
For Kurdish, in-the-wild collection lands in a particular setting: the language is often the language of home and community rather than of offices, so natural recordings happen in living rooms, at gatherings, and in shops, with the phone as the device — authentic, but concentrated in a narrow band of environments and audio quality. The speech is also naturally mixed, since any shift to administrative or technical talk pulls in the state language of the country, and that mixing is part of what the data is meant to capture, so filtering it out would flatten what makes it real.
The field to pin down first: Device and environment are logged per item, and the delivery states whether state-language segments were kept and tagged, since the natural mixing is part of the recording rather than an error to clean up.
At a glance
| Language | Kurdish |
|---|---|
| Primary region | Middle East & North Africa |
| Writing system | Arabic / Latin |
| Category | In-the-Wild Speech |
| Specification field to settle first | Device and environment are logged per item, and the delivery states whether state-language segments were kept and tagged, since the natural mixing is part of the recording rather than an error to clean up. |
| Delivery | Sourced to order, pilot batch before the full run |
What in-the-wild speech data is
Speech collected under fully natural conditions — no studio, no topic constraints — as close to real usage as collection gets.
What buyers get wrong about it
Real and usable pull against each other — the more natural the audio, the harder it is to annotate. The balance has to be designed into the collection plan, not patched in afterward.
The specification field that decides the quote
Recording device (phone, headset, professional mic) and collection environment must be logged per file.
The language side: what Kurdish demands
The two main branches of Kurdish (Sorani and Kurmanji) have low mutual intelligibility, close to two separate languages, and they use different scripts. Public resources are so thin that even TTS datasets are rare — a textbook scarce language.
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
| Component | What it is |
|---|---|
| Audio files | Format, sampling rate and segmentation length set to your pipeline. Named to a convention you specify. |
| Transcription | Orthographic or phonetic, produced under a guideline you review before production starts. |
| Speaker metadata | Age band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced. |
| Recording conditions | Environment, device and, where relevant, measured signal-to-noise ratio per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed speaker consent covering your intended use, with the transfer mechanism addressed where required. |
| Collection methodology | How speakers were recruited, screened and scheduled — the part that tells you how biased the pool is. |
| Quality report | Pilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them. |
Questions we get about Kurdish In-the-Wild Speech
How many distinct speakers can you provide for Kurdish In-the-Wild Speech?
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. Device and environment are logged per item, and the delivery states whether state-language segments were kept and tagged, since the natural mixing is part of the recording rather than an error to clean up.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. For Kurdish, in-the-wild collection lands in a particular setting: the language is often the language of home and community rather than of offices, so natural recordings happen in living rooms, at gatherings, and in shops, with the phone as the device — authentic, but concentrated in a narrow band of environments and audio quality. 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 Kurdish In-the-Wild Speech 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 Kurdish
-
Kurdish Multilingual Speech
Speech data covering multiple languages within one project, used for multilingual ASR, cross-lingual transfer, and language identification.
-
Kurdish Noisy Speech
Speech collected under background noise — street, in-car, restaurant, office and other real environments — used for noise-robust models and speech enhancement.
-
Kurdish Code-Switching Speech
Speech that mixes two or more languages inside a single utterance — Hinglish, Spanglish, Taglish — used for recognition in real spoken settings.
-
Kurdish Children Speech
Speech data from child speakers, grouped by age band, used for children's speech recognition and children's education products.
-
Kurdish Audiobook
Continuous long-form narration in audiobook style, steady in intonation and generous in duration, the main source material for high-quality TTS.
-
Kurdish Short Video Speech
Speech in the talking-head style of short video — fast, emotionally strong, colloquial — used for short video subtitles and content understanding.
In-the-Wild Speech in other languages
-
Filipino In-the-Wild Speech
Southeast Asia
-
Persian In-the-Wild Speech
Middle East & North Africa
-
Tamil In-the-Wild Speech
South Asia
-
Telugu In-the-Wild Speech
South Asia
-
Malayalam In-the-Wild Speech
South Asia
-
Nepali In-the-Wild Speech
South Asia
Request Kurdish In-the-Wild Speech
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.