LanguageEnglish

Articles

M3U vs M3U8: a channel list is not always a video manifest

Compare M3U channel catalogues with M3U8 HLS multivariant and media playlists, using annotated examples that explain what each file actually describes.

Published by InoxTV · Published

Last updated

Comparing M3U vs M3U8 becomes easier when you separate a file's name from its role. An IPTV catalogue can list many channels. An HLS manifest can describe how to deliver one presentation. Both may use extended playlist syntax, and a channel catalogue can point to an HLS manifest. The shared appearance does not make them interchangeable inputs for every application.

What the extension tells you

M3U is a playlist format with a long history across media applications. The M3U8 extension conventionally indicates UTF-8 text, which can represent channel names and other information in many writing systems. HLS uses a defined playlist format with its own required tags and rules. Simply seeing the number eight in a filename does not establish that those rules are followed.

Some servers expose a playlist through an endpoint without either suffix. Others use query parameters to choose the response format. A browser download called playlist.txt may therefore contain useful playlist data, while a file named channels.m3u8 might actually hold a sign-in page or error response. Contents, content type and the source's instructions are more informative than a guessed extension.

Layer one: a catalogue of channels

A catalogue answers a navigation question: what choices should the player present? Each entry commonly has a name and a playback address, with optional grouping and guide identifiers. These fields organise the interface. They do not describe how the video is compressed or how a live broadcast is divided into downloadable pieces.

#EXTM3U
#EXTINF:-1 tvg-id="demo.news",Example News
https://media.example.com/news/master.m3u8

This fictional entry offers one channel called Example News. The following address is the next resource a player would request after selection. It does not embed video inside the catalogue. For a fuller explanation of the optional metadata, see reading an M3U channel list. The reserved example domain here supplies no working broadcast.

Layer two: a choice of HLS renditions

An HLS multivariant playlist, called a master playlist in RFC 8216, can advertise alternative renditions of the same presentation. They might differ in bitrate, resolution or other characteristics. A compatible player can choose among the advertised options according to its implementation, estimated connection capacity and device capabilities. Adaptation is possible only when suitable alternatives are actually provided.

#EXTM3U
#EXT-X-STREAM-INF:BANDWIDTH=1500000,RESOLUTION=640x360
low/index.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=4500000,RESOLUTION=1280x720
high/index.m3u8

This simplified example points to two subordinate playlists. Its bandwidth values describe advertised variants; they are not a speed test of your internet connection. The relative paths are resolved against the address of the manifest. Copying only a relative path into another context loses the base address needed to locate it. Real manifests can contain additional information about audio, subtitles and codecs.

Layer three: a sequence of media segments

A media playlist identifies the pieces that form a rendition over time. Its entries can include segment durations, sequence information and locations. For a live presentation the list may change as new segments become available and older ones leave the viewing window. A successfully downloaded copy can therefore become stale; repeatedly opening an old saved copy is not equivalent to following a live service.

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:6
#EXT-X-MEDIA-SEQUENCE:100
#EXTINF:6.0,
segment100.ts
#EXTINF:6.0,
segment101.ts

The segment addresses above are fictional. The durations describe pieces of one presentation, not separate channels. The EXTINF tag also appears in other extended M3U contexts, so identify the surrounding HLS tags instead of deciding from one familiar line. RFC 8216 defines the required playlist behaviour and additional tags used for encryption, discontinuities and other delivery details.

Why this distinction helps troubleshooting

A working channel list proves that catalogue information was obtained. A working multivariant manifest proves that rendition descriptions were obtained. Neither result proves that every subsequent resource is available or authorised. Playback may still fail while requesting a subordinate playlist or segment, or when the device tries to decode the media it receives.

This also explains why a connection can appear active while the first picture takes time to arrive. Several dependent requests may be involved before sufficient playable data reaches the decoder. The playback-start sequence separates those stages. A symptom should be associated with evidence from its stage rather than with a blanket claim that the playlist format is broken.

Use the source's intended entry point

Keep the full relationship between resources in mind when investigating an error. A request to one hostname may succeed while a later media request goes to a different host with different availability or authorisation requirements.

If your authorised provider gives you a channel-catalogue URL, import it using the documented playlist workflow. Do not replace it with a random segment or subordinate manifest obtained during inspection. Such addresses may be temporary, tied to a session or unsuitable as a permanent catalogue entry. An address that played once does not necessarily form a stable setup.

When asking for help, describe whether the problem concerns importing a catalogue, selecting a rendition or playing media. Do not post private manifests or signed URLs publicly. For InoxTV's supported setup fields, use the M3U setup guide; for picture-quality terminology, continue with bitrate, resolution and frame rate.

References

Questions people ask

Does renaming .m3u to .m3u8 convert a stream to HLS?
No. A filename change does not create HLS tags, media segments or a compatible encoding. The file contents and the server responses determine how the media is delivered.
Is M3U8 always a single television channel?
No. The extension is associated with UTF-8 playlist text and is used by HLS, but it does not by itself identify a file's purpose. Inspect its contents and follow the source's setup instructions.
Why can a manifest open while playback still fails?
The manifest is only one request. Its referenced playlists, keys or media segments may be unavailable, require authorisation or use unsupported media. Receiving the first text file is not an end-to-end playback test.