react-player and video-react are both React-based libraries designed to simplify video playback in web applications, but they serve different use cases and support different media sources. react-player is a versatile wrapper that supports multiple third-party players (like YouTube, Vimeo, and HLS streams) through a unified API, while video-react is a customizable HTML5 video player built specifically for self-hosted MP4/WebM content with a focus on UI control and accessibility.
When you need to play video in a React app, picking the right library depends heavily on your source type, customization needs, and whether you’re using third-party platforms or self-hosted files. react-player and video-react take fundamentally different approaches — one prioritizes broad compatibility, the other deep control over native playback.
react-player wraps multiple underlying players to support a wide range of sources:
<video> element// react-player: Works with any supported URL
import ReactPlayer from 'react-player';
<ReactPlayer
url='https://www.youtube.com/watch?v=ysz5S6PUM-U'
controls={true}
/>
// Also works with HLS
<ReactPlayer
url='https://example.com/stream.m3u8'
controls={true}
/>
video-react only supports standard HTML5-compatible video formats (MP4, WebM, Ogg) served directly from your own infrastructure. It does not support YouTube, Vimeo, or adaptive streaming out of the box.
// video-react: Only self-hosted files
import { Player } from 'video-react';
<Player>
<source src="/videos/sample.mp4" type="video/mp4" />
</Player>
⚠️ If you try to pass a YouTube URL to
video-react, it will fail because the underlying<video>element cannot play external platform URLs.
react-player provides a minimal, consistent set of controls across all platforms. You can enable/disable them, but you cannot deeply customize the look or behavior of YouTube’s or Vimeo’s native UIs due to iframe sandboxing.
// react-player: Limited to enabling/disabling controls
<ReactPlayer
url='https://vimeo.com/123456'
controls={true} // uses Vimeo's own player UI
playing={true}
volume={0.8}
/>
video-react gives you full control over every UI component (play/pause, volume, progress bar, captions, etc.). You can replace or extend any part of the interface using its component-based architecture.
// video-react: Fully customizable UI
import { Player, ControlBar, PlayToggle, VolumeMenuButton } from 'video-react';
<Player>
<source src="/videos/demo.mp4" />
<ControlBar>
<PlayToggle />
<VolumeMenuButton vertical={true} />
{/* Add custom buttons or remove defaults */}
</ControlBar>
</Player>
This makes video-react far better for branded experiences or accessibility requirements (e.g., high-contrast themes, keyboard navigation enhancements).
react-player automatically handles HLS and DASH by dynamically loading hls.js or dash.js when needed. You don’t need to manage the underlying tech.
// react-player: HLS just works
<ReactPlayer
url='https://cph-p2p-msl.akamaized.net/hls/live/2000341/test/master.m3u8'
controls={true}
/>
video-react does not support HLS or DASH natively. To play such streams, you’d need to integrate hls.js manually and manage the video element lifecycle yourself — which defeats the purpose of using a high-level player.
// video-react: Not possible out of the box
// You'd have to do something like:
// const videoRef = useRef();
// useEffect(() => {
// if(Hls.isSupported()) {
// const hls = new Hls();
// hls.loadSource('stream.m3u8');
// hls.attachMedia(videoRef.current);
// }
// }, []);
// <video ref={videoRef} className="video-react" />
react-player inherits accessibility features from the underlying platform (e.g., YouTube’s player is generally accessible). However, you have no control over ARIA labels, keyboard shortcuts, or screen reader announcements.
video-react is built with accessibility as a core principle. It includes proper ARIA roles, keyboard navigation (space to play/pause, arrow keys for seek/volume), and supports internationalization of control labels.
// video-react: Customize ARIA labels
<Player>
<source src="/video.mp4" />
<ControlBar>
<PlayToggle aria-label="Play or pause video" />
</ControlBar>
</Player>
If your project requires WCAG compliance or custom keyboard interactions, video-react is the safer choice for self-hosted content.
react-player exposes high-level events like onPlay, onPause, onProgress, and onDuration. The API is simple but abstracted — you don’t get direct access to the underlying <video> or iframe.
// react-player: Unified event callbacks
<ReactPlayer
url='video.mp4'
onPlay={() => console.log('Playing')}
onProgress={(state) => console.log('Played:', state.played)}
/>
video-react provides both high-level props and direct access to the video element’s state via its internal Redux-like store. You can also listen to native HTML5 video events if needed.
// video-react: Access internal state
import { Player } from 'video-react';
function MyPlayer() {
const playerRef = useRef();
const handleStateChange = (state, prevState) => {
if (state.paused !== prevState.paused) {
console.log('Playback state changed');
}
};
return (
<Player
ref={playerRef}
onStateChange={handleStateChange}
>
<source src="/video.mp4" />
</Player>
);
}
This level of detail is useful for analytics, custom scrubbing logic, or syncing video with other UI elements.
react-player if you need pixel-perfect control over the player UI for self-hosted videos or must meet strict accessibility standards that go beyond what YouTube/Vimeo provide.video-react if you need to embed third-party platform videos or play adaptive streams without building your own integration layer.react-player as your “universal video embed” tool — especially when dealing with user-generated content that might come from anywhere.video-react when you control the video files and need a polished, accessible, brand-consistent player experience.Both are well-maintained and production-ready, but they solve different problems. Don’t try to force one into the other’s role — pick based on your media source strategy, not just API preferences.
Choose react-player if you need to embed videos from various external platforms (YouTube, Vimeo, Facebook, etc.) or stream adaptive formats like HLS or DASH without managing low-level video element APIs. It’s ideal when your application consumes mixed media sources and you want a consistent interface across them.
Choose video-react if you’re serving self-hosted video files (MP4, WebM) and require fine-grained control over the player UI, accessibility features, and custom styling. It’s best suited for applications where you own the video assets and need a fully customizable, accessible HTML5 video experience.
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.
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.
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.
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}.
| Prop | Description | Default |
|---|---|---|
src | The url of a video or song to play | undefined |
playing | Set to true or false to play or pause the media | undefined |
preload | Applies the preload attribute where supported | undefined |
playsInline | Applies the playsInline attribute where supported | false |
disableRemotePlayback | Applies the disableRemotePlayback attribute where supported | false |
crossOrigin | Applies the crossOrigin attribute where supported | undefined |
loop | Set to true or false to loop the media | false |
controls | Set to true or false to display native player controls.◦ For Vimeo videos, hiding controls must be enabled by the video owner. | false |
volume | Set the volume of the player, between 0 and 1◦ null uses default volume on all players #357 | null |
muted | Mutes the player | false |
playbackRate | Set the playback rate of the player ◦ Only supported by YouTube, Wistia, and file paths | 1 |
pip | Set to true or false to enable or disable picture-in-picture mode◦ Only available when playing file URLs in certain browsers | false |
width | Set the width of the player | 320px |
height | Set the height of the player | 180px |
style | Add inline styles to the root element | {} |
light | Set 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 |
fallback | Element or component to use as a fallback if you are using lazy loading | null |
wrapper | Element or component to use as the container element | null |
playIcon | Element or component to use as the play icon in light mode | |
previewTabIndex | Set the tab index to be used on light mode | 0 |
Callback props take a function that gets fired on various player events:
| Prop | Description |
|---|---|
onClickPreview | Called when user clicks the light mode preview |
onReady | Called when media is loaded and ready to play. If playing is set to true, media will play immediately |
onStart | Called when media starts playing |
onPlay | Called when the playing prop is set to true |
onPlaying | Called when media actually starts playing |
onProgress | Called when media data is loaded |
onTimeUpdate | Called when the media's current time changes |
onDurationChange | Callback containing duration of the media, in seconds |
onPause | Called when media is paused |
onWaiting | Called when media is buffering and waiting for more data |
onSeeking | Called when media is seeking |
onSeeked | Called when media has finished seeking |
onRateChange | Called when playback rate of the player changed ◦ Only supported by YouTube, Vimeo (if enabled), Wistia, and file paths |
onEnded | Called when media finishes playing ◦ Does not fire when loop is set to true |
onError | Called when an error occurs whilst attempting to play media |
onEnterPictureInPicture | Called when entering picture-in-picture mode |
onLeavePictureInPicture | Called when leaving picture-in-picture mode |
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:
| Method | Description |
|---|---|
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() |
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.
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.
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>
);
}
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.
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' }}
/>
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"
}
}
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.
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).
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>
v3ReactPlayer 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
v2ReactPlayer 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.
<video> or <audio> elementshls.jsdash.js<mux-player> elementSee the contribution guidelines before creating a pull request.
![]() Jackson Doherty |
Joseph Fung |