Public Xtream playlists

How Xtream entries work (and why they list differently)

Entries here are not files but access endpoints: a host URL plus credentials that a player queries over a structured API. That changes what “indexed” means. The directory records the endpoint's source and format, but channel contents live server-side and can only be observed through an authenticated check, never by downloading text. Analysis: this is why Xtream entries stay Unchecked longer than M3U ones. Verifying them requires credential-based probing rather than a simple fetch, so each check is heavier and rarer.

Never post host + username + password together to ask for help. Anyone holding the triplet holds the access. Describe the Xtream test verdict (host reachable, auth accepted/rejected) instead; it reports status without exposing secrets.

What Unchecked means for an endpoint

For M3U entries, Unchecked means “not yet fetched and parsed.” For Xtream entries it means something broader: neither reachability, nor authentication behavior, nor category contents have been observed. An Unchecked endpoint therefore carries three unknowns instead of one: host liveness, credential validity, and content state. Analysis: rank Xtream candidates by source reputation and recency rather than treating all Unchecked entries as equal; then let the Xtream test convert unknowns into timestamped observations one stage at a time (host, then auth, then categories).

Never “verify” an endpoint by posting it publicly for others to try. Publicizing a host plus credentials destroys the access you were testing. Test privately, share only verdicts.

Using an Xtream entry safely

1. Read the detail page: source, recorded host pattern, and any credential terms the source states.
2. Verify host reachability and auth with the Xtream test before configuring any player. The password field clears after each run and nothing is stored.
3. Enter the triplet directly into the player's Xtream section (not an M3U field), watching for trailing spaces.
4. If login succeeds but categories are empty, check expiry and connection slots first. The full tree is in What is Xtream Codes.

FAQ

Why are there fewer Xtream entries than M3U? Public, credential-free Xtream endpoints are rarer than public M3U files by nature. Logins are provisioned per account, files are published openly.

Can I convert an Xtream login to M3U myself? No client-side conversion exists; some providers issue an M3U URL for the same account. Use the official one.

Is testing my own login here private? The Xtream test sends credentials once for the check, never logs or stores them, and clears the password field afterward. Still, never test someone else's credentials.

Does the port in the host matter? Yes. Host, port, and http-vs-https together identify the endpoint. A correct host with the wrong port fails exactly like a dead server, so copy the triplet verbatim rather than reconstructing it.

HTTP or HTTPS for the host? Whichever the source specifies. Guessing wrong produces connection failures that look like outages; confirm the scheme from the provider's documentation before changing anything else.

How do I share test results safely? Quote the verdict (reachable/unreachable, auth accepted/rejected, categories empty/populated) with the timestamp. Never the host, username, or password.

How these entries are checked

Methodology: status badges appear only with a real check timestamp; until then entries show as Unchecked with unknown counts. Channel counts come from parsed data, never estimates, and HTTP 200 on a playlist URL never implies every stream plays. Third-party sources are attributed and their licensing is stated only when known. The full methodology — badge meanings, freshness reading, and what we never claim — is on the main directory page.

Sources

Entry data comes from attributed third-party sources on each detail page. API behavior background: What is Xtream Codes? and the structured-data example at iptv-org/api (verified October 2026).