Buying Video Training Data: A Checklist for AI Teams

Written by

in

Buying video or audio training data looks simple on a price sheet — dollars per hour, per terabyte or per clip — and gets complicated the moment the first delivery lands in your bucket. This checklist is what an AI team should agree with a data vendor before paying for volume: what to specify, what to ask for in writing, how to test a sample, and the red flags that predict a painful project.

TL;DR

  • Write the spec as acceptance tests, not adjectives. "High quality" is not a spec; "≥1080p, single shot, ≤5% OCR-heavy clips" is.
  • Get provenance per sample, not per delivery: source ID, collection time, license status at collection.
  • Insist on a sample batch run through your own pipeline before committing volume.
  • Compare price per usable hour, after your own filtering and deduplication, not price per delivered terabyte.
  • Agree on takedown handling before you need it.

1. Provenance and rights

Ask first, because everything else is wasted if the answers are unacceptable to your legal team.

  • Where does the content come from, and how was it collected?
  • Is there a per-sample record of source (platform and ID or URL), collection timestamp, and license status at collection time?
  • Can you filter by license (for example, Creative Commons only)? See finding and filtering Creative Commons YouTube videos for what that does and doesn't settle.
  • How are takedown and opt-out requests handled after delivery? Will the vendor notify you so you can remove affected samples and derived clips?
  • What does the contract say about your permitted uses, and who carries which risks?

Platform terms, copyright and privacy law (faces and voices can be personal data) all apply to video. Your legal team should review the answers for your jurisdiction and use case; a vendor's assurances don't replace that.

2. Content specification

Turn what you want into numbers the vendor can measure and you can verify:

Dimension Example spec
Volume 50,000 hours, delivered in monthly tranches of ~8,000 hours
Resolution / frame rate ≥1080p source, ≥24 fps, native (not upscaled)
Duration Source videos 1–30 min; or clips 4–20 s after splitting
Language (audio) ≥70% English, ≥10% each of Spanish, German, Japanese
Content mix Category distribution, with caps per channel to avoid a few uploaders dominating
Exclusions No livestream VODs, no Shorts, no screen recordings, no compilations
Recency Uploaded after a given date, if freshness matters
Modalities Video + original audio + manual subtitles where available + metadata JSON

Per-uploader caps are easy to forget and matter a lot: without them, a handful of prolific channels can make up a large share of a dataset and skew style, voice and content.

3. Quality and filtering

  • What filtering has the vendor already applied (shot detection, motion, OCR/text, blur, NSFW, faces)? Ask for the filter list and per-filter keep-rates.
  • Will they deliver the raw scores per sample, so you can apply your own thresholds? This is worth more than their thresholds. See video data curation for generative models.
  • Are captions or transcripts included? Which model produced them, and is that recorded per sample? See recaptioning video datasets.

4. Deduplication and contamination

  • Is the delivery deduplicated within itself — exact (hash) and near-duplicate (perceptual or embedding)?
  • Can it be deduplicated against data you already own, and across tranches, so you never pay twice for the same video?
  • Can the vendor exclude a list of IDs you provide, such as your evaluation sets or previous purchases?

Duplicates are the most common hidden cost: they inflate volume metrics and quietly overweight some content in training.

5. Metadata schema

Agree on the schema before the first delivery, with types and units. A minimal per-sample record:

{
  "sample_id": "c7f1e2...",
  "source": "youtube",
  "source_id": "dQw4w9WgXcQ",
  "collected_at": "2026-11-02T08:14:55Z",
  "license_at_collection": "creativeCommon",
  "duration_s": 212.4,
  "width": 1920,
  "height": 1080,
  "fps": 25.0,
  "video_codec": "vp9",
  "audio_codec": "opus",
  "language": "en",
  "title": "...",
  "channel_id": "UC...",
  "upload_date": "2025-06-18",
  "subtitles": ["en"],
  "file_path": "s3://bucket/tranche-03/shard-000412.tar",
  "sha256": "9f2c..."
}

Ask for JSONL or Parquet, one schema version per delivery, and a changelog when fields change.

6. Delivery

  • Where: directly into your S3, GCS or Azure bucket. Give the vendor write-only credentials scoped to one prefix.
  • Layout: sharded files (for example WebDataset-style tar shards) rather than millions of small objects, plus a metadata table.
  • Integrity: a manifest per tranche listing every file with size and sha256, so you can verify completeness automatically.
  • Cadence: tranche size and schedule, and what happens if a tranche fails acceptance.
  • Incremental updates: if you need ongoing collection, how new data is identified and delivered without re-sending old samples.

Ingress into major cloud object stores is generally free, but reading data back out is not. Plan where you will process it. The capacity arithmetic is in bandwidth for large-scale video downloads.

7. The sample batch and acceptance tests

Never commit volume without running a sample through your own pipeline. A useful acceptance test, written down and agreed with the vendor:

Test Pass criterion (example)
Integrity 100% of files match manifest size and sha256
Schema 100% of records validate against the agreed schema
Spec compliance ≥98% of samples meet resolution, duration and language specs
Duplicates ≤1% near-duplicates within tranche; 0 overlap with your exclusion list
Usable yield After your own curation filters, ≥X% of hours remain
Provenance 100% of samples have source ID, collection time and license field

The "usable yield" line is the one that decides cost. Run your real curation pipeline on the sample and compute it; that number turns a price per delivered hour into a price per hour you will actually train on.

8. Comparing prices

Vendors quote in different units: per hour, per clip, per terabyte, per petabyte, or as bandwidth if you collect yourself. Normalize to one number:

effective cost per usable hour = total price ÷ (delivered hours × usable yield)

A cheaper per-terabyte price with 40% usable yield costs more than a higher price with 80%. If you collect yourself instead, add engineering time, proxy or bandwidth costs, storage, and the cost of retries and failures.

Red flags

  • No per-sample provenance, or "we can't tell you where it came from".
  • No sample batch, or a sample that is clearly hand-picked rather than random.
  • Volume quoted only in terabytes with no hours, resolution or duplicate rate.
  • No answer on takedown handling.
  • No checksums or manifests — you will be debugging missing files for months.
  • Refusal to dedupe against your existing data or evaluation sets.

How Corpora works

Corpora collects YouTube video, audio, subtitles and structured metadata and delivers it to your S3, GCS or Azure bucket as deduplicated data with sha256 checksums and manifests, in your preferred layout, priced per delivered petabyte. Every project starts with a free sample batch so you can run your own acceptance tests. Teams that prefer to collect themselves can use dedicated 1–40 Gbps unmetered proxy capacity instead. See pricing or talk to sales.

FAQ

What should a video training data contract specify?

Content spec as measurable criteria, per-sample provenance, metadata schema, delivery layout and integrity checks, acceptance tests on a sample, deduplication commitments and takedown handling.

How do I compare vendors who price differently?

Run each vendor's sample through your own curation pipeline, measure usable yield, and compare effective cost per usable hour.

Should I buy curated clips or raw videos?

Raw videos with per-sample scores give you the most flexibility, because your thresholds will change. Curated clips save processing time if the vendor's filtering matches your model's needs.

Is buying data cheaper than collecting it ourselves?

It depends on volume and your team's time. Compare the vendor's effective cost per usable hour with your own bandwidth, proxy, storage, engineering and failure costs at the same volume.