Adaptive Bitrate (ABR)
The technology that keeps video playing smoothly — regardless of how fast or slow your viewers' internet connection is.
ABR ships several quality versions of a video and lets the player pick the right one, live, per viewer — so nobody buffers and nobody is stuck at 480p on a fast line.
What is Adaptive Bitrate (ABR)?
Adaptive Bitrate streaming (ABR) is a method of video delivery where the player continuously monitors the viewer's available bandwidth and switches between different quality levels to maintain smooth playback. Instead of delivering a single fixed-quality stream, the video is prepared in several versions — typically 480p480pStandard-definition video, 480 pixels tall — 854×480 in 16:9. The fallback rung of the adaptive ladder for slow or metered connections.Open definition →, 720p720pHigh definition at 1280×720 — 921,600 pixels per frame. The entry point to HD and the fallback rung below Full HD.Open definition →, 1080p1080p (Full HD)Full HD at 1920×1080 — just over two million pixels. The default target for course, sales and web video.Open definition → and 4K4K (2160p)Ultra HD at 3840×2160 — four times the pixels of Full HD, and the point where codec choice starts paying for itself.Open definition → — and the player requests whichever version best matches the current connection speed.
The switching is invisible. A viewer on a slow mobile connection might spend most of their session watching at 480p, while someone on fiber gets uninterrupted 4K — and neither viewer has to do anything manually. If a mobile viewer suddenly gets a stronger signal, the player upgrades quality within seconds.
ABR is how every major streaming platform — Netflix, YouTube, Hulu — delivers video at scale. It's not a premium feature; it's the default expectation of modern video delivery.
Quality renditions in a Kinescope ABR stream
How Adaptive Bitrate works
ABR isn't magic — it's a well-defined pipeline: one upload fans out into a ladder of renditions, gets cut into segments, indexed by a manifest, and handed to the player.
The Kinescope video pipeline
Walking that pipeline stage by stage:
The source video is transcodedTranscodingRe-encoding a source video into multiple resolutions and bitrates so a player can switch between quality levels on the fly.Open definition → into several versions at different resolutionsResolutionThe pixel dimensions of a video frame — 480p, 720p, 1080p, 2160p (4K). Determines how sharp the picture looks on a given screen.Open definition → and bitratesBitrateThe amount of data used per second of video. Higher bitrate means more detail and a larger file; the core lever behind streaming quality.Open definition →. A typical ABR ladder for a 1080p upload produces 1080p, 720p, 480p and 360p renditions. A 4K source adds a 2160p rendition at the top.
Each rendition is cut into segments — typically 2–6 seconds each. Every segment is a standalone chunk the player can download and play independently, making quality switching possible mid-stream.
A manifestManifestA small index file (.m3u8 or .mpd) that lists every available rendition and segment so the player knows what it can request.Open definition → file (.m3u8 for HLSHLS (HTTP Live Streaming)Apple’s adaptive streaming protocol. Uses .m3u8 manifests and segmented delivery; supported on every browser, device and smart TV.Open definition →, .mpd for DASHDASHDynamic Adaptive Streaming over HTTP — an open ISO standard using .mpd manifests, common for DRM-protected premium content.Open definition →) lists all available renditions and their segment URLs. The player downloads this file first to understand what quality options exist.
The player measures download speed as it fetches segments. Based on current throughput and buffer level, an ABR algorithm decides which rendition to request next — switching can happen every few seconds, invisibly.
Common ABR algorithms
Different players implement different switching strategies. The three most common:
Throughput-based
Picks quality based on recent download speed. Simple, widely used. Can over-react to short bandwidth spikes.
Buffer-based (BBA)
Uses buffer fill level rather than bandwidth. More stable — upgrades when buffer is healthy, downgrades before it empties, which is what prevents bufferingBufferingWhen playback pauses to load more data. ABR exists largely to prevent it by stepping quality down before the buffer empties.Open definition →.
BOLA / model-based
Lyapunov optimization — balances throughput and buffer to maximize perceived quality. Used in dash.js and Shaka Player.
Recommended bitrate by resolution
Industry-standard target bitrates for H.264 (AVC) encoding. H.265 and AV1 achieve similar quality at roughly half these values.
| Resolution | Name | Min bitrate | Recommended | Typical use |
|---|---|---|---|---|
| 360p | SD | 300 kbps | 500–800 kbps | Fallback, very slow connections |
| 480p | SD | 600 kbps | 1–1.5 Mbps | Mobile, 3G/4G |
| 720p | HD | 1.5 Mbps | 2.5–4 Mbps | Most viewers — sweet spot |
| 1080p | Full HD | 3 Mbps | 5–8 Mbps | Desktop, WiFi, smart TV |
| 2160p | 4K | 10 Mbps | 15–25 Mbps | High-end displays, fiber |
Highlighted rows are the sweet spot for most audiences. Kinescope builds the full rendition ladder automatically from your source, so each viewer gets the best resolution their connection allows.
Want a feel for the numbers? Estimate the size of a single rendition and the connection a viewer needs:
Kinescope bitrate & file-size estimator
Estimated size
—
Connection needed
—
A single-rendition estimate at the recommended bitrate. Real adaptive delivery stores the whole ladder — Kinescope builds and serves it for you.
ABR vs. fixed bitrate streaming
Before ABR became standard, video was delivered at a single fixed bitrate. That model forced a hard tradeoff: serve high quality and risk buffering on slow connections, or serve low quality and disappoint everyone on fast connections.
| Aspect | Fixed bitrate | Adaptive Bitrate (ABR) |
|---|---|---|
| Quality on slow connections | Buffering / stall | Smooth at lower res |
| Quality on fast connections | Capped at one level | Maximum available quality |
| Bandwidth efficiency | Wastes bandwidth on static scenes | Adapts to both viewer bandwidth and scene complexity |
| Infrastructure complexity | Single file per video | Multiple renditions + manifest (handled by platform) |
| Viewer experience | All-or-nothing | Optimized per viewer |
| CDNCDN (Content Delivery Network)A global network of edge servers that caches video close to viewers, cutting latency and absorbing traffic spikes.Open definition → load | Uniform | Lower average — slow connections fetch less data |
ABR protocols: HLS and DASH
HLS (HTTP Live Streaming) was developed by Apple and is the most universally supported protocol. It uses .m3u8 manifest files and .ts video segments. Every browser, mobile OS and smart TV platform supports HLS. Kinescope uses HLS as its primary delivery protocol across both video hosting and live streaming.
DASH (Dynamic Adaptive Streaming over HTTP) is an open ISO standard. It uses .mpd manifests and .mp4 segments. Widely used for DRM-protected premium content, it is offered by Kinescope alongside HLS.
Low-Latency HLS (LL-HLS)
Standard HLS introduces 10–30 seconds of latencyLatencyThe delay between a moment happening and a viewer seeing it. Critical for live — Low-Latency HLS brings it down to 2–5 seconds.Open definition → — fine for on-demand video, but a problem for live events. LL-HLS cuts this to a few seconds by using partial segments and server push. Kinescope's live streamingLive streamReal-time video delivered as it is captured, transcoded and segmented on the fly — webinars, events, broadcasts.Open definition → runs at roughly 5–10 seconds of signal delay, with LL-HLS available for lower-latency, interactive broadcasts like webinars and Q&As.
Further reading
- Apple — HTTP Live Streaming (HLS) — the original HLS specification and developer resources.
- Adaptive bitrate streaming — Wikipedia — a vendor-neutral overview of the field.
