You’ve probably noticed that you rarely need to manually change the video quality on services like YouTube or Netflix. The stream just works, adjusting itself to look sharp on a strong connection and avoiding stutters on a weak one. This isn't magic; it's a sophisticated system called Adaptive Bitrate Streaming (ABR).

Instead of serving one massive video file, the server prepares multiple versions of the same video. Each version is encoded at a different quality level, creating a range from low-resolution, low-bitrate streams to crisp, high-definition ones. The video player on your device then intelligently picks the best version it can handle at any given moment, ensuring smooth playback.

The collection of different video versions is called an ABR ladder. Think of it like a staircase where each step represents a different combination of resolution and bitrate. When your network is strong, the player climbs to the top steps for the best quality. If your connection falters, it quickly steps down to a lower-quality version to avoid buffering. This process of encoding a video at multiple bitrates is the first crucial step in the ABR workflow.

But having different versions isn't enough. The video also needs to be broken down into small, manageable pieces, typically a few seconds long. These pieces are called segments or chunks. This segmentation is what allows the player to switch quality levels mid-stream. Instead of downloading one continuous file, it downloads a sequence of chunks, and it can decide which ladder rung to pull the next chunk from.

So how does the player know which bitrates are available and where to find all these chunks? It consults a manifest file. This is a small text file that acts as a playlist or an index for the video stream. It lists all the available ABR ladder rungs and provides the URLs for each sequential video chunk.

The two most common manifest formats are:

• M3U8: Used by HTTP Live Streaming (HLS), developed by Apple.
• MPD (Media Presentation Description): Used by Dynamic Adaptive Streaming over HTTP (DASH), an open standard.

When you press play, the client first downloads this manifest file. It sees the available streams (low, medium, high), picks one, and then starts requesting the individual video chunks listed in that stream's own playlist.

The real intelligence of ABR lies in the client-side video player. It constantly monitors network conditions to decide which chunk to download next. The player's logic generally follows one of two main strategies.

This is a reactive approach, responding directly to network performance.

This method is more conservative, prioritising a stall-free experience above all else. Modern players often use a hybrid of both approaches, using throughput to make opportunistic quality increases and buffer health to prevent playback stalls. This dynamic interplay ensures the best possible viewing experience under constantly changing network conditions.