Browser & Device Reference
This article lists which browsers and devices are officially supported by JW Player 8, including any existing limitations and differences between desktop and mobile. For JW Player 7 support, please see the JW7 Browser & Device Reference.
At JW Player, we endeavor to track and fix bugs across all browser versions that we officially support. But that does not mean that our player ceases to work on older browser versions. While we do not guarantee functionality, the player works well across nearly all browsers released within the past two years. We aim to officially support the 2-4 most recent versions of any browser, and make determinations about when to retire support for a version when plays dip below 0.75% per day.
The following desktop browsers are currently supported by JW Player 8:
- Not all media formats are supported in every browser (for example WebM video, Vorbis audio, and DASH). See Supported Media Formats for full details.
- Flash is no longer supported in JW Player and is only used to play HLS streams in IE11 on Windows 7.
We fully test and support the latest versions on the most popular devices. This table lists which mobile browsers are officially supported by JW Player 8 using HTML5:
|iPhone 5s+||Safari||iOS 9+|
|iPad 2+||Safari||iOS 9+|
|Any running Android 4.0+||Chrome||Android 4.0+|
|Facebook In-App Browser1||iOS/Android|
For a list of stats of device and operating system adoption, view these MixPanel trends.
As with desktop browsers, playback support for the various media formats varies. MP4 video and AAC/MP3 audio are safe formats for mobile. See Supported Media Formats for more details.
There are limitations to video playback on mobile devices compared to desktop browsers:
- Playing multiple videos at the same time is not possible on mobile web. However, playing multiple videos at the same time is possible using the JW Player SDKs.
- Some LG phones have not been configured to the current version of the SSL spec, and as a result, the device will not load any content over HTTPS. This issue has been observed in Android 4.
Did you find this article helpful?
Please log in to rate this article.