What is a Video Manifest?
A video manifest lists resources available to a streaming player, including renditions, segment locations, timing, and sometimes captions or encryption data. HLS playlists and MPEG-DASH MPDs are common forms.
How Video Manifests work
A manifest is a control document that describes how a player should assemble media resources over time; it usually contains references rather than the media payload itself. Variant descriptions expose alternative encodes, while track descriptions associate audio, video, subtitles, and timing. For live playback the document is refreshed as the availability window advances, whereas an on-demand version is generally stable. It is generated during packaging and consumed before and throughout adaptive playback.
Key facts
- 1Declared codecs and track properties must agree with the referenced initialization data; a misleading declaration can make a player choose a rendition it cannot decode.
- 2Live manifests use ordered media references and explicit timeline transitions; a missing sequence update or discontinuity marker can cause repeats, gaps, or timestamp jumps.
- 3Relative media addresses are resolved from the manifest location, so URL rewriting, signing, redirects, CORS policy, and cache lifetime can all affect segment retrieval.
When Video Manifests matter
Generate manifests that expose only compatible renditions, tracks, and protection data to each player. Incorrect URLs, durations, codec declarations, or encryption signaling can stop adaptation or playback.
Common use cases for streaming
These examples cover streaming broadly, not specifically Video Manifests.
- Delivering long-form, episodic, educational, live, or user-generated video over variable networks.
- Providing low-bandwidth through high-resolution renditions from one master.
- Combining captions, alternate audio, encryption, thumbnails, and ad markers with playback media.
Working with streaming
This guidance covers streaming broadly, not just Video Manifests.
An encoder creates several quality levels, and a packager divides them into aligned segments referenced by a manifest. During playback, the client estimates throughput and buffer health, then requests an appropriate segment from one rendition at a time.
Streaming quality depends on the relationship between renditions, segments, manifests, players, and the network. A valid encode can still perform poorly if keyframes are misaligned, the ladder is inefficient, or the player cannot switch cleanly.
What you gain
- Segmented delivery lets playback begin without downloading the entire program.
- Multiple renditions let a player adapt quality as network and device conditions change.
- HTTP-based protocols can reuse ordinary web caching and delivery infrastructure.
What it costs
- Short segments can reduce switching and live latency but increase request and packaging overhead.
- A dense rendition ladder offers finer adaptation while increasing encoding, storage, and cache cost.
- More aggressive quality selection can improve sharpness but raises rebuffering risk on unstable networks.
Before production
- 1Test the rendition ladder on slow, changing, and high-latency connections.
- 2Align segments and keyframes, then validate manifests in the target players.
- 3Measure startup, rebuffering, quality switches, CDN efficiency, and playback failures.