What is IPTV?

How IPTV works

You buy a subscription from an IPTV provider. The provider hands you one of two things: an M3U playlist — a plain-text file listing every channel and its stream URL — or an Xtream Codes login, which is a server address, a username, and a password. Either one is enough for a player to build your channel list.

When you pick a channel, the player opens the stream URL and bytes start flowing — usually packaged as MPEG-TS, the same container broadcast television uses. The player unpacks the stream, decodes the video and audio, and puts a picture on screen. A schedule of what’s on — the EPG — usually comes from the provider too, so the player can show a real TV guide.

IPTV is a delivery method, not a service in itself. The channels, the quality, and the terms all come from the provider you subscribe to; the player is just the thing that turns their streams into television.

What you need is short: a subscription, a player, and an ordinary connection. Live TV runs at a steady few megabits per second per stream, so any reasonable broadband handles it — and picture quality is decided by how the provider encodes the channel. A player can render the stream faithfully; it can’t add pixels the provider didn’t send.

In Twiga

Twiga plays the IPTV you already pay for, in a browser tab — no install. You point it at your provider with an M3U link or an Xtream login, and it ingests your channels, sealing each channel URL with a key only you hold.

The metadata gets the same care as the stream: your TV guide is fetched over Tor, and playlist refreshes go via the VPN exits — the same split every Twiga source gets.

From there the stream takes a different path than in most players: it routes through Twiga’s blind relay and leaves from a VPN exit, so your provider sees Twiga’s IP instead of your home IP — and the relay in the middle has no decoder, so it can’t read what passes through. Your browser does all the decoding itself.