Articles
M3U playlist format: how to read a channel list
Read an annotated M3U playlist example, understand EXTINF and tvg-id fields, and inspect channel URLs safely before importing your own playlist.
Published by InoxTV · Published
Last updated
The M3U playlist format is text that describes media entries and where to find them. Reading a short example can help you distinguish a catalogue problem from a playback problem before changing application settings. The example below is deliberately fictional: its reserved example domain is not a source of television, and copying it into a player will not provide working channels.
Start with a small, readable example
#EXTM3U
#EXTINF:-1 tvg-id="demo.news" group-title="Examples",Example News
https://media.example.com/news/index.m3u8
#EXTINF:-1 tvg-id="demo.documentary" group-title="Examples",Example Documentary
https://media.example.com/documentary/index.m3u8
The first line announces an extended M3U file. Each entry then has a line of descriptive information followed by a location. In this example, the locations point to HLS playlists, but an M3U entry does not have to end with that extension. The address could represent a different supported media format or a server endpoint that returns media without an obvious filename.
Open a copy in a plain-text editor when inspecting a file you own or are authorised to use. Avoid word processors that change quotation marks or save rich-text formatting. Preserve the original file so that an experiment with a label does not become the only copy of your working list.
What the descriptive fields tell you
The EXTINF line holds information associated with the next entry. In many IPTV catalogues, a duration of minus one represents an entry without a known fixed duration. The text following the comma is the display name. The attributes before it are conventions used by particular players and providers; their support is not identical in every application.
| Example field | Purpose | What it cannot prove |
|---|---|---|
tvg-id="demo.news" | A channel identifier that can be associated with guide data | That a matching guide entry exists |
group-title="Examples" | A suggested category for organising entries | That all players interpret groups identically |
Example News | A readable channel name | That the stream is online or licensed |
| The following URL | The location requested for playback | That the account is authorised to access it |
A logo address, when present, is another resource the interface may request. A missing picture therefore does not necessarily mean the video is broken. Equally, a correctly displayed logo is not a playback test. Keeping names, artwork, identifiers and video locations separate makes your observations much more precise.
A channel list can point to another playlist
It is normal for the outer catalogue to contain addresses whose responses are themselves playlists. The outer list answers which channel the viewer selected. An HLS manifest can then describe the media renditions or the sequence of small segments used to deliver that channel. These are different layers, even if both use related text syntax.
For that reason, the presence of an M3U8 suffix is not enough to decide whether a URL belongs in a catalogue importer or a media player. The M3U and HLS comparison explains the distinguishing tags. Follow the instructions from your authorised source rather than changing file extensions until an importer accepts them.
Check identifiers when the guide is missing
In the fictional example, the identifier demo.news can correspond to a channel declared in an XMLTV guide. The programme records refer back to that guide channel identifier. If the source uses demo.news.hd instead, similar display names do not necessarily produce a match. The exact matching behaviour depends on the application and the source's conventions.
Before editing identifiers, compare the catalogue and guide that are intended to work together. A region-specific feed may use a different identifier from a national feed with a similar name. Broadly replacing names across a large file can introduce incorrect matches. Work on one clearly understood example and read how XMLTV matching works before changing the full list.
Inspect structure without exposing an account
A URL can contain credentials in its path as well as after a question mark. Redacting only a parameter called password is not sufficient. There may be a token, account number or signed address elsewhere. When preparing an example for support, replace the complete location with a reserved example address and describe the response or error separately.
Do not upload a private playlist to an online formatter or validator simply because it offers a convenient preview. A downloaded catalogue may expose every stream address associated with the account. Keep backups in storage you control and consider who can access a synced folder. The playlist privacy guide includes a practical redaction checklist.
Recognise what editing can and cannot fix
A plain-text copy may reveal an incomplete address, an accidental line break, or an HTML sign-in page saved with an M3U extension. Those are useful findings. However, a syntactically plausible file can still point to unavailable media. Changing a group name, identifier or file suffix cannot renew an account, bypass a server restriction or grant permission to watch content.
If a catalogue loads but one entry fails, record whether other entries work and whether the failure follows the same authorised stream in another compatible setup. If the catalogue itself will not import, preserve the original response and check the playlist loading guide. Once the structure is understood, the InoxTV M3U setup guide provides the actual import steps.
