Open speech datasets provide or reference recordings and, depending on the release, transcripts, speaker labels or other annotations. LibriSpeech, Common Voice and VoxCeleb serve different research tasks. Start with the exact release and the model job: a corpus useful for one benchmark may lack the labels, recording conditions or permissions your project needs.
This guide compares documented corpus designs and shows how to turn a possible limitation into a checkable sourcing decision. An open release that meets the required task, coverage and permitted uses can remain the right choice. Another source or additional annotation is worth assessing when you identify a specific unresolved gap.
For a procurement decision, compare an open release with a specific listed asset. Browse Spirelight's conversational dataset catalogue and request a representative sample; confirm availability, coverage, permissions and written terms before selection.
The major open speech datasets
LibriSpeech contains approximately 1,000 hours of 16 kHz read English speech derived from LibriVox audiobooks. OpenSLR's release documentation states CC BY 4.0 and separates training, development and test material, including clean and other subsets. Those facts describe this corpus; they do not establish the performance of a particular model on your recordings. Keep the prescribed splits when using its benchmark protocol.
Mozilla Common Voice includes distinct scripted and spontaneous speech series. Mozilla's 18 September 2026 announcement names Scripted 27.0 and Spontaneous 5.0; these are dated examples, not a claim about the latest release. The English Scripted 27 page describes read speech and distinguishes recorded from validated hours. The English Spontaneous 5 page describes responses to prompts, including material without transcripts. Both pages display CC0 labels alongside separate usage information. Read the applicable release and access conditions; a licence label alone does not answer every speaker-privacy or permitted-use question.
VoxCeleb uses segments extracted from online interview videos for speaker-recognition research. Check the official VoxCeleb documentation for the version, speaker labels and evaluation design. Interview provenance does not establish every individual's consent status or every downstream use. The university's dataset privacy notice describes its own processing context; do not treat it as a licence or a privacy exemption for your organisation. Obtain the applicable access, source and permission records for your intended use.
AudioSet targets general sound events. Google's AudioSet overview describes an ontology of 632 classes and roughly two million labelled ten-second video segments. The download documentation distinguishes the 527 classes used in the annotated sets and offers segment identifiers, labels and extracted features. These are different counts, not conflicting descriptions. Check which artefacts you need and how source media can be accessed; licences stated for released annotations or ontology do not by themselves establish every right in an underlying video.
GigaSpeech provides a useful counterexample to treating open speech as entirely read speech. Its official 2021 v1 documentation describes 10,000 hours of transcribed English drawn from audiobooks, podcasts and online video, with read and spontaneous sources. Compare the particular subset, source conditions, transcript preparation and splits. A repository's code licence badge is not sufficient evidence of all permissions for its audio.
Other task-specific options: MLCommons' People's Speech documentation describes a large transcribed English release with stated attribution and share-alike licensing components. LJ Speech documents about 24 hours of read speech from one speaker, with corresponding text; that is a different starting point from multi-speaker conversation. The Google FLEURS dataset card describes parallel sentence-based data across 102 languages for evaluation. The TED-LIUM 3 author paper documents a TED-talk-derived English recognition corpus; check a current release's actual terms and access separately. Neither a historical paper nor this overview certifies current download availability or permission.
What open datasets are good for
Match a documented release to a specific job: reproducing a published recognition benchmark, testing a speaker-recognition system, exploring synthesis with paired audio and text, or inspecting sound-event labels. Record the subset, version, preprocessing and evaluation protocol so another person can understand the result. A comparison is only meaningful within the conditions actually tested.
Open material may also support prototyping, training or adaptation when its contents and terms fit the proposed method. Do not assume one required sequence from open pretraining to paid fine-tuning. An existing model, a small evaluation set, extra labels or a different release may address the immediate need. Define the gap before deciding how many additional hours to source.
Where open datasets stop being enough
- Speech style and capture: distinguish read, prompted and spontaneous speech from microphone distance, channel, device and noise. LibriSpeech's read audiobook design and Common Voice's separate series illustrate why the corpus name alone is insufficient. For a conversational task, inspect actual turns, interruptions and any required overlap labels; the conversational speech data guide covers that brief.
- Labels and validation: total audio duration is not necessarily the amount of validated, transcribed or speaker-labelled material available for your task. Verify the release's definitions and inspect a permitted sample. Missing turn boundaries, for example, may call for additional annotation rather than new recordings.
- Coverage: compare language, locale, speakers and recording conditions with your intended evaluation. A language name or overall hour count does not establish coverage of a particular dialect or device. Avoid treating contributor demographics as representative of your users without evidence; request appropriate records where available and justified.
- Source and permissions: check the exact release's licence, attribution or share-alike duties, source and platform permissions, privacy information and applicable lawful basis. Keep unresolved rights questions separate from technical fit. The speech data licensing guide lists questions to investigate; it does not replace the actual source records or project-specific review.
- Evaluation independence: check what is known about the model version's training data and the proposed split. If prior exposure is unknown, record that limitation and consider an appropriately held-out evaluation source. A benchmark score remains evidence about that test; it does not establish performance across every deployment condition.
Turn a limitation into a sourcing decision
The following examples are hypothetical planning decisions, not tests we ran, client results or claims about a supplier's available stock. Each starts with evidence you can request or inspect rather than assuming all open or commercial data has the same strengths.
| Observed evidence | Decision to resolve | Practical next step |
|---|---|---|
| A release lists total audio and a smaller validated transcript subset. | Which subset meets the supervised recognition brief? | Scope the qualifying subset first; assess additional transcription or another documented source only for the remainder. |
| An authorised conversation sample has transcripts but no speaker-turn labels. | Can the existing recordings support the diarization task? | Check speakers, channels and overlap, then price the required annotation and acceptance process before commissioning replacement audio. |
| The files and labels meet the technical checks, but source permissions remain unresolved. | Can this specific use proceed? | Keep the rights decision open for the applicable review. A successful model test or paid invoice does not close it. |
Record the exact release, intended task, required coverage, label definitions, test protocol, source records and unresolved questions in the speech dataset specification worksheet. Keep the original source identifiers and a record of transformations so that the candidate you assess is the one your team proposes to use.
When to license or commission data instead
If an open release meets the required coverage, permitted uses and evaluation needs, use the supported option. If a material gap remains, compare preparing or annotating that source, selecting another documented asset, and a feasible new collection. Consider the whole proposed scope and acceptance work; neither a free download nor a commercial label establishes the final implementation effort or suitability.
Spirelight's catalogue has 60 conversational speech dataset listings with recording details and sample-request options. Confirm current availability, sample coverage, permitted uses and written commercial terms for the specific asset. The buying AI training data guide covers comparing a listed dataset with a custom recording scope. Custom collection needs a feasibility assessment and agreed recruitment, recording, annotation, responsibilities, schedule and acceptance; a missing open-data feature is not proof that any supplier can deliver it.