This documentation may be out-of-date. Please refer to the documentation for the latest ExoPlayer release on developer.android.com.

ExoPlayer supports DASH with multiple container formats. Media streams must be demuxed, meaning that video, audio and text must be defined in distinct AdaptationSet elements in the DASH manifest (CEA-608 is an exception as described in the table below). The contained audio and video sample formats must also be supported (see the sample formats section for details).

Feature Supported Comments
FMP4 YES Demuxed streams only
WebM YES Demuxed streams only
Matroska YES Demuxed streams only
MPEG-TS NO No support planned
Closed captions/subtitles    
TTML YES Raw, or embedded in FMP4 according to ISO/IEC 14496-30
WebVTT YES Raw, or embedded in FMP4 according to ISO/IEC 14496-30
CEA-608 YES Carried in SEI messages embedded in FMP4 video streams
EMSG metadata YES Embedded in FMP4
Content protection    
Widevine YES “cenc” scheme: API 19+; “cbcs” scheme: API 25+
PlayReady SL2000 YES Android TV, “cenc” scheme only
ClearKey YES API 21+, “cenc” scheme only
Live playback    
Regular live playback YES  
Ultra low-latency CMAF live playback YES  

Using MediaItem

To play a DASH stream, you need to depend on the DASH module.

implementation 'com.google.android.exoplayer:exoplayer-dash:2.X.X'

You can then create a MediaItem for a DASH MPD URI and pass it to the player.

// Create a player instance.
ExoPlayer player = new ExoPlayer.Builder(context).build();
// Set the media item to be played.
// Prepare the player.

If your URI doesn’t end with .mpd, you can pass MimeTypes.APPLICATION_MPD to setMimeType of MediaItem.Builder to explicitly indicate the type of the content.

ExoPlayer will automatically adapt between representations defined in the manifest, taking into account both available bandwidth and device capabilities.

Using DashMediaSource

For more customization options, you can create a DashMediaSource and pass it directly to the player instead of a MediaItem.

// Create a data source factory.
DataSource.Factory dataSourceFactory = new DefaultHttpDataSource.Factory();
// Create a DASH media source pointing to a DASH manifest uri.
MediaSource mediaSource =
    new DashMediaSource.Factory(dataSourceFactory)
// Create a player instance.
ExoPlayer player = new ExoPlayer.Builder(context).build();
// Set the media source to be played.
// Prepare the player.

Accessing the manifest

You can retrieve the current manifest by calling Player.getCurrentManifest. For DASH you should cast the returned object to DashManifest. The onTimelineChanged callback of Player.Listener is also called whenever the manifest is loaded. This will happen once for a on-demand content, and possibly many times for live content. The code snippet below shows how an app can do something whenever the manifest is loaded.

    new Player.Listener() {
      public void onTimelineChanged(
          Timeline timeline, @Player.TimelineChangeReason int reason) {
        Object manifest = player.getCurrentManifest();
        if (manifest != null) {
          DashManifest dashManifest = (DashManifest) manifest;
          // Do something with the manifest.

Customizing playback

ExoPlayer provides multiple ways for you to tailor playback experience to your app’s needs. See the Customization page for examples.