---
title: "HLS (HTTP Live Streaming) — How It Works | Kinescope"
description: "HLS (HTTP Live Streaming) is Apple's adaptive streaming protocol — .m3u8 manifests and segmented delivery that plays on every browser, device and smart TV."
url: https://kinescope.com/glossary/hls
---

# *HLS* (HTTP Live Streaming)

The adaptive streaming protocol that carries video to virtually every browser, phone and smart TV — using short segments and a small playlist file.

**Updated:** October 2026 **5 min read** **Protocols · Streaming**

In short

HLS chops a video into short segments at several qualities and describes them in a tiny .m3u8 playlist — the near-universal way streaming reaches every browser, phone and TV.

## What is HLS (HTTP Live Streaming)?

HLS (HTTP Live Streaming) is an [adaptive bitrate](https://kinescope.com/glossary/adaptive-bitrate) Adaptive Bitrate (ABR)Automatically adjusts video quality in real time to match each viewer’s connection speed — smooth playback from 480p to 4K with no buffering.[Open definition →](https://kinescope.com/glossary/adaptive-bitrate) streaming protocol developed by Apple. Instead of sending one large video file, HLS breaks the video into a series of short segments — typically 2–6 seconds each — encoded at several quality levels, and describes them in a small playlist file called a [manifest](https://kinescope.com/glossary/manifest) ManifestA small index file (.m3u8 or .mpd) that lists every available rendition and segment so the player knows what it can request.[Open definition →](https://kinescope.com/glossary/manifest) .

Because segments are delivered over ordinary HTTP, HLS travels through any standard web server, cache and [CDN](https://kinescope.com/glossary/cdn) CDN (Content Delivery Network)A global network of edge servers that caches video close to viewers, cutting latency and absorbing traffic spikes.[Open definition →](https://kinescope.com/glossary/cdn) — no special streaming server required. That simplicity is why HLS became the most widely supported streaming protocol in the world: it plays natively on Safari, iOS, Android, and every major smart-TV platform, and through JavaScript players like hls.js everywhere else.

Originally built for live streaming, HLS is now used for both live and on-demand video across the industry — from short marketing clips to full [live broadcasts](https://kinescope.com/products/streaming).

## How HLS works

An HLS stream has two moving parts: manifests that describe the stream, and media segments that carry the actual video. It rides the same pipeline every adaptive stream does:

The Kinescope video pipeline

Upload Source file

[Transcode Rendition ladder](https://kinescope.com/glossary/transcoding) [Segment 2–6s chunks](https://kinescope.com/glossary/hls) [Manifest .m3u8 / .mpd](https://kinescope.com/glossary/manifest) [Player Adaptive playback](https://kinescope.com/glossary/adaptive-bitrate)

HLS is the packaging and delivery half of this pipeline: the segments and the .m3u8 manifest the player reads.

Following the stream from source to screen:

**Transcoding into a rendition ladder**

The source is [transcoded](https://kinescope.com/glossary/transcoding) TranscodingRe-encoding a source video into multiple resolutions and bitrates so a player can switch between quality levels on the fly.[Open definition →](https://kinescope.com/glossary/transcoding) into several resolutions and bitrates — for example 1080p, 720p, 480p and 360p — so the player has quality options to switch between.

**Segmenting each rendition**

Every rendition is cut into short chunks. Historically these were MPEG-TS `.ts` files; modern HLS also supports fragmented MP4 (`fMP4`), which lets HLS and DASH share the same media.

**Writing the manifests**

A **master playlist** (`.m3u8`) lists the available renditions; each rendition has its own **media playlist** listing its segment URLs in order. The player fetches the master first.

**Adaptive playback**

The player measures throughput as it downloads segments and requests the next segment from whichever rendition best fits the connection — switching quality invisibly, segment by segment.

How Kinescope handles this

### HLS, packaged and played — nothing to configure

Upload a video and Kinescope produces HLS automatically: transcoding builds the ladder, the manifests are written for you, and an adaptive player reads them on every browser, phone and TV. **The primary protocol for hosting and live.**

[Explore the adaptive player](https://kinescope.com/products/video-player)

## HLS vs. DASH

HLS and [DASH](https://kinescope.com/glossary/dash) DASHDynamic Adaptive Streaming over HTTP — an open ISO standard using .mpd manifests, common for DRM-protected premium content.[Open definition →](https://kinescope.com/glossary/dash) are the two dominant adaptive streaming protocols. They solve the same problem in similar ways; the differences are mostly about origin, device support, and [DRM](https://kinescope.com/glossary/drm) DRMEncryption of the video file plus a licence server that issues a per-session key — so a downloaded copy stays unplayable.[Open definition →](https://kinescope.com/glossary/drm) .

| Aspect | HLS | DASH |
| --- | --- | --- |
| Created by | Apple | MPEG (open ISO standard) |
| Manifest | `.m3u8` | `.mpd` |
| Segments | .ts or fMP4 | fMP4 |
| Device support | Universal, native on Apple | Broad, but not native on Apple |
| Native DRM | FairPlay | Widevine / PlayReady |
| Typical use | Default for most delivery | DRM-heavy premium content |

Most platforms serve both from the same fMP4 media to cover every device and DRM system. Kinescope offers HLS as its primary protocol, with DASH available for [DRM-protected](https://kinescope.com/solutions/video-hosting-drm) playback.

## Low-Latency HLS (LL-HLS)

Standard HLS introduces roughly 10–30 seconds of [latency](https://kinescope.com/glossary/latency) LatencyThe delay between a moment happening and a viewer seeing it. Critical for live — Low-Latency HLS brings it down to 2–5 seconds.[Open definition →](https://kinescope.com/glossary/latency) — acceptable for on-demand, but too much for interactive live. [Low-Latency HLS (LL-HLS)](https://kinescope.com/glossary/ll-hls) Low-Latency HLS (LL-HLS)Apple’s HLS extension that publishes partial segments and holds playlist requests, cutting live delay from 10–30 seconds to a few.[Open definition →](https://kinescope.com/glossary/ll-hls) , an official Apple extension, cuts the delay to a few seconds using partial segments and server push, so the player can start rendering a [CMAF](https://kinescope.com/glossary/cmaf) CMAF (Common Media Application Format)One fragmented-MP4 packaging that HLS and DASH can both play — a single set of segments for every device and the base of low-latency live.[Open definition →](https://kinescope.com/glossary/cmaf) chunk before it is fully written.

Kinescope's [live streaming](https://kinescope.com/glossary/live-stream) Live streamReal-time video delivered as it is captured, transcoded and segmented on the fly — webinars, events, broadcasts.[Open definition →](https://kinescope.com/glossary/live-stream) runs at roughly 5–10 seconds of signal delay, with LL-HLS available for lower-latency, interactive broadcasts such as webinars and Q&As.

Delivery, handled

### Every segment, served from a nearby edge

Because HLS rides plain HTTP, it caches beautifully. Kinescope serves your segments and manifests from a CDN across 84+ countries — **fast starts and steady playback**, wherever the viewer is.

[See the global CDN](https://kinescope.com/products/content-delivery-network)

## Further reading

-   [Apple — HTTP Live Streaming (HLS)](https://developer.apple.com/streaming/) — the official specification and developer resources.
-   [Online HLS player](https://kinescope.com/tools/hls-player) — paste an .m3u8 link to play it and see its renditions.
-   [HTTP Live Streaming — Wikipedia](https://en.wikipedia.org/wiki/HTTP_Live_Streaming) — a vendor-neutral overview.

[![Denis Konnov](https://kinescope.com/blog-assets/authors/denis-konnov.jpeg)](https://kinescope.com/authors/denis-konnov)

Written by

[Denis Konnov](https://kinescope.com/authors/denis-konnov) Verified

CMO at Kinescope

Denis leads marketing and content at Kinescope, working closely with the platform's engineers. This glossary is reviewed and kept up to date by the team building Kinescope's streaming, encoding and CDN delivery infrastructure.

## FAQ

Can’t find the answer you need? Check out our [Help Center](https://docs.kinescope.com/).

An MP4 is a single self-contained file downloaded (or progressively streamed) at one fixed quality. HLS instead splits the video into many short segments across several quality renditions and lets the player switch between them mid-playback based on bandwidth. MP4 is fine for a small download; HLS is what streaming platforms use for smooth adaptive delivery at scale.

An .m3u8 is the HLS manifest (playlist) — a small text file that lists the available quality renditions and the URLs of each video segment. The player downloads it first to learn what qualities exist, then requests segments accordingly. A master .m3u8 points to per-rendition media playlists.

They are related but not identical. Adaptive Bitrate (ABR) is the concept of switching quality to match bandwidth; HLS is one of the transport protocols (alongside DASH) that carries an ABR stream. HLS delivers ABR using .m3u8 manifests and segmented media.

Yes. HLS supports encryption and DRM — Apple FairPlay is the native DRM for HLS, and platforms often pair it with Widevine (usually via DASH) to cover every device. On Kinescope, DRM protection is available on paid plans without any separate configuration.

## Streaming that just plays.

Kinescope handles transcoding, HLS packaging, CDN delivery and the player — out of the box.

[Start free](https://app.kinescope.io/user/create?lang=en)[Read the docs](https://docs.kinescope.com/)
