hls.js vs react-player vs video.js vs plyr vs plyr-react vs videojs-record
Web Video Playback Libraries Comparison
1 Year
hls.jsreact-playervideo.jsplyrplyr-reactvideojs-recordSimilar Packages:
What's Web Video Playback Libraries?

These libraries are designed to facilitate video playback in web applications, providing various functionalities such as support for different video formats, customizable player interfaces, and integration with streaming protocols. They cater to different needs, from simple video playback to complex streaming scenarios, making it easier for developers to implement video features in their applications.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
hls.js1,047,76915,48623.9 MB1685 days agoApache-2.0
react-player1,021,0139,6591.5 MB98a year agoMIT
video.js640,53938,63717.9 MB5742 months agoApache-2.0
plyr149,43128,5505.3 MB9182 years agoMIT
plyr-react18,64749467.4 kB532 years agoMIT
videojs-record15,9681,4131.55 MB67a year agoMIT
Feature Comparison: hls.js vs react-player vs video.js vs plyr vs plyr-react vs videojs-record

Streaming Support

  • hls.js:

    hls.js is specifically designed for HLS streaming, allowing for adaptive bitrate streaming which adjusts video quality based on the user's network conditions, ensuring smooth playback even on fluctuating connections.

  • react-player:

    react-player supports a wide range of video sources including YouTube, Vimeo, and custom URLs, making it versatile for different streaming needs. However, it does not have built-in support for adaptive streaming.

  • video.js:

    video.js supports a variety of streaming protocols including HLS and DASH, making it a robust choice for applications that require extensive streaming capabilities.

  • plyr:

    Plyr supports various video formats including MP4, YouTube, and Vimeo, but does not specialize in streaming protocols. It is more suited for standard video playback rather than live streaming.

  • plyr-react:

    Similar to Plyr, plyr-react supports multiple video formats but is optimized for React applications. It does not provide specific streaming capabilities but can be used with other libraries for streaming.

  • videojs-record:

    videojs-record builds on video.js and allows for recording video and audio streams, making it ideal for applications that need to capture user-generated content.

Customization

  • hls.js:

    hls.js is a low-level library with minimal UI components, allowing developers to build their own custom player interfaces. This provides flexibility but requires more development effort for UI.

  • react-player:

    react-player is flexible and allows for customization of the player component, including controls and playback options, but relies on the underlying video source for UI elements.

  • video.js:

    video.js is highly customizable with a rich plugin ecosystem, allowing developers to extend functionality and modify the player interface to fit specific needs.

  • plyr:

    Plyr offers a highly customizable player interface with options for themes, controls, and layout, making it easy to match the player with the application's design.

  • plyr-react:

    Plyr-react inherits Plyr's customization features and allows for easy integration of custom styles and components within a React application, providing a cohesive user experience.

  • videojs-record:

    videojs-record allows for customization of the recording interface and settings, enabling developers to tailor the user experience for recording video and audio.

Accessibility

  • hls.js:

    hls.js does not provide built-in accessibility features, as it focuses on streaming functionality. Developers need to implement accessibility features separately.

  • react-player:

    react-player does not have specific accessibility features, so developers must implement their own solutions to ensure the player is accessible to all users.

  • video.js:

    video.js has a strong focus on accessibility, providing features like keyboard navigation and support for screen readers, making it a good choice for inclusive applications.

  • plyr:

    Plyr is designed with accessibility in mind, providing keyboard navigation and screen reader support, making it suitable for a wide range of users.

  • plyr-react:

    Plyr-react inherits Plyr's accessibility features, ensuring that the player is usable for all users, including those with disabilities, when integrated into React applications.

  • videojs-record:

    videojs-record provides some accessibility features, but developers need to ensure that the recording interface is accessible to all users as it may require additional implementation.

Integration

  • hls.js:

    hls.js can be integrated into any web application but requires additional work to create a player interface, making it less convenient for quick implementations.

  • react-player:

    react-player is designed for React applications and allows for easy integration of various video sources, making it a flexible choice for developers.

  • video.js:

    video.js can be integrated into any web application and has a large community and resources available, making it easy to find support and examples.

  • plyr:

    Plyr is easy to integrate into any web project and provides a straightforward API for developers, making it a popular choice for quick setups.

  • plyr-react:

    plyr-react is specifically designed for React applications, making integration seamless and straightforward for developers familiar with React.

  • videojs-record:

    videojs-record extends video.js and can be easily integrated into applications that already use video.js, providing additional recording functionality.

Community and Support

  • hls.js:

    hls.js has a growing community and is actively maintained, but it may not have as extensive resources as larger libraries.

  • react-player:

    react-player has a strong community and is well-documented, making it easy for developers to get started and find solutions to common problems.

  • video.js:

    video.js has a large and active community with extensive documentation, tutorials, and plugins available, making it a reliable choice for developers.

  • plyr:

    Plyr has a supportive community and good documentation, making it easy for developers to find help and examples.

  • plyr-react:

    plyr-react benefits from the Plyr community and has documentation tailored for React developers, ensuring support for integration issues.

  • videojs-record:

    videojs-record has a smaller community compared to video.js but benefits from the video.js ecosystem, providing some level of support and resources.

How to Choose: hls.js vs react-player vs video.js vs plyr vs plyr-react vs videojs-record
  • hls.js:

    Choose hls.js if you need to implement HTTP Live Streaming (HLS) in your web application. It is lightweight and specifically designed for HLS playback, making it ideal for streaming live video content.

  • react-player:

    Use react-player if you need a versatile player that supports multiple video sources, including YouTube and Vimeo. It is highly customizable and works well within React applications, making it a good choice for projects that require flexibility in video sources.

  • video.js:

    Choose video.js for a robust and widely-used video player that supports a variety of formats and has a large plugin ecosystem. It is suitable for applications that require extensive customization and features like analytics and advertising.

  • plyr:

    Select Plyr for a simple, customizable, and accessible video player that supports various media types. It provides a clean interface and is easy to integrate into any project, making it suitable for general video playback needs.

  • plyr-react:

    Opt for plyr-react if you are developing a React application and want to leverage Plyr's features with React's component-based architecture. It allows for seamless integration and customization within React apps.

  • videojs-record:

    Select videojs-record if you need to implement recording capabilities in your video player. It extends video.js to allow users to record audio and video directly from the browser, making it ideal for applications that require user-generated content.

README for hls.js

npm npm Sauce Test Status jsDeliver

HLS.js

HLS.js is a JavaScript library that implements an HTTP Live Streaming client. It relies on HTML5 video and MediaSource Extensions for playback.

It works by transmuxing MPEG-2 Transport Stream and AAC/MP3 streams into ISO BMFF (MP4) fragments. Transmuxing is performed asynchronously using a Web Worker when available in the browser. HLS.js also supports HLS + fmp4, as announced during WWDC2016.

HLS.js works directly on top of a standard HTML<video> element.

HLS.js is written in ECMAScript6 (*.js) and TypeScript (*.ts) (strongly typed superset of ES6), and transpiled in ECMAScript5 using Babel and the TypeScript compiler.

Rollup is used to build the distro bundle and serve the local development environment.

Features

  • VOD & Live playlists
    • DVR support on Live playlists
  • Fragmented MP4 container
  • MPEG-2 TS container
    • ITU-T Rec. H.264 and ISO/IEC 14496-10 Elementary Stream
    • ITU-T Rec. H.265 and ISO/IEC 23008-2 Elementary Stream
    • ISO/IEC 13818-7 ADTS AAC Elementary Stream
    • ISO/IEC 11172-3 / ISO/IEC 13818-3 (MPEG-1/2 Audio Layer III) Elementary Stream
    • ATSC A/52 / AC-3 / Dolby Digital Elementary Stream
    • Packetized metadata (ID3v2.3.0) Elementary Stream
  • AAC container (audio only streams)
  • MPEG Audio container (MPEG-1/2 Audio Layer III audio only streams)
  • Timed Metadata for HTTP Live Streaming (ID3 format carried in MPEG-2 TS, Emsg in CMAF/Fragmented MP4, and DATERANGE playlist tags)
  • AES-128 decryption
  • "identity" format SAMPLE-AES decryption of MPEG-2 TS segments only
  • Encrypted media extensions (EME) support for DRM (digital rights management)
    • FairPlay, PlayReady, Widevine CDMs with fmp4 segments
  • Level capping based on HTMLMediaElement resolution, dropped-frames, and HDCP-Level
  • CEA-608/708 captions
  • WebVTT subtitles
  • Alternate Audio Track Rendition (Master Playlist with Alternative Audio) for VoD and Live playlists
  • Adaptive streaming
    • Manual & Auto Quality Switching
      • 3 Quality Switching modes are available (controllable through API means)
        • Instant switching (immediate quality switch at current video position)
        • Smooth switching (quality switch for next loaded fragment)
        • Bandwidth conservative switching (quality switch change for next loaded fragment, without flushing the buffer)
      • In Auto-Quality mode, emergency switch down in case bandwidth is suddenly dropping to minimize buffering.
  • Accurate Seeking on VoD & Live (not limited to fragment or keyframe boundary)
  • Ability to seek in buffer and back buffer without redownloading segments
  • Built-in Analytics
    • All internal events can be monitored (Network Events, Video Events)
    • Playback session metrics are also exposed
  • Resilience to errors
    • Retry mechanism embedded in the library
    • Recovery actions can be triggered fix fatal media or network errors
  • Redundant/Failover Playlists
  • HLS Variable Substitution

Supported HLS tags

For details on the HLS format and these tags' meanings, see https://datatracker.ietf.org/doc/html/draft-pantos-hls-rfc8216bis

Multivariant Playlist tags

  • #EXT-X-STREAM-INF:<attribute-list> <URI>
  • #EXT-X-MEDIA:<attribute-list>
  • #EXT-X-SESSION-DATA:<attribute-list>
  • #EXT-X-SESSION-KEY:<attribute-list> EME Key-System selection and preloading
  • #EXT-X-START:TIME-OFFSET=<n>
  • #EXT-X-CONTENT-STEERING:<attribute-list> Content Steering
  • #EXT-X-DEFINE:<attribute-list> Variable Substitution (NAME,VALUE,QUERYPARAM attributes)

Media Playlist tags

  • #EXTM3U (ignored)
  • #EXT-X-INDEPENDENT-SEGMENTS (ignored)
  • #EXT-X-VERSION=<n> (value is ignored)
  • #EXTINF:<duration>,[<title>]
  • #EXT-X-ENDLIST
  • #EXT-X-MEDIA-SEQUENCE=<n>
  • #EXT-X-TARGETDURATION=<n>
  • #EXT-X-DISCONTINUITY
  • #EXT-X-DISCONTINUITY-SEQUENCE=<n>
  • #EXT-X-BITRATE
  • #EXT-X-BYTERANGE=<n>[@<o>]
  • #EXT-X-MAP:<attribute-list>
  • #EXT-X-KEY:<attribute-list> (KEYFORMAT="identity",METHOD=SAMPLE-AES is only supports with MPEG-2 TS segments)
  • #EXT-X-PROGRAM-DATE-TIME:<attribute-list>
  • #EXT-X-START:TIME-OFFSET=<n>
  • #EXT-X-SERVER-CONTROL:<attribute-list>
  • #EXT-X-PART-INF:PART-TARGET=<n>
  • #EXT-X-PART:<attribute-list>
  • #EXT-X-SKIP:<attribute-list> Delta Playlists
  • #EXT-X-RENDITION-REPORT:<attribute-list>
  • #EXT-X-DATERANGE:<attribute-list> Metadata
    • HLS EXT-X-DATERANGE Schema for Interstitials
  • #EXT-X-DEFINE:<attribute-list> Variable Import and Substitution (NAME,VALUE,IMPORT,QUERYPARAM attributes)
  • #EXT-X-GAP (Skips loading GAP segments and parts. Skips playback of unbuffered program containing only GAP content and no suitable alternates. See #2940)

Parsed but missing feature support:

  • #EXT-X-PRELOAD-HINT:<attribute-list> (See #5074)
    • #5074

Not Supported

For a complete list of issues, see "Top priorities" in the Release Planning and Backlog project tab. Codec support is dependent on the runtime environment (for example, not all browsers on the same OS support HEVC).

  • #EXT-X-I-FRAME-STREAM-INF I-frame Media Playlist files
  • REQ-VIDEO-LAYOUT is not used in variant filtering or selection
  • "identity" format SAMPLE-AES method keys with fmp4, aac, mp3, vtt... segments (MPEG-2 TS only)
  • MPEG-2 TS segments with FairPlay Streaming, PlayReady, or Widevine encryption
  • FairPlay Streaming legacy keys (For com.apple.fps.1_0 use native Safari playback)
  • MP3 elementary stream audio in IE and Edge (<=18) on Windows 10 (See #1641 and Microsoft answers forum)

Server-side-rendering (SSR) and require from a Node.js runtime

You can safely require this library in Node and absolutely nothing will happen. A dummy object is exported so that requiring the library does not throw an error. HLS.js is not instantiable in Node.js. See #1841 for more details.

Getting started with development

Open in StackBlitz

First, checkout the repository and install the required dependencies

git clone https://github.com/video-dev/hls.js.git
cd hls.js
# After cloning or pulling from the repository, make sure all dependencies are up-to-date
npm install ci
# Run dev-server for demo page (recompiles on file-watch, but doesn't write to actual dist fs artifacts)
npm run dev
# After making changes run the sanity-check task to verify all checks before committing changes
npm run sanity-check

The dev server will host files on port 8000. Once started, the demo can be found running at http://localhost:8000/demo/.

Before submitting a PR, please see our contribution guidelines. Join the discussion on Slack via video-dev.org in #hlsjs for updates and questions about development.

Build tasks

Build all flavors (suitable for prod-mode/CI):

npm install ci
npm run build

Only debug-mode artifacts:

npm run build:debug

Build and watch (customized dev setups where you'll want to host through another server - for example in a sub-module/project)

npm run build:watch

Only specific flavor (known configs are: debug, dist, light, light-dist, demo):

npm run build -- --env dist # replace "dist" by other configuration name, see above ^

Note: The "demo" config is always built.

NOTE: hls.light.*.js dist files do not include alternate-audio, subtitles, CMCD, EME (DRM), or Variable Substitution support. In addition, the following types are not available in the light build:

  • AudioStreamController
  • AudioTrackController
  • CuesInterface
  • EMEController
  • SubtitleStreamController
  • SubtitleTrackController
  • TimelineController
  • CmcdController

Linter (ESlint)

Run linter:

npm run lint

Run linter with auto-fix mode:

npm run lint:fix

Run linter with errors only (no warnings)

npm run lint:quiet

Formatting Code

Run prettier to format code

npm run prettier

Type Check

Run type-check to verify TypeScript types

npm run type-check

Automated tests (Mocha/Karma)

Run all tests at once:

npm test

Run unit tests:

npm run test:unit

Run unit tests in watch mode:

npm run test:unit:watch

Run functional (integration) tests:

npm run test:func

Design

An overview of this project's design, it's modules, events, and error handling can be found here.

API docs and usage guide

Note you can access the docs for a particular version using "https://github.com/video-dev/hls.js/tree/deployments"

Demo

Latest Release

https://hlsjs.video-dev.org/demo

Master

https://hlsjs-dev.video-dev.org/demo

Specific Version

Find the commit on https://github.com/video-dev/hls.js/tree/deployments.

Compatibility

HLS.js is only compatible with browsers supporting MediaSource extensions (MSE) API with 'video/MP4' mime-type inputs.

HLS.js is supported on:

  • Chrome 39+ for Android
  • Chrome 39+ for Desktop
  • Firefox 41+ for Android
  • Firefox 42+ for Desktop
  • Edge for Windows 10+
  • Safari 9+ for macOS 10.11+
  • Safari for iPadOS 13+
  • Safari for iOS 17.1+ since HLS version 1.5.0 using Managed Media Source (MMS) WebKit blog

A Promise polyfill is required in browsers missing native promise support.

Please note:

Safari browsers (iOS, iPadOS, and macOS) have built-in HLS support through the plain video "tag" source URL. See the example below (Using HLS.js) to run appropriate feature detection and choose between using HLS.js or natively built-in HLS support.

When a platform has neither MediaSource nor native HLS support, the browser cannot play HLS.

Keep in mind that if the intention is to support HLS on multiple platforms, beyond those compatible with HLS.js, the HLS streams need to strictly follow the specifications of RFC8216, especially if apps, smart TVs, and set-top boxes are to be supported.

Find a support matrix of the MediaSource API here: https://developer.mozilla.org/en-US/docs/Web/API/MediaSource

Using HLS.js

Installation

Prepackaged builds are included with each release. Or install the hls.js as a dependency of your project:

npm install --save hls.js

A canary channel is also available if you prefer to work off the development branch (master):

npm install hls.js@canary

Embedding HLS.js

Directly include dist/hls.js or dist/hls.min.js in a script tag on the page. This setup prioritizes HLS.js MSE playback over native browser support for HLS playback in HTMLMediaElements:

<script src="https://cdn.jsdelivr.net/npm/hls.js@1"></script>
<!-- Or if you want the latest version from the main branch -->
<!-- <script src="https://cdn.jsdelivr.net/npm/hls.js@canary"></script> -->
<video id="video"></video>
<script>
  var video = document.getElementById('video');
  var videoSrc = 'https://test-streams.mux.dev/x36xhzz/x36xhzz.m3u8';
  if (Hls.isSupported()) {
    var hls = new Hls();
    hls.loadSource(videoSrc);
    hls.attachMedia(video);
  }
  // HLS.js is not supported on platforms that do not have Media Source
  // Extensions (MSE) enabled.
  //
  // When the browser has built-in HLS support (check using `canPlayType`),
  // we can provide an HLS manifest (i.e. .m3u8 URL) directly to the video
  // element through the `src` property. This is using the built-in support
  // of the plain video element, without using HLS.js.
  else if (video.canPlayType('application/vnd.apple.mpegurl')) {
    video.src = videoSrc;
  }
</script>

Alternative setup

To check for native browser support first and then fallback to HLS.js, swap these conditionals. See this comment to understand some of the tradeoffs.

<script src="https://cdn.jsdelivr.net/npm/hls.js@1"></script>
<!-- Or if you want the latest version from the main branch -->
<!-- <script src="https://cdn.jsdelivr.net/npm/hls.js@canary"></script> -->
<video id="video"></video>
<script>
  var video = document.getElementById('video');
  var videoSrc = 'https://test-streams.mux.dev/x36xhzz/x36xhzz.m3u8';
  //
  // First check for native browser HLS support
  //
  if (video.canPlayType('application/vnd.apple.mpegurl')) {
    video.src = videoSrc;
    //
    // If no native HLS support, check if HLS.js is supported
    //
  } else if (Hls.isSupported()) {
    var hls = new Hls();
    hls.loadSource(videoSrc);
    hls.attachMedia(video);
  }
</script>

Ensure correct time in video

HLS transcoding of an original video file often pushes the time of the first frame a bit. If you depend on having an exact match of frame times between original video and HLS stream, you need to account for this:

let tOffset = 0;
const getAppendedOffset = (eventName, { frag }) => {
  if (frag.type === 'main' && frag.sn !== 'initSegment' && frag.elementaryStreams.video) {
    const { start, startDTS, startPTS, maxStartPTS, elementaryStreams } = frag;
    tOffset = elementaryStreams.video.startPTS - start;
    hls.off(Hls.Events.BUFFER_APPENDED, getAppendedOffset);
    console.log('video timestamp offset:', tOffset, { start, startDTS, startPTS, maxStartPTS, elementaryStreams });
  }
}
hls.on(Hls.Events.BUFFER_APPENDED, getAppendedOffset);
// and account for this offset, for example like this:
const video = document.querySelector('video');
video.addEventListener('timeupdate', () => setTime(Math.max(0, video.currentTime - tOffset))
const seek = (t) => video.currentTime = t + tOffset;
const getDuration = () => video.duration - tOffset;

For more embed and API examples see docs/API.md.

CORS

All HLS resources must be delivered with CORS headers permitting GET requests.

Video Control

Video is controlled through HTML <video> element HTMLVideoElement methods, events and optional UI controls (<video controls>).

Build a Custom UI

Player Integration

The following players integrate HLS.js for HLS playback:

They use HLS.js in production!

| | | | | | :----------------------------------------------------------------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cdn77 | | | | | | | | |

Chrome/Firefox integration

made by gramk, plays hls from address bar and m3u8 links

License

HLS.js is released under Apache 2.0 License