react-player と video-react はどちらも React アプリケーションで動画再生を実現するためのライブラリですが、設計思想と対応範囲が大きく異なります。react-player は YouTube、Vimeo、SoundCloud、Facebook、Twitch、Streamable、Wistia、Mixcloud、DailyMotion、PeerTube など、多様な外部動画サービスを単一のコンポーネントで統一的に扱える汎用的なプレイヤーです。一方、video-react は HTML5 <video> 要素をラップし、React 向けにカスタマイズ可能な UI コンポーネント群(再生コントロール、プログレスバー、フルスクリーンなど)を提供するライブラリで、主にローカルまたは自前ホストの MP4/WebM 動画向けに設計されています。
React アプリで動画を再生する際、react-player と video-react はよく検討される2つの選択肢です。しかし、その目的と能力は根本的に異なります。どちらを選ぶべきかは、あなたのアプリが「どの動画を」「どのように」再生したいかに完全に依存します。
react-player は、外部動画サービスとの統合に特化しています。
// react-player: 外部動画の例
import ReactPlayer from 'react-player';
function App() {
return (
<ReactPlayer
url='https://www.youtube.com/watch?v=ysz5S6PUM-U'
width='100%'
height='100%'
controls={true}
/>
);
}
video-react は、HTML5 <video> 要素の拡張に特化しています。
// video-react: HTML5動画の例
import { Player, ControlBar, PlayToggle, SeekBar } from 'video-react';
import 'video-react/dist/video-react.css';
function App() {
return (
<Player src="/videos/sample.mp4">
<ControlBar>
<PlayToggle />
<SeekBar />
</ControlBar>
</Player>
);
}
💡 補足:
video-reactはvideo.jsの React 版ではなく、独自実装のプレイヤーです。video.jsを React で使いたい場合は別途ラッパーが必要です。
react-player の UI は、各サービスの iframe 内に閉じています。
controls prop)はできますが、ボタンの配置やデザインを変更することはできません。// react-player: UI カスタマイズはほぼ不可能
<ReactPlayer
url="/local/video.mp4"
controls={true} // ブラウザ標準コントロールのみ
/>
video-react は、UI コンポーネントを自由に組み立てられます。
ControlBar 内に含めるコンポーネント(PlayToggle, VolumeMenuButton, FullscreenToggle など)を任意に選べます。// video-react: UI を自由に構成
<Player src="/videos/demo.mp4">
<ControlBar>
<PlayToggle /> {/* 再生/一時停止ボタン */}
<SeekBar /> {/* シークバー */}
{/* 音量やフルスクリーンは省略可能 */}
</ControlBar>
</Player>
react-player は、統一されたイベント API を提供します。
onPlay, onPause, onProgress, onDuration などのコールバックが、どの動画ソースでも同じ形で利用可能。// react-player: 統一イベント
<ReactPlayer
url="https://vimeo.com/..."
onPlay={() => console.log('再生開始')}
onProgress={(state) => console.log('現在位置:', state.playedSeconds)}
/>
video-react は、HTML5 <video> イベントをラップした形で提供します。
onPlay, onPause, onTimeUpdate などのネイティブイベントをそのまま利用可能。currentTime, duration など)を取得できます。// video-react: ネイティブイベント利用
function App() {
const playerRef = useRef(null);
const handlePlay = () => {
console.log('再生中');
const player = playerRef.current?.getState()?.player;
console.log('現在時間:', player.currentTime);
};
return (
<Player
ref={playerRef}
src="/videos/sample.mp4"
onPlay={handlePlay}
/>
);
}
react-player の制約video-react の制約.d.ts ファイルが含まれておらず、型安全性を求めるプロジェクトでは注意が必要です。<video> の制約をそのまま引き継ぎます。| 要件 | 推奨パッケージ |
|---|---|
| YouTube / Vimeo / Twitch などの外部動画を埋め込む | react-player |
| 自前ホストの MP4/WebM 動画をカスタム UI で再生 | video-react |
| 動画ソースが動的に切り替わる(例: CMS 連携) | react-player |
| プレイヤー UI をブランドに合わせて完全カスタマイズ | video-react |
| HLS/DASH ストリーミングが必要 | どちらも非対応(hls.js + video-react の組み合わせを検討) |
— 「動画がどこにあるか?」 が最も重要な質問です。
react-playervideo-reactこの一点でほぼ決まります。UI カスタマイズ性やイベント制御は二次的な要件であり、まず動画ソースの性質を確認することが先決です。
react-player は、複数のサードパーティ動画サービス(YouTube、Vimeo など)を1つのコンポーネントで扱いたい場合や、外部動画の埋め込みを簡単に実装したいプロジェクトに最適です。特に CMS 連携や動画ソースが動的に変わるアプリケーションでは、URL を渡すだけで自動で適切なプレイヤーを切り替えてくれるため、開発効率が大幅に向上します。ただし、UI の細かいカスタマイズや独自のコントロールレイアウトが必要な場合は制限があります。
video-react は、HTML5 動画(MP4、WebM など)を高度にカスタマイズ可能な UI で再生したい場合に適しています。コントロールバーの構成要素を自由に組み替えられ、CSS クラスによるスタイリングも容易です。ただし、YouTube や Vimeo などの外部サービスには対応しておらず、純粋に自前ホストの動画ファイル専用である点に注意が必要です。また、TypeScript サポートは公式には提供されていません。
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 |