react-player vs react-youtube
Embedding Video Content in React Applications
react-playerreact-youtubeSimilar Packages:

Embedding Video Content in React Applications

react-player and react-youtube are both React components designed to embed video players into web applications, but they serve different scopes. react-player is a general-purpose wrapper that supports multiple video platforms including YouTube, Vimeo, SoundCloud, and local file paths through a unified API. It abstracts away the differences between providers, offering a consistent interface for playback control and events. react-youtube, on the other hand, is a specialized component built specifically for the YouTube IFrame Player API. It provides direct access to YouTube-specific features and configuration options that may not be exposed by general wrappers, making it ideal for projects focused exclusively on YouTube content.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
react-player010,27740.5 kB6110 months agoMIT
react-youtube01,90374.2 kB83-MIT

react-player vs react-youtube: Architecture, API, and Use Cases

Both react-player and react-youtube solve the problem of embedding video content in React applications, but they approach it from different angles. react-player acts as a universal adapter for many video services, while react-youtube is a dedicated client for the YouTube IFrame API. Understanding their architectural differences is key to choosing the right tool for your media strategy.

๐ŸŽฌ Initialization: Universal URLs vs Specific IDs

react-player accepts a full URL string.

  • You pass the direct link to the video (e.g., https://www.youtube.com/watch?v=...).
  • The component detects the provider automatically and loads the correct player.
// react-player: Pass full URL
import ReactPlayer from 'react-player';

function Video() {
  return <ReactPlayer url='https://www.youtube.com/watch?v=ysz5S6PUM-U' />;
}

react-youtube requires a specific video ID.

  • You extract the ID (e.g., ysz5S6PUM-U) and pass it as a prop.
  • This forces you to handle URL parsing logic in your application code.
// react-youtube: Pass Video ID
import YouTube from 'react-youtube';

function Video() {
  return <YouTube videoId='ysz5S6PUM-U' />;
}

๐ŸŽฎ Playback Control: Props vs Internal API

react-player uses React props to control state.

  • You manage playing, volume, and muted via standard React state.
  • The component syncs these props with the underlying player automatically.
// react-player: Controlled via props
function ControlledPlayer() {
  const [playing, setPlaying] = useState(false);

  return (
    <ReactPlayer 
      url='https://www.youtube.com/watch?v=ysz5S6PUM-U' 
      playing={playing}
      onPlay={() => setPlaying(true)}
    />
  );
}

react-youtube exposes the internal player instance via events.

  • You often use refs or event callbacks to access the player object.
  • This allows direct calls to YouTube API methods like player.playVideo().
// react-youtube: Controlled via player instance
function ControlledPlayer() {
  const onReady = (event) => {
    const player = event.target;
    player.playVideo(); // Direct API call
  };

  return <YouTube videoId='ysz5S6PUM-U' onReady={onReady} />;
}

๐Ÿ“ก Event Handling: Unified vs Provider-Specific

react-player normalizes events across platforms.

  • Events like onPlay, onPause, and onEnd work the same for YouTube, Vimeo, or files.
  • You get a consistent data structure regardless of the video source.
// react-player: Unified events
<ReactPlayer 
  url='https://www.youtube.com/watch?v=ysz5S6PUM-U' 
  onPlay={() => console.log('Started')}
  onEnded={() => console.log('Finished')}
/>

react-youtube uses YouTube's specific event objects.

  • Callbacks receive the original YouTube IFrame API event data.
  • You have access to detailed player states (e.g., buffering, cued) specific to YouTube.
// react-youtube: YouTube specific events
const onStateChange = (event) => {
  if (event.data === window.YT.PlayerState.ENDED) {
    console.log('Finished');
  }
};

<YouTube videoId='ysz5S6PUM-U' onStateChange={onStateChange} />;

๐Ÿ“ Layout and Styling: Built-in Wrappers vs Container CSS

react-player includes built-in aspect ratio handling.

  • It wraps the iframe in a div that maintains video proportions by default.
  • You can override this with width and height props, but defaults are safe.
// react-player: Built-in sizing
<ReactPlayer 
  url='https://www.youtube.com/watch?v=ysz5S6PUM-U' 
  width='100%'
  height='auto'
/>

react-youtube relies on your container styles.

  • The component renders an iframe that needs a parent container to define size.
  • You must manage responsive aspect ratios using CSS (e.g., padding-bottom hack).
// react-youtube: Container dependent
<div style={{ position: 'relative', paddingBottom: '56.25%' }}>
  <YouTube 
    videoId='ysz5S6PUM-U' 
    opts={{ width: '100%', height: '100%' }}
    style={{ position: 'absolute', top: 0, left: 0 }}
  />
</div>

๐Ÿ”Œ Configuration: Abstracted vs Direct Access

react-player abstracts provider configuration.

  • You pass a config prop to tweak provider-specific settings.
  • Some advanced YouTube parameters might be hidden or simplified.
// react-player: Abstracted config
<ReactPlayer 
  url='https://www.youtube.com/watch?v=ysz5S6PUM-U' 
  config={{
    youtube: {
      playerVars: { showinfo: 1 }
    }
  }}
/>

react-youtube gives direct access to playerVars.

  • You pass an opts object that maps directly to the YouTube IFrame API.
  • Full control over parameters like controls, modestbranding, and rel.
// react-youtube: Direct playerVars
<YouTube 
  videoId='ysz5S6PUM-U' 
  opts={{
    playerVars: {
      autoplay: 1,
      controls: 0,
      modestbranding: 1
    }
  }}
/>

๐ŸŒฑ Similarities: Shared Ground Between react-player and react-youtube

While their scopes differ, both libraries share core goals and implementation strategies.

1. โš›๏ธ Both Are React Wrappers

  • Both wrap the underlying JavaScript player APIs in React components.
  • They handle mounting and unmounting of iframes automatically.
// Example: Both use standard React component structure
// react-player
<ReactPlayer url='...' />

// react-youtube
<YouTube videoId='...' />

2. ๐Ÿ“น Both Support Lazy Loading

  • Both libraries load the heavy player scripts only when needed.
  • This helps keep initial page load times faster.
// Both handle script injection internally
// No need to manually add YouTube IFrame API script to head

3. ๐ŸŽง Both Handle Audio/Video Events

  • Both provide callbacks for critical lifecycle events.
  • You can track play, pause, progress, and end states in both.
// react-player
onProgress={({ played }) => console.log(played)}

// react-youtube
onProgress={(event) => console.log(event.target.getCurrentTime())}

4. ๐Ÿ“ฑ Both Support Responsive Design

  • Both can be styled to fit mobile and desktop layouts.
  • react-player does it via props; react-youtube via CSS.
// react-player
width='100%'

// react-youtube
opts={{ width: '100%' }}

5. ๐Ÿ› ๏ธ Both Are Open Source

  • Both are maintained by the community on GitHub.
  • Issues and feature requests are handled publicly.
// Both available via npm
npm install react-player
npm install react-youtube

๐Ÿ“Š Summary: Key Similarities

FeatureShared by react-player and react-youtube
Core Techโš›๏ธ React Components, IFrame Wrapping
Loading๐Ÿ“น Lazy load player scripts
Events๐ŸŽง Play, Pause, Progress, End
Responsiveness๐Ÿ“ฑ Supports mobile and desktop layouts
Availability๐Ÿ› ๏ธ Open Source, npm packages

๐Ÿ†š Summary: Key Differences

Featurereact-playerreact-youtube
Input๐ŸŒ Full URL (Auto-detect)๐Ÿ†” Video ID Only
Scope๐Ÿ“บ Multi-platform (YT, Vimeo, etc.)๐Ÿ“บ YouTube Only
Control๐ŸŽฎ React Props (playing, volume)๐ŸŽฎ Internal Player API
Events๐Ÿ“ก Unified/Normalized๐Ÿ“ก YouTube Specific Objects
Layout๐Ÿ“ Built-in Aspect Ratio๐Ÿ“ Container CSS Required
Config๐Ÿ”Œ Abstracted config prop๐Ÿ”Œ Direct playerVars access

๐Ÿ’ก The Big Picture

react-player is like a universal remote ๐Ÿ“บ โ€” it works with many devices and hides the complex buttons behind a simple interface. Ideal for content platforms, learning management systems, or dashboards where video sources vary.

react-youtube is like a specialized tool ๐Ÿ”ง โ€” it gives you direct access to the engine of a specific machine. Perfect for marketing sites, portfolios, or apps where YouTube is the sole video provider and specific player tweaks are required.

Final Thought: If you only ever use YouTube, react-youtube offers more control with less abstraction. If you anticipate needing Vimeo or local files later, react-player saves you from refactoring your video architecture down the line.

How to Choose: react-player vs react-youtube

  • react-player:

    Choose react-player if your application needs to support multiple video sources like Vimeo, SoundCloud, or direct file URLs alongside YouTube. It is the better option when you want a consistent API across different providers without writing platform-specific code. This package is also suitable if you prefer built-in handling for aspect ratios and basic playback controls without digging into provider-specific documentation.

  • react-youtube:

    Choose react-youtube if your project relies exclusively on YouTube videos and requires fine-grained control over YouTube-specific player variables. It is the preferred choice when you need access to advanced YouTube IFrame API features that general wrappers might abstract away or not support. This package is also a good fit if you want a lighter dependency footprint and do not need the overhead of supporting multiple video platforms.

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