HLS (HTTP Live Streaming)
HLS delivers video as short file segments over ordinary web servers and CDNs — the widest compatibility of any method, at the cost of higher latency.
How does delivery work?
The video is cut into segments a few seconds long and published alongside a playlist; the player reads the playlist and fetches segments in order. Because it needs no special server — just HTTP and a CDN — it scales well to large audiences.
Why does latency accumulate?
Encoding a segment, publishing it, and the player buffering several ahead all add up. Default configurations typically land at 10–30 seconds. Shorter segments cut the delay but raise request volume and the risk of stalls.
Where does it fit in live commerce?
Broadcasts with large audiences where real-time interaction isn't decisive. Where chat Q&A carries the show, or where order decides the outcome — first-come offers, auctions — low-latency HLS or WebRTC deserve a look instead.
Frequently Asked Questions
Q. How is HLS different from RTMP?
They cover different legs. RTMP is mostly camera-to-server ingest; HLS is server-to-viewer delivery. Using both in one broadcast is the normal arrangement.
Q. Why is HLS still so widely used?
Reach. It plays on browsers, mobile, and TVs with no special preparation, and it rides existing CDNs — which keeps cost and stability favorable when an audience surges.
Q. How is quality adjusted?
Several renditions are published and the player moves between them based on network conditions, dropping quality to avoid stalling. Two viewers can be watching different renditions at the same moment.
Related terms
Learn more
Last updated