What is AVOD?
Advertising-based video on demand, or AVOD, provides programming whenever viewers request it and funds access wholly or partly through advertising. Ads may appear before, during, or after the content.
How AVOD works
AVOD is a distribution and revenue model layered over on-demand playback rather than a media codec or streaming protocol. A session must combine requested programming with selected ad opportunities, tracking, policy, and entitlement decisions. Ads can be stitched into the stream by the service or scheduled separately by the player, with different implications for seeking and measurement. Packaging workflows preserve cue points and create compatible renditions for both content and creatives.
Key facts
- 1Ad decisioning and media delivery are separate concerns: a decision service selects a creative, while the player or packager must still present compatible encoded segments.
- 2Server-side insertion can make program and advertising appear as one stream, but accurate reporting still depends on event signaling and cannot be inferred from file delivery alone.
- 3Creative duration, codec, resolution, audio layout, and segment boundaries need alignment with the program path; mismatches can cause discontinuities or playback failure.
When AVOD matters
An AVOD service must coordinate playback with ad selection, insertion markers, and measurement. Client-side insertion is simpler to separate, while server-side insertion can reduce visible transitions.
Common use cases for streaming
These examples cover streaming broadly, not specifically AVOD.
- 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 AVOD.
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.