M3U vs Xtream Codes
Most providers hand out both, without explaining that they are the same content over two different mechanisms. The choice changes how fast the app opens, whether the line-up stays current, and whether you get a programme guide at all.
What an M3U playlist is
One text file listing every channel and its address. The player downloads all of it, then plays from the list. It is universal — every player made in the last twenty years reads it — and it is a snapshot: when the provider changes the line-up, your copy is stale until you refresh it.
What the Xtream Codes API is
A conversation instead of a file. The player asks for categories, then for the channels in the one you opened, then for a stream when you press play. Nothing is downloaded before it is needed, so the app opens at once however large the library is.
Where the difference shows
On a large subscription. Twenty thousand channels as a playlist is several megabytes parsed on every refresh; as an API call it is a category list. The API also carries structure a flat file loses — films and series as their own things, with seasons, episodes and often the programme guide.
Which to choose
Use Xtream Codes when your provider offers it. Use M3U when it is all you were given, when you are testing a trial, or when the playlist comes from something that has no API at all — your own file, a free public list, a home media server.
The same subscription, two doorways
A provider sells you one account. What differs is the door you come in through. An M3U link is a text file the server writes out on request: every channel, one line each, in whatever order the panel felt like. The Xtream API is that same catalogue queried properly — categories, films and series as separate things, posters, plots, and the date your account runs out. Same channels, same streams, same bill. What changes is how much the app is allowed to know about them.
What a plain M3U cannot tell the app
Four things, and they are the four you notice. It cannot say which entries are live television and which are films, so everything lands in one list. It has no season and episode structure, so a series arrives as eighty loose files. It carries no posters and no plots. And it cannot report when your subscription expires, so no app can warn you before it does. None of that is the player falling short — the information was never in the file.
Tivsy turns one into the other for you
If the link your provider sent looks like …/get.php?username=…&password=…, that is an Xtream panel exporting an M3U, and your account details are sitting in the address itself. Paste it exactly as it came and Tivsy reads them out and connects to the API instead, so you get the structured catalogue without needing to know any of this. The username and password go to the Keychain; only the host is kept in the database.
Common questions
How do I tell which one I was given?
A single long link, usually containing get.php, is a playlist. A short address plus a separate username and password is an Xtream account. A link with get.php contains the username and password inside it, so it can be turned into an Xtream login.
Do they give different channels?
No. Same account, same content, different route. If a channel is missing from one it is missing from the other.
Is one of them more private?
They are equivalent. Both send your credentials to the same provider. Neither involves the player's developer, because there is no account and no server in between.
Can I use both at once?
Yes. Tivsy treats each source separately, so you can add a work playlist, a home server and an Xtream account, and search across all of them.
My provider only sent an M3U link. Am I stuck with the flat list?
Probably not. Look at the link itself: if the path is get.php and it carries a username and password, Tivsy uses the API automatically the moment you paste it. If it is a plain file link — ending in .m3u or .m3u8 with no credentials in it — then there is no API behind it to reach, and the flat list is genuinely all the file holds.
Does one of them use less data?
Not for video: the streams are byte-for-byte the same. The difference is in refreshing. An M3U refresh re-downloads the entire file, which on a large subscription is several megabytes every time. The API is asked only for the parts that changed. Over a month on mobile data that adds up; on Wi-Fi you will never notice it.
Whichever you use, the app is the same empty player: it brings the interface, the guide and the resume, and you bring the source.