MPD

Media Presentation Description

Services →
Introduced in Rel-9

MPD is an XML-based document used in DASH to describe a multimedia presentation's structure, available media segments, and their characteristics for adaptive bitrate streaming.

Category
Services
Introduced
Rel-9
Where
Services › Codecs
Specifications
32 specs
MPD Description Purpose Related Classification Specifications

Description

The Media Presentation Description (MPD) is a core metadata file defined by 3GPP for the Dynamic Adaptive Streaming over HTTP (DASH) standard. It is an XML document that provides a complete blueprint of a multimedia presentation, enabling a DASH client to dynamically request and adaptively play back media content. The MPD describes the temporal and structural relationships between media components, such as video, audio, and subtitles, which are segmented and stored on an HTTP server. It does not contain the media data itself but acts as a manifest or playlist, detailing how the presentation is organized over time (Periods) and how each media component is represented across different qualities (Representations) within Adaptation Sets.

Architecturally, the MPD is structured hierarchically. At the top level, it defines the overall presentation with attributes like media presentation duration and minimum buffer time. The presentation is divided into sequential Periods, which represent contiguous time intervals of the content, allowing for changes in content (e.g., main feature to advertisement) or encoding parameters. Within each Period, Adaptation Sets group media components that are logically associated, such as all video streams or all audio tracks in different languages. Each Adaptation Set contains multiple Representations, which are alternative encodings of the same media component at different bitrates, resolutions, or codecs. Each Representation is further divided into Segments, which are the actual media files (e.g., .mp4 or .m4s chunks) that the client downloads via HTTP GET requests. The MPD provides URLs, byte ranges, and timing information for these segments.

How it works involves the client first fetching and parsing the MPD before playback begins. Based on the MPD information and real-time network conditions (e.g., available bandwidth), the client's adaptation logic selects the most appropriate Representation to download segment by segment. This enables adaptive bitrate streaming, where the client can switch to a higher or lower quality Representation between segments to maintain smooth playback without buffering. The MPD can be static (all information is known in advance) or dynamic (updated periodically for live streaming, with new Periods and Segments added as they become available). The MPD also contains essential metadata such as codec information (e.g., HEVC, AAC), DRM protection system details (e.g., Common Encryption, signaling for MPEG-CENC), and accessibility features like role descriptors for different audio tracks (e.g., commentary, descriptive video). Its role is to decouple the media description from the delivery, providing a flexible, standardized way to enable efficient, reliable, and high-quality streaming services over best-effort IP networks like the internet and mobile networks.

Purpose & Motivation

The MPD was created to address the challenges of delivering high-quality, adaptive video streaming over HTTP, which became the dominant method for internet video distribution. Prior to DASH and the MPD, proprietary adaptive streaming solutions (like Apple's HLS or Microsoft's Smooth Streaming) used different manifest formats, leading to fragmentation and increased complexity for content providers who had to encode and store multiple versions of their content for different devices and platforms. The MDP, as part of the standardized DASH specification, provides a unified, interoperable format that enables a single set of encoded media segments to be described and delivered to any compliant client, reducing storage and operational costs.

The motivation for its development within 3GPP stemmed from the need to efficiently deliver multimedia services over mobile networks, where bandwidth is variable and congestion can occur. Traditional progressive download or non-adaptive streaming often resulted in poor user experience, with frequent buffering or low video quality. The MPD enables intelligent client-side adaptation by providing all necessary information for the client to make informed decisions about which media segment to fetch next based on current network conditions and device capabilities. This solves the problem of delivering a consistent, high-quality viewing experience across diverse networks and devices, which is critical for mobile operators and content providers.

Historically, it was introduced in 3GPP Release 9 as part of the initial DASH specifications, providing a foundational element for 3GPP's Packet-Switched Streaming Service (PSS) and later for Enhanced Multimedia Broadcast/Multicast Service (eMBMS) and 5G Media Streaming. It addressed the limitations of earlier 3GPP streaming protocols that were not natively adaptive or HTTP-based. By leveraging HTTP's ubiquity, caching, and firewall traversal, and combining it with the rich description in the MPD, DASH became a key enabler for scalable, efficient video delivery, forming the basis for modern streaming services, including over-the-top (OTT) platforms and broadcast-like services in mobile networks.

Classification

Part ofDASH

Evolution Across Releases

Rel-9 Initial

Introduced the initial MPD specification as part of the baseline Dynamic Adaptive Streaming over HTTP (DASH) standard. Defined the core XML schema, hierarchical structure with Periods, Adaptation Sets, and Representations, and support for on-demand content with static MPDs. Established the foundation for adaptive media delivery over 3GPP networks.

Explore further

Broader topics and technologies where MPD plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 22.816 ve10 3GPP TV Service Enhancement Technical Report Rel-14
TS 26.116 vj00 TV Video Formats for 3GPP Services 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.234 vj00 3GPP PSS Protocols and Codecs Specification Rel-19
TS 26.244 vj00 3GPP File Format (3GP) Specification Rel-19
TS 26.247 vj00 3GPP Progressive Download & DASH over HTTP Rel-19
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.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 26.517 vj10 5G MBS User Service Protocols and Formats Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TS 26.827 vc00 IMS-based Streaming & Download Delivery Enhancements Rel-12
TS 26.848 vc00 Enhanced MBMS for DASH over broadcast/unicast Rel-12
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
TR 26.905 vj00 Study on Mobile 3D Video 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.929 vj00 QoE Metrics for VR Services Study Rel-19
TR 26.938 vj00 DASH Deployment Guidelines for 3GPP Networks 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.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
TS 28.406 vj00 QoE measurement collection: info definition & transport Rel-19
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
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.