Using DASH Streaming

To access these features, Upgrade Now
This page has moved to a new location.  Please visit the updated location here.

Thanks for your patience while we update our documentation.

You will be automatically redirected in 10 seconds.

With an understanding of the underlying technologies behind MPEG DASH, it's time to configure JW Player 7 to play DASH streams.

DASH Configuration Options

If you are utilizing a form of DRM with your MPEG DASH setup, this block is used to configure it. A DRM block should be located inside of the source object within a playlist array. Additional information is found below in the Configuring DRM section.
1An Enterprise license is required to configure DRM


Creating DASH Streams

To package your content, A DASH packager is required to get your media ready to stream with JW Player. There are a few open-source packagers available for MP4 / ISO BMFF streams, including:

The DASH packager will convert your content to a valid, segmented ISOBMFF file and generate a DASH manifest (MPD file). Most DASH packagers can not transcode your media into multiple resolutions and bitrates. (DASHEncoder does both.)

Unsupported DASH Features

The following features are not supported with JW Player 7. Potential workarounds are listed:

  • Multitrack Audio - Currently supported with our Flash-based HLS provider.
  • DVR - Currently unsupported with our DASH provider..

Note: Embedded captions are now supported in vod streams in JW Player 7.7


The use of DRM can only be configured when a DASH stream is being used with an Enterprise license. Specific DRM configuration options are then nested inside of the drm object in a playlist source. Examples of embedding DRM are found in our DRM Article

This is Google's form of DRM. Widevine DRM will work only on Google Chrome and Firefox 47+. Inside of this configuration block, a url pointing to the location of your DRM server is required. An optional headers array can also be added for additional HTTP security. If you wish to enable this feature, it will need to be enabled by your stream provider.
Microsoft's form of DRM. This method of DRM will function on Internet Explorer 11+ and Edge on Windows 8.1+. A DRM server URL is required in the configuration block. Similar to Widevine, an optional headers array can also be added for additional HTTP security.
A basic form of DRM that lists a decryption key inside of your player configuration. This is the least secure form of DRM, though it is the simplest to implement across browsers. There are no additional server resources required to decrypt content with this method.
Using Multiple DRM Types
Using multiple forms of DRM can be configured by including the DRM type inside of a matching source object. In this scenario, it is possible to utilize different custom headers for each DRM type as well.

Embed examples of all of the above DRM types can be found in our DRM Article


A resultant embed with a DASH stream and DRM can be located below:


Did you find this article helpful?

Please log in to rate this article.