Skip to content

CONCEPT Cited by 2 sources

Bitrate ladder

Definition

A bitrate ladder is the set of pre-encoded renditions of the same source content that a streaming service publishes for adaptive bitrate (ABR) playback. Each rung is a distinct (resolution, nominal bitrate) pair (often with other axes: codec, framerate, HDR mode). The client player picks a rung dynamically based on runtime signals (throughput, CPU, screen size) and can switch rungs across segment boundaries.

Canonical Netflix framing (Source: sources/2026-04-02-netflix-smarter-live-streaming-vbr-at-scale): "we produce a set of streams at different resolutions and nominal bitrates — often called a bitrate ladder — so devices can adapt to their current network conditions by switching between them."

Ladder shape and design degrees of freedom

Each rung trades bitrate against resolution (and therefore visual quality at that resolution). A typical ladder for a single title might look like:

Rung Resolution Nominal bitrate
1 240p 300 kbps
2 360p 600 kbps
3 480p 1.2 Mbps
4 720p 2.5 Mbps
5 1080p 5 Mbps
6 1080p 8 Mbps (high-detail)
… 4K 15+ Mbps

Design axes:

  • Per-codec ladders — AV1, HEVC, AVC are usually three separate ladders because each codec's bitrate-to-quality curve is different.
  • Per-content-complexity ladders — some services run per-title optimised ladders (easy content gets a shorter + lower-bitrate ladder; hard content gets a longer + higher-bitrate ladder).
  • Per-device-profile rungs — a 4K rung exists only if devices in the target market can drive 4K playback.

Why the ladder structure forces decode-side decisions

DASH / HLS publish the whole ladder to the player; the player picks rungs based on local signals. This forces the production side to emit N encodings per title (see concepts/multi-lane-encoding-pipeline) but keeps the client-side simple: fetch manifest → choose rung → segment-fetch loop.

Rate-control mode interacts with ladder design

A critical and often-missed coupling: the same nominal bitrate means different things under CBR and VBR. Under CBR, a 5 Mbps rung actually emits ≈5 Mbps second-to-second; under capped VBR, the same 5 Mbps-nominal rung may average well below 5 Mbps and spike up to the cap on hard scenes. Blindly re-using a CBR ladder when switching to VBR therefore under-spends on low rungs and causes quality to drop (Source: sources/2026-04-02-netflix-smarter-live-streaming-vbr-at-scale).

Netflix's 2026-01-26 Live CBR → VBR cutover surfaced this as a concrete ≈1-VMAF-point drop on the bottom rungs of the Live ladder. The fix was rung-by-rung VMAF-matched ladder tuning: compare each rung's VMAF between CBR and VBR, and lift the VBR nominal just enough to close the gap wherever it exceeded ≈1 VMAF point. Higher-bitrate rungs (the 8 Mbps rung in the Netflix example) were already close to CBR quality and were left unchanged.

Seen in

Last updated · 319 distilled / 1,201 read