Xtream Codes
How to Add Xtream Codes to OTT Navigator
Understand the Xtream-style provider format, what each credential means, how the setup differs from an M3U URL, and how to isolate authentication, catalog, EPG, and playback failures.
What Xtream Codes means in OTT Navigator
Xtream Codes is a provider-input method in which the service typically gives you separate connection information instead of asking you to paste one complete M3U playlist URL. In the common setup, that means a server or portal address, a username, and a password.
OTT Navigator supports Xtream Codes for provider content. The app is still the player: the provider supplies the account and streams, while OTT Navigator uses the supplied information to load the available content.
How to recognize the format
If your provider gives you three separate values resembling a server address, username, and password, the Xtream-style method is generally the relevant one. The official OTT Navigator FAQ also identifies a get.phpURL containing username and password parameters as an indication that the Xtream Codes template may be appropriate.
Do not decide from the word “IPTV” alone. Look at the actual information your provider supplied and preserve the server address exactly as given.
What each credential does
| Credential | Role | Common mistake |
|---|---|---|
| Server / portal address | Identifies the provider endpoint used by the app. | Changing the host, path, or port. |
| Username | Identifies the provider account. | Adding spaces or copying extra punctuation. |
| Password | Authenticates the account. | Using an old password or altering special characters. |
How to add Xtream credentials
- Open the provider configuration area in OTT Navigator.
- Select the Xtream Codes method when it matches the information supplied by your provider.
- Enter the server address, username, and password exactly as supplied.
- Save the provider and allow OTT Navigator to request the available library.
- Check whether Live TV categories and channels appear.
- Then test Movies or Series if those sections are included with your account.
- Only after the catalog loads should you move on to playback or EPG diagnosis.
Menu labels can vary with app versions and device layouts, so the important part is choosing the provider method that matches the credential format rather than relying on one exact button name.
Xtream Codes versus an M3U URL
| Input you received | Typical method | How to handle it |
|---|---|---|
| One complete playlist URL | M3U / playlist URL | Paste the complete address without editing it. |
| Server + username + password | Xtream-style credentials | Enter each value in its corresponding field. |
A get.php address may look like a normal M3U URL while carrying username and password parameters. In that situation, the same information can sometimes be represented through the Xtream template. Do not manually reconstruct credentials unless you understand the provider's format.
Diagnose authentication failures first
If the provider cannot be loaded, troubleshoot the connection and credentials before changing player settings. A playback setting cannot repair an account that was rejected during provider authentication.
| Symptom | Check first | Likely layer |
|---|---|---|
| Credentials rejected | Server, username, password, account status. | Authentication / provider |
| Nothing loads | Network access and whether the provider endpoint is reachable. | Network / provider |
| Live TV loads but Movies or Series are absent | Whether those categories are included with the account. | Provider catalog / account |
| Categories appear incomplete | Refresh/reload behavior and provider-side availability. | Provider response / catalog |
| Catalog loads but streams fail | Test several channels and compare networks/devices. | Stream / network / playback |
Why valid Xtream credentials do not guarantee playback
Successful authentication answers one question: the player can communicate with the provider using the supplied account details. It does not prove that every channel, stream type, codec, or network path will work on the playback device.
| Result | What it separates | Next test |
|---|---|---|
| Authentication fails | Credentials/server/account access | Recheck server, username, password, and provider status. |
| Login works, no channels | Account response/catalog or provider configuration | Reload the source and inspect what the provider returns. |
| Channels appear, playback fails | Stream/network/device playback layer | Test several channels and compare behavior. |
| Playback works, EPG is wrong | Guide source/mapping/time zone | Troubleshoot EPG independently. |
When the credentials work but playback does not
A successful login only proves that the provider information was accepted. It does not prove that every individual stream is available or compatible with the current network and playback environment.
- Test more than one channel instead of treating a single failed stream as a provider-wide failure.
- Compare a working and failing channel when possible.
- Check whether the same account behaves differently on another authorized device or network.
- If only particular streams fail, record the pattern before contacting the provider.
- Use the dedicated buffering and playback troubleshooting guides before repeatedly replacing credentials.
EPG problems are a separate layer
If channels and playback work but program information is missing, do not assume the Xtream credentials are invalid. EPG data can depend on the provider configuration, channel identifiers, and EPG source mapping.
Learn how OTT Navigator EPG works →Protect your provider credentials
Treat the server address, username, password, and any generated playlist URL as private account information. Do not place real credentials in public screenshots, Git repositories, issue reports, analytics URLs, or sample code. When asking for technical help, redact usernames, passwords, tokens, and unique provider domains where possible.
Related guides
Official sources
For current app capabilities, distribution details, and documented settings, verify details against the product's published resources.