How adaptive bitrate actually works

"Adaptive bitrate" gets thrown around as marketing. Here's what's actually happening under the hood — and why it's the single most important feature in mobile streaming.

Why streams freeze

Your encoder produces video at some rate — say 6 Mbps. Your network delivers whatever it can — say suddenly 3 Mbps. The difference has nowhere to go, so it queues in buffers. Latency climbs, the queue grows, and eventually playback stalls: the freeze. When the network recovers, the backlog rushes through: the fast-forward effect every IRL viewer knows.

The feedback loop

An adaptive encoder watches how fast data is actually being accepted by the network — via transport feedback like acknowledgments and send-queue depth. The loop is simple: if delivery lags production, cut the encoder's bitrate now, before the queue builds. If delivery has headroom, raise it gently.

Down fast, up slow

Good adaptation is asymmetric. Drops are cliff-shaped (you turned a corner, lost line-of-sight to the cell), so bitrate must fall in seconds. Recoveries are gradual and uncertain, so ramping up too eagerly just re-triggers the freeze. The result viewers see: a briefly softer picture instead of a frozen one — a trade every streamer should take.

Resolution belongs in the loop too

1080p at 1.5 Mbps looks like smeared blocks; 720p at 1.5 Mbps looks soft but watchable. Smart systems adapt resolution alongside bitrate so quality degrades gracefully.

What to look for in an app

Ask one question: "if my bandwidth halves mid-stream, what happens in the next five seconds?" If the answer isn't "bitrate follows automatically", keep looking.