Tutorials Streaming

Roger Pantos: Streaming as Ordinary Web Files

By Infinite Creation · Profile

unknown-

No freely licensed image known

At a Glance

Roger Pantos designed HTTP Live Streaming at Apple, published in 2009. Instead of a specialised streaming protocol and server, HLS cuts video into short segments served as ordinary files over HTTP, listed in a plain-text playlist, with multiple quality versions the player can switch between. It became the dominant approach to internet video delivery.

Anchor year: 2009, HTTP Live Streaming
Worked at: Apple, United States
Strand: overlooked, the last link in the chain

Career

The problem as it stood

Streaming used dedicated protocols and servers, which firewalls blocked, caches could not store, and content delivery networks were not built for. Scaling to a large audience meant building specialised infrastructure everywhere.

What he actually did

Pantos' design segments the video into files of a few seconds each and describes them in a text playlist. The client fetches segments in sequence by ordinary HTTP. Several parallel renditions at different bitrates let the player switch quality between segments as conditions change.

How it worked

The insight is that the internet's entire delivery infrastructure, web servers, proxies, caches, CDNs, is already optimised for HTTP file delivery. Making video look like ordinary files means all of it works unchanged. Adaptive bitrate falls out naturally, because switching rendition is just fetching the next segment from a different list.

What it made possible

Streaming at global scale on existing infrastructure, adaptive quality as standard, and video delivery to phones over variable mobile connections. HLS and the similar MPEG-DASH carry the overwhelming majority of internet video today.

What happened to him

He has continued to develop the specification, published through the IETF, over more than a decade of revisions.

Where the credit landed

Pantos is named on the specification and is entirely unknown publicly, which is normal for protocol authors. HLS is the last technical link in this corpus's chain: the mechanism by which the descendants of Muybridge's sampled motion and Ahmed's transform actually arrive on a screen. It is a design whose cleverness lies in requiring nothing new of anyone.

Known For

Making video look like ordinary files means all existing web infrastructure works unchanged.
Adaptive bitrate falls out naturally from segmenting.
HLS and DASH carry the overwhelming majority of internet video today.

Knowledge Base

What You'll Learn

The final delivery mechanism succeeded by asking the internet for nothing it did not already have.

Why reusing HTTP beat purpose-built protocols

A dedicated streaming protocol is technically better suited to the task and requires new servers, new firewall rules, new caches and new CDN support everywhere. HLS is technically worse. Segmenting adds latency, and needs none of that, so it deployed globally almost immediately. This is the same pattern as the compact cassette, MIDI and the web: the design that demands least of everyone else wins, even when a better one exists.

Where This Fits

HLS turned streaming into ordinary web files, the modern transmission link in A History of Broadcast Technology.

FAQ

Q: What is HLS?
A: HTTP Live Streaming: video cut into short segments served as ordinary files over HTTP and listed in a text playlist, with multiple bitrate versions the player switches between as network conditions change.

Q: Why is HLS better than a dedicated streaming protocol?
A: It is technically worse in some respects, notably latency, but it uses ordinary web infrastructure. Servers, caches and CDNs. With no changes, so it scales globally without new deployment.

Vocabulary

Segmented delivery. Splitting a stream into short files delivered in sequence, rather than as one continuous connection. Lets ordinary web servers and caches carry video without special streaming software.

Playlist or manifest. A text file listing the segments making up a stream, refreshed as new ones appear. The client reads it to know what to request next, which is what keeps a live stream running.

Adaptive bitrate. Offering the same content at several qualities and letting the player switch between them as conditions change. Trades resolution for continuity, which viewers tolerate far better than stalling.

Edge cache. A copy of content stored near viewers rather than at the origin server. Segmented delivery works well with caching, because each segment is an ordinary file that can be stored and reused.

Sources

The specification was checked in both of its published forms. Checked 20 August 2026.

Roger Pantos, HTTP Live Streaming, Internet-Draft version 00. Dated 1 May 2009, with Roger Pantos of Apple as editor. This is the first published form of HLS and the document the 2009 anchor year above refers to. It expired, as Internet-Drafts do.
RFC 8216, HTTP Live Streaming. August 2017. Worth noting what it is and is not: an Independent Submission with informational status, not an IETF standard. It lists R. Pantos of Apple as editor and W. May of MLB Advanced Media, and it documents version 7 rather than the 2009 original.