How to Encrypt Video for HLS

In this post, we’ll look at what encryption HLS supports and how to encrypt your videos with ffmpeg.

Encryption is the process of encoding information in such a way that only authorised parties can read it. The encryption process requires some kind of secret (key) together with an encryption algorithm.

There are many different types of encryption algorithms but HLS only supports AES-128. The Advanced Encryption Standard (AES) is an example of a block cipher, which encrypts (and decrypts) data in fixed-size blocks. It’s a symmetric key algorithm, which means that the key that is used to encrypt data is also used to decrypt it. AES-128 uses a key length of 128 bits (16 bytes).

HLS uses AES in cipher block chaining (CBC) mode. This means each block is encrypted using the cipher text of the preceding block, but this gives us a problem: how do we encrypt the first block? There is no block before it! To get around this problem we use what is known as an initialisation vector (IV). In this instance, it’s a 16-byte random value that is used to intialize the encryption process. It doesn’t need to be kept secret for the encryption to be secure.

Before we can encrypt our videos, we need an encryption key. I’m going to use OpenSSL to create the key, which we can do like so:

$ openssl rand 16 > enc.key

This instructs OpenSSL to generate a random 16-byte value, which corresponds to the key length (128 bits).

The next step is to generate an IV. This step is optional. (If no value is provided, the segment sequence number will be used instead.)

$ openssl rand -hex 16

Make a note of the output as you’ll need it shortly.

To encrypt the video we need to tell ffmpeg what encryption key to use, the URI of the key, and so on. We do this with -hls_key_info_file option passing it the location of a key info file. The file must be in the following format:

Path to key file
IV (optional)

The first line specifies the URI of the key, which will be written to the playlist. The second line is the path to the file containing the encryption key, and the (optional) third line contains the initialisation vector. Here’s an example (enc.keyinfo):

Now that we have everything we need, run the following command to encrypt the video segments:

ffmpeg -y \
    -i \
    -hls_time 9 \
    -hls_key_info_file enc.keyinfo
    -hls_playlist_type vod \
    -hls_segment_filename "fileSequence%d.ts" \

Take a look at the generated playlist (prog_index.m3u8). It should look something like this:


Note the URI of the encryption key. The player will retrieve the key from this location to decrypt the media segments. To protect the key from eavesdroppers it should be served over HTTPS. You may also want to implement some of authentication mechanism to restrict who has access to the key. If you’re interested, the book goes into some detail about how to achieve this. Click here to buy a copy.

To verify that the segments really are encrypted, try playing them using a media player like QuickTime or VLC. You shouldn’t be able to. Now run the command above without the encryption and then try playing a segment. Notice the difference.

In this instance, all the segments are encrypted with the same key. It can be beneficial to periodically change the encryption keys to minimise the impact if a particular key is exposed. This is known as key rotation, and the amount of time between successive key generations is referred to as the key rotation period.

To enable key rotation, set the -hls_flags option to periodic_rekey. When enabled, the key info file will be checked periodically. If the file has changed, segments will then be encrypted with the new encryption key. However, we still need to come up with a way of generating new keys and updating the key info file. Here’s an example of how it could be done:

while true
    sleep 15
    openssl rand 16 > enc$i.key
    echo$i.key > $tmpfile
    echo enc$i.key >> $tmpfile
    echo `openssl rand -hex 16` >> $tmpfile
    mv $tmpfile enc.keyinfo
    let i++

The script uses the same values as before for the base URL (for each key) and key info file. It generates a new encryption key every 15 seconds, updating the key info file accordingly. (In practice you would choose a much longer key rotation period.)

To test it, run ffmpeg again but this time enable key rotation. At the same time, open a new terminal and run the script from the same directory. (The script will run forever until you terminate it.) When ffmpeg has finished, terminate the script.

Take a look at the playlist. You should now see a number of different key entries in the playlist. All the segments that follow a key tag (#EXT-X-KEY) are now encrypted using the key specified by the tag, instead of using one key to encrypt all segments like before.

Even though HLS supports encryption, which provides some sort of content protection, it isn’t a full DRM solution. If that kind of thing interests you then you may want to take a look at Apple’s FairPlay Streaming solution.

27 thoughts on “How to Encrypt Video for HLS

  1. Mehmood

    Hi Simon,
    Your post is great. I am new to HLS and your site is really helpful.
    I have a question. How can I use mediafilesegmenter to encrypt every segment of the file with different key ? Apple docs says such thing is supported but I couldn’t find any help regarding it.

    It would be great if you can guide about it, provide command of it.

    1. sbuckle Post author

      Hi Mehmood,

      You can use the -key-rotation-period option of mediafilesegmenter. It takes as an argument a number that specifies how many segments to encrypt before generating a new key. If you want to encrypt every segment with a different key then I guess you will need to set it to 1.

      There’s more information in the Security chapter of the book if you are interested.


  2. Rj

    Hi Simon

    I am new to HLS AES encryption can i get the example of the above procedure in the book meaning a video file taken and encryption explained in step by step fashion including openssl and ffmpeg

    Thanks however for this informative article


  3. Steve

    Hi Simon, I hope this thread is still active. I’m new to ffmpeg and tried the commands you mentioned to encrypt HLS with an openssl key, and it all worked. But one basic question- how do I direct the all the encrypted HLS chunks to a separate folder? In your script they just end up in the folder where I ran the script, so its a little messy. Many thanks

    1. Simon Post author

      Hi Steve,

      You can specify a relative or absolute path to the HLS segments. The following example will output the segments in a directory relative to the location where you run the command:

      ffmpeg -y \
          -i \
          -hls_time 9 \
          -hls_key_info_file enc.keyinfo \
          -hls_playlist_type vod \
          -hls_segment_filename "hls/fileSequence%d.ts" \
          -use_localtime_mkdir 1 \

      Make sure the directory you are writing the segments to exists. Take a look at the available options for more information.

  4. ads1018

    Hey Simon, great post. I’m trying to implement an auth system so that when I stream a file, encrypted, over RTMP using ffmpeg you can only consume the the stream if they have a valid decryption key. Is this possible? If the decryption key is included in the generated playlist then *anyone* can consume it which isn’t ideal. Any thoughts, on how to achieve this? Ideally, I don’t have to use a crazy proprietary DRM solution with a license server.

    1. Simon Post author

      Even though the reference to the key is embedded in an HLS playlist, you can protect access to it. I’m going to assume that the key(s) and/or the playlist are served over HTTPS. You can use something like basic authentication, which requires a username and password, or use client certificates and enable TLS client authentication to restrict access. That’s not going to prevent an authorised user from accessing the key, but it will prevent an unauthorised user from doing so. Other than that, you’re going to have to resort to a DRM solution.

  5. Steve

    Hi Simon- With the help of your book, I have implemented HLS encryption successfully. The HLS encrypted chunks are stored on a protected server, and the embedded HLS player accesses the keys from the path in the playlist.m3u8 file. The keys are located on the same server that embeds the player, and viewers must be authenticated before accessing the player. To prevent just any site from accessing the key path, I have implemented CORS and only allowed the server where the player is embedded to access. Is there a better, more secure way to restrict access to the keys than CORS? Again, the player and the key store folder are both on the same site- both are off of the site root folder. Thanks for any advice you can give me.

    1. Simon Post author

      Here’s one idea. You could try including some sort of authentication token in the playlist URL, e.g. /playlist.m3u8?token=ABCDEFG. As the viewer is authenticated, you could tie the token to their identity.

      You would then check on the server if the token is valid or not. If it is valid, you could then set a (session) cookie. Any subsequent requests to the server, e.g. for the key(s), will include the Cookie header that you can then use to determine if the request is allowed or not.

      An alternative approach to using a cookie could be to generate the playlist dynamically and include the token in the path to the encryption key. There’s an example in the book of how to generate a playlist with PHP that you could use as a starting point.

      However, as I mentioned in a comment above, it won’t prevent an authorised user from accessing the key.

  6. Zulhilmi Zainudin

    Hi Simon,

    I have 2 questions here:

    1. What do you actually mean by “it won’t prevent an authorised user from accessing the key”? Could you give some examples?

    2. Does HLS works on Android and Windows? I mean, does it work in Android and Windows based web browsers i.e. native browser, Chrome, Firefox and etc?


    1. Simon Post author

      Let’s assume that you run some sort of video website and users can only watch your videos if they are logged in. (How authentication is implemented is not relevant in this example.) If you are authorized to watch a video, you can access the playlist from your browser. If you can view the playlist, you can see the URL of the decryption key. Type that URL into the browser and you can download the key, which means you can decrypt the individual media segments.

      Depends what version of Android you are using. Take a look at the supported media formats, specifically the supported network protocols. I’m not a Windows user but in my experience (on Mac and Linux) HLS works fine in modern versions of desktop browsers like Chrome and Firefox.

      1. Hafsa Naz

        So if a user who can watch an encrypted videos, has the access to the URL of the decryption key to decrypt all individual segments, why to encrypt it in the first place? Is there are way to deal with it?

  7. ssaguiar2Sergio

    How could we use this with segments, not hls, in ffmpeg?
    I have a problem that the subtitles are in dvbsub format and hls doesn’t work with this format, when using hls but encryption only works with hls.

    Any clues?

    Thank you very much

  8. ssaguiar

    Your post is great, but wish to ask a question.
    I already have done it to encrypt the hls stream, as you have told and it works fine with ffmpeg.
    Now, as the key is exposed, I wish to implement the key rotation using ffmpeg.
    I purchased your book today but it shows only how too use mediafilesegmenter and mediastreamsegmenter to make it.

    Is ther any way to make this (key rotation) using ffmpeg?

    Thank you very much for any help

    1. Simon Post author

      If -hls_flags periodic_rekey is enabled, the key info file will be checked periodically for changes. If the file has changed, segments will be encrypted with the new key. However, you will have to write a script (or something) to update the file with the new encryption key. I don’t think it’s possible to specify how often the file is checked.

  9. Naga Sai

    Hi Simon,

    Thank you for the great post. I am able to encrypt the video and was able to play the videos using video.js.

    when i installed third party video downloader plugins for browsers and downloaded video. It started downloading in mp4 format and it was playing without any keys.

    Can you please tell on how to prevent the video from playing even if downloaded using browser plugins


    1. Simon Post author

      If the plugin thinks the video is MP4, check the MIME type is configured correctly. The Content-Type header for .ts files should be set to video/MP2T.

      You need to implement some form of authorization to restrict access to the key if you haven’t already (see my previous comment). If you don’t do this then anybody can download the key and decrypt the video segments, which I suspect is what is happening in your case.

  10. Michael

    Hi Steve,
    great post and easy to understand, thanks.

    Currently I’m running a server where videos are streamed as unencrypted HLS and we have authorization to restrict access to distinct users.
    Now, my customer wants to switch to encrypted hls cause they think that logged in users might use a plugin in their browser to download the video and locally store it as MP4.

    But there are also hls downloaders that claim to be able to download and decrypt encrypted hls videos.
    As far as I understood your article encrypted hls has to send the encryption key to the client in one way or another.
    I think a browser plugin has the same access to the key as the browser itself.

    So my question is: does encrypted hls bring any advantages over non encrypted hls when we have a legitimated user using such a plugin?

    Thanks a lot

    1. Simon Post author

      You are correct about HLS downloaders. Coincidentally, I used one recently to test an encrypted video stream and it downloaded the video and stored it as an MP4. Interestingly, the one I tried didn’t work with the videos on this site.

      To answer your question, I would say no. If a user is authenticated and therefore has direct access to the key, then presumably the plugin also has the same access. It may be possible to thwart these kinds of tools but I don’t know enough about how they work.

      However, there are legitimate reasons why you would want to encrypt your videos. For example, if you distribute your videos via a CDN. In this scenario, the content is typically distributed globally on servers you have no control over – it depends on the CDN that you use – so it would make sense to encrypt the video segments.

  11. ssaguiar

    Hi Simon

    I have implemented the encryption for my ffmpeg stream and it works very well.
    I have a question about the detection of a freezed video.

    I need to restart the ffmpeg process when the image is froozen.

    I am trying a complex filter as:

    -filter_complex “select=’not(mod(n,600))’,select=’lt(scene\,0.06)’,showinfo” \
    -vsync vfr /var/www/html/hls/live/CAM1/movement/scn_%03d.jpg \

    MOVEMENT is the ffmpeg copied and renamed.

    The above script works and it generates the jpeg images.
    The question is: how to use this to kill the ffmpeg instance?

    I apologise if this is not the place to ask such question, but I didn’t find another place.

    Thank you very much for your excelent tutorials and the amazing book.

  12. Zoltán Tamási


    Thank you for the great article. What I’m wondering about is whether it’s possible to use a pass-phrase based key derivation. I’d like to implement a simple use-case where my goal is to protect some of my videos using a password. Is there any kind of built-in support for this scenario, or is the key file approach the only way?

    Thank you for your response in advance, regards,

    1. Simon Post author

      As far as I know, the key file is the only way. You could try enabling HTTP Basic/Digest authentication on the URL of the key. This will prompt the user for a password.


Leave a Reply to alexhal99 Cancel reply