Playlist will not load: the six causes we see most

A playlist that will not load is usually one of 6 things. They are listed roughly in order of how often we see them, except the third, which is out of order because it wastes the most time.

1. The credentials expired, or the subscription was suspended#

The dullest answer and the most common one. Providers expire accounts, and a rejected login and an unreachable host look alike from the outside, so the failure often reads as a network problem. Inside the app they are kept apart: when the provider does answer, an account it marks expired, disabled or banned, or a password it refuses, is reported as that rather than as a network failure.

Test it outside the app: open the provider address in a browser and see whether it answers. If it refuses you there too, nothing on your machine is at fault.

2. You are at your connection limit#

An import or a refresh may need a connection of its own, and a subscription allowing 2 with 2 already in use has none to give. The failure is intermittent and follows no pattern you can see, because it depends on what everyone else in the house is doing. For a provider login the numbers are not hidden: the provider's login reply carries both the connections your subscription allows and the connections in use, and the app reads both when it first checks the account.

Stop every other stream and retry once. If it works, the diagnosis is settled. Provider connection limits covers the accounting, including why a connection can stay spent for a while after you stopped watching.

3. It fails on one machine and works everywhere else#

This one is out of order because it is the expensive one.

The symptom is specific and misleading: the login or refresh call fails on one device, while the same account works on another. Same host, same credentials, same network. Everything about it says the provider is broken.

It took me a long time to see the first time, precisely because everything that normally indicates a working setup was working. I blamed the provider first. The test that identifies it: try the same account on a different machine on the same network. If that one logs in fine, the provider is not the cause, and the difference is in the software or settings of the first machine.

4. It is a URL, but not the right kind of URL#

Providers hand out several addresses and they are not interchangeable. A provider login address, a playlist export URL and a guide URL look similar and do different things.

The three shapes, which providers rarely label:

provider login   https://provider.example.com          host + username + password
playlist         https://provider.example.com/playlist.m3u
guide            https://provider.example.com/guide.xml

If you have a username, a password and a host, add it as a provider login rather than pasting a generated playlist URL. You get categories, a connection count and catch-up that a flat export cannot express. M3U versus a provider login covers the difference.

URLs are accepted up to 2048 characters, so length is rarely the issue. Copy and paste rather than typing. A single wrong character in a token fails exactly like expired credentials.

5. The account is at 10 cloud playlists#

The ceiling is 10, and the check runs when an upload starts rather than when it finishes, so you find out before spending the bandwidth. Remove one you no longer use.

6. The file itself is malformed#

This is the case where "added successfully" and "works on your device" are two different events.

The server does not parse your playlist. A file import is stored encrypted and a URL import records the address; the parsing happens on the device that is going to play it. So a source can be added to your account without complaint and then fail on one machine. That is not a contradiction. One check does run before a file leaves your device: it must be named .m3u or .m3u8 and begin with #EXTM3U or #EXTINF, so a saved error page is refused at the upload rather than stored and broken later.

What goes wrong inside files is more mundane than people expect. A fixture pack of 51 real-world files turned up 3 distinct faults, each capable of losing an entire provider's data over a single byte: an unescaped ampersand, a file declaring UTF-8 while carrying Latin-1 bytes, and a stray control character. All 3 are now repaired rather than fatal, and the repairs are counted, so a file that needed patching says so. Compressed input is identified by its leading bytes rather than its name, and decompression stops at 2 GiB of output or 400 times the compressed size, so a URL that promises one thing and serves another still works, and a hostile archive does not fill a disk.

Slow is not the same as broken#

Rule this out before concluding anything. A playlist from a provider can hold thousands of entries across many groups of very different sizes. Parsing and indexing that on first import takes real time, and a device that looks stuck may be working.

Give a first import a few minutes. Every launch after it is fast, because the index is built once.

If the source loads and the channels are there but the schedule is empty, that is a different problem: an empty guide. If channels load and will not play, fixing buffering and stuttering starts with the classification.