What is FVOD?

FVOD, or free video on demand, provides programs on demand without charging viewers directly for access. The service is often funded through advertising or sponsorship.

Video master

Adaptive streaming

Adaptive playback

Adaptive streaming packages one source into aligned renditions that a player selects segment by segment. This diagram shows streaming broadly, not specifically FVOD.

How FVOD works

FVOD describes an access and revenue arrangement, not a codec, container, or streaming protocol. Viewers can start catalog titles without a direct rental or subscription charge, while the operator may fund distribution through advertisements, sponsorship, public funding, or another business goal. FVOD and AVOD overlap but neither is a subset of the other: free services can use funding other than advertising, while ad-supported services can also charge a subscription. In a media service, the FVOD decision affects entitlement, ad orchestration, analytics, and rights policy around an otherwise conventional on-demand pipeline.

Key facts

An FVOD asset can use the same HLS or DASH renditions as a paid title; its free status is enforced by catalog and entitlement systems rather than encoded into the media segments.
Server-side ad insertion can personalize manifests or stitch ad media into the stream, while client-side insertion coordinates separate playback. Each model has different failure and measurement behavior.
Free viewing does not imply unrestricted access: accounts, age gates, regional rights, or limited availability windows can still apply and must remain consistent across APIs and players.

Working with streaming

This guidance covers streaming broadly, not just FVOD.

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

Test the rendition ladder on slow, changing, and high-latency connections.
Align segments and keyframes, then validate manifests in the target players.
Measure startup, rebuffering, quality switches, CDN efficiency, and playback failures.