The download is a player: an app that reads a playlist and renders video. It ships with no channels inside it. A typical Android player package runs 60-100 MB, one widely mirrored build is 98.89 MB and needs Android 6.0 or newer, and installers ask for another 200-300 MB of temporary free space while they unpack. After install the app is inert until you give it a source: an M3U playlist link, or a portal login made of host, username and password. That source is your subscription, bought separately from the app. Mixing up the two is the most common reason a fresh install shows an empty channel list.

1. 1Player app: 60-100 MB, no channels inside it
2. 2Temporary install headroom: 200-300 MB
3. 3Source: an M3U link, or host plus username plus password

Order of preference: the device's own store, then the app maker's own site, then nothing else. Roku, Apple TV, Samsung and LG gate installs through their stores, so there is no file to fetch at all. Android TV and Fire TV allow sideloading, and that is where trouble starts, because mirror sites repackage installers and a repackaged build can carry adware. If you do sideload, use an HTTPS link; the Downloader utility fails on plain HTTP far more often. Fire TV has also begun flagging some third-party installs during 2026, so confirm your device still accepts the player before you pay for anything.

1. 1Store install first, developer domain second, mirrors last
2. 2HTTPS links fail less often than HTTP inside sideload tools
3. 3Check the device still permits the app before subscribing

The app is small; the streams are not. At 1080p a live channel runs roughly 5-8 Mbps and uses about 3 GB an hour. At 4K it is roughly 15-25 Mbps and about 7 GB an hour. HEVC carries the same picture at about half the bitrate of H.264, which matters most on a crowded home network. So the download is a one-time 100 MB event, and the planning number that counts is throughput: a household running three 4K streams wants headroom near 75 Mbps, not a bigger drive. Plans sized at 1-5 simultaneous connections let you decide that in advance rather than during a live game.

1. 11080p: about 5-8 Mbps, roughly 3 GB per hour
2. 24K: about 15-25 Mbps, roughly 7 GB per hour
3. 3HEVC: about half the bitrate of H.264 for the same picture

Mostly no, and this is where the word download misleads people. A live channel is sent as short segments of about six seconds each and is gone once played, so there is nothing to keep. VOD titles stream on demand from the server, which is why a catalog of 219,577+ titles occupies no space on your device. Some players can record a live stream to internal storage or a USB drive, which is a recording feature bounded by your own disk rather than a download feature. If the plan is a flight or a commute with no signal, a subscription of this kind is the wrong tool for that job.

1. 1Live arrives in roughly 6-second segments and is not stored
2. 2VOD streams on demand, so the catalog costs you no disk
3. 3Player recording is local capture, limited by your own storage

A parse error means the package is corrupt or built for the wrong processor architecture: clear the download cache, delete the partial file, and fetch it again over HTTPS. An app that installs but never opens is usually an architecture or Android-version mismatch. A player that opens but stalls on the channel list is a size problem, since player apps hold the whole list in memory and get unstable above roughly 18,000 visible channels, so hiding groups you never watch is a genuine fix. Some faults are not local at all: oversold server capacity buffers whatever you change on the device, which is why uptime is a fair question before you subscribe.