Catalogue · தமிழ்
Ready-made Tamil speech datasets
Corpora already recorded in Tamil and available under licence, plus what to check before buying existing data instead of commissioning a build.
- Language
- Tamil (ta-IN)
- Licence
- Perpetual, commercial, model-training permitted
- Availability
- Subject to consent scope; confirmed on enquiry
- Lead time
- Days, not weeks
Available corpus types
| Corpus | Typical band | Annotation | Best for |
|---|---|---|---|
| Tamil scripted speech | 100-500 hours | Verbatim + timestamps | Prompt-read speech from a phonetically balanced script, the baseline corpus type for ASR and TTS training. |
| Tamil spontaneous speech | 100-500 hours | Verbatim + timestamps | Unscripted monologue on prompted topics, which carries the disfluencies and prosody that scripted data never produces. |
| Tamil conversational speech | 100-500 hours | Verbatim + speaker turns + timestamps | Two-party conversation recorded on separate channels, with overlap and turn-taking preserved. |
| Tamil telephony speech | 50-300 hours | Verbatim + timestamps | Narrowband call audio captured over a telephony path, matching what a deployed contact-centre model actually receives. |
Availability is confirmed per enquiry. Some material can only be licensed within the consent scope the speakers originally agreed to, and we will not stretch that to close a sale.
Ready-made versus commissioned
| Ready-made | Commissioned build | |
|---|---|---|
| Lead time | Days | 3-16 weeks |
| Cost per hour | Lower | Higher |
| Cohort control | Fixed by the original spec | Yours |
| Dialect quotas | As recorded | Designed |
| Exclusivity | Non-exclusive | Exclusive if you want it |
| Best for | Baselines, prototypes, augmentation | Production models |
What to check before licensing existing data
- Consent scope: does it permit commercial model training, and by a third party?
- Dialect distribution: a corpus that is 90% one urban variety will not generalise across Tamil Nadu, Puducherry, parts of Karnataka and Kerala
- Recording conditions: studio-only data underperforms badly on noisy deployments
- Transcription convention: Transcribers normalising spoken Tamil into literary Tamil, destroying the acoustic-text alignment will otherwise surface as tokenisation noise
- Overlap: check whether the corpus already sits in the public sets you trained on
Where the public corpora fall short
Almost all public Tamil audio is literary read speech from news or scripture. Genuine colloquial Tamil, especially southern and Kongu varieties, is the single biggest gap for anyone building Tamil voice products.
This is usually the reason buyers move from licensing to commissioning: the free and cheap material covers the easy half of the language.
What a usable Tamil corpus has to cover
- Dialect spread across Chennai (Madras Bashai), Kongu (Coimbatore), Madurai, Nellai (Tirunelveli) rather than a single prestige variety
- The phonetic contrasts that Tamil models actually get wrong: Extreme diglossia: written Tamil and spoken Tamil differ so much that read-speech corpora are near-useless for conversational ASR
- Code-mixed speech transcribed rather than discarded — Tanglish is the default urban register. Technology, finance, and workplace vocabulary is largely English embedded in Tamil syntax.
- Recording geography covering Chennai, Coimbatore, Madurai, Tiruchirappalli, since dialect follows location
- Utterance types beyond read prompts: Colloquial spontaneous conversation transcribed verbatim, Diglossia pairs: the same content in written and spoken register, Command-and-control and IVR-style utterances
Recruit by district rather than by city alone; Chennai-only cohorts produce models that degrade sharply in the south and west of the state.
Frequently asked
Can I buy an existing Tamil dataset today?
Where a corpus exists within an appropriate consent and licence scope, yes — usually within days. We confirm availability against your intended use before quoting.
Is the licence exclusive?
Ready-made corpora are licensed non-exclusively. Exclusivity is available on commissioned builds.
Can we augment a ready-made corpus with new recordings?
That is the most common pattern: licence the base, then commission the dialects, conditions or domain vocabulary it lacks.
Do you provide a data sheet?
Yes — speaker counts, demographic distribution, condition mix, annotation convention and known limitations, before you commit.
Related pages
Check Tamil availability
Tell us the hours, corpus type and intended use. We confirm what is licensable now and what needs recording.