Xtream Converter: Turn Xtream Codes Login Into a Playlist

An Xtream converter derives the URLs a player actually uses from your three login pieces: portal address, username, and password. It’s a convenience tool — every Xtream-native player does this math internally — but it’s useful when setting up manually or feeding a generic player. This guide explains the conversion and the safety rules.

What the converter produces

From portal.example:8080, USER, and PASS, an Xtream converter generates the standard URLs:

# M3U playlist
http://portal.example:8080/get.php?username=USER&password=PASS&type=m3u_plus

# Single live stream
http://portal.example:8080/live/USER/PASS/1001.m3u8

# VOD movie
http://portal.example:8080/movie/USER/PASS/2001.mp4

# Series episode
http://portal.example:8080/series/USER/PASS/3001.mkv

These patterns are fixed and documented in The Xtream Codes API. A converter just fills in your values.

The four URL forms, explained

Every portal exposes the same small set of derived URL shapes, each with a specific purpose:

• get.php (playlist) — returns the extended M3U file for your whole subscription. Choose type=m3u_plus to include tvg-id, tvg-name, tvg-logo, and group-title attributes needed by apps for groups and the EPG. A plain type=m3u omits them. Use type=ts or type=m3u8 variants only if your player requires a specific container.
• /live/USER/PASS/ID.m3u8 — a single live channel. This is what apps play in the background; you rarely need it yourself except for quick VLC tests.
• /movie/USER/PASS/ID.mp4 — a single VOD title. The extension reflects the actual container; the portal picks it, not you.
• /series/USER/PASS/ID.mkv — a single series episode. The ID is the episode’s own ID from the series info, not the show ID.

Knowing which form maps to which feature helps you pick the right one and confirms your converter produced the expected output.

How the conversion actually works

The player does the same thing a converter does, but automatically: you enter host, username, and password once, and the app builds get.php and /live/ URLs on demand. That is why the login flow hides these links from you.

What often confuses people is the port. The portal base URL is usually host plus a port such as 8080, written as portal.example:8080. Some players only type up to the domain and keep the port in a separate field, so a converter must preserve the correct base to build valid links. If your derived URL drops the port, the request will time out — the converter (or your manual string) forgot to carry it.

Doing the conversion yourself

You don’t need a tool. The URL is deterministic:

1. Take your portal base URL, e.g. http://portal.example:8080.
2. Append /get.php?username=USER&password=PASS&type=m3u_plus for the playlist.
3. Append /live/USER/PASS/STREAMID.m3u8 for an individual channel.

You can even verify it in a browser — the playlist link returns the extended M3U file. Confirm it parses with the M3U validator.

When a converter is actually useful

• Players that take a playlist URL, not a login — VLC, generic apps, or your own scripts. You give them the derived get.php link instead of credentials.
• Quick stream testing — paste a single /live/ link into VLC to test one channel without full setup.
• Automation — building a custom dashboard or monitor that needs direct stream URLs.

Otherwise, stick with a native Xtream player — see Xtream Codes player — which derives these links itself and keeps your credentials out of URLs you paste elsewhere.

Security rules for converters

Your username and password are embedded in every derived URL. That has two consequences:

1. Never paste a derived URL into a web converter, forum, or support chat — it’s equivalent to sharing your password.
2. Treat playlist files as credentials — a .m3u8 from get.php contains your full login. See Xtream Codes security.
3. Prefer local tools — if you automate this, run the conversion locally, not through a third-party website.

Verifying the conversion before you rely on it

A quick sanity check catches most mistakes before you load a playlist into a player. First, confirm the derived URL responds: open get.php in a browser and check it returns the M3U text rather than a login error or an empty body. Next, confirm the port survived — a Connection timed out or ECONNREFUSED almost always means the base URL dropped the :8080 (or the portal’s own port). Finally, run the returned content through the M3U validator to confirm the structure and catch truncated entries.

The same checks work for a single /live/ link: if it fails but the playlist loads, the issue is specific to that channel rather than your credentials. This mirrors what an IPTV checker verifies automatically — reachability first, then channel-by-channel playback.

Related reading

• The Xtream Codes API — the exact URL patterns.
• Xtream Codes Authentication — how the login is verified.
• M3U Validator — check the derived playlist after conversion.