← Swarmify Blog

DASH vs HLS in 2026: Latency, DRM, CMAF, and Which Protocol to Use

HLS and MPEG-DASH both deliver adaptive streaming over HTTP—but they differ in device support, DRM ecosystems, and how low you can push live latency. Here’s the practical 2026 breakdown.

Adam Binst · August 9, 2022 · Updated November 18, 2026 · 9 min read
Streaming pipelines with a padlock and speed gauges leading to video screens

TL;DR

  • Choose HLS when native Safari playback matters.
  • Choose DASH for a DASH-capable Android or smart-TV stack, particularly when it already uses Widevine or PlayReady.
  • CMAF can let both protocols share compatible media segments, while retaining separate playlists or manifests.
  • Test codecs, DRM, latency, and playback on your actual target devices.

What Is Adaptive Bitrate Streaming?

Adaptive bitrate (ABR) streaming offers multiple renditions of the same video. The player estimates network throughput and buffer conditions, then selects a suitable rendition to reduce interruptions. HLS and DASH describe the renditions available to the player.

What Is HLS?

Created by Apple in 2009, HLS (HTTP Live Streaming) is defined in RFC 8216 and was originally designed to solve a specific problem: getting video to play smoothly on iPhones over standard HTTP networks.

HLS works natively on Apple devices and Safari. Compatible web players also enable playback on other browsers and platforms.

How it works: HLS divides video into segments referenced by a playlist ending in .m3u8. The player can switch renditions as network conditions change. Our M3U8 player guide covers ways to play these files.

Apple’s HLS documentation describes low-latency HLS alongside conventional streaming. Actual live latency depends on the encoder, packaging, network, and player configuration.

What Is DASH?

MPEG-DASH (Dynamic Adaptive Streaming over HTTP) is an international standard, ISO/IEC 23009-1, for adaptive streaming. It separates the streaming protocol from the choice of media codecs; playback still depends on the codecs supported by the device and player.

DASH uses an XML-based manifest file (ending in .mpd) to tell a compatible player where to find video segments.

How Does CMAF Work With HLS and DASH?

CMAF (Common Media Application Format) can reduce duplication when delivering compatible media through both HLS and DASH.

Instead of creating separate media for each protocol, a compatible workflow can use one set of fragmented MP4 media with separate HLS playlists and DASH manifests. Codec, encryption, packaging, and device requirements determine whether those media can actually be shared. Learn more about video container formats.

Apple’s CMAF guidance describes using CMAF media with HLS. Sharing media can reduce storage and caching duplication, but the savings depend on the rest of the workflow.

Control room routing video streams to phones, laptops, and monitors

HLS vs. DASH: Key Differences Compared

The main differences are in manifests, playback support, and delivery configuration:

Feature HLS (HTTP Live Streaming) MPEG-DASH
Specification Apple-developed; published as an RFC MPEG international standard
Browser playback Native in Safari; player support elsewhere Requires a compatible player and media APIs
iOS Safari Support ✅ Native Compatible player required; support depends on device and configuration
Low latency mode LL-HLS uses partial segments and blocking playlist reloads Low-latency DASH can deliver CMAF chunks before segment completion
Manifest M3U8 playlists XML MPD
Video codecs Apple authoring permits H.264, HEVC, Dolby Vision, and AV1 Codec agnostic; device decoding support still matters
DRM System FairPlay on Apple devices; other systems vary by player Widevine or PlayReady on compatible devices

1. Device Compatibility: The “Safari Factor”

Safari on Apple devices supports HLS playback natively. DASH requires a compatible player. WebKit added Managed Media Source to iPhone in Safari 17.1; it requires an AirPlay source alternative or remote playback to be disabled. A compatible player can use that API for DASH.

2. Latency: LL-HLS vs. LL-DASH

Video latency is the delay between an event and playback. Apple’s LL-HLS example uses six-second segments divided into 200-millisecond parts; parts can be published before the full segment is complete. Its playlist example also uses blocking reloads and a part hold-back to keep the player near the live edge.

AWS reports that regular HLS typically runs 12–30 seconds behind live, versus 5–10 seconds for its LL-HLS workflows. In its documented test, one-second parts produced roughly 4–6 seconds of measured latency across the tested players. For hls.js specifically, latency fell from 8 seconds with two-second parts to 5 seconds with one-second parts, a 37.5% reduction in that test.

In the same AWS Media Services test, AVPlayer’s measured latency fell from 9.75 to 5.95 seconds when part duration changed from two seconds to one, a reduction of about 39%. This comparison reflects the test’s specific encoder, CDN, player, and hold-back settings.

For low-latency DASH, DASH-IF describes serving CMAF chunks before a segment is complete. Its dash.js example sets a four-second live delay; reducing that target can make the playback buffer less stable. These are configuration examples, not guarantees of end-to-end latency: measure from capture to playback across the encoder, CDN, and player.

3. DRM (Digital Rights Management)

Premium video services use DRM to restrict playback. The choice follows the device and player ecosystem rather than the protocol alone: Apple devices commonly use FairPlay, while compatible devices may use Widevine or PlayReady. HLS can also be used with other DRM systems on supported platforms.

Using CMAF with common encryption can help share encrypted media across delivery workflows. Apple’s CMAF guidance supports the cbcs scheme for encrypted HLS, but not the cenc encryption scheme. A shared encrypted copy therefore needs cbcs support in the target DASH players and DRM systems as well as compatible key delivery; otherwise, separate encrypted media may be necessary.

4. Codec & Video Quality

The codec affects file size, visual quality, and which devices can play a stream:

H.264 (AVC) is a widely supported baseline. HEVC and AV1 can improve compression, but support depends on the device, browser, and encoding profile. VP9 is another codec used in streaming; verify decoding support on your target devices.

Apple’s HLS authoring requirements include H.264, HEVC, and AV1. For on-demand video, Apple requires the average segment bitrate to be within 10% of the playlist’s declared average bandwidth. DASH also accommodates multiple codecs; choosing DASH does not guarantee that a device can decode every stream.

Apple’s authoring specification also requires measured peak bitrate for on-demand content to be within 10% of the playlist’s declared peak bandwidth. Accurate declarations help players choose an appropriate rendition.

For live streams, Apple’s authoring requirements set a different tolerance: measured peak bitrate must stay below 125% of the declared peak bandwidth. This is a packaging requirement for Apple devices, not a guarantee of available network capacity.

Scalability & CDN Behavior

Protocol choice affects more than just the player — it determines how well your video scales across a content delivery network.

Segment size matters. At one request per segment per track, six-second segments mean ten requests per minute; two-second segments mean thirty. Using the six-second segment duration that Apple recommends in its authoring specification reduces those segment requests by about 67% compared with two-second segments. Audio, playlists, partial segments, and retries add requests.

For example, if a live event needs lower delay than a conventional HLS stream, try LL-HLS with partial segments rather than simply cutting the full segment duration. Apple’s example retains six-second parent segments while publishing smaller parts. For on-demand training videos with no live-edge requirement, longer segments can reduce request volume without adding live delay.

Edge caching efficiency. Compatible HLS and DASH manifests can reference shared CMAF media, allowing a CDN to reuse cached resources. Actual savings depend on cache keys, packaging, and traffic.

Origin protection. An origin shield is a mid-tier cache between the CDN edge and origin. Live manifest traffic depends on playlist or MPD refresh settings and the player. Load-test the complete configuration.

Implementation: Getting Started

If you’re handling encoding yourself, start with this HLS fMP4 example, then evaluate a dual-protocol packager if your audience needs DASH too:

Step 1: Create HLS fMP4 output. This single-rendition FFmpeg example creates an HLS playlist and fragmented MP4 segments, not a DASH manifest or adaptive bitrate ladder:

ffmpeg -i input.mp4 \
  -c:v libx264 -preset medium -crf 23 -force_key_frames 'expr:gte(t,n_forced*6)' \
  -c:a aac -b:a 128k \
  -hls_segment_type fmp4 \
  -hls_time 6 \
  -hls_playlist_type vod \
  -f hls output.m3u8

For dual delivery, Shaka Packager’s DASH tutorial demonstrates producing HLS and DASH manifests from the same fragmented MP4 outputs. For example, with two pre-encoded, keyframe-aligned video files and audio in the first input:

packager \
  in=low.mp4,stream=audio,output=audio.mp4,playlist_name=audio.m3u8,hls_group_id=audio,hls_name=English \
  in=low.mp4,stream=video,output=low-video.mp4,playlist_name=low.m3u8 \
  in=high.mp4,stream=video,output=high-video.mp4,playlist_name=high.m3u8 \
  --hls_master_playlist_output master.m3u8 \
  --mpd_output stream.mpd

This unencrypted on-demand example packages the existing encodes; it does not create the bitrate ladder or configure DRM. The master playlist and MPD reference the same media outputs.

Step 2: Choose a player. On the client side, you need a JavaScript player that handles manifest parsing and adaptive switching:

  • HLS.js — handles HLS through supported browser media APIs.
  • dash.js — a DASH-IF reference player for DASH deployments.
  • Video.js — its bundled HTTP streaming component supports HLS and DASH on compatible browsers.

Step 3: Configure your CDN. Ensure your CDN is configured to serve the correct Content-Type headers: application/vnd.apple.mpegurl for .m3u8 files and application/dash+xml for .mpd files. Incorrect MIME types are a common cause of playback failures.

For a production ABR ladder, encode multiple renditions with aligned keyframes and validate playback across the ladder.

Which Protocol Should You Pick?

For a public website with iPhone and Safari visitors, start with HLS: Safari can play it without a JavaScript manifest parser. Add an HLS-capable player for browsers that need one.

For an Android app or smart-TV deployment already built around a DASH player and Widevine, DASH is a practical choice. Check the specific TV models and DRM licenses rather than assuming every device supports the same combination.

For a service serving both Apple devices and an existing DASH audience, offer both. CMAF can let compatible renditions share media while each player receives its own manifest.

🎬 Tired of YouTube’s limitations? SmartVideo offers ad-free playback without YouTube branding or suggested videos. See how it compares as a YouTube alternative.

Frequently Asked Questions

What is the main difference between HLS and DASH?

Apple developed HLS, whose specification is published as an RFC; MPEG-DASH is an international standard. They use different manifest formats and player ecosystems, while both support adaptive streaming.

Which is better for low latency: HLS or DASH?

Neither wins by protocol name alone. Use LL-HLS for native Apple playback and low-latency DASH for an existing DASH player stack. AWS reports 5–10 seconds for its LL-HLS workflows; DASH-IF illustrates a four-second player delay target, which is not an end-to-end measurement. Compare capture-to-screen results for your own workflow.

Does HLS support 4K video?

Yes. HLS supports 4K and HDR on compatible devices. HEVC is one option, but the codec and profile must match the device.

Can I play DASH on an iPhone?

Safari does not play DASH manifests natively, but a compatible JavaScript player can use Managed Media Source on supported iPhones. Availability also depends on codecs and configuration, including AirPlay handling.

What is CMAF and why does it matter?

CMAF defines a format for segmented media. Compatible HLS playlists and DASH manifests can reference the same media, reducing duplication when codec and encryption requirements permit.

Is RTMP still used for streaming?

RTMP is still commonly used for ingest, such as sending video from OBS to a server. Browser playback historically relied on Flash; services often convert the incoming stream to HLS or DASH for viewer delivery.

What is adaptive bitrate streaming?

Adaptive bitrate streaming offers multiple renditions. The player selects among them using network and buffer conditions, switching to a lower or higher bitrate as conditions change.


At Swarmify, our mission is to bring an accelerated, distraction-free video experience to websites of all sizes. Whether you’re a website owner, an agency, or you just want to get in on our affiliate program, we have a plan for you!

Keep Visitors on Your Page, Not YouTube’s

SmartVideo’s player is 2x lighter than a YouTube embed, with zero ads. No suggested videos, no one else’s logo.

Build your player
10% conversion increase
“We’ve had a 10% increase in conversion rate from lead to customer.”
Pedro C.
Dir. of Digital Marketing, White Jacobs
Instant side-by-side winner
“SmartVideo loaded immediately; YouTube took 5 seconds to start. It became a no-brainer.”
Aaron H.
IT Director, PizzaTV
Rankings improved
“Our search-engine rankings went up after we switched over to Swarmify.”
Philip A.
Owner, Ignite Images