Fix Missing EPG & Optimize XMLTV Data: tvg-id Matching, Gzip Compression, & Multi-Source Merging (2026)

[PTIPTV]

 

Fix Missing EPG & Optimize XMLTV Data: tvg-id Matching, Gzip Compression, & Multi-Source Merging (2026)

A fully functional Electronic Program Guide (EPG) is what turns a raw stream playlist into a polished, cable-like interface. However, missing program grids, blank "No Information" tags, and slow database updating across players like TiviMate, OTT Navigator, and Enigma2 are frequently caused by tvg-id attribute mismatches, uncompressed raw XML payloads, or incorrect UTC time offset tags.

This technical guide breaks down the architecture of the XMLTV standard, demonstrates how to fix identifier mismatches, optimizes update speeds using Gzip compression (.xml.gz), and explains how to merge multiple EPG feeds into a single optimized URL.

 

 

EPG Data Delivery Methods Comparison

Delivery Format	Network Bandwidth	Parsing Hardware Impact	Auto-Refresh Speed	Primary Use Case
Uncompressed .xml	High Payload (20MB–100MB+)	Low CPU usage during parse	Slow download / High network load	Internal LAN / Server-side parsing
Gzip Compressed .xml.gz	Ultra-Low Payload (2MB–10MB)	Moderate CPU spike (Instant RAM unzip)	Fast download / Instant fetch	Android TV, TV Sticks, Remote EPGs
Xtream API JSON Direct	Medium Payload	Low CPU / Incremental database	Fast background polling	Xtream Codes / XUI One Portals

 

1. The Root Cause of Missing EPG: tvg-id vs id Matching

When an IPTV player attempts to render guide data for a channel, it performs a strict string comparison between the channel's tvg-id parameter in your M3U playlist and the <channel id="..."> tag inside the XMLTV feed.

Structure Breakdown:

In M3U Playlist:

Extrait de code

#EXTINF:-1 tvg-id="BeIN_Sports_1_Premium.qatar" tvg-name="beIN Sports 1 HD" group-title="Sports",beIN Sports 1 HD
http://your-server.com:8080/live/user/pass/101.m3u8

 

In XMLTV Feed (epg.xml😞

XML

<tv generator-info-name="CustomEPG">
  <channel id="BeIN_Sports_1_Premium.qatar">
    <display-name lang="ar">beIN Sports 1 HD</display-name>
    <icon src="http://your-server.com/picons/bein1.png"/>
  </channel>
  
  <programme start="20260805200000 +0000" stop="20260805220000 +0000" channel="BeIN_Sports_1_Premium.qatar">
    <title lang="ar">Champions League Match</title>
    <desc lang="ar">Live broadcast of the match.</desc>
  </programme>
</tv>

 

Key Rule: If tvg-id in the M3U (BeIN_Sports_1_Premium.qatar) does not match the channel id in the XMLTV file character-for-character (including case sensitivity), the player will leave the program grid empty.

2. Optimizing Download Performance with .xml.gz Compression

Fetching raw, uncompressed 50MB XML files every 24 hours places heavy bandwidth loads on your server and causes TV stick apps (like Firestick 4K or Chromecast) to time out during background updates.

Enabling Gzip Compression on Web Server (Nginx):

If hosting a custom XMLTV guide, enable Nginx static Gzip compression to reduce the transfer payload by up to 90%:

Nginx

# Add to /etc/nginx/conf.d/epg.conf
location ~* \.(xml|xml\.gz)$ {
    root /var/www/epg/;
    gzip_static on;
    gzip_types application/xml text/xml;
    add_header Content-Encoding gzip;
    expires 12h;
    add_header Cache-Control "public, no-transform";
}

 

When providing an EPG URL to clients, always prefer supplying [http://domain.com/epg.xml.gz](http://domain.com/epg.xml.gz) instead of raw .xml.

 

3. Merging Multiple EPG Sources & Fixing Time Offsets

If your main provider fails to supply guide data for international or niche channels, you can stack external EPG feeds (such as iptv-org/epg or custom XMLTV endpoints).

A. Assigning Multiple EPG Sources in TiviMate:

1. Navigate to Settings > EPG > EPG Sources.

2. Click Add Source and insert your secondary XMLTV URL (.xml.gz).

3. Go to Playlists > [Your Playlist] > EPG Sources.

4. Enable both Primary and Secondary EPG sources.

5. In the Channel Guide, long-press a channel with missing guide data $\rightarrow$ Select Assign EPG $\rightarrow$ Search and bind the matching channel manually.

B. Correcting Timezone Offset Issues (e.g., Guide is 2 Hours Ahead):

XMLTV timestamps use ISO 8601 formatting with UTC offset tags (e.g., 20260805200000 +0000). If your local guide shows programs shifted by a few hours:

• Open your IPTV Player's EPG Settings.

• Adjust Time Shift / EPG Offset to match your local timezone offset (e.g., -2.0 hours or +1.0 hour).

 

4. Troubleshooting Common EPG Errors

Error 1: "XML Parsing Error: Unclosed Tag"

• Cause: A corrupted server-side script generated an incomplete XML file (e.g., missing </programme> or </tv> closing tag at the end of the file).

• Fix: Validate the XML file using an online XML validator or parse tool (xmllint --noout epg.xml).

Error 2: EPG Loads Initially, Then Disappears

• Cause: Storage limit reached on budget TV streaming hardware (e.g., 8GB storage filling up with cached EPG databases).

• Fix: In player settings (e.g., TiviMate), set EPG Retention Days from 7 days down to 2 days or 1 day, and clear app cache regularly.

 

Frequently Asked Questions (FAQ)

Q1: Can I use one XMLTV EPG link for multiple separate M3U playlists?

A: Yes. As long as the tvg-id tags across different M3U playlists match the unique channel IDs in that central XMLTV file, a single EPG source can populate multiple playlists simultaneously.

Q2: Why does my Xtream Codes connection load EPG automatically without an XMLTV URL?

A: Xtream API handles EPG mapping directly through its database panel using JSON endpoints (/xmltv.php?username=...&password=...), bypassing the need to enter external XML URLs manually.

Q3: How often should IPTV players refresh EPG data in the background?

A: Setting updates to every 12 to 24 hours is optimal. Refreshing every hour wastes server bandwidth and can result in temporary IP rate-limiting from EPG provider hosts.