DASH

Dynamic Adaptive Streaming over HTTP

Services →
Introduced in Rel-10

DASH is an adaptive bitrate streaming standard that delivers media over HTTP by enabling clients to dynamically select video quality based on network conditions for smooth playback in mobile and broadband networks.

Category
Services
Introduced
Rel-10
Where
Services › Codecs
Specifications
45 specs
DASH Description Purpose Related Classification Detected Changes Specifications

Description

Dynamic Adaptive Streaming over HTTP (DASH) is an international standard for adaptive bitrate streaming that delivers media content from conventional HTTP web servers. Its architecture is client-driven, where the client autonomously selects media segments from different representations (bitrates, resolutions, codecs) listed in a Media Presentation Description (MPD) file. The MPD is an XML document that describes the structure of the media presentation, including timing, URLs, and characteristics of available media segments. The client periodically fetches this MPD and then requests individual media segments (typically a few seconds in duration) via standard HTTP GET requests. The core intelligence resides in the client's adaptation logic, which monitors real-time network conditions (like available bandwidth) and device parameters (like CPU load and screen resolution) to choose the next segment from the most appropriate representation, aiming to maximize quality while minimizing rebuffering.

The protocol operates by dividing the media content into a sequence of small HTTP-based file segments. Each segment contains a short interval of playback time, and for each interval, multiple alternative segments are encoded at different bitrates and resolutions. The client downloads these segments one by one. After downloading a segment, the client assesses conditions and decides which bitrate to select for the next segment. This decision happens seamlessly during playback, allowing for adaptation to changing network throughput, such as when a user moves from a 5G to a Wi-Fi network. DASH is codec-agnostic, supporting common video and audio codecs like AVC/H.264, HEVC/H.265, and AAC, and it can deliver both live and on-demand content.

Key components include the DASH client (the media player with adaptation logic), the HTTP server(s) hosting the segments and MPD, and the MPD itself. The MPD describes the temporal structure (Periods, Adaptation Sets, Representations, and Segments), accessibility (URL templates), and media characteristics (codec, resolution, bitrate). DASH's role in 3GPP networks is as a service enabler for media delivery, particularly for Multimedia Broadcast/Multicast Service (MBMS) and unicast streaming. It is integrated into the 3GPP Packet-Switched Streaming Service (PSS) and Multimedia Telephony Service (MTSI), providing a standardized method for efficient, scalable, and high-quality video streaming over mobile and fixed networks. Its use of HTTP allows it to leverage existing web infrastructure, including CDNs and caching proxies, making deployment straightforward and cost-effective.

Purpose & Motivation

DASH was created to address the challenges of delivering high-quality video over best-effort IP networks, particularly the Internet and mobile networks, where bandwidth fluctuates significantly. Prior to adaptive streaming, video was delivered via progressive download or real-time streaming protocols like RTSP, which often led to frequent buffering or poor quality when network conditions degraded. These methods typically locked the client into a single bitrate for the entire session, resulting in a suboptimal user experience. DASH solves this by enabling the client to adapt the media bitrate in real-time, ensuring continuous playback by trading off instantaneous video quality against the risk of rebuffering.

The historical context includes the proliferation of proprietary adaptive streaming solutions (like Apple's HLS and Microsoft's Smooth Streaming) which fragmented the market. 3GPP, in collaboration with MPEG, standardized DASH to create a single, interoperable solution. This was motivated by the need for a universal standard that could be deployed across different networks (3G, 4G, 5G, fixed) and devices, reducing complexity for content providers and enabling innovation in client adaptation algorithms. Standardization through 3GPP and ISO/IEC (as MPEG-DASH) ensured wide industry adoption.

DASH specifically addresses limitations of previous approaches by being purely HTTP-based, which simplifies traversal of firewalls and NATs, leverages ubiquitous HTTP caching for scalability, and decouples the streaming logic from the transport protocol. It gives content providers control over the offered representations and clients the intelligence to choose optimally, creating a robust system for delivering media in dynamic network environments, which is essential for mobile video consumption.

Classification

Part ofCMAF
Related approachesMBMSMTSI

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the primary update for the DASH function was the registration of URNs for DASH profiles. This formalized the identification of specific DASH application profiles within the 3GPP ecosystem.

  • URN Registration for DASH profiles TS 26.116CR0008
Rel-16 2 changes

In Release 16, the key new feature for DASH was the introduction of support for hybrid HLS/DASH services. This built upon the foundational support for HLS (HTTP Live Streaming) services that was also newly specified in this release. These enhancements allowed for services that could utilize both streaming formats.

  • Support of HLS and hybrid HLS/DASH services TS 26.347CR0008
  • Support of hybrid HLS/DASH services TS 26.348CR0007
Rel-18 2 changes

In Release 18, the updates to DASH focused on specific technical corrections in audio handling. These included a fix for the stereo channel mapping of HE-AAC and xHE-AAC codecs within a DASH adaptation set. Furthermore, a correction was made regarding audio encapsulation formats, specifically addressing issues in ISO BMFF, 3GP, CMAF, and DASH for 5G Media Streaming.

  • Correction to HE-AAC and xHE-AAC stereo mapping to DASH adaptation set TS 26.117CR0010
  • [5GMS3] Correction on Audio encapsulation in ISO BMFF, 3GP file format, CMAF and DASH TS 26.117CR0008

Explore further

Broader topics and technologies where DASH plays a role.

Defining Specifications

3GPP specifications that define or reference DASH, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15
TS 26.116 vj00 TV Video Formats for 3GPP Services Rel-19
TS 26.117 vj00 5G Media Streaming Speech/Audio Capabilities Rel-19
TS 26.118 vj00 Virtual Reality Media Formats Rel-19
TS 26.233 vf00 3GPP Packet-Switched Streaming Service (PSS) Rel-15
TS 26.307 vj00 3GPP HTML5 Profile Specification Rel-19
TS 26.346 vj20 MBMS User Services Media Codecs & Protocols Rel-19
TS 26.347 vj00 MBMS Transport Protocol and API (TRAPI) Rel-19
TS 26.348 vj00 xMB Interface Specification Rel-19
TS 26.501 vj30 5G Media Streaming (5GMS) Architecture Rel-19
TS 26.511 vj00 5G Media Streaming Profiles, Codecs & Formats Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 26.517 vj10 5G MBS User Service Protocols and Formats Rel-19
TS 26.802 vj20 Multicast Enhancements for 5G Media Streaming Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18
TS 26.827 vc00 IMS-based Streaming & Download Delivery Enhancements Rel-12
TS 26.841 vj00 Study on Media Messaging Enhancements Rel-19
TS 26.848 vc00 Enhanced MBMS for DASH over broadcast/unicast Rel-12
TS 26.849 vc10 MBMS Operation on Demand (MooD) Rel-12
TS 26.851 vb20 Enhancements to Multimedia (EMM) for PSS, MMS, MBMS Rel-11
TS 26.852 ve20 MBMS user service profiles, APIs and transport enabler study Rel-14
TS 26.854 vj00 Study on Haptics in 5G Media Services Rel-19
TR 26.857 vi00 Technical Report on Media Service Enablers Rel-18
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16
TR 26.905 vj00 Study on Mobile 3D Video Services Rel-19
TR 26.906 vj00 HEVC Evaluation for 3GPP Services Rel-19
TR 26.909 vj00 QoE Enhancement for Streaming Services Rel-19
TR 26.917 vj00 TV Service Enhancements over 3GPP Rel-19
TR 26.918 vj00 Virtual Reality Relevance Study for 3GPP Rel-19
TR 26.926 vj00 Traffic Models & Quality Evaluation for Media/XR in 5G Rel-19
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19
TR 26.929 vj00 QoE Metrics for VR Services Study Rel-19
TR 26.938 vj00 DASH Deployment Guidelines for 3GPP Networks Rel-19
TR 26.946 vj00 MBMS User Services Overview Rel-19
TR 26.948 vj00 Video enhancements for 3GPP Multimedia Services Rel-19
TR 26.949 vj00 TV Service Profiles for 3GPP Networks Rel-19
TR 26.955 vj00 Video Codec Analysis for 5G Services Rel-19
TR 26.956 vj01 Beyond 2D Video Formats & Codecs Study Rel-19
TR 26.957 vj00 Evaluation of MPEG DASH SAND for 3GPP Rel-19
TR 26.981 vj00 MBMS Provisioning & Content Ingestion Interface Study Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TR 26.999 vj00 VR Streaming Interoperability Test Material Rel-19
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19
TR 38.835 vi01 Technical Report on XR Enhancements for NR Rel-18
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.