If IPTV video works but the guide does not, troubleshoot EPG separately from playback. Refresh the guide, verify the XMLTV/EPG source, compare playlist tvg-id values with guide channel IDs, check for renamed/duplicate channels, set the device to the correct automatic time zone, remove unnecessary manual EPG shifts, clear only the guide cache when data is stale, and test whether the problem follows the same guide source in another compatible player. That sequence tells you whether the failure is mapping, time, cache, player behavior or upstream guide data.
An EPG is metadata. It does not carry the television video itself. Jellyfin's current Live TV documentation describes guide data as a separate source that must be mapped to the corresponding live channels; Kodi IPTV Simple likewise treats M3U as the channel source and XMLTV as the EPG source. That separation is the key to diagnosing guide problems correctly.
1. What an IPTV EPG actually contains
EPG stands for Electronic Programme Guide. In a typical IPTV setup, the player needs two kinds of information:
- Channel/playback data — the entries and stream URLs used to open Live TV.
- Guide data — programme titles, start/stop times, descriptions and the channel identity those programmes belong to.
XMLTV is one of the most common guide formats. Its basic model is simple: define a channel, then define programme entries whose channel attribute points back to that channel ID. If the player's live-channel identity does not match the XMLTV identity, the player has schedule data but does not know where to display it.
This is why reinstalling a player is often wasted effort when Live TV works but programme names are blank. First verify the guide source and mapping.
2. XMLTV anatomy: the three identifiers that matter most
The playlist supplies a guide identity
The tvg-id is commonly used by IPTV players to match this playlist channel to the guide. The example domain is intentionally non-routable.
The XMLTV channel ID needs to line up
If the channel ID and playlist tvg-id disagree, programme data may exist but never attach to the live channel.
Kodi IPTV Simple documents the same relationship explicitly: it first tries to match the XMLTV channel ID to the M3U tvg-id, then can fall back to name-based matching. Jellyfin exposes the relationship through its manual “Map Channels” workflow.
EPG channel-ID mapping checker
Paste only channel identifiers—not playlist URLs or credentials. This runs entirely in your browser and simply compares the two values.
3. IPTV EPG Guide: 9 fixes for missing, partial or wrong guide data
Prove that playback and EPG are separate symptoms
Open two or three live channels. If video plays but programme titles are missing, stop troubleshooting credentials and codecs. You have already proved the account can deliver streams; focus on the guide source, mapping, cache and time handling.
Refresh the guide before rebuilding the account
Use the player's EPG/guide refresh function first. Some apps fetch playlist data and EPG data on different schedules. A normal refresh preserves the login and categories while requesting fresh programme listings.
Verify the guide source exists and is reachable
If your setup uses a separate XMLTV URL, confirm that it is still configured and authorized. A playlist can keep working after an EPG URL changes or expires. Do not paste a credential-bearing guide URL into public web tools just to test it.
Match M3U tvg-id to the XMLTV channel id
Compare one working channel and one missing channel. If the M3U says tvg-id="news.hd" but XMLTV uses id="news", many players will treat them as different channels. Correct mapping at the provider/player layer rather than applying a time shift.
Check renamed, duplicated and regional variants
HD, FHD, backup and regional versions often have nearly identical display names but different IDs. Name-only matching can attach the schedule to the wrong variant or leave one blank. Prefer stable IDs where the player and source support them.
Set the device time zone correctly before adding an EPG shift
Use automatic date/time and the correct regional time zone on the TV, streaming box or phone. A wrong device zone can move every listing by the same amount. Fix the device clock first; otherwise a manual EPG offset can hide the real problem.
Remove stale manual offsets after DST changes
A fixed +1 or -1 hour correction can appear correct in winter and become wrong after daylight-saving time changes. IANA maintains current time-zone/DST rules used by major operating systems. Prefer the correct regional time zone over a permanent manual correction whenever possible.
Clear the EPG cache only when refresh still shows old data
Guide caching improves load time, but it can preserve stale listings. If the provider confirms the guide is updated and a normal refresh does not change the player, clear the guide/EPG cache or database for that app if the platform exposes the option. Avoid clearing all app data unless necessary.
Test the same guide/account in another compatible player
If possible, compare one known channel in another player that supports the same authorized source. If the same channel is missing there too, provider-side guide coverage/mapping becomes more likely. If it works elsewhere, investigate the first player's mapping, cache or time settings.
4. EPG is present but one or two hours wrong: diagnose time before data
A guide that is consistently wrong by an exact number of hours is different from a guide with missing programmes. The data is usually present; the timestamp is being interpreted or shifted incorrectly somewhere between the XMLTV source and the screen.
| Symptom | Most useful first check | Avoid doing first |
|---|---|---|
| Every channel is +1 hour | Device time zone, automatic clock, player EPG offset. | Reinstalling the app or editing channel IDs. |
| Guide became wrong after clock change | Remove old manual shift; refresh after confirming regional time zone. | Adding a second offset on top of the first. |
| Only one country's channels are offset | Check whether that source uses a different regional time zone. | Applying a global shift to every channel. |
| Only one channel is offset | Provider guide entry or channel-specific shift/mapping. | Changing the device's system time. |
XMLTV times can carry an explicit offset
The widely used XMLTV DTD supports programme start/stop timestamps with explicit time-zone information such as +0200. If no explicit zone is provided in the classic XMLTV format, UTC is assumed by the DTD. The player then has to display that timestamp in the viewer's local time correctly.
Do not use a global shift for a regional subset problem
Kodi IPTV Simple supports both a global EPG time shift and per-channel tvg-shift values. That flexibility is useful, but it also makes it possible to “fix” one group while breaking another. Use the smallest scope that matches the actual problem.
If every listing is exactly one hour late, write that down. Then check device zone, DST and existing EPG shifts in that order. Random offsets can hide which layer was wrong.
5. Why only some IPTV channels are missing EPG data
A partially populated guide is usually more informative than a completely blank one. It proves that the app can read at least some guide data. Focus on identity and coverage.
Working SD channel, blank HD channel
The HD variant may use a different tvg-id while the XMLTV source contains only the base channel. Compare both IDs before changing the EPG URL.
Channel was recently renamed
The playlist name changed but the guide ID did not—or vice versa. Stable IDs are more reliable than display-name matching when the source supports them.
Guide has no programmes for the channel
The XMLTV file can define a channel but contain no programme entries for the current date. That is upstream guide coverage, not a player cache problem.
Two playlist entries map to one guide ID
The schedule may appear on one duplicate while the other stays blank or shows confusing data. Inspect variants, group names and stable identifiers.
Jellyfin makes this mapping relationship visible
Jellyfin's current Live TV setup separates an M3U tuner from the XMLTV guide provider and includes a Map Channels step. That is a useful mental model even if you use another player: live channels and guide channels are separate datasets that must be paired correctly.
6. Refresh intervals, stale listings and EPG cache
Players cache guide data because a multi-day XMLTV file can be large and expensive to parse repeatedly. Caching is useful until the cached data becomes older than the source.
Refresh first
Use the built-in guide refresh. Jellyfin automatically imports guide data after mapping and also exposes manual guide refresh when needed. Kodi IPTV Simple can cache XMLTV locally and has a specific guide-cache clear function for configuration changes.
Clear guide cache second
If the source has changed but the display has not, clear only the EPG/guide cache where the application offers that control. This preserves playlists, favorites and account details more safely than deleting all application storage.
Re-add the source only when configuration itself is wrong
Deleting and re-adding the IPTV account should be later in the sequence. If the EPG URL, mapping or source configuration is wrong, rebuild that component intentionally. Do not use account deletion as a generic “refresh” button.
7. Is it the player, the EPG source or the provider mapping?
| Observed result | Most likely area to inspect | Why |
|---|---|---|
| Video works; guide blank in every compatible player | Guide source / provider mapping | The playback account works, but the same guide failure follows the source. |
| Guide works in player B but not player A | Player A config/cache/mapping behavior | The source contains usable data because another client can display it. |
| All channels have the same time offset | Device zone / global EPG shift | Mapping is probably working because programme rows exist. |
| Only specific channels are blank | Channel ID/name mapping or source coverage | A total EPG-source failure would affect more of the guide. |
| Yesterday's shows remain after refresh | Guide cache or stale upstream file | Compare source freshness and player cache before changing channel IDs. |
For Smarters-specific account and login setup, use the IPTV Smarters Pro Setup Guide. For M3U/tvg-id context, the M3U vs Xtream Codes guide explains playlist metadata and account formats. For region-specific time-zone behavior, the Scandinavian IPTV guide includes the practical CET/CEST versus EET/EEST distinction.
EPG symptom checker
Select the closest symptom. The tool does not access your playlist or guide; it simply gives you the next controlled checks.
8. What to send support when EPG still does not work
A useful EPG support report is small and specific. Do not send a giant playlist file or expose credentials when one channel example will demonstrate the problem.
One working + one failing channel
Give the display names and, where safe, the tvg-id values. That makes comparison much easier.
Exact time error
Say “guide is exactly +1 hour” instead of “times are wrong,” and include your device time zone.
Player + version + device
Different clients match XMLTV channels and cache guide data differently.
Refresh/cache result
State whether a guide refresh or EPG-cache clear changed anything.
Cross-player result
If the same guide works in a second compatible player, say so—it narrows the fault quickly.
Passwords or credential-bearing URLs
Send only what support genuinely needs and use the provider's official secure channel.
If you use EagleCast TV and the guide remains missing or incorrectly mapped after these checks, use the official support page and include the smallest reproducible example.
Technical references used in this guide
Frequently asked questions about IPTV EPG data
These answers focus on the problems that change the diagnosis: blank guide, tvg-id mapping, exact time offsets, stale cache, separate XMLTV sources and partial channel coverage.
What is an IPTV EPG?+
EPG stands for Electronic Programme Guide. It is schedule metadata that tells a compatible player what programme is on a channel now and what comes next. In many IPTV setups the video playlist and the guide are separate data sources. XMLTV is a common guide format: it defines channels and programme entries with start times, stop times, titles and channel references.
Why do IPTV channels work but the EPG is blank?+
Because playback and guide data are separate layers. The playlist can load and video can play while the XMLTV/EPG source is missing, unreachable, stale or not mapped to the playlist channels. Refresh the guide separately, verify the EPG source, then check whether each playlist tvg-id matches a guide channel id.
What is tvg-id and why does it matter?+
tvg-id is commonly used in an M3U channel entry as the identifier used to map that channel to XMLTV guide data. Kodi's IPTV Simple documentation states that tvg-id is matched against the XMLTV channel id first. If the IDs do not match, a player may try weaker name-based matching or may show no guide at all.
Why is my IPTV EPG exactly one or two hours wrong?+
A consistent whole-hour error usually points toward time-zone handling or an EPG shift rather than missing data. First set the device to the correct automatic time zone, then remove unnecessary manual offsets and refresh the guide. Only use an EPG shift when the guide source genuinely requires one. Daylight-saving changes can make a hard-coded offset wrong later.
Should I clear the EPG cache when listings are stale?+
Yes, but only after a normal guide refresh fails. Many players cache guide data to avoid downloading and parsing it every time the app opens. A stale cache can preserve old listings even after the provider updates the source. Clearing only the EPG/guide cache is preferable to deleting the entire app or account.
Can I use a separate XMLTV URL with an M3U playlist?+
Yes when the player supports a separate guide source. Jellyfin, for example, supports an M3U tuner and a separate XMLTV TV Guide Data Provider, then maps guide channels to tuner channels. Kodi IPTV Simple likewise supports a separate XMLTV path/URL and channel matching through tvg-id and names.
Why are only some channels missing guide data?+
Partial EPG usually points to mapping or source coverage rather than a total EPG failure. Compare the playlist tvg-id for a working channel and a missing channel against the XMLTV channel ids. Also check renamed HD/SD/region variants, duplicate channel names and whether the guide source actually contains programmes for that channel.
A reliable EPG fix starts by separating guide data from video playback.
If the stream plays, preserve that working layer. Refresh the guide, verify the XMLTV source, compare tvg-id with guide channel IDs, check variants, set the correct device time zone, remove unnecessary manual shifts and clear only the guide cache when data is stale. Cross-checking one channel in another compatible player then tells you whether the remaining issue is local configuration or upstream guide data.