HLS (HTTP Live Streaming)
HLS is an adaptive streaming protocol where video is divided into small segments (typically 2-10 seconds), and a playlist file tells players where to find segments at various quality levels.
Where we use this- Delivery: from the origin, through the CDN, to the viewer's player.
- It plays on almost every device and passes through corporate firewalls.
- Latency. Standard HLS runs well behind real time; LL-HLS closes most of the gap.
What it means in live production.
HLS is an adaptive streaming protocol where video is divided into small segments (typically 2-10 seconds), and a playlist file tells players where to find segments at various quality levels. Players request segments sequentially, adapting quality based on network conditions. HLS is the standard for streaming to web browsers and mobile devices globally.
HLS works through HTTP, the same protocol web browsers use. This means HLS can work through any internet infrastructure without special ports or protocols. it works through corporate firewalls, cellular networks, and any network allowing HTTPS traffic. This ubiquity is why HLS dominates streaming.
How it works on a live production.
The mechanics: your encoder produces multiple bitrate versions of the stream (1080p, 720p, 480p, etc.), breaking each bitrate into segments and writing them to a web server. The encoder also generates a playlist file (m3u8) listing all available segments. A player downloads the playlist, examines available segments and quality options, requests segments at appropriate quality, and decodes them sequentially.
At Creative Broadcast Agency, HLS is our default for event streaming, corporate streaming, and webinars. For most audiences, HLS provides the right balance of quality, compatibility, latency, and reliability.
Latency with HLS depends on segment length. 2-second segments give roughly 6-8 seconds glass-to-glass latency (segments must be complete before playback). Smaller segments reduce latency but increase encoder complexity and playback instability. LLHLS (Low-Latency HLS) with 1-second segments or partial segment transmission achieves 2-4 second latency.
HLS has disadvantages: live content is cut into segments, meaning seeking live stream shows you jumping between segments (you can't smoothly pause/resume live content). Bitrate switches can cause quality dips. Buffering strategies differ across players, creating inconsistent experiences.
For esports broadcasts, where latency matters and viewers expect smooth playback, we often augment HLS with SRT contribution feeds and sometimes LLHLS output for primary audiences while maintaining standard HLS for broader compatibility.
Low-latency streaming
HLS is the default delivery format for our streams, and LL-HLS when latency matters.
Low-latency streaming
Sub-500ms glass-to-glass streaming via SRT and WebRTC. Real-time interaction for esports, auctions, trading floors, and live Q&A events.
ReadSRT (Secure Reliable Transport)
SRT is a modern streaming protocol designed to reliably transmit video over unpredictable networks, particularly useful for live streaming from remote locations with unstable internet, field coverage, and contribution feeds from distributed sources.
ReadRTMP vs SRT: which live streaming protocol should you use?
RTMP and SRT are the two protocols most often used to send a live feed from a venue to a platform or control room.
ReadNDI (Network Device Interface)
NDI is a protocol for real-time video transmission over IP networks, designed to be simpler and more flexible than SMPTE 2110 or SDI.
ReadIP-Based Broadcasting
IP-based broadcasting uses standard internet protocols (Ethernet, TCP/IP) to distribute broadcast signals instead of legacy specialised broadcast protocols (SDI, AES).
ReadQuestions people ask about this.
Why is HLS slower than RTMP?
HLS is segmented. each segment must be encoded and written to storage before playback can begin. This inherent segmentation creates latency. RTMP streams data continuously without waiting for segment completion, achieving lower latency. The trade-off: HLS works everywhere (through firewalls), RTMP requires open ports and special streaming infrastructure.
Can we stream to multiple platforms simultaneously using HLS?
Not exactly. HLS is typically streamed to a CDN or hosting platform (YouTube, Twitch, your website) rather than directly distributed. You might stream via SRT contribution to YouTube, which converts to HLS for delivery. Or you use a service that accepts HLS and re-delivers via other formats.
Do all devices support HLS?
Modern devices do (iOS, Android, modern web browsers, smart TVs). Older devices might require specific player software. For broadest compatibility, HLS is the standard choice. For specialized requirements (WebRTC for sub-second latency, DASH for specific clients), alternatives exist.
How do we decide segment length for HLS?
Balance between latency and stability. 10-second segments give 20-30 second total latency but are stable. 2-second segments give 6-8 second latency but require more reliable encoding and delivery. For corporate events, 10-second segments are fine. For esports, 2-3 second segments are standard.
Tell us the date, the venue and who is watching.
We scope every live production against its run of show, not a package.
CBA low latency streaming covers every show it produces, because transport decides whether the picture holds.