react-player vs react-youtube vs react-lite-youtube-embed
React Video Player Libraries
react-playerreact-youtubereact-lite-youtube-embedSimilar Packages:
React Video Player Libraries

These libraries provide React components for embedding and controlling video playback from platforms like YouTube. They simplify the process of integrating video content into React applications, offering various features and customization options to enhance user experience. Each library has its own strengths, catering to different needs in terms of performance, ease of use, and feature set.

Npm Package Weekly Downloads Trend
3 Years
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
react-player1,471,76410,04440.5 kB346 days agoMIT
react-youtube596,4841,89174.2 kB84-MIT
react-lite-youtube-embed80,312346108 kB04 days agoMIT
Feature Comparison: react-player vs react-youtube vs react-lite-youtube-embed

Lightweight Design

  • react-player:

    react-player is more feature-rich, which can lead to a larger bundle size. However, it provides extensive functionality that may justify the additional weight for applications requiring multiple media sources and advanced features.

  • react-youtube:

    react-youtube balances lightweight design with functionality, providing a straightforward way to embed YouTube videos without excessive overhead. It is optimized for simplicity while still offering essential features.

  • react-lite-youtube-embed:

    react-lite-youtube-embed is designed to be minimalistic, ensuring fast loading times and a small footprint. It avoids unnecessary dependencies and focuses solely on embedding YouTube videos, making it an excellent choice for performance-sensitive applications.

Customization Options

  • react-player:

    react-player offers a high level of customization, allowing developers to control playback options, styles, and events. This makes it suitable for applications that require a tailored video player experience.

  • react-youtube:

    react-youtube provides basic customization options, such as player parameters and event handling, making it easy to adapt the player to specific needs without overwhelming complexity.

  • react-lite-youtube-embed:

    Customization options are limited in react-lite-youtube-embed, focusing on the core functionality of embedding videos. It is best for developers who prefer a straightforward implementation without the need for extensive customization.

Ease of Use

  • react-player:

    react-player has a steeper learning curve due to its extensive features, but it is well-documented, making it manageable for developers willing to invest time in understanding its capabilities.

  • react-youtube:

    react-youtube is user-friendly and straightforward, making it easy for developers to get started with embedding YouTube videos. Its API is intuitive, allowing for quick integration into projects.

  • react-lite-youtube-embed:

    react-lite-youtube-embed is extremely easy to use, with a simple API that allows developers to quickly embed YouTube videos with minimal setup. This makes it ideal for beginners or projects that prioritize speed of implementation.

Event Handling

  • react-player:

    react-player excels in event handling, providing a comprehensive set of events that can be listened to, such as onPlay, onPause, and onEnded. This makes it suitable for applications that require detailed tracking of user interactions with the video.

  • react-youtube:

    react-youtube provides essential event handling features, allowing developers to listen for events like play, pause, and end, making it a good choice for applications that need to respond to user actions.

  • react-lite-youtube-embed:

    react-lite-youtube-embed offers basic event handling capabilities, allowing developers to respond to video interactions, but it is limited compared to other libraries.

Support for Multiple Media Sources

  • react-player:

    react-player supports a wide range of media sources, including YouTube, Vimeo, and custom URLs. This versatility makes it an excellent choice for applications that need to handle various types of media content.

  • react-youtube:

    react-youtube is focused solely on YouTube, providing a dedicated solution for embedding YouTube videos. It is not suitable for applications that require support for other media platforms.

  • react-lite-youtube-embed:

    react-lite-youtube-embed is specifically designed for YouTube videos and does not support other media sources, making it less versatile for applications that require multi-source support.

How to Choose: react-player vs react-youtube vs react-lite-youtube-embed
  • react-player:

    Select react-player if you require a versatile and feature-rich player that supports multiple media sources, including YouTube, Vimeo, and custom URLs. It is suitable for applications that need extensive control over playback options and a customizable interface.

  • react-youtube:

    Opt for react-youtube if you want a straightforward and easy-to-use library specifically designed for YouTube videos. It offers a simple API for embedding YouTube videos with built-in controls and event handling, making it a great choice for projects focused solely on YouTube content.

  • react-lite-youtube-embed:

    Choose react-lite-youtube-embed if you need a lightweight solution that focuses on minimalism and performance, especially for projects where loading speed is critical. It is ideal for simple use cases where you want to embed YouTube videos without additional overhead.

README for react-player

ReactPlayer

Latest npm version Test Coverage Become a sponsor on Patreon

A React component for playing a variety of URLs, including file paths, HLS, DASH, YouTube, Vimeo, Wistia and Mux.


Version 3 of ReactPlayer is a major update with a new architecture and many new features. It is not backwards compatible with v2, so please see the migration guide for details.

Using Next.js and need to handle video upload/processing? Check out next-video.

✨ The future of ReactPlayer

Maintenance of ReactPlayer is being taken over by Mux. Mux is a video api for developers. The team at Mux have worked on many highly respected projects and are committed to improving video tooling for developers.

ReactPlayer will remain open source, but with a higher rate of fixes and releases over time. Thanks to everyone in the community for your ongoing support.

Usage

npm install react-player # or yarn add react-player
import React from 'react'
import ReactPlayer from 'react-player'

// Render a YouTube video player
<ReactPlayer src='https://www.youtube.com/watch?v=LXb3EKWsInQ' />

If your build system supports import() statements and code splitting enable this to lazy load the appropriate player for the src you pass in. This adds several reactPlayer chunks to your output, but reduces your main bundle size.

Demo page: https://cookpete.github.io/react-player

The component parses a URL and loads in the appropriate markup and external SDKs to play media from various sources. Props can be passed in to control playback and react to events such as buffering or media ending. See the demo source for a full example.

For platforms without direct use of npm modules, a minified version of ReactPlayer is located in dist after installing. To generate this file yourself, checkout the repo and run npm run build:dist.

Autoplay

As of Chrome 66, videos must be muted in order to play automatically. Some players, like Facebook, cannot be unmuted until the user interacts with the video, so you may want to enable controls to allow users to unmute videos themselves. Please set muted={true}.

Props

PropDescriptionDefault
srcThe url of a video or song to playundefined
playingSet to true or false to play or pause the mediaundefined
preloadApplies the preload attribute where supportedundefined
playsInlineApplies the playsInline attribute where supportedfalse
disableRemotePlaybackApplies the disableRemotePlayback attribute where supportedfalse
crossOriginApplies the crossOrigin attribute where supportedundefined
loopSet to true or false to loop the mediafalse
controlsSet to true or false to display native player controls.
  ◦  For Vimeo videos, hiding controls must be enabled by the video owner.
false
volumeSet the volume of the player, between 0 and 1
  ◦  null uses default volume on all players #357
null
mutedMutes the playerfalse
playbackRateSet the playback rate of the player
  ◦  Only supported by YouTube, Wistia, and file paths
1
pipSet to true or false to enable or disable picture-in-picture mode
  ◦  Only available when playing file URLs in certain browsers
false
widthSet the width of the player320px
heightSet the height of the player180px
styleAdd inline styles to the root element{}
lightSet to true to show just the video thumbnail, which loads the full player on click
  ◦  Pass in an image URL to override the preview image
false
fallbackElement or component to use as a fallback if you are using lazy loadingnull
wrapperElement or component to use as the container elementnull
playIconElement or component to use as the play icon in light mode
previewTabIndexSet the tab index to be used on light mode0

Callback props

Callback props take a function that gets fired on various player events:

PropDescription
onClickPreviewCalled when user clicks the light mode preview
onReadyCalled when media is loaded and ready to play. If playing is set to true, media will play immediately
onStartCalled when media starts playing
onPlayCalled when the playing prop is set to true
onPlayingCalled when media actually starts playing
onProgressCalled when media data is loaded
onTimeUpdateCalled when the media's current time changes
onDurationChangeCallback containing duration of the media, in seconds
onPauseCalled when media is paused
onWaitingCalled when media is buffering and waiting for more data
onSeekingCalled when media is seeking
onSeekedCalled when media has finished seeking
onRateChangeCalled when playback rate of the player changed
  ◦  Only supported by YouTube, Vimeo (if enabled), Wistia, and file paths
onEndedCalled when media finishes playing
  ◦  Does not fire when loop is set to true
onErrorCalled when an error occurs whilst attempting to play media
onEnterPictureInPictureCalled when entering picture-in-picture mode
onLeavePictureInPictureCalled when leaving picture-in-picture mode

Config prop

There is a single config prop to override settings for each type of player:

<ReactPlayer
  src={src}
  config={{
    youtube: {
      color: 'white',
    },
  }}
/>

Settings for each player live under different keys:

KeyOptions
youtubehttps://developers.google.com/youtube/player_parameters#Parameters
vimeohttps://developer.vimeo.com/player/sdk/embed
hlshttps://github.com/video-dev/hls.js/blob/master/docs/API.md#fine-tuning

Methods

Static Methods

MethodDescription
ReactPlayer.canPlay(src)Determine if a URL can be played. This does not detect media that is unplayable due to privacy settings, streaming permissions, etc. In that case, the onError prop will be invoked after attempting to play. Any URL that does not match any patterns will fall back to a native HTML5 media player.
ReactPlayer.addCustomPlayer(CustomPlayer)Add a custom player. See Adding custom players
ReactPlayer.removeCustomPlayers()Remove any players that have been added using addCustomPlayer()

Instance Methods

Use ref to call instance methods on the player. See the demo app for an example of this. Since v3, the instance methods aim to be compatible with the HTMLMediaElement interface.

Advanced Usage

Custom player controls

By default ReactPlayer is a chromeless player. By setting the controls prop to true, you can enable the native controls for the player. However, the controls will look different for each player. The ones based on HTML5 media players will look like the native controls for that browser, while the ones based on third-party players will look like the native controls for that player.

<ReactPlayer src='https://www.youtube.com/watch?v=LXb3EKWsInQ' controls />

If you like to add your own custom controls in a convenient way, you can use Media Chrome. Media Chrome is a library that provides a set of UI components that can be used to quickly build custom media controls.

Simple example (Codesandbox)
import ReactPlayer from "react-player";
import {
  MediaController,
  MediaControlBar,
  MediaTimeRange,
  MediaTimeDisplay,
  MediaVolumeRange,
  MediaPlaybackRateButton,
  MediaPlayButton,
  MediaSeekBackwardButton,
  MediaSeekForwardButton,
  MediaMuteButton,
  MediaFullscreenButton,
} from "media-chrome/react";

export default function Player() {
  return (
    <MediaController
      style={{
        width: "100%",
        aspectRatio: "16/9",
      }}
    >
      <ReactPlayer
        slot="media"
        src="https://stream.mux.com/maVbJv2GSYNRgS02kPXOOGdJMWGU1mkA019ZUjYE7VU7k"
        controls={false}
        style={{
          width: "100%",
          height: "100%",
          "--controls": "none",
        }}
      ></ReactPlayer>
      <MediaControlBar>
        <MediaPlayButton />
        <MediaSeekBackwardButton seekOffset={10} />
        <MediaSeekForwardButton seekOffset={10} />
        <MediaTimeRange />
        <MediaTimeDisplay showDuration />
        <MediaMuteButton />
        <MediaVolumeRange />
        <MediaPlaybackRateButton />
        <MediaFullscreenButton />
      </MediaControlBar>
    </MediaController>
  );
}

Light player

The light prop will render a video thumbnail with simple play icon, and only load the full player once a user has interacted with the image. Noembed is used to fetch thumbnails for a video URL. Note that automatic thumbnail fetching for Facebook, Wistia, Mixcloud and file URLs are not supported, and ongoing support for other URLs is not guaranteed.

If you want to pass in your own thumbnail to use, set light to the image URL rather than true.

You can also pass a component through the light prop:

<ReactPlayer light={<img src='https://example.com/thumbnail.png' alt='Thumbnail' />} />

The styles for the preview image and play icon can be overridden by targeting the CSS classes react-player__preview, react-player__shadow and react-player__play-icon.

Responsive player

Set width to 100%, height to auto and add an aspectRatio like 16 / 9 to get a responsive player:

<ReactPlayer
  src="https://www.youtube.com/watch?v=LXb3EKWsInQ"
  style={{ width: '100%', height: 'auto', aspectRatio: '16/9' }}
/>

SDK Overrides

You can use your own version of any player SDK by using NPM resolutions. For example, to use a specific version of hls.js, add the following to your package.json:

{
  "resolutions": {
    "hls.js": "1.6.2"
  }
}

Adding custom players

If you have your own player that is compatible with ReactPlayer’s internal architecture, you can add it using addCustomPlayer:

import YourOwnPlayer from './somewhere';
ReactPlayer.addCustomPlayer(YourOwnPlayer);

Use removeCustomPlayers to clear all custom players:

ReactPlayer.removeCustomPlayers();

It is your responsibility to ensure that custom players keep up with any internal changes to ReactPlayer in later versions.

Mobile considerations

Due to various restrictions, ReactPlayer is not guaranteed to function properly on mobile devices. The YouTube player documentation, for example, explains that certain mobile browsers require user interaction before playing:

The HTML5 <video> element, in certain mobile browsers (such as Chrome and Safari), only allows playback to take place if it’s initiated by a user interaction (such as tapping on the player).

Multiple Sources and Tracks

Since v3 if the player supports multiple sources and / or tracks, it works the same as the native <source and <track> elements in the HTML <video> or <audio> element.

<ReactPlayer controls>
  <source src="foo.webm" type="video/webm">
  <source src="foo.ogg" type="video/ogg">
  <track kind="subtitles" src="subs/subtitles.en.vtt" srclang="en" default>
  <track kind="subtitles" src="subs/subtitles.ja.vtt" srclang="ja">
  <track kind="subtitles" src="subs/subtitles.de.vtt" srclang="de">
</ReactPlayer>

Migrating to v3

ReactPlayer v3 is a major update with a new architecture and many new features. It is not backwards compatible with v2, so please see the migration guide for details.

Some providers have not been updated for v3, it is recommended to keep using v2 and vote to add this provider to v3 in discussions

Migrating to v2

ReactPlayer v2 changes single player imports and adds lazy loading players. Support for preload has also been removed, plus some other changes. See MIGRATING.md for information.

Supported media

Contributing

See the contribution guidelines before creating a pull request.

Thanks


Jackson Doherty

Joseph Fung