A playlist repo, not a streaming service
iptv-org/iptv is easy to misunderstand if you only see the star count. It is not an app, a media server, or a paid IPTV service. It is a large repository of M3U playlist links for publicly available live TV streams, organized so they can be opened in players such as VLC or consumed by other tools.
That distinction matters. The repository does not host video files. It stores user-submitted stream URLs and generated playlist files. The README points users to a single all-channel playlist, plus split playlists by category, language, country, region, and other groupings. The companion projects around it handle channel metadata, EPG data, and API surfaces.
The practical reason it keeps trending is simple: it is one of the easiest ways to test IPTV players, media-center setups, stream validation tools, and public-channel discovery without building a channel database yourself. As of 2026-06, the repo has about 119,000 stars, more than 6,000 forks, and a very active issue flow.
How to use it
The main playlist URL is:
https://iptv-org.github.io/iptv/index.m3u
Paste that URL into a video player that supports live network streams, then open it. VLC is the example shown in the README, but the playlist is standard M3U, so many IPTV players and media-center tools can load it.
The full playlist is only one entry point. PLAYLISTS.md publishes grouped variants. You can choose playlists by category, language, country, region, subdivision, block, or source. That matters because the all-channel list is broad. A player, test harness, or household setup usually wants a narrower slice.
The project is split across several repos
The iptv repo is the playlist layer. It is not the only source of truth in the organization:
iptv-org/databasestores channel data. If a channel name, logo, language, or category is wrong, the README says to report it there.iptv-org/epgpublishes Electronic Program Guide data for many channels.iptv-org/apidocuments the API surface.iptv-org/awesome-iptvcollects related apps and IPTV resources.
That split is a strength and a source of confusion. If you file the wrong issue in the playlist repo, maintainers may redirect you. If you use the project programmatically, do not scrape the README and call it an API. Use the API repo or generated playlist files for the layer you actually need.
Contribution rules are stricter than the repo name suggests
The contribution guide is mostly about quality control. A stream link should be stable, direct, not already present, and tested in a normal player for at least a minute. Links that go through Xtream Codes servers are excluded because they fail quickly and create maintenance churn. Broken stream reports need a valid link that still appears in the playlist, and maintainers expect reporters to check whether a failure is just geo-blocking.
That is why the issue tracker is full of small “Add” and “Edit” tickets. The repo behaves more like a data-maintenance queue than a software tracker. Recent issues are mostly channel additions, edits, and removals. That is healthy for this kind of project, but it also means users should expect change. A playlist entry that works today can disappear, fail, or become geo-blocked later.
Legal boundary
The README’s legal section is unusually important here. It says the repo does not store video files and contains links to streams the maintainers believe were made publicly available by copyright holders. It also provides a copyright-claim issue template for removal requests.
That does not make every downstream use risk-free. If you embed these playlists into a product, redistribute a filtered copy, or present channels to users in a commercial context, you need your own review. The repo’s claim is narrower: it links to public stream URLs and will remove links through its process. It cannot remove the underlying video from the web, because the actual host is somewhere else.
For individual testing, VLC use, or open tooling, the boundary is clear enough. For anything public-facing, treat the playlist as input data that still needs policy and rights review.
Where it fits
Use iptv-org/iptv when you need:
- a ready-made M3U playlist for live public channels;
- playlist slices by language, country, or category;
- realistic stream data for IPTV player testing;
- a maintained issue workflow for reporting broken or missing streams;
- a companion ecosystem for EPG and API data.
Do not use it when you need guaranteed uptime, licensed commercial carriage, private channels, video-on-demand, or a support contract. The FAQ explicitly says the project does not plan to add VOD. It is a public-link index maintained by a community, not a broadcast provider.
Star growth
The sampled star curve shows a long-lived project with periodic attention spikes rather than a new launch. That fits the repo’s shape: it has existed since 2018, but it can reappear on trending when playlist demand, media-player testing, or public-stream discussions flare up. The June 14, 2026 morning report captured it at #9 with +46 stars over the prior Beijing-morning window.
Related
For another large curated index, see public-apis. If you are tracking what else entered the same morning report, read the daily digest and the weekly report.
FAQ
What is iptv-org/iptv? It is a GitHub repository of M3U playlist links for publicly available live TV streams. It is not a streaming app and does not host video files.
How do I open the playlist in VLC? Open VLC’s network stream dialog and paste https://iptv-org.github.io/iptv/index.m3u, or choose a narrower playlist from PLAYLISTS.md.
Does iptv-org include VOD? No. The FAQ says the project is not planning to include Video On Demand in the playlist.
Where does EPG data come from? EPG data is handled by the iptv-org/epg repository, not the playlist repo itself.
Can I add a channel? Yes, but the contribution guide asks you to provide a stable direct stream link, verify it in a player, make sure it is not already present, avoid Xtream Codes links, and use the correct channel ID.
Is iptv-org/iptv legal to use? The repo says it only links to publicly available streams and does not store video. That is not a blanket legal answer for every downstream use. Public products and commercial uses need their own rights review.