Disclosure: I work with TurboTV, an IPTV subscription service in the USA. This post is the technical explainer we give our own customers — no sales pitch, just how the moving parts fit together.
IPTV is just video delivered like web traffic
IPTV (Internet Protocol Television) sends TV channels over your internet connection instead of cable or satellite. Your app asks a server for a stream, the server sends video packets back, and the app decodes them. Almost everything else — channel lists, guides, logins — is bookkeeping around that one exchange.
The playlist: M3U and Xtream Codes
Your provider gives the app a map of what exists. The classic format is an M3U playlist: a text file listing stream URLs with names and groups. The alternative most apps prefer is the Xtream Codes API: you enter a username, password and server URL, and the app downloads the same map through an API — which is why a single wrong character (or a hidden space from copy-pasting) breaks the whole login. We compared the two formats here: https://turbotv.co/m3u-vs-xtream-codes/
The guide: EPG
The channel list says what you can watch; the EPG (Electronic Program Guide) says when. It is a separate data feed (usually XMLTV) that your app downloads and matches to channels by ID. When the guide is blank but channels play, the stream is fine — the guide feed, your device clock, or the match between the two is what failed.
Why buffering is usually local
A stream is a continuous flow of packets sized for your connection. If the flow stalls, look in order: the speed actually reaching the TV (not the plan you pay for), Wi-Fi interference, then the server. Our plain-English version of the full checklist: https://turbotv.co/what-is-iptv/ and the setup hub at https://turbotv.co/iptv-setup-guide/
Questions about any of the above — ask in the comments and I'll answer technically.


