Adaptive bitrate streaming, or ABR, is the technology that decides which version of a video your device plays at any given moment. It runs silently in the background every time someone watches a video on YouTube, Netflix, or a brand's website, and most viewers never think about it. For creators and production studios, understanding how it works changes how you think about encoding, delivery, and the relationship between production quality and what audiences actually see.
What adaptive bitrate streaming actually does
When a video is prepared for delivery, it isn't encoded as a single file. It's encoded as multiple versions of the same content at different quality levels, sometimes called renditions. A typical streaming pipeline might produce 6 to 8 renditions, ranging from a low-resolution 360p version suitable for slow mobile connections up to a 4K or 1080p version for fast broadband. Each rendition is then split into short segments, usually 2 to 10 seconds long.
The player on the viewer's device downloads these segments one at a time. Before each download, it checks the current network speed and available buffer. If the connection is fast and stable, it selects the next segment from a high-quality rendition. If the connection drops, the player switches down to a lower rendition without pausing playback. The switch happens between segments, so viewers see a momentary dip in sharpness rather than a buffering spinner. That trade-off is deliberate. Uninterrupted playback scores higher in audience retention than pristine quality with stops.
The two dominant ABR protocols in use today are HLS (HTTP Live Streaming), developed by Apple, and MPEG-DASH, the international open standard. Most major platforms support both. HLS remains the more widely deployed of the two, particularly on mobile devices and smart TVs in the Australian market.
Why production decisions affect ABR performance
ABR doesn't begin at the CDN. It begins at the encoding stage, and the choices made there determine how well the technology performs for your audience. Compression is the critical variable. A video with complex, high-motion content, like a live concert or a fast-cut action sequence, requires more data per second to maintain acceptable quality at any given resolution. That means the low-bitrate renditions suffer more visibly than they would for a static talking-head interview.
This is worth understanding before production, not after. If a video is destined for mobile-first audiences with variable connections, shooting in high-contrast environments with lots of camera movement creates a harder encoding problem. The ABR system will still function, but the quality floor of the lower renditions drops. West Melbourne Studios factors encoding performance into production planning, particularly for content where the delivery platform is known to be mobile-heavy or where live streaming is involved.
The relationship between compression and perceived quality is one of the least-discussed aspects of the whole production-to-delivery chain. How video compression affects perceived quality online covers that relationship in detail, and it's worth reading alongside this piece if you're thinking through a full delivery strategy.
What CDNs do in the chain
A content delivery network (CDN) stores the video renditions and segments on servers physically close to the viewer. For an Australian audience, that typically means edge nodes in Sydney, Melbourne, and Brisbane rather than a single origin server in the United States. When the player requests a new segment, it pulls from the nearest edge node, reducing latency and improving the accuracy of the ABR algorithm's quality selection.
Without CDN distribution, the ABR system still works, but the player's bandwidth measurements become less reliable. A viewer in Melbourne pulling segments from a US-based origin will see inconsistent download times that cause the player to underestimate available bandwidth, defaulting to lower-quality renditions more often than necessary. For brands publishing video at scale, CDN infrastructure isn't optional.
How ABR intersects with viewer behaviour
ABR systems are optimised for continuous playback, not for visual quality at a specific moment. That design choice shapes viewer behaviour in ways brands and creators don't always account for. Viewers who jump to specific timestamps, which is common with long-form content using chapter markers, trigger a buffer reset. The player starts the ABR process from scratch at that new point, often defaulting to a lower-quality rendition for the first few seconds before climbing back up. This is particularly relevant for content where a viewer's first impression of a specific section matters.
Chapter markers have become a standard navigation tool in long-form video, and understanding that each jump resets the ABR state is useful context for anyone producing or editing that kind of content. How chapter markers are changing long-form video navigation goes deeper on the viewer behaviour side of that equation.
Offline viewing changes the equation entirely. Downloads bypass ABR because the full file is stored locally at a fixed quality level chosen at download time. That means offline viewers get consistent quality regardless of their later network conditions, but they're locked into whatever rendition the platform selected when they hit download. Platforms like Netflix let users choose the download quality manually. Most others make the decision automatically based on available storage.
Practical implications for brands commissioning video
If you're commissioning video for a campaign or a product launch, ABR has two direct implications for how you brief your production studio.
First, delivery platform matters at the brief stage. A video destined for your own website, served via a self-hosted player, needs more careful encoding planning than one uploaded to YouTube, where Google's infrastructure handles rendition generation automatically. For self-hosted video, the encoding ladder (the set of renditions produced) needs to be specified, not assumed.
Second, master file quality has a ceiling effect on ABR performance. If the production delivers a compressed, low-bitrate master file, no amount of CDN infrastructure or encoding sophistication can recover detail that was never captured. The quality ceiling of every rendition is set by the master. This is why West Melbourne Studios delivers archival-quality master files as a standard part of every project, separate from the distribution-ready exports. It keeps future re-encoding options open as delivery standards evolve.
ABR streaming is now the default infrastructure behind almost every video experience a viewer encounters. It runs well when it's thought about early, and it creates problems that are difficult to diagnose when it isn't.