Live video streaming with open source Video.js

Video.js is a widely used protocol that will serve your live video stream to a wide range of devices.
162 readers like this
162 readers like this
video editing dashboard

Last year, I wrote about creating a video streaming server with Linux. That project uses the Real-Time Messaging Protocol (RTMP), Nginx web server, Open Broadcast Studio (OBS), and VLC media player.

I used VLC to play our video stream, which may be fine for a small local deployment but isn't very practical on a large scale. First, your viewers have to use VLC, and RTMP streams can provide inconsistent playback. This is where Video.js comes into play! Video.js is an open source JavaScript framework for creating custom HTML5 video players. Video.js is incredibly powerful, and it's used by a host of very popular websites—largely due to its open nature and how easy it is to get up and running.

Get started with Video.js

This project is based off of the video streaming project I wrote about last year. Since that project was set to serve RTMP streams, to use Video.js, you'll need to make some adjustments to that Nginx configuration. HTTP Live Streaming (HLS) is a widely used protocol developed by Apple that will serve your stream better to a multitude of devices. HLS will take your stream, break it into chunks, and serve it via a specialized playlist. This allows for a more fault-tolerant stream that can play on more devices.

First, create a directory that will house the HLS stream and give Nginx permission to write to it:

mkdir /mnt/hls
chown www:www /mnt/hls

Next, fire up your text editor, open the Nginx.conf file, and add the following under the application live section:

       application live {
            live on;
            # Turn on HLS
            hls on;
            hls_path /mnt/hls/;
            hls_fragment 3;
            hls_playlist_length 60;
            # disable consuming the stream from nginx as rtmp
            deny play all;

Take note of the HLS fragment and playlist length settings. You may want to adjust them later, depending on your streaming needs, but this is a good baseline to start with. Next, we need to ensure that Nginx is able to listen for requests from our player and understand how to present it to the user. So, we'll want to add a new section at the bottom of our nginx.conf file.

server {
        listen 8080;

        location / {
            # Disable cache
            add_header 'Cache-Control' 'no-cache';

            # CORS setup
            add_header 'Access-Control-Allow-Origin' '*' always;
            add_header 'Access-Control-Expose-Headers' 'Content-Length';

            # allow CORS preflight requests
            if ($request_method = 'OPTIONS') {
                add_header 'Access-Control-Allow-Origin' '*';
                add_header 'Access-Control-Max-Age' 1728000;
                add_header 'Content-Type' 'text/plain charset=UTF-8';
                add_header 'Content-Length' 0;
                return 204;

            types {
                application/dash+xml mpd;
                application/ m3u8;
                video/mp2t ts;

            root /mnt/;

Visit Video.js's Getting started page to download the latest release and check out the release notes. Also on that page, Video.js has a great introductory template you can use to create a very basic web player. I'll break down the important bits of that template and insert the pieces you need to get your new HTML player to use your stream.

The head links in the Video.js library from a content-delivery network (CDN). You can also opt to download and store Video.js locally on your web server if you want.

  <link href="" rel="stylesheet" />

  <!-- If you'd like to support IE8 (for Video.js versions prior to v7) -->
  <script src=""></script>

Now to the real meat of the player. The body section sets the parameters of how the video player will be displayed. Within the video element, you need to define the properties of your player. How big do you want it to be? Do you want it to have a poster (i.e., a thumbnail)? Does it need any special player controls? This example defines a simple 600x600 pixel player with an appropriate (to me) thumbnail featuring Beastie (the BSD Demon) and Tux (the Linux penguin).


Now that you've set how you want your player to look, you need to tell it what to play. Video.js can handle a large number of different formats, including HLS streams.

    <source src="http://MY-WEB-SERVER:8080/hls/STREAM-KEY.m3u8" type="application/x-mpegURL" />
    <p class="vjs-no-js">
      To view this video please enable JavaScript, and consider upgrading to a
      web browser that
      <a href="" target="_blank"
        >supports HTML5 video</a

Record your streams

Keeping a copy of your streams is super easy. Just add the following at the bottom of your application live section in the nginx.conf file:

# Enable stream recording
record all;
record_path /mnt/recordings/;
record_unique on;

Make sure that record_path exists and that Nginx has permissions to write to it:

chown -R www:www /mnt/recordings

Down the stream

That's it! You should now have a spiffy new HTML5-friendly live video player. There are lots of great resources out there on how to expand all your video-making adventures. If you have any questions or suggestions, feel free to reach out to me on Twitter or leave a comment below.

What to read next
School IT Director - Open Source Evangelist - Technology Enthusiast - Husband - Dad


I want to arrange for a video on demand (with on-the-fly transcoding to 480p, h.264+aac, *.mp4) streaming service from my GNU Linux computer to my Android (v5 & v7) mobile phones having Google Chrome installed.
The service will be accessed within my home using Wi-Fi or Bluetooth, so security is not that much important, just the server need to be easy to configure & without too much dependencies.

What should I use, and please also mention some links to setup guides.

Hi, I have a question regarding HLS

A while back I made a program that was able to save HLS live streams and it was purely done in Golang.

The streams it saved would be choppy with random lags that weren't present in the stream itself even though the program would download the sequences correctly.

It wasn't until I relied on FFmpeg to save the stream that it got fixed and I have no idea why that was.

The way it worked was it would request the playlist.m3u8, see what sequences to download and then it would download all sequences and check for a new m3u8. (only one resolution, usually the highest)

The downloaded files would be appended to one big file.

Do you have any idea why it may have been so choppy?

Hey Jack,
I'm not honestly sure. Did the choppiness seem to happen on a consistent interval?

In reply to by Jack Fletcher (not verified)

Hello and thank you.

I wonder if you could post a complete nginx configuration? Considering there are two articles and numerous 'add section' steps it would be good to have a complete example.

Best wishes

There's a typo in the second line:-

"Real-Time Messaging Protocol (RMTP)" should read: Real-Time Messaging Protocol (RTMP).

There's the same error on line 13 - RMTP.

Hi Aaron,
I was going through your old tutorial "Create your own video streaming server with Linux" and was trying to replicate it.
I am a complete beginner at this,and i got stuck at the point where i had to restart nginx by typing sudo systemctl restart nginx.
I got an error saying

nginx.service :Failed with result 'exit code'
Failed to start a high performance web server and a reverse proxy server

can you please help me out here?

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.