Middle East & North Africa · Arabic
Arabic (Gulf) Conversational Speech Dataset
Arabic (Gulf) conversational 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 conversational speech in Arabic (Gulf) is its own problem
Gulf Arabic has a marker no other Arabic variety shares: ق is realized as /ɡ/, and the sound carries meaning — a speaker who produces /q/ sounds like they are reciting rather than speaking. Annotators trained on the written standard habitually write ق anyway, silently erasing the feature that makes a recording Gulf. The second issue is who is in the room: in a Saudi city, everyday conversation often pairs a Gulf native with an Egyptian, Sudanese, or South Asian colleague whose Arabic is fluent but phonologically foreign, so a natural recording is often not Gulf on both sides.
The field to pin down first: Annotate each speaker's variety separately (Saudi Eastern Province / Najdi / Kuwaiti / Bahraini / Emirati / expatriate second-language Arabic), and state whether mixed-variety pairs are accepted or must be held as separate groups.
At a glance
| Language | Arabic (Gulf) |
|---|---|
| Primary region | Middle East & North Africa |
| Writing system | Arabic |
| Category | Conversational Speech |
| Specification field to settle first | Annotate each speaker's variety separately (Saudi Eastern Province / Najdi / Kuwaiti / Bahraini / Emirati / expatriate second-language Arabic), and state whether mixed-variety pairs are accepted or must be held as separate groups. |
| Delivery | Sourced to order, pilot batch before the full run |
What conversational speech data is
Speech from natural conversation between two or more people, on open or semi-structured topics, used for conversational AI, voice assistants, and small talk models.
What buyers get wrong about it
Natural conversation is full of overlapping speech, interruptions, particles, and laughter. Whether to keep these "messy" parts is the first thing to lock down on a project like this.
The specification field that decides the quote
Whether overlapping speech is kept or split — the two outputs cannot be mixed in a single delivery batch.
The language side: what Arabic (Gulf) demands
Gulf Arabic differs noticeably across Saudi Arabia, the UAE, and Kuwait, yet buyers usually search for saudi directly. Recording and annotating by country from the start is far less work than splitting a mixed batch afterward.
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 Arabic (Gulf) Conversational Speech
How many distinct speakers can you provide for Arabic (Gulf) Conversational 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. Annotate each speaker's variety separately (Saudi Eastern Province / Najdi / Kuwaiti / Bahraini / Emirati / expatriate second-language Arabic), and state whether mixed-variety pairs are accepted or must be held as separate groups.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. Gulf Arabic has a marker no other Arabic variety shares: ق is realized as /ɡ/, and the sound carries meaning — a speaker who produces /q/ sounds like they are reciting rather than speaking. 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 Arabic (Gulf) Conversational 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 Arabic (Gulf)
-
Arabic (Gulf) Call Center Speech
Recorded customer-service calls, real or simulated, capturing both the agent and the caller side, used for call center QC, intent recognition, and dialogue systems.
-
Arabic (Gulf) Singing Voice
Vocal recordings with melody, in both a cappella and accompanied form, used for singing voice synthesis, music information retrieval, and lyric alignment.
-
Arabic (Gulf) Speech Commands
Targeted recordings of short command words or phrases, usually with many speakers reading each entry several times over, used for wake words and on-device command recognition.
-
Arabic (Gulf) Read Speech
Recordings of speakers reading specified text, with clear pronunciation and known text, the base material for TTS and ASR.
-
Arabic (Gulf) Podcast Speech
Long-form podcast and interview audio, either solo monologue or two-person conversation, used for long-form speech recognition and speaker modeling.
-
Arabic (Gulf) Multilingual Speech
Speech data covering multiple languages within one project, used for multilingual ASR, cross-lingual transfer, and language identification.
Conversational Speech in other languages
-
Khmer Conversational Speech
Southeast Asia
-
Arabic (Egyptian) Conversational Speech
Middle East & North Africa
-
Kannada Conversational Speech
South Asia
-
Punjabi Conversational Speech
South Asia
-
Burmese Conversational Speech
Southeast Asia
-
Amharic Conversational Speech
Sub-Saharan Africa
Request Arabic (Gulf) Conversational 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.