Creating HTTP Live Streaming video is just a click away!

Stream your video from an ordinary HTTP server to a mobile device.

● Automatically detects the Apple recommended encoding specifications for HTTP Live Streaming.

● Encoding, Segmenting & Indexing all in one tool.

● Availability of conversion queue for batch processing.

● Ability to create only desired streams for a variant playlist.

● Ability to change bit-rate, dimension and video profile of any Stream.

● Ability to specify the duration of segments as well as the HLS Version.

● Availability of Audio only Stream for low bandwidth connections.

● Availability of Encryption Option.

● No need of mediafilesegmenter or variantplaylistcreator.

● Supports most widely used video containers such as .mp4, .m4v, .mkv, .avi, etc.

Steps :

1. Open the video file by clicking 'Open Video'.

2. Specify the desired gears, bit-rate and other options.

3. Click 'Create HLS' and choose a folder to keep the files.

Automatic Gears


One Stop Solution

One Click M3U8 automatically detects Apple Recommended Encoding Settings for HTTP Streaming from the input video. The user has total control over in specifying desired gears, duration of the segments, HLS Version, bit-rate, dimension, encryption and video profile.

The created video content can now be protected by industry standard AES-128 Encryption just by selecting the option. The URL prefix option comes in handy if the user decides to move the keys to a HTTPS Server.

No other Tools needed.

The application encodes, creates all the segments, index files and the data for index files. Encoding, Segmenting & Indexing all in one tool. And it's blazing fast!

App in Action


Does One Click M3U8 creates the HTTP Live Streaming content as per Apple's recommended settings?

Yes. Here is the link. Look for section "Preparing Media for Delivery to iOS-Based Devices" all the way near the bottom of the page.


Do you have a sample .m3u8 created by 'One Click M3U8'?

Yes. Here it is. If you are viewing this page in a iOS device touching the link will play the video.


Do you have a sample input .mp4 and output .m3u8?

Yes. It's here.


My video is lengthy and it takes huge time to create HLS media. Is there a way reduce the time taken to render?

That's  because the app has to encode same input video to different bit rates. Avoid higher bit rate gears by deselecting the check boxes. Also you can avoid higher resolution and/or higher bit rate if your end user might not require them.


Is there a way to play the created m3u8 variant playlist video in desktop?

Yes. JWPlayer has a solution. Here is a sample .m3u8 playing in JWPlayer Premium.





















What is HLS?

HLS stands for HTTP Live Streaming. To Stream a video from an ordinary HTTP Sever to an iOS device, the source video needs to be converted to format as explained by Apple here. Apple has more FAQ here.


What are the different HLS Versions?

There are several HLS Versions available depending upon the capabilities of a video stream. Here is the HLS Version 3 defined by ietf . The HLS version is linked to to iOS Version. For example HLS Version 3 content can only be viewed on a device that is running above iOS version 4.2. Every new HLS Version add new capabilities such as HLS 4 supports byterange and HLS5 supports the use subtitles. One Click M3U8 currently supports HLS 2 & 3.


What is Video Profile ?

As the HLS Version is linked to iOS Version, the Video Profile is linked to the iOS device Hardware. For example iPad, iPhone 3G, and iPod touch (2nd generation and later) support H.264 Baseline 3.1. If your app runs on older versions of iPhone or iPod touch, however, you should use H.264 Baseline 3.0 for compatibility. If your content is intended solely for iPad, Apple TV, iPhone 4 and later, and OS X computers, you should use Main Level 3.1. One Click M3U8 creates the all various video profiles supported by all the iOS devices.


Can you explain more about the encryption feature?

The users can now protect their content by enabling this option. Once enabled the created content is encrypted using industry standard AES-128 encryption. The sequence number of the media file is used as the IV(Initialization Vector) when encrypting or decrypting, that's why EXT-X-KEY tag does not have the IV attribute. The keys are always created in a folder called 'Keys', If the user decides to move the keys to a HTTPS server (ideally) the URL prefix field comes in handy.