MPEG-DASH
Adaptive Bitrate Streaming At Scale
MPEG-DASH
MPEG-DASH (Dynamic Adaptive Streaming over HTTP) is the open, vendor-neutral standard for delivering adaptive-bitrate video to viewers at scale over HTTP. It delivers segmented files that any CDN can cache and a wide range of players can consume, with particularly strong support across Android devices and HTML5 players. Wowza Streaming Engine packages a single live ingest into MPEG-DASH, then serves it as an HTTP caching origin to the edge network of your choice, or can be pushed to a CDN or storage.
MPEG-DASH Benefits Include:
- Open, Vendor-Neutral Standard: MPEG-DASH is an international ISO standard so it avoids lock-in and stays interoperable across players, devices, and infrastructure.
- Adaptive Bitrate Delivery: Generate multiple renditions of a single source, and switch between them automatically as bandwidth changes to keep playback smooth.
- CDN-Friendly Scale: MPEG-DASH delivers video as segmented, cacheable HTTP files, so standard CDNs distribute a stream to large concurrent audiences at predictable cost.
- Broad Player Support: MPEG-DASH plays on HTML5 players like Google Shaka Player or DASH-compatible players such as ExoPolayer.
- Codec Flexibility: MPEG-DASH supports H.264 as its baseline and can carry HEVC/H.265 through fmp4 or CMAF packaging, as well as WebM for VP8/9 and Opus.
- Content Protection: Wowza Streaming Engine can secure MPEG-DASH streams with Common Encryption and multi-platform DRM (WideVine, PlayReady) to protect high-value content for both live and on-demand delivery.
Deliver MPEG-DASH with Wowza Streaming Engine
One ingest path feeds many delivery paths, all from the same Wowza Streaming Engine media server:
Wowza Streaming Engine acts as a full HTTP streaming server and origin. One ingest path feeds many delivery paths, all from the same media server:
- Ingest an RTMP, SRT, RTSP, or WebRTC source and repackage it for delivery over MPEG-DASH, without building a second workflow.
- Generate adaptive-bitrate renditions with the Wowza Transcoder and normalize source codecs to H.264 or H.265 for efficient delivery.
- Serve as an HTTP caching origin to a CDN edge, including Fastly and Amazon CloudFront, to scale a stream horizontally to large audiences.
Wowza Streaming Engine’s MPEG-DASH implementation includes:
- Three DASH Packaging Modes: Package a single ingest as standard MPEG-DASH, CMAF MPEG-DASH, or WebM in DASH and produce fMP4 segments referenced by a .mpd manifest.
- CMAF Efficiency: Package content in fMP4 CMAF that both HLS and MPEG-DASH playlists reference, which streamlines encoding, reduces storage, and lowers CDN cost when delivering both protocols from one source.
- HTTP Caching Origin and Live Repeater: Configure a Live HTTP Origin application, or a CMAF live stream repeater in an origin/edge configuration, to distribute MPEG-DASH at scale across edge servers and CDNs. Or, use a Stream Target to push to the CDN or network storage and prevent the streaming server from being overrun with requests.
- Content Encryption: Apply Common Encryption and DRM to MPEG-DASH streams, including in origin/edge repeater configurations where DASH segments are built and encrypted on the edge.
- REST API and Automation: Create applications, enable and configure packagers, and configure delivery through the Wowza Streaming Engine REST API for repeatable, infrastructure-as-code deployments.
- Deployment Flexibility: Runs on bare metal, virtual machines, in containers, on-premises, hybrid, cloud, or at the edge, behind the same load balancers and gateways as the rest of your stack.
Applications of MPEG-DASH for Wowza
Wowza Streaming Engine turns any live ingest into open, standards-based delivery that scales across audiences and platforms:
- A CDN-friendly delivery path that scales a single live event to large concurrent audiences over standard HTTP infrastructure.
- A native delivery format for Android and HTML5 environments where an open, vendor-neutral standard is preferred.
- A protected-delivery path for premium live and on-demand content using Common Encryption and DRM.
- A bridge that converts contribution and real-time protocols into scalable, cross-platform playback without re-architecting the ingest side.
Wowza also extends MPEG-DASH across the workflows you already run:
- Deliver One Source Everywhere: Package a single ingest into MPEG-DASH alongside HLS and WebRTC from the same server to match each audience to the right device and scale.
- Package Once for HLS and DASH: Use the CMAF packager so HLS playlists and DASH manifests reference the same segments, cutting storage, encoding, and CDN costs.
- Build Origin-and-Edge Architectures: Pair a Live HTTP Origin application or CMAF live stream repeater with a CDN to distribute MPEG-DASH across a global footprint.
- Protect High-Value Content: Apply Common Encryption (CENC) and DRM to CMAF MPEG-DASH streams so protected content reaches supported players securely.
MPEG-DASH Frequently Asked Questions
What is MPEG-DASH?
MPEG-DASH (Dynamic Adaptive Streaming over HTTP) is an open ISO standard, created by the Moving Picture Experts Group, that delivers live and on-demand video as segmented, adaptive-bitrate files over standard HTTP. Because it is codec-agnostic and vendor-neutral, MPEG-DASH plays across a wide range of devices and players and scales over any HTTP CDN. Wowza Streaming Engine ingests contribution protocols such as RTMP, SRT, and WebRTC, then repackages the stream into MPEG-DASH for scalable delivery to viewers.
What is MPEG-DASH latency?
MPEG-DASH latency is typically 6 to 30 seconds end-to-end, because players buffer several segments before playback begins. Operators can reduce latency by tuning segment duration and the number of segments returned in the manifest, balancing lower delay against playback stability. For sub-second delivery to large audiences, production deployments pair MPEG-DASH with a real-time protocol such as WebRTC from the same Wowza Streaming Engine ingest.
What is the difference between MPEG-DASH and HLS?
MPEG-DASH is an open ISO standard with strong support on Android and HTML5 players, while HLS is Apple’s HTTP streaming protocol with native support across Apple devices. Both deliver segmented, adaptive-bitrate video over HTTP and scale well over CDNs. Wowza Streaming Engine can package a single ingest for both using the CMAF packager, so HLS playlists and MPEG-DASH manifests reference the same segments. This comparison shows where each fits:
| Attribute | MPEG-DASH | HLS |
| Standard | Open ISO standard (MPEG) | Apple specification |
| Native device strength | Android, HTML5 players | Apple devices, Safari |
| Typical latency | 6-30 seconds | 6-30 seconds |
| Manifest | .mpd | .m3u8 |
| Container | fMP4, CMAF, or WebM | MPEG-TS or CMAF |
What is CMAF, and how does it relate to MPEG-DASH?
CMAF (Common Media Application Format) is an open ISO standard container for both HLS and MPEG-DASH. Wowza Streaming Engine uses the CMAF packager to produce these shared segments, so a DASH manifest and an HLS playlist can reference the same media files. This streamlines encoding, reduces caching, optimizes CDN bandwidth, and lowers cost when delivering both protocols at scale.
Is MPEG-DASH free?
Yes. MPEG-DASH is an open, published ISO standard, and many open-source players support it. Most production deployments pair MPEG-DASH with a commercial media server such as Wowza Streaming Engine to handle ingest, transcoding, adaptive-bitrate packaging, security, and multi-protocol delivery at scale.
Does MPEG-DASH support encryption?
Yes. MPEG-DASH delivers over HTTPS with TLS, and Wowza Streaming Engine can protect MPEG-DASH content using Common Encryption (CENC), which applies AES to secure both live and on-demand streams and DRM for licensing. In origin/edge repeater configurations, the origin acquires the encryption keys and DASH segments are built and encrypted on the edge instances.
What codecs does MPEG-DASH support?
MPEG-DASH is codec-agnostic and supports H.264 as its broadly compatible baseline. For more efficient delivery, Wowza Streaming Engine can ingest or transcode to HEVC/H.265 and package it through CMAF for MPEG-DASH playback on supported players. It also supports VP8 and VP9 with WebM. Adaptive-bitrate HEVC delivery uses the Wowza Transcoder, which runs on Windows and Linux.
How do you set up MPEG-DASH streaming in Wowza Streaming Engine?
MPEG-DASH streaming in Wowza Streaming Engine takes three steps:
- Create a live application and enable MPEG-DASH as a playback type.
- Enable the appropriate packager, using the standard MPEG-DASH packager, or the CMAF packager when delivering HLS and MPEG-DASH from the same source.
- Connect a source encoder or camera, publish the stream, and optionally add a Live HTTP Origin application, Stream Target, or CMAF live stream repeater to scale delivery through a CDN.
Administrators can complete the configuration in Wowza Streaming Engine Manager or programmatically through the Wowza Streaming Engine REST API.
Is MPEG-DASH good for live streaming?
Yes. MPEG-DASH is well suited to large-audience live and on-demand delivery because it uses standard HTTP infrastructure, scales over any CDN, and plays across a wide range of devices as an open standard. Its role is last-mile delivery to viewers. Production deployments commonly ingest a contribution protocol such as RTMP or SRT into Wowza Streaming Engine, which repackages the stream into MPEG-DASH, often alongside HLS through CMAF, for cross-platform delivery at scale.