Reviewed: August 2, 2026
If your IPTV EPG is not working, first determine whether the guide source is empty, the player cannot download it, channels do not match guide IDs, listings are shifted in time, or only part of the catalog is affected. Live playback and programme-guide data are separate layers, so a channel can play normally while its schedule remains blank.
This guide uses a measurement-first process for authorized playlists and services. It does not recommend public credential lists, scraped guides, random time shifts, or uploading a private M3U or Xtream login to an online “EPG fixer.”
Quick answer: Refresh the playlist and EPG once, confirm the device's date and time zone, and compare one working channel with one blank channel. If every channel is blank, test the guide source or account. If only some channels are blank, investigate channel-ID mapping. If all listings are off by the same amount, verify timestamps and time zone before applying an offset.
Identify the EPG Symptom
| What you see | Likely layer | First useful check |
|---|---|---|
| “No information” on every channel | Source URL, account, download, or cache | Refresh once and verify that the authorized guide source returns data |
| Guide works for some channels only | Channel-ID mapping or incomplete source | Compare the affected channel's playlist ID with the guide channel ID |
| Every programme is early or late by the same amount | Device clock, source timestamps, or time zone | Enable automatic time and verify one known live programme |
| Only one group has no guide | Source coverage, group filter, or mapping | Compare another channel from the same group |
| Guide was correct, then became stale | Refresh schedule, cache, token, or provider outage | Check the last successful update and account status |
| Channels disappeared with the guide | Playlist or account problem, not EPG alone | Refresh the playlist separately and check account expiry |
| Guide loads but selecting old shows fails | Catch-up entitlement or URL problem | Separate EPG display from catch-up playback |
Write down the player and version, device, playlist type, last successful guide update, one affected channel, one working channel, and the exact non-sensitive error. Never include the full playlist URL, server address, username, password, token, or QR code in screenshots.
Understand the Three Separate Layers
An electronic programme guide usually depends on three data sets:
- The channel catalog — an M3U playlist, Xtream-style account, tuner backend, or another authorized source.
- The programme schedule — often XMLTV data or structured guide responses from the service.
- The mapping rule — an identifier that connects a playlist channel with the corresponding guide channel.
The Kodi IPTV Simple Client documentation, for example, treats M3U as the live-channel source and XMLTV as the EPG source. The guide can fail even when the stream URL remains valid. Our electronic programme guide explainer covers the underlying terms.
Do not diagnose a blank EPG by repeatedly changing video decoders or buffer sizes. Those settings affect playback, not the schedule download or channel mapping.
Step 1: Refresh the Playlist and EPG Once
Use the player's documented update or refresh control. Some players offer separate actions for the playlist and EPG; others refresh both when the profile updates. Allow the operation to finish before reopening the guide.
Do not press refresh repeatedly. Large playlists and compressed XMLTV files can take time to download and parse, and repeated requests may trigger rate limits or replace a useful error with a generic failure.
Record whether the player reports:
- an EPG update time;
- a downloaded channel or programme count;
- an HTTP, authentication, parsing, or timeout error;
- zero programmes despite a successful playlist update;
- a failure only on one saved profile.
If the playlist also fails, work on the account, URL, or network first. If live channels load but the guide alone fails, continue with the schedule source and mapping checks.
Step 2: Verify Date, Time, and Time Zone
Set the streaming device to obtain its date, time, and time zone automatically from the operating system or network when supported. Restart the player after correcting a clearly wrong clock.
A bad device clock can make valid programmes appear outside the current guide window, interfere with certificate validation, or shift “now” to the wrong schedule position. Compare the device clock with a trusted phone and confirm the selected region observes the expected daylight-saving rules.
Do not immediately apply a +1, −4, or other offset copied from a forum. First check whether:
- every channel is shifted by exactly the same amount;
- only channels from one source or country are shifted;
- the XMLTV programme timestamps include a time-zone offset;
- the player applies both a global and per-channel shift;
- daylight-saving time changed recently.
Kodi's IPTV Simple Client supports a global EPG time shift and per-channel values. Its documentation warns that the global setting can override or combine with channel-specific shifts. Use an offset only after the evidence shows a consistent source-level difference.
Step 3: Check Whether the Guide Source Contains Data
For an authorized M3U/XMLTV setup, confirm that the exact XMLTV URL or local file configured in the player still exists and is current. For an Xtream-style account, confirm the account is active and the service currently supplies EPG data.
Do not open a credential-bearing guide URL in a shared browser, copy it into an online validator, or post it in support. Some guide URLs contain usernames, passwords, tokens, or account identifiers. Ask the authorized service to confirm the guide endpoint without exposing it.
When you control the XMLTV file, check a local copy for these structural elements:
- a root
<tv>element; - one or more
<channel id="…">entries; <programme>entries withstart,stop, andchannelattributes;- channel values in programme entries that correspond to defined channel IDs;
- timestamps covering the present date rather than an expired window.
A file can download successfully yet contain no current programmes. It can also be valid XML but fail to map to the playlist.
Step 4: Compare Channel IDs
Partial guide failures most often point to mapping. In an M3U entry, tvg-id commonly identifies the channel. In XMLTV, the <channel> element has an id, and each <programme> refers to a channel value.
Kodi documents a matching sequence that first compares XMLTV channel IDs with M3U tvg-id values, then tries display names or playlist channel names. Exact behavior differs by player, but stable unique IDs are safer than relying on display names that can change.
Compare one working and one blank channel:
| Field | Working example | Blank example to investigate |
|---|---|---|
| Playlist channel name | News One HD | News One FHD |
Playlist tvg-id | news.one | missing or news1 |
XMLTV channel id | news.one | news.one |
Programme channel | news.one | news.one |
The blank channel may play because its stream URL is valid while the absent or different tvg-id prevents guide matching. If you own the playlist and guide, correct the identifiers at the source. If the service controls them, send the non-sensitive channel names and IDs to support rather than editing credentials or downloading a replacement guide from an unknown site.
Step 5: Check Case, Spaces, and Duplicate Channels
Some players match IDs case-sensitively; News.One and news.one may not be the same. Kodi IPTV Simple Client includes an option to ignore case for EPG channel IDs, but correcting the source is preferable when you control it.
Also check for:
- leading or trailing spaces;
- copied punctuation or region suffixes;
- the same
tvg-idassigned to several channels; - separate SD, HD, and 4K variants sharing one schedule;
- renamed channels whose old guide ID remains in the playlist;
- guide entries using display names instead of stable IDs.
Do not globally replace names in a private playlist without a backup. One change can repair a channel while breaking another that legitimately uses a similar label.
Step 6: Separate M3U/XMLTV from Xtream Synchronization
With a separate M3U and XMLTV configuration, verify both locations independently and make sure the player is using the intended pair. Kodi supports multiple M3U/XMLTV configuration pairs, so assigning a guide to the wrong profile can produce a complete but unmatched schedule.
With an authorized Xtream Codes API login, the player may request account, category, stream, and guide information from the same server. A successful login does not guarantee the guide endpoint is populated. Refresh the profile, check account status, and ask the service whether EPG is currently available for the affected channels.
Do not convert a private Xtream login into an M3U or XMLTV URL on a third-party website. Query-style URLs can expose credentials in browser history, proxy logs, server logs, and screenshots.
Step 7: Clear Only the Relevant Cache
Use cache clearing only after confirming that the source or mapping changed and a normal refresh still shows old data. Prefer the player's documented EPG-cache or guide-data reset over clearing all application data.
Kodi's official IPTV Simple Client documentation distinguishes guide cache from the full PVR cache. It directs users to the Guide cache for EPG-related configuration changes and the full cache for channel-related changes.
Clearing application data can erase playlists, profile names, favorites, parental-control settings, recording paths, and credentials. Export or record non-sensitive configuration first, and never assume that an account can be recovered from the app after deletion.
Step 8: Review Refresh and Cache Settings
If the guide becomes stale every day, inspect the refresh schedule. Kodi IPTV Simple Client offers disabled, repeated-interval, and once-per-day modes for M3U/XMLTV refresh. It notes that caching behavior changes when automatic refresh is used.
Choose a reasonable schedule supported by the source. Refreshing every few minutes does not create newer listings if the provider publishes once a day, and excessive polling can cause timeouts or rate limiting. A daily source may need one scheduled update after its publication time plus a manual fallback.
Keep the device awake and connected long enough for scheduled updates. On mobile or TV platforms, battery optimization, background restrictions, low storage, or force-stopping the player can prevent background work.
Step 9: Diagnose Partial or Expired Guide Windows
An EPG can contain yesterday's programmes but nothing for today, or current listings but no future days. Check the earliest and latest programme timestamps before assuming the player is broken.
Possible causes include:
- the provider has not published the next guide window;
- the downloaded file is an old cached copy;
- the account token expired;
- the player filters programmes outside its configured past/future range;
- one country's source updated while another did not;
- a large file was truncated during download.
If several independent devices using the same authorized source show the identical cutoff, the source is the stronger suspect. Report the exact last visible programme time and affected channel group to the operator.
Step 10: Keep EPG and Catch-Up Problems Separate
Seeing old programmes in the guide does not prove that catch-up playback is included. Catch-up requires an authorized archive, suitable stream URL or programme identifier, account entitlement, and player support.
If the guide displays correctly but an old programme will not play, test the current live channel. Then check the account's catch-up window, eligible channels, connection limit, and player documentation. Do not change the EPG time shift to repair a catch-up URL failure.
Player-Neutral Recovery Order
Use this order to preserve evidence and settings:
- Confirm the device clock and internet connection.
- Refresh the guide once and record the result.
- Refresh the associated playlist or account once.
- Compare one working and one blank channel.
- Verify source coverage and current programme dates.
- Compare playlist IDs with guide IDs.
- Correct the source or contact the authorized operator.
- Clear only the EPG cache if stale data remains.
- Re-add the profile only after backing up recoverable settings.
- Reinstall the official player only as a final app-level test.
This order avoids destructive resets and distinguishes a bad source from a bad player configuration.
Frequently Asked Questions
Why does IPTV play but show “No information”?
The stream and guide are separate. The stream URL or account can work while the XMLTV data is empty, expired, unreachable, or unable to match the channel ID.
Should I change the EPG time shift?
Only when all affected listings have a consistent measured offset and the device clock, source timestamps, and daylight-saving rules are correct. Do not use a shift to repair missing programmes or mismatched channels.
Can I download a free EPG from another website?
Use only a source you are authorized to access and whose provenance, privacy, and terms you can verify. An unrelated guide may have incompatible IDs, incomplete rights information, tracking, or malicious downloads. Never upload private playlist credentials to obtain it.
Why is the guide wrong on only one channel?
That usually indicates a channel-specific ID, display-name, duplicate-entry, or source-schedule problem. Compare that channel with a working one before changing global settings.
Will clearing app data fix the EPG?
It may remove a corrupt local state, but it can also erase every playlist and setting. Use the guide-cache control first and retain account recovery information securely.
Primary Sources
- Kodi Wiki: IPTV Simple Client and M3U/XMLTV guide mapping
- Kodi IPTV Simple Client repository and configuration documentation
- OWASP REST Security: sensitive credentials in URLs
- MDN: Transport Layer Security and HTTPS
- TiviMate terms: player and content-source separation
Bottom Line
When an IPTV EPG is not working, diagnose the guide as its own data path. Refresh once, verify the clock and source window, compare channel IDs, separate M3U/XMLTV from Xtream synchronization, and clear only the relevant cache. Fix the source or mapping that evidence identifies instead of hiding the problem with random offsets, destructive resets, or untrusted guide downloads.