M3U guides for the parts tools cannot decide

• Guide M3U playlist format explained What the header does, how an EXTINF line is assembled, which attributes players actually read, and the faults that stop a file loading.
• Guide M3U vs M3U8 One is an encoding, one is a streaming protocol, and the file extension blurs both. What actually changes when you rename a file.
• Guide Removing duplicate channels Exact duplicates are easy and near-duplicates are a judgement call. How to tell them apart, and when a duplicate is deliberate.
• Guide How to open an M3U or M3U8 file Why nothing opens it on double-click, which players read a playlist, and why Safari plays an HLS manifest that Chrome only downloads.
• Guide Playlist URL vs file on disk The same text over HTTP behaves differently: content types, redirects, tokens and CORS explain why a URL works in one program only.

Read the one that matches the symptom, not the one whose title sounds most general. These symptoms cover almost everything people arrive with:

• The file opens to nothing, or one channel is missing. That is a structural fault, and the format guide lists the failures in the order a parser meets them, with the line each one lives on.
• The names are full of symbols instead of accents. That is an encoding problem, not a formatting one. The M3U vs M3U8 guide explains why the extension carries the encoding convention and what re-saving can and cannot repair.
• The same channel appears more than once. The duplicate guide separates exact repeats from near-repeats, because only one of those is safe to remove automatically.
• Nothing opens the file at all. That is usually a missing file association rather than a broken playlist. The opening guide lists which players read a playlist and which browsers cannot.
• It works in one program and not another. A URL is fetched under different rules than a file. The playlist URL guide explains content types and CORS, which is where that difference lives.

If you have not looked at the file yet, start with the format guide: it is the only one that explains what the lines are before telling you what is wrong with them.

Most playlist problems people search for are not tool problems. They are questions about the format — why a file with the right extension will not open, why a channel keeps appearing twice, why the names are full of symbols instead of accents. A validator can tell you a file is structurally correct while saying nothing about any of that, because structure and meaning are separate.

So the format guide starts from the line a player actually reads and works outward from there. The M3U versus M3U8 guide separates two things that share an extension and almost nothing else. The duplicate guide covers the case where the honest answer is “it depends”, which is the case tools usually handle worst.

Everything here assumes you already have a file and want to understand it.

None of the three explains where to get playlists. That is a different subject with different risks, and this site stays out of it: there is no catalogue of channels here, no subscription sold, and no list of “best” sources. A guide that recommends providers is a guide that has to keep checking whether those providers still exist and whether they are legal to use, and that is not what this site is for.

They also do not test whether a stream works. Every check described here reads the file, not the network — which is why the tools never contact a URL you paste into them. If a channel plays in one player and not another, the guides explain the structural reasons; they cannot tell you whether a server is up, because answering that would mean requesting it from your browser.

Where a rule is a convention rather than a specification, the guides say so. Much of what is published as M3U documentation presents player behaviour as if it were a standard, and that is the single most common source of bad advice on this format. If you want to know who writes these pages and how they are checked, the about page covers it.