A FAST channel without a valid EPG is invisible. Services like Pluto TV, Samsung TV Plus, LG Channels and The Roku Channel pull your schedule from a feed you provide, and XMLTV is the format most schedules start life in. Get it wrong and your channel does not appear in the guide. Here is the practical setup, with a complete sample file and every element explained.
What an EPG actually is
An Electronic Program Guide is a schedule of what is airing on your channel, when, with metadata like title, description, episode number, genre, rating, and length. Services use it to populate the channel guide and to power 'what's on next' surfaces.
XMLTV is the most common format for that schedule: an XML file that lists <channel> and <programme> entries, each airing with start and stop times and its own metadata. It is defined by a public DTD maintained by the XMLTV project.
How an XMLTV file is structured
An XMLTV file has one <tv> root. Inside it, each <channel> declares a station with an id, and each <programme> is one airing that points back to its channel through its channel attribute. That link between the two values is the thing that most often breaks.
A complete sample XMLTV feed
Here is a complete feed for one channel with three back-to-back programmes - a movie, a branded interstitial, and an episodic series. Note the contiguous start and stop times (no gaps), the explicit +0000 UTC offset on every timestamp, and the child elements in the order the DTD sets:
<?xml version="1.0" encoding="UTF-8"?>
<tv generator-info-name="OTTEngine Scheduler" source-info-name="OTTEngine">
<channel id="ottengine.action">
<display-name>OTT Action</display-name>
<icon src="https://cdn.ottengine.com/epg/ott-action.png" />
</channel>
<programme channel="ottengine.action" start="20260418000000 +0000" stop="20260418010000 +0000">
<title lang="en">Midnight Pursuit</title>
<desc lang="en">A detective races against the clock to stop a citywide heist.</desc>
<date>2019</date>
<category lang="en">Movie</category>
<length units="minutes">60</length>
<icon src="https://cdn.ottengine.com/epg/midnight-pursuit.png" />
<rating system="MPAA"><value>PG-13</value></rating>
</programme>
<programme channel="ottengine.action" start="20260418010000 +0000" stop="20260418010030 +0000">
<title lang="en">OTT Action Presents</title>
<desc lang="en">A 30-second branded promo - what's coming up this week on OTT Action.</desc>
<category lang="en">Interstitial</category>
<length units="seconds">30</length>
</programme>
<programme channel="ottengine.action" start="20260418010030 +0000" stop="20260418020030 +0000">
<title lang="en">Steel Horizon</title>
<sub-title lang="en">The Long Drop</sub-title>
<desc lang="en">The crew discovers the rig is hiding more than ore.</desc>
<category lang="en">Series</category>
<length units="minutes">60</length>
<episode-num system="xmltv_ns">0 . 3 . 0/1</episode-num>
<episode-num system="onscreen">S1 E4</episode-num>
<previously-shown />
<rating system="VCHIP"><value>TV-14</value></rating>
</programme>
</tv>
Paste this into our free XMLTV EPG Validator and it passes with one expected warning, because the example's dates are in the past. Then delete a timezone offset or a <title> and watch the errors light up. Everything runs in your browser; nothing is uploaded.
Every element, explained
The elements a FAST feed actually uses, with what the DTD requires and what services expect in practice:
| Element | Lives in | Required | What it holds |
|---|---|---|---|
<tv> | root | Yes | The whole file. Optional attributes name the source and the generator. |
<channel id> | <tv> | Yes | One station. The id is what every programme points back to. |
<display-name> | <channel> | Yes, one or more | The channel's name as the guide shows it. |
<icon src> | <channel> or <programme> | No | A logo or programme image URL. |
<programme start channel> | <tv> | Yes | One airing. start and channel are required by the DTD. |
stop (attribute) | <programme> | Optional in the DTD | Include it anyway: a guide needs to know when each airing ends. |
<title> | <programme> | Yes, one or more | The programme name. Add lang for each language. |
<sub-title> | <programme> | No | The episode title. |
<desc> | <programme> | No, but expected | The description viewers read in the guide. |
<date> | <programme> | No | The production or release date, for example 2019. |
<category> | <programme> | No, but expected | The genre. Repeat it for more than one. |
<length units> | <programme> | No | The running time, in seconds, minutes or hours. |
<episode-num system> | <programme> | No | xmltv_ns is zero-based season.episode.part, so 0 . 3 . 0/1 is season 1, episode 4. onscreen is the number as printed. |
<previously-shown> / <new> | <programme> | No | Empty flags for a repeat or a first airing. |
<rating system><value> | <programme> | No | A content rating and the scheme it belongs to, such as MPAA for films or VCHIP for US TV ratings. |
<image type> | <programme> | No | A newer element for posters, backdrops and stills. Fewer services read it than <icon>. |
Timestamps use YYYYMMDDhhmmss, a space, and a UTC offset, as in 20260418000000 +0000. When the offset is missing, the DTD says to assume UTC, which is why local times written without an offset show up in the guide hours out. Write every time in UTC with +0000, or in local time with the correct offset, and never mix the two in one feed.
What each FAST service ingests
Not every service takes XMLTV directly. Frequency, a FAST playout vendor, publishes the EPG format it delivers to each destination, and it is a useful picture of how varied they are:
| Service | EPG format Frequency delivers | Delivery |
|---|---|---|
| Plex | XMLTV | Pull |
| Tubi | XMLTV | Pull |
| Pluto TV | Frequency's custom format | Pull |
| The Roku Channel (US and Canada) | Roku True EPG | Pull |
| Samsung TV Plus | Frequency's standardized format | Pull |
| LG | LG's own format | Pull |
| VIZIO | VIZIO's own format | Pull |
| Xumo | Gracenote | Pull |
| Sling TV | Gracenote | Push |
Source: Frequency, EPG formats per distributor. Another vendor may deliver a different format to the same service, so treat this as a map of the variety, not a rulebook. The practical lesson: keep XMLTV as your source of truth and let your playout vendor convert it, and ask each service for its partner specification before launch - format, forward schedule depth, refresh cadence and image sizes. The major services do not publish theirs openly.
Schedule depth and refresh cadence
Every service expects a forward schedule, and each sets its own minimum depth in its partner specification. Get the number when you sign, keep more than that in the feed at all times, and alert when it runs short, because a feed that quietly runs out of schedule is one of the easiest ways to fall out of a guide.
Refresh the feed often enough that a schedule change reaches the guide before it airs. Hourly is a safe default, and a programming swap or a live cut-in should be in the very next refresh.
Handling gaps and filler
Every second of your 24-hour day should be covered by a <programme> entry, with each start equal to the previous stop. A gap shows up as a hole in the guide, and it is one of the first things a service's ingest check looks for. Use filler programmes - house promos, branded interstitials - to fill any space between scheduled content.
Filler programme entries should still have real titles and descriptions; 'Filler' or 'Promo' as a title looks unprofessional in the guide.
Stream alignment with EPG
The live stream has to match the schedule. If your EPG says 'Show A airs at 14:00 UTC' but the stream is showing minute 23 of Show A at that moment, the guide is misleading viewers and every 'watch from the start' link lands in the wrong place. Each service sets its own tolerance, so ask for it.
SCTE-35 markers in the stream, placed at programme boundaries and ad breaks, keep the stream, the ads and the schedule telling the same story. Our SCTE-35 decoder shows what your cues actually say.
Validate before you deliver
Validate every feed before a service sees it. Our free, browser-based XMLTV EPG Validator checks for exactly the problems above - missing timezone offsets, schedule gaps, orphaned channel IDs, reversed times, and forward-depth shortfalls - without uploading anything.
Then build the same checks into your scheduling pipeline, so a broken feed is caught before it ships, not after a service drops the channel from its guide.
Common reasons a feed is rejected
- Times in local time without an offset.
- Gaps between programmes.
- A forward schedule shorter than the service's minimum.
- A programme's
channelvalue that does not match any<channel id>. - Missing ratings on content that needs one.
- Programme entries that do not match the live stream.
- A channel ID that differs from the one in the service contract.
The bottom line
EPGs are mechanical but unforgiving - and they are the single most common reason FAST channels disappear from guides. OTTEngine publishes an XMLTV feed for each 24/7 channel you schedule, at a public URL a service can pull. Every plan from Studio up, at $79 a month, includes one channel, and each extra channel is $79 a month. The same schedule plays in your own apps too, whether that means Tizen OS app development, an LG webOS TV app or a channel from our Roku channel maker. Start a free trial to schedule your own channel end to end.
Frequently Asked Questions
What is XMLTV?
An open XML format for TV schedules: a <tv> root holding <channel> and <programme> elements. It is the most common way to hand an EPG to a FAST service, though some services take their own formats or Gracenote data instead.
What time format does XMLTV use?
YYYYMMDDhhmmss followed by a space and a UTC offset, for example 20260418000000 +0000. The XMLTV DTD assumes UTC when the offset is missing, so a local time written without one lands in the guide at the wrong hour.
How many days of forward schedule do I need?
Each service sets its own minimum in its partner specification, and the major services do not publish theirs openly. Ask for the number when you sign, keep more than that in the feed at all times, and alert when it runs short.
How often should I refresh my EPG feed?
Often enough that a schedule change reaches the guide before it airs. Hourly is a safe default, and a programming swap or a live cut-in should be in the very next refresh.
Can I have gaps in my schedule?
No. Every second of the 24-hour day should be covered by a programme entry, or the guide shows a hole. Fill the space between scheduled content with branded filler that has a real title and description.
Does every FAST service accept XMLTV?
No. Frequency, a FAST playout vendor, delivers XMLTV to Plex and Tubi, its own or service-specific formats to Pluto TV, The Roku Channel, Samsung TV Plus, LG and VIZIO, and Gracenote data to Xumo and Sling TV. Keep XMLTV as your source of truth and let your playout vendor convert it.
What is SCTE-35 and why does it matter for EPG?
SCTE-35 markers in the stream signal ad breaks and, with segmentation descriptors, programme boundaries. Keeping them in step with the published schedule means the stream, the ads and the guide agree on when a show starts.