What the checker looks for
An XMLTV guide has three failure modes: no data (empty files, stale files whose listings ended yesterday), bad data (timestamps without timezone offsets — the classic cause of a guide shifted by exactly N hours — missing titles, programmes that end before they start), and a broken join (channels declared with no programmes, or programmes pointing at channel IDs the file never declares — which is why some channels show listings and others sit empty). The checker reports each explicitly, so your note to a provider can say “1,912 of 3,240 declared channels have no programme data” instead of “guide doesn't work.”
If the guide checks out but your player still shows nothing, the fault is on the playlist side of the join — work through the EPG repair guide. And if you're wondering what a good setup looks like end to end, start at adding an M3U playlist or the Xtream login guide.
This page is static. Checks run in your browser; URLs you fetch are contacted directly by your browser, files and pasted XML never leave your device, and we run no analytics of any kind — same policy as the app.
Questions that come up
Why did fetching my URL fail when the URL works in my player?
Two browser rules get in the way. First, mixed content: browsers block http:// fetches from an https page like this one, and most EPG URLs are plain http. Second, CORS: a web page may not read another server's response unless that server opts in, and EPG servers rarely do. Players aren't web pages, so neither rule applies to them. Use the file picker or paste path here — same data, no network rules in the way.
Is anything uploaded?
No. There is no server component at all — view the page source and you'll find the whole checker inside it. Paste and file checks work with the network cable out.
Handles .gz files?
Yes, in modern browsers, on-device. If yours can't, unzip the file first and pick the .xml.
What faults does the EPG checker detect?
Invalid XML, empty guides, channels declared with no programme data, programmes pointing at undeclared channels, timestamps missing timezone offsets (the classic cause of a shifted guide), stale data entirely in the past, missing titles, and negative-length programmes — plus the guide's real forward depth in hours.
How big a file can it take?
Tens of megabytes is fine; very large national guides may take a few seconds to parse on a phone. Above roughly 150 MB, browsers get memory-shy — trim the source or use a desktop.