Definition
A playback manifest is a metadata file that tells a video player what playback assets exist and where to fetch them.
The player needs to know:
- which resolutions are available
- which bitrates are available
- where each segment lives
- how long segments are
- which audio tracks exist
- which subtitle tracks exist
- how tracks align on the playback timeline
Without a manifest, the player would have to guess the URL structure and quality options. That makes playback brittle.
The Pain That Forces This Concept
Video playback is not a single file download in a serious streaming system.
One title may have:
- multiple video renditions
- multiple audio languages
- subtitles
- thumbnails
- regional availability rules
- DRM or tokenized access
- segments spread behind CDN paths
The player needs a compact description of this world before it starts fetching media.
Mental Model
The manifest is the map. Segments are the terrain.
manifest
1080p -> segment URLs
720p -> segment URLs
480p -> segment URLs
audio -> segment URLs
The manifest should be small, cacheable, and safe to fetch before the player starts downloading larger media segments.
How It Works
After transcoding finishes, the packaging step creates manifests.
source video
-> renditions
-> segments
-> manifest
-> publish to storage/CDN
During playback:
1. Player requests playback metadata from the application API.
2. API checks entitlement, region, device, and content availability.
3. API returns a manifest URL or signed playback token.
4. Player fetches the manifest.
5. Player downloads segments listed by the manifest.
The manifest can point to CDN paths rather than origin storage. This is what makes video delivery cache-friendly.
Tradeoffs
| Choice | Benefit | Cost |
|---|---|---|
| Static manifests | Highly cacheable | Less runtime personalization |
| Dynamic manifests | Support entitlement and device rules | Harder to cache |
| Signed segment URLs | Stronger access control | URL churn can reduce cache efficiency |
| Stable CDN paths | Better cache reuse | Requires separate authorization strategy |
The manifest sits between product rules and media delivery. If it changes too often, caching suffers. If it is too static, authorization and personalization become harder.
Operational Reality
Operators watch:
- manifest generation failures
- missing segment references
- manifest fetch latency
- cache hit ratio for manifests
- playback errors caused by bad URLs
- track alignment failures
- stale manifests after reprocessing
Failure modes:
- manifest references a segment that was not published
- one rendition is missing from the manifest
- signed URLs expire during playback
- audio and video timelines drift
- CDN caches an outdated manifest
- playback API returns a manifest before processing is complete