Xtream Codes vs M3U — Which Connection Should You Use?

2026-09-04 · Foundations · 5 min read

Your provider has handed you either a long URL or a set of three credentials, and your player is asking which you want to use. They reach the same streams. What differs is how the player gets there, and that changes speed, features, and what breaks later.

The short answer

Use Xtream Codes when your provider and your player both support it. It is faster, brings the guide and catch-up without extra configuration, and survives your provider moving servers.

Use M3U when they do not, or when you need the source to work in VLC, Kodi, a browser, or hardware that supports nothing else.

The rest of this explains why, and what to do when either misbehaves.

What each one actually is

M3U is a file. Plain text, one entry per stream, each with a display name, a logo URL, a category, and the address of the stream itself. Your provider gives you a URL that returns this file. The player downloads it, reads every line, and builds a list.

A single entry looks roughly like this:

#EXTINF:-1 tvg-id="channel.one" tvg-logo="https://…/logo.png" group-title="News",Channel One
https://server.example:8080/live/user/pass/12345.ts

Everything the player knows comes from that text. There is no way to ask the file a question — no way to request only the sports category, or check whether catch-up exists. It is a list, and the player takes all of it or none.

Xtream Codes is an API. Rather than a file, your provider gives you a server address, a username and a password. The player calls endpoints on that server and receives structured JSON in reply: the category list, the channels within one category, the guide for one channel, the series episodes for one show.

The practical difference is that the player can ask targeted questions instead of downloading everything.

What that difference costs you

Loading time. This is the one people notice. An M3U file for a large catalogue can exceed 30 MB — every channel, every film, every episode of every series, on one line each. All of it downloads and parses before the app shows anything. Xtream Codes fetches the category list on launch, which is a few kilobytes, and loads a category's contents when you open it. On a modest Android box the gap between them is the difference between an app that opens and an app you wait for.

Memory. A parsed M3U lives in memory in full. On a 1 GB Fire TV Stick a large playlist is enough on its own to cause the stutter people blame on their connection. If your device is old and your playlist is large, switching connection method is a more effective fix than any buffer setting — see the buffering guide for how to tell the two apart.

The programme guide. With Xtream Codes the guide arrives through the same API, already matched to your channels. With M3U the guide is a separate XMLTV file you usually have to supply yourself, and its channel identifiers have to match the tvg-id values in the playlist. When they do not, you get a channel list with an empty guide beside it — the most common EPG failure, and one M3U causes far more often.

Catch-up. Rewinding live television to something broadcast days ago requires the player to ask the server what is available. That question only exists in the API — which is why catch-up, recording and rewind behave so differently depending on how you connect. Some providers encode catch-up hints into M3U attributes, but support is inconsistent and frequently silent when it fails.

Series handling. Xtream Codes returns series as a structure — show, then season, then episode. M3U returns a flat list of every episode as an individual entry, which the player must group by parsing the names. It works, roughly, until a provider names things inconsistently.

Surviving a server change. Providers migrate servers. An M3U URL usually contains the old hostname and simply stops working, so you re-enter it. Xtream Codes credentials often survive the move, because the login is resolved server-side.

Compatibility. This is M3U's win, and it is not a small one. Every media player made in the last fifteen years understands an M3U file. Xtream Codes needs a player built for it. If you want one source that works in VLC on a laptop, in Kodi on a Raspberry Pi and in a player on the television, M3U is the only answer.

Converting between them

They are the same account, so you can usually move from one to the other without asking your provider.

A typical M3U URL looks like:

http://server.example:8080/get.php?username=USER&password=PASS&type=m3u_plus

The three Xtream Codes fields are inside it:

• Server URL — http://server.example:8080 — the scheme, host and port, and nothing after them
• Username — the username parameter
• Password — the password parameter

Going the other way, assemble the get.php URL from the same three values.

The mistakes that account for most failures

Pasting the whole URL into the server field. By a wide margin the most common, and the first thing to check when a login fails. The server field wants http://server.example:8080 and stops there. Including /get.php?username=… produces a login failure that looks like wrong credentials.

Dropping the port. http://server.example and http://server.example:8080 are different addresses. If your provider specified a port, it is required.

The wrong scheme. A provider on HTTPS will refuse plain HTTP, and the reverse. Try the other one before concluding anything is wrong.

Assuming credentials are wrong when the connection limit is reached. Most providers permit one or two simultaneous streams. A third device is refused with an error that reads like an authentication failure. Close the other sessions and retry before changing anything.

Using type=m3u instead of m3u_plus. The plain variant omits logos, categories and guide identifiers. The playlist loads and looks stripped for reasons that are not obvious.

What we do in Xtiva

Xtiva supports both, and lets you add several of either and switch between them without re-entering anything. If your provider supports Xtream Codes, that is the one we would point you at — the loading difference is large enough to change how the app feels.

As always: Xtiva ships with no channels, playlists or streams of any kind. You supply your own provider, and you are responsible for the legality of the service you connect to.

Next: adding a playlist on Android TV, Google TV and Fire TV, or back to what an IPTV player is.