faq

FAQ

Table of Contents

Q: What is Video.js?

Video.js is an extendable framework/library around the native video element. It does the following:

  • Offers a plugin API so that different types of video can be handed to the native video element (e.g. HLS, Flash, HTML5 video, etc).
  • Unifies the native video API across browsers (polyfilling support for features if necessary)
  • Offers an extendable and themable UI
  • Ensures accessibility for keyboard and screen reader users
  • Has a set of core plugins that offer support for additional video formats:
  • Supports DRM video via a core plugin:
  • Is extensible with lots of plugins offering support for all kinds of features. See the plugin list on videojs.com

Q: How do I install Video.js?

Currently Video.js can be installed using npm, serving a release file from a GitHub tag, or even using a CDN hosted version. For information on doing any of those see the setup guide.

Q: Is Video.js on bower?

Versions prior to Video.js 6 support bower, however, as of Video.js 6, bower is no longer officially supported. Please see https://github.com/videojs/video.js/issues/4012 for more information.

Q: What do Video.js version numbers mean?

Video.js follows semver which means that the API should not change out from under a user unless there is a major version increase.

Q: How can I troubleshoot playback issues?

See the troubleshooting guide. If troubleshooting does not solve your issue, please ask in Slack or submit an issue.

When seeking help about a playback issue the problem is often specific to the video file used, the way the video is hosted or the browser, so make sure to include all of that information and a reduced test case.

Q: A video does not play in a specific browser. Why?

See the troubleshooting guide. If troubleshooting does not solve your issue, please ask in Slack or submit an issue.

Q: Why does the entire video download before playback? Why does the video load for a long time?

See the troubleshooting guide. If troubleshooting does not solve your issue, please ask in Slack or submit an issue.

Q: I see an error thrown that mentions vdata12345. What is that?

See the troubleshooting guide. If troubleshooting does not solve your issue, please ask in Slack or submit an issue.

Q: I think I found a bug with Video.js or I want to add a feature. What should I do?

If you think that you can fix the issue or add the feature

A pull request would be very welcome in the Video.js repo. Make sure to follow the contributing guide and the pull request template.

If you don't think you can fix the issue or add the feature

Open an issue on the Video.js repo. Make sure that you follow the issue template and the contributing guide so that we can better assist you with your issue.

Q: What is a reduced test case?

A reduced test case is an example of the problem that you are facing in isolation. Think of it as example page that reproduces the issue in the least amount of possible code.

It's important to add a reduced case. Even if the problem seems obvious it may not be to others. Having a example to refer to also makes the difference between somebody being able to take a look and immediately see what's wrong, and needing to take time to recreate what they think you are describing.

We have a starter example for reduced test cases. To learn more about reduced test cases visit css-tricks

Q: What media formats does Video.js support?

This depends on the formats supported by the browser's HTML5 video element, and the playback techs/plugins made available to Video.js. For more information on media formats see the troubleshooting guide.

Q: How does Video.js choose which source to use?

When an array of sources is available, Video.js test each source in the order given. For each source, each tech in the techOrder will be checked to see if it can play it whether directly or via source handler (such as videojs-contrib-hls). The first match will be chosen.

Q: How do I autoplay a video?

Due to recent changes in autoplay behavior we no longer recommend using the autoplay attribute on the video element. It's still supported by Video.js but, many browsers, including Chrome, are changing their autoplay attribute behavior.

Instead we recommend using the autoplay option rather than the autoplay attribute, for more information on using that. see the [autoplay option][autoplay-option] in the Video.js options guide.

For more information on the autoplay changes see our blog post: https://blog.videojs.com/autoplay-best-practices-with-video-js/

Q: How can I autoplay a video on a mobile device?

Most mobile devices have blocked autoplaying videos until recently. For mobile devices that don't support autoplaying, autoplay isn't supported by Video.js. For those devices that support autoplaying, like iOS10 and Chrome for Android 53+, you must mute the video or have a video without audio tracks to be able to play it.

We do not recommend doing this manually using attributes on the video element. Instead, you should pass the [autoplay option][autoplay-option] with a value of 'any' or 'muted'. See the previous link for more information on using that option.

NOTE: At this point, the autoplay attribute and option are NOT a guarantee that your video will autoplay.

Q: How can I play RTMP video in Video.js?

RTMP requires Flash to play back. You'll need both a browser that supports Flash and the Flash tech.

In Video.js version 6, the Flash tech is not included by default and is available as a separate videojs-flash package. In previous versions it was builtin to Video.js.

The RTMP source should be set with an appropriate type -- rtmp/mp4 or rtmp/flv. Be aware of that Video.js splits the connection url and stream name with the & character, for example: rtmp://example.com/live&foo or rtmp://example.com/fms&mp4:path/to/file.mp4.

If the server requires query parameters for authentication, these should be added to the connection part URL, for example rtmp://example.com/live?token=1234&foo.

Bear in mind that mobile browsers do not support Flash, and modern desktop browsers make it increasingly difficult to use Flash or disable it by default for your end users. Consider moving to a modern format such as HLS or DASH.

It's impossible to hide the network requests a browser makes and difficult to sufficiently obfuscate URLs in the source. Techniques such as token authentication may help but are outside of the scope of Video.js.

For content that must be highly secure videojs-contrib-eme adds DRM support.

Q: Can I turn off Video.js logging?

Yes! This can be achieved by adding the following code after including Video.js, but before creating any player(s):

videojs.log.level('off');

For more information, including which logging levels are available, check out the debugging guide.

Q: What is a plugin?

A plugin is a group of reusable functionality that can be re-used by others. For instance a plugin could add a button to Video.js that makes the video replay 10 times in a row before it stops playback for good. If such a plugin existed and was published users could include it on their page to share that functionality.

Q: How do I make a plugin for Video.js?

See the plugin guide for information on making a plugin for Video.js.

Q: How do I add a button to Video.js?

See the components guide for an example of adding a button to Video.js.

Q: Where can I find a list of Video.js plugins?

A list of plugins published to npm with the videojs-plugin keyword is maintained on videojs.com.

Q: How can I get my plugin listed on the website?

Add the 'videojs-plugin' keyword to your array in package.json and publish your package to npm. If you use the plugin generator this will be done automatically for you. See the plugins guide for more information.

Q: Where can I find a list of Video.js skins?

See the Video.js GitHub wiki.

Q: Does Video.js work as an audio only player?

Yes! It can be used to play audio only files in a <video> or <audio> tag. Note that audio-only sources do not work with the Flash playback tech.

Q: Does Video.js support audio tracks?

Yes! See the audio tracks guide for information on using audio tracks.

Q: Does Video.js support video tracks?

Alternate video tracks support is in development. See video tracks guide for more information on using video tracks.

Q: Does Video.js support text tracks (captions, subtitles, etc)?

Yes! See the text tracks guide for information on using text tracks.

Q: Does Video.js support HLS (HTTP Live streaming) video?

Video.js supports HLS video if the native HTML5 element supports HLS (e.g. Safari, Edge, Chrome for Android, and iOS). For browsers without native support the videojs-contrib-hls project which adds support.

Note that for non-native playback of HLS it is essential that the server hosting the video sets CORS headers.

Q: Does Video.js support MPEG DASH video?

MPEG DASH support is provided byt the videojs-contrib-dash package.

Like HLS, DASH streams require CORS headers.

Q: Does Video.js support live video?

Yes! Common formats for live are HLS or historically RTMP. HLS is supported via videojs-contrib-hls. and RTMP via videojs-flash.

Q: Can Video.js play YouTube videos?

There is an official plugin that adds support, videojs-youtube.

Q: Can Video.js play Vimeo videos?

There is an official plugin that adds support, videojs-vimeo.

Q: Does Video.js support DRM video?

There is an official plugin that adds support, videojs-contrib-eme.

Q: Does Video.js have any support for advertisement integrations?

There is an official plugin that adds core advertising support, videojs-contrib-ads. Further plugins build on this which handle the communication with the ad server and display of the ad, for instance Google's IMA plugin.

Q: Can Video.js be required in node.js?

Yes! Video.js is published on NPM.

Q: Does Video.js work with webpack?

Yes! See the Webpack and Video.js configuration guide.

Q: Does Video.js work with react?

Yes! See ReactJS integration example.