Watching live television or on-demand video over the internet may appear straightforward, but delivering smooth playback involves several technical processes. A streaming platform must send video across different network conditions, support multiple devices, and adjust picture quality when internet speeds change. Two technologies commonly used to manage this process are HTTP Live Streaming (HLS) and MPEG-DASH.

Both are adaptive bitrate streaming methods that deliver video through standard internet infrastructure. They divide media into smaller segments and allow compatible players to select suitable quality levels during playback. However, they differ in their origins, playlist formats, ecosystem support, and implementation details. Understanding these differences helps explain how modern streaming services deliver content to viewers, including households in Sweden using smart TVs, computers, and mobile devices.

What Are HLS and MPEG-DASH?

HLS, short for HTTP Live Streaming, was developed by Apple to deliver video over HTTP connections. It became widely adopted because it works with Apple's software ecosystem and can be implemented across many other platforms through compatible players.

MPEG-DASH, or Dynamic Adaptive Streaming over HTTP, is an international streaming standard developed through MPEG. Rather than being tied to one company's technology, it provides a standardised framework for delivering adaptive video through different devices and software environments.

Both approaches use ordinary HTTP delivery, often through content delivery networks (CDNs). This means video segments can be distributed using infrastructure similar to that used for websites and other online content.

The main distinction is how each system describes available media, organises playback information, and handles compatibility across devices and applications.

How These Video Protocols Deliver Streaming Content

The fundamental purpose of video protocols such as HLS and MPEG-DASH is to make internet video playback more adaptable to changing network conditions. Instead of sending one continuous, fixed-quality video stream, a streaming service prepares several versions of the same content at different resolutions and bitrates.

For example, a programme might be available in standard definition, HD, and 4K. Each version is divided into short media segments. A compatible player downloads these segments as playback progresses and selects an appropriate quality based on available bandwidth, device capabilities, and buffer conditions.

This process is known as adaptive bitrate streaming (ABR).

If a viewer's internet connection becomes slower, the player can switch to a lower bitrate to reduce buffering. When network conditions improve, it may select a higher-quality version. The transition is generally designed to happen without requiring the viewer to restart playback.

This approach is particularly useful for households where several devices share one internet connection or where viewers switch between home broadband and mobile networks.

How HLS Works

HLS organises streaming information through playlists, commonly using the M3U8 file format. These playlists tell the player where to find media segments and which quality options are available.

A typical HLS setup includes two main playlist types:

• Master playlist: Lists available video and audio variants, including different resolutions and bitrates.

• Media playlist: Identifies the individual segments that make up a particular stream.

The player reads the playlist, selects an appropriate version, and requests the required segments through HTTP. As conditions change, it can move between available quality levels.

HLS has evolved considerably since its introduction. Earlier implementations commonly used MPEG-2 Transport Stream segments, while modern deployments can also use fragmented MP4 media. This flexibility allows services to support different devices and delivery requirements.

HLS also supports low-latency extensions designed to reduce the delay between a live event and what viewers see on their screens. These capabilities are useful for live sports, news, and interactive broadcasts where timing matters.

How MPEG-DASH Works

MPEG-DASH follows a similar adaptive streaming principle but uses a different structure to describe available content.

Its central information file is called a Media Presentation Description (MPD). This XML-based document tells the player how the media is organised, which representations are available, and how segments can be accessed.

An MPD can describe multiple video resolutions, audio languages, subtitle tracks, and different periods within a presentation. The player uses this information to request the appropriate media segments.

MPEG-DASH commonly uses fragmented MP4, although its specifications support different media arrangements. It is designed to work across a broad range of devices and software environments.

One important advantage is its standardised approach to describing streaming presentations. However, actual playback compatibility still depends on the player, supported codecs, device capabilities, and any digital rights management requirements.

Like HLS, MPEG-DASH also has low-latency options. These can reduce live-streaming delays when the content packaging, delivery infrastructure, and playback application are configured to support them.

HLS vs MPEG-DASH: Key Differences

Although both technologies provide adaptive streaming, their implementation details can influence which one a platform chooses.

Neither technology is automatically better in every situation. HLS may be a natural choice for services prioritising Apple-device compatibility, while MPEG-DASH can suit platforms seeking a standards-based approach across a varied device ecosystem.

Some services support both to reach a wider audience.

Why Device and Codec Compatibility Matter

A streaming protocol does not determine picture quality by itself. The video codec, resolution, bitrate, device hardware, and playback software all influence the final result.

For instance, a stream encoded using H.264 may work on a wider range of older devices than one using a newer codec that requires more recent hardware support. HEVC and AV1 can offer improved compression efficiency in suitable environments, but device and browser support must be considered.

Content protection is another factor. Streaming services may use digital rights management (DRM) systems to control access to licensed content. FairPlay is commonly used in Apple's ecosystem, while Widevine and PlayReady are frequently associated with other platforms. The selected streaming format and DRM configuration must work together with the playback device.

For viewers, these technical differences may appear as playback errors, missing video, or an application that works on one device but not another.

Which Protocol Is Better for Live Streaming?

The right choice depends on the service's audience, infrastructure, and performance requirements.

For live sports and other time-sensitive broadcasts, latency is an important consideration. Traditional segment-based streaming can introduce a delay because the player needs to download and buffer media before displaying it. Low-latency implementations reduce this delay through smaller segments or partial segments and more frequent delivery.

However, low latency requires coordination between the encoder, packager, CDN, and playback application. Simply choosing HLS or MPEG-DASH does not guarantee a near-real-time experience.

For on-demand films and television programmes, compatibility and reliable playback may matter more than achieving the lowest possible delay. Both protocols can deliver high-quality on-demand content when configured correctly.

Conclusion

HLS and MPEG-DASH solve the same broad problem: delivering internet video that can adapt to changing network conditions and different playback devices. They use different manifest formats and have distinct ecosystem strengths, but both support adaptive bitrate streaming and modern live and on-demand applications.

For viewers, the protocol is usually less important than the quality of the overall streaming setup. Device compatibility, internet stability, encoding choices, content delivery infrastructure, and player implementation all contribute to a reliable experience. Understanding how these technologies work makes it easier to appreciate the systems behind modern internet television.