If you’re training a speech recognition model, a text to speech voice or a voice agent, you need recorded human speech, and the kind that makes those models good is the hardest to get legally. Natural conversation between real people, with interruptions, accents and background noise, is scarce and carries more rights than any other modality. Read-aloud corpora are easy to license and produce stilted models. Read on to find out where AI teams get speech training data for each use case, what the rights have to cover, and what a training-ready dataset looks like.
Our guide to licensed audio data for AI covers music, ambient sound and the wider audio catalog. This page is about speech.
Who needs speech data, and for what
Four buyer groups drive most of the demand. Speech recognition teams need volume and diversity: many speakers, accents, acoustic conditions, and domain vocabularies, paired with accurate transcripts. Voice synthesis and cloning teams need clean, well-recorded speech with documented consent from the speaker, because the output imitates a human voice. Voice agent builders need the hardest thing: natural multi-speaker conversation, since an agent trained on scripted speech handles real customers badly. And multimodal and video model teams need speech in context, faces and voices together, synchronized and cleared as one asset.
Each of these has a different tolerance for the channels below, which is why the market has not consolidated into one kind of vendor.
Speech recognition training data
Speech to text models learn from volume and variety. The dataset needs many speakers, many accents, real acoustic conditions (phones, cars, call centers, open offices) and the vocabulary of the domain the model will work in, each recording paired with an accurate transcript. Read-aloud corpora give you clean audio and little else, because nobody dictates the way they talk. Conversational recordings with transcripts, speaker labels and timing are what move a recognizer from demo to product, and they’re the recordings that are hardest to clear.
Text to speech training data
TTS and voice cloning models need the opposite: clean, well-recorded speech from a consistent speaker, in a quiet room, with the speaker’s documented consent to AI training. The output imitates a human voice, so the consent has to name that use, and voice likeness rights apply on top of copyright in the recording. Scripted studio recordings are the base layer here, and natural conversation adds the prosody (pauses, emphasis, hesitation) that makes a synthetic voice sound like a person. Both have to come with a paper trail from the speaker.
Voice assistant and conversational AI training data
Voice agents need the hardest data of all: real multi-speaker conversation, with turn-taking, overlapping speech, interruptions and repair, because an agent trained on scripted speech handles real customers badly. Podcast conversations, multilingual dialogue and commentary give a model the shape of how people talk to each other. The rights stack is the same as the other two use cases, with one addition: every speaker in the conversation has to have opted in, not just the host.
The sourcing channels
| Channel | What you get | Watch for |
|---|---|---|
| Custom collection vendors | Speech recorded to your spec | Cost and turnaround; quality depends on the brief |
| Dataset marketplaces | Off-the-shelf speech datasets | Variable provenance; check per-asset rights |
| Open corpora | Free research datasets | License limits, read-aloud style, heavily overtrained |
| Platform and web audio | Scale | Rights problems stack fast; consent rarely covers training |
| Licensed data marketplaces | Real-world conversational audio, cleared for training | Catalog fit; confirm the modality depth you need |
Custom collection is the established route: vendors like Appen, Shaip, and LXT recruit speakers and record to specification across dozens or hundreds of languages. It works, and for niche requirements like regulated-industry vocabulary it is often the only option, but you pay per produced hour and wait for the pipeline.
Our guide to AI data collection companies and services compares those vendors and what to check before you sign.
Dataset marketplaces such as Defined.ai sell ready-made speech corpora, which is faster for pilots. The thing to verify is provenance: a marketplace aggregating from many sources is only as clean as its weakest contributor, so ask for rights documentation per dataset, not a blanket assurance.
Open corpora like read-speech research sets are free and everyone has trained on them, which is the problem. They add little differentiation, most are read-aloud rather than conversational, and research licenses often exclude commercial training.
Platform audio, podcasts, videos, and call recordings scraped at scale, is where speech sourcing goes wrong. A recording of a voice stacks several rights at once, and platform terms of service, speaker consent, and copyright in the underlying content each fail separately. The lawsuits working through the courts cover this pattern in detail; our guide to AI training data lawsuits tracks them.
Licensed marketplaces are the newer channel: real-world audio that already exists, conversational and natural, licensed for training directly from the people who own it. That is the category Troveo operates in, covered below.
Speech data services or licensed datasets
AI speech data services record speech to your brief, and a licensed dataset is speech that already exists, cleared for training. A service suits a requirement nothing on the market covers (a rare language, a regulated vocabulary, a specific device). A licensed dataset suits the rest, and it’s faster, because the recordings exist and the rights are already documented. Most speech programs end up using both: a licensed base of natural speech, and a smaller commissioned set for the gaps.
The rights stack in a human voice
Speech data carries more rights than almost any other modality. There is copyright in the recording, and a performance right in the speech itself. There is the speaker's consent, which needs to name AI training explicitly, not just "recording and distribution." There are voice likeness rights, which have tightened as cloning got good; a model that can reproduce someone's voice raises questions no platform license answers. And in some jurisdictions a voiceprint qualifies as biometric data, which brings its own consent requirements.
The practical test is simple and unforgiving: for each recording, can the provider produce a document in which someone with the authority to do so licensed that recording for AI training? If the answer is a scraped archive and a theory, the risk transfers to you. What separates real clearance from a label is covered in rights-cleared training data.
What training-ready speech data looks like
Raw audio is not training data. Training-ready speech comes with accurate transcripts, speaker labels and diarization, language and accent metadata, acoustic condition notes, and consistent formats your pipeline can ingest without a cleanup project. For conversational data specifically, the markers of quality are natural turn-taking, overlapping speech, and real acoustics rather than studio sterility, the things scripted corpora cannot fake.
Where Troveo fits
Troveo's catalog is real-world audio and video licensed from more than 7,000 rights holders, and speech runs through most of it: multi-speaker podcast conversations, multilingual conversations across languages and accents, sports and gaming commentary, scripted studio recordings, and talking-head video where face and voice are synchronized and cleared together. Every asset is licensed for AI training with documentation per asset, the speakers opted in and get paid, and the data ships cleaned and normalized to your spec.
That makes Troveo the fit when the need is natural human speech as it actually occurs, rather than speech produced to a script. Talk to us about what your model needs to hear, or start with our guide to how to buy AI training data if you're earlier in the process.
