HLS & Low-Latency HLS (LL-HLS)
Confident, Reliable Last-Mile Delivery
HLS & Low-Latency HLS (LL-HLS)
HTTP Live Streaming (HLS) is the most broadly compatible way to deliver adaptive-bitrate video to viewers at scale. Low-Latency HLS (LL-HLS) extends that same delivery model to bring latency down without giving up HTTP reach or CDN economics. Wowza Streaming Engine packages a single live ingest into HLS and LL-HLS from one workflow to the edge network or destination of your choice.
HLS & LL-HLS Benefits Include:
- Universal Playback Reach: HLS plays natively on Apple devices, Safari, and across HTML5 players, set-top boxes, smart TVs, and mobile apps. One delivery format covers the widest possible audience.
- Adaptive Bitrate Delivery: The Wowza Transcoder generates multiple renditions of a single source, and players switch between them automatically as bandwidth changes to keep playback smooth.
- CDN-Friendly Scale: HLS delivers video over HTTP as segmented, cacheable files, so standard CDNs distribute a stream to large concurrent audiences at a predictable cost.
- Controllable, Tunable Latency: LL-HLS uses CMAF packaging and HTTP/2 to deliver partial segments, cutting glass-to-glass delay while keeping the HTTP delivery model intact.
- Built-In Backward Compatibility: A single LL-HLS stream reaches both new and older clients, with standard HLS as a fallback for players that don’t support LL-HLS.
- Secure Delivery: Wowza StreamLock SSL/TLS certificate management and HTTPS delivery ensure HLS and LL-HLS stream transport is secure. Multi-DRM ensures only entitled viewers can play the stream.
Deliver HLS & LL-HLS with Wowza Streaming Engine
One ingest path feeds many delivery paths, all from the same Wowza Streaming Engine media server:
- Ingest an RTMP, SRT, MPEG-TS, RTSP, or WebRTC source and repackage it for delivery over HLS, CMAF HLS, or LL-HLS, without building a second workflow.
- Generate adaptive bitrate renditions with the Wowza Transcoder, normalize codecs, and produce HEVC/H.265 output for efficient ABR delivery.
- Serve as an HTTP caching origin to a CDN edge to scale a stream horizontally to large audiences.
Wowza Streaming Engine’s HLS and LL-HLS implementation includes:
- Three HLS Packaging Modes: Package a single ingest as standard HLS (MPEG-TS segments over HTTP/1.1) or as LL-HLS (CMAF fMP4 partial segments over HTTP/2).
- CMAF Efficiency: Package content as CMAF that both HLS and MPEG-DASH playlists reference, streamlining encoding, reducing caching, and lowering CDN cost when delivering both protocols at scale.
- HEVC/H.265 Delivery: Ingest or transcode to HEVC/H.265 and deliver single or adaptive-bitrate HLS output for playback on iOS, macOS, and tvOS.
- Real-Time Transcoding: Run the Wowza Transcoder to generate ABR renditions and normalize source codecs to H.264 or H.265 for delivery.
- HTTP Caching Origin: Configure a Live HTTP Origin application to feed CDN edges that pull from the Wowza Streaming Engine origin for low-latency delivery at scale, or push chunks from Wowza Streaming Engine to storage for CDN delivery and origin protection.
- REST API and Automation: Create applications, enable/configure packaging, and configure delivery programmatically through the Wowza Streaming Engine REST API for repeatable, infrastructure-as-code deployments.
- Deployment Flexibility: Runs on bare metal, virtual machines, Docker, or in containers, on-premises, hybrid, cloud, or at the edge, behind the same load balancers and gateways as the rest of your stack.
Applications of HLS & LL-HLS for Wowza
Wowza Streaming Engine turns any live ingest into scalable, standards-based delivery that reaches viewers on the devices they already use:
- A CDN-friendly delivery path that scales a single live event to large concurrent audiences over standard HTTP infrastructure.
- A reduced-latency option through LL-HLS for sports, gaming, UGC content, and interactive broadcasts where a few seconds of delay changes the outcome.
- A broad-device distribution format that reaches all devices from one stream, including HTML5 players, smart TVs, mobile devices, and set-top boxes.
- A bridge that converts real-time and contribution protocols into scalable playback without re-architecting the ingest side.
Wowza also extends HLS and LL-HLS across the workflows you already run:
- Deliver One Source Everywhere: Package a single ingest into HLS, LL-HLS, MPEG-DASH, and WebRTC from the same server.
- Build Origin-and-Edge Architectures: Pair a Live HTTP Origin application with Fastly, CloudFront, or Google Cloud Media CDN to distribute low-latency HLS across a global footprint.
- Serve Adaptive Bitrate at Scale: Generate multiple renditions so players adapt to network conditions and viewers keep watching through congestion.
- Protect High-Value Content: Apply Common Encryption and DRM to CMAF HLS streams so protected content reaches supported players securely.
- Record and Stream Simultaneously: Deliver live video over HLS and LL-HLS while preserving a recording of the same ingest for VOD archives or on-demand publishing.
HLS & LL-HLS Frequently Asked Questions
What is HLS?
HLS (HTTP Live Streaming) is a protocol created by Apple that delivers live and on-demand video as segmented, adaptive-bitrate files over standard HTTP. Because it delivers media as cacheable files, any CDN can cache and distribute HLS, and nearly every modern device can play it. Wowza Streaming Engine ingests contribution protocols such as RTMP, SRT, MPEG-TS, and WebRTC, then repackages the stream into HLS for scalable delivery to viewers.
What is LL-HLS?
LL-HLS (Low-Latency HLS) is an extension of the HLS specification from Apple that reduces streaming latency while remaining backward compatible with standard HLS. Wowza Streaming Engine produces LL-HLS using the CMAF packager, which generates smaller partial segments delivered to players over HTTP/2. A player that supports HLS but not LL-HLS falls back to playing the stream as standard HLS.
What is HLS latency?
Standard HLS latency is typically 6 to 30 seconds end-to-end, because players buffer several segments before playback begins. LL-HLS reduces this to roughly 2 to 5 seconds by delivering partial segments as they are produced rather than waiting for a full segment to complete. Wowza Streaming Engine lets operators tune segment and chunk sizes to balance latency against playback stability.
What is the difference between HLS and LL-HLS?
HLS delivers complete video segments over HTTP/1.1 and prioritizes broad compatibility and scale, while LL-HLS delivers smaller partial segments over HTTP/2 to lower latency. Both use the same HTTP delivery model, and LL-HLS is backward compatible, so a single LL-HLS stream serves both low-latency players and standard HLS players. This comparison shows where each fits:
| Attribute | HLS | LL-HLS |
| Primary role | Scalable delivery to large audiences | Lower-latency delivery to large audiences |
| Typical latency | 6-30 seconds | 2-5 seconds |
| Transport | HTTP/1.1 | HTTP/2 (HTTPS required) |
| Container | MPEG-TS or fMP4 (CMAF) | fMP4 (CMAF) |
| Backward compatibility | Baseline | Falls back to standard HLS |
What is the difference between HLS and DASH?
HLS is Apple’s HTTP streaming protocol with native support across Apple devices, while MPEG-DASH is an open ISO standard with strong support on Android and HTML5 players. Both deliver segmented, adaptive-bitrate video over HTTP and scale well over CDNs.
Is HLS free?
Yes. HLS is an openly published specification with no licensing fee, and many open-source players support it. Most production deployments pair HLS with a commercial media server such as Wowza Streaming Engine to handle ingest, transcoding, adaptive-bitrate packaging, security, and multi-protocol delivery at scale.
Does HLS support encryption?
Yes. HLS and LL-HLS can be delivered over HTTPS with transport layer security (required for LL-HLS). Wowza StreamLock provides SSL/TLS certificate management for securing HTTPS delivery. For content protection beyond transport encryption, Wowza Streaming Engine fully supports multi-vendor DRM to secure both standard and CMAF HLS streams.
What codecs does HLS support?
HLS supports H.264 video with AAC audio as its universal baseline, which plays across virtually all HLS-capable devices. For more efficient delivery, Wowza Streaming Engine can ingest or transcode to HEVC/H.265 and deliver it over HLS through the CMAF packager for playback on Apple devices, including iOS, macOS, and tvOS. Adaptive-bitrate HEVC delivery uses the Wowza Transcoder, which runs on Windows and Linux.
How do you set up HLS and LL-HLS streaming in Wowza Streaming Engine?
HLS and LL-HLS streaming in Wowza Streaming Engine takes three, sometimes four, steps:
- Create a live application.
- For LL-HLS, configure an SSL/TLS certificate on the vHOST level for HTTPS playback.
- Enable the appropriate packager for the delivery format, using the Cupertino packager for standard HLS or the CMAF packager for CMAF HLS and LL-HLS.
- Connect a source encoder or camera, publish the stream, and optionally add a Live HTTP Origin application or use a Stream Target to scale delivery through a CDN.
Administrators can complete the configuration in Wowza Streaming Engine Manager or programmatically through the Wowza Streaming Engine REST API. Step-by-step instructions live in the Wowza documentation.
Is HLS still used for live streaming?
Yes. HLS remains the most widely used delivery protocol in live streaming because it plays on nearly every device and scales over standard CDN infrastructure. Its role is last-mile delivery to viewers, and LL-HLS now extends it into lower-latency use cases. Production deployments commonly ingest a contribution protocol such as RTMP or SRT into Wowza Streaming Engine, which repackages the stream into HLS and LL-HLS for delivery at scale.