Open-source project
ngo5/IPTV avatar
ngo5/IPTV

ngo5/IPTV: a curated index of IPV4 and IPV6 TVBox live and on-demand sources

IPV4/IPV6 TVBOX 电视直播点播源收集

6,051 stars584 forksUnknownLicense varies

At a glance

What is it?
ngo5/IPTV is not a player and not a scraper. It is a hand-maintained README that points TVBox-style apps at third-party M3U playlists, VOD JSON endpoints and EPG feeds, with the working and dead entries both left visible.
Who is it for?
Adopt ngo5/IPTV if you already run TVBox, FongMi or a similar shell app and want a single page that lists IPV4 and IPV6 M3U playlists, VOD JSON endpoints and EPG URLs without hunting through Telegram channels. Skip it if you want a player, a self-hosted service or anything with an uptime guarantee: the repository ships no code for fetching or checking streams, and the README itself warns that many playlists are smooth only in specific regions.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 31 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on September 30, 2026, and from our analysis. They are not legal advice.

Editorial analysis

What ngo5/IPTV actually is: a README, not a program

The repository has four top-level entries: Instructions/, README.md, app/ and m3u/. The README is the product. It is a Chinese-language index of IPTV resources for TVBox-family applications, split into live sources (直播源), on-demand sources (点播源), EPG endpoints, and a long table of recommended players. The description line calls it "IPV4/IPV6 TVBOX 电视直播点播源收集", a collection of live and VOD sources.

That framing matters, because the commonest misunderstanding is that this is software you install and run. It is not. There is no server, no scheduler, no health checker in the repository. The value is curation: someone else has already gone through the ecosystem of public playlists and JSON endpoints, labelled each one IPV4 or IPV6, and marked whether it carries EPG data and channel logos. If you have ever spent an evening pasting M3U URLs from chat groups into a TV box and finding half of them dead, the appeal is obvious.

The audience is narrow and specific. You need a TVBox-style shell app (the README's own term is 空壳软件, "empty shell software") that accepts an external source URL. If your player only plays a file you hand it, this list gives you nothing but raw URLs to copy.

How the source tables are organised, and what the columns tell you

The live source table has five columns: name, address, type, EPG and logo. Type is either IPV4 or IPV6, which is the single most consequential field for a reader. An IPV6 playlist is useless on an ISP that has not deployed IPv6, and the README states plainly that many live sources are only smooth in particular regions, so a playlist that works in one city may stall in another.

EPG and logo are checkmarks or crosses. A cross in the EPG column means you get channel names without a programme guide; a cross in the logo column means no channel icons. The README notes that TVBOX itself shows neither logos nor a programme guide for live TV, while the 影视 (FongMi) apps do, so the column values only matter relative to your player.

Rows are struck through with Markdown strikethrough when a source is dead or withdrawn. In the live table, joevess, Ftindy and AKTV are struck through. In the VOD table, 肥猫, 摸鱼儿, zwc365 and OK猫开发 are struck through, and the OK影视 player entry is struck through with a note that the project deleted its repository and a fork exists at lystv/fmapp. Strikethrough is the only status signal in the whole document. Nothing records when a row was struck, and nothing is removed, so the table accumulates history rather than staying clean.

Installing nothing: wiring a VOD source and a live playlist into a shell app

There is no package to install. The README's recommended path is to pick a shell app from its 空壳软件 table, install that app, then paste a source URL into it. FongMi影视 is listed for Android TV and phone, TVBOX for Android TV, TVBox-Swift for macOS and iOS, TV-Multiplatform for Windows, macOS and Linux, and Kodi for all platforms.

The README advises entering a VOD source first, because the app will then fill in live sources automatically. One of the listed VOD endpoints is the qist project's jsm.json:

bash
https://raw.githubusercontent.com/qist/tvbox/refs/heads/master/jsm.json

Paste that into the app's configuration or source field. What you should see is the app populating a catalogue of on-demand content, and, per the README's advice, a set of live channels derived from the same configuration.

If you want live TV directly instead, the live table offers M3U playlists. The fanmingming entry is IPV6 and carries both EPG and logos:

bash
https://live.fanmingming.cn/tv/m3u/ipv6.m3u

Load it as an M3U playlist in your player. If your network has no IPv6 route, expect failures; switch to an IPV4 row such as the YanG-1989 gather playlist instead:

bash
https://tv.iill.top/m3u/Gather

For a programme guide, the README lists 112114 and its mirror, plus ERW:

bash
https://epg.112114.xyz/pp.xml
https://e.erw.cc/e.xml

Point your app's EPG field at one of those XMLTV URLs. The README adds that if 112114 does not open, try the fanmingming mirror at https://live.fanmingming.com/e.xml. To check whether a playlist's streams are actually alive, the README points at a separate project, zhimin-dev/iptv-checker, rather than offering any checking of its own.

The failure modes the README admits to, and the ones it does not

The README is unusually candid in places. It says VOD sources fail easily and get reported by users, and advises following the original publisher's address rather than a mirror. It warns that paid sources cannot be trusted, on the reasoning that the sellers are not rights holders. It notes that TiviMate cannot scan a QR code to import a source and that automatic source and EPG updates require a paid tier, that Kodi needs a manual language change and a VPN to install its IPTV add-on, and that TiviMate, Kodi and the iOS apps are live-only, with no VOD.

What it does not give you is any way to verify freshness. There is no timestamp per row, no changelog, no automated check. A row's presence means only that the maintainer has not struck it through yet. Several rows in both tables are already struck through, which tells you the list is maintained by hand and that removals lag reality.

There is also a legal and ethical dimension the README does not address. The sources are third-party streams of television channels, and the README's own warning about paid sources being untrustworthy implies the maintainer is aware of the provenance problem without resolving it. If you need content you are licensed to redistribute, or you are deploying for an organisation, this is the wrong tool entirely: it aggregates public endpoints of unknown origin, and the repository carries no licence file, so there is no stated grant of rights over the compilation itself.

How it differs from Guovin/iptv-api and other generating projects

The nearest real alternative is Guovin/iptv-api, which appears in ngo5/IPTV's own live table twice, once for IPV6 and once for IPV4 output. The difference in approach is fundamental. Guovin/iptv-api is a program: it collects candidate streams and produces result playlists as build output, which is why the URLs point at an output/ path on a branch. It does work on your behalf.

ngo5/IPTV does no work. It links to Guovin's generated output alongside a dozen hand-listed playlists from other maintainers, and lets you choose. That means ngo5/IPTV can include sources Guovin would never generate, and it can also include sources Guovin's pipeline would have filtered out as dead. There is no quality gate here beyond the maintainer's judgement.

A second comparison is the checker the README recommends, zhimin-dev/iptv-checker. That tool tests whether streams respond. ngo5/IPTV does not test anything. If you want a list that is continuously validated, you want a generator plus a checker, not this index. If you want breadth and the ability to see what other people are publishing, the index wins, because a generator only ever shows you its own output.

Maintenance cost, upgrade path and licence position

The last push to the repository was on 2026-08-31, which is recent enough that the index is being touched, but the releases tell a different story: the most recent listed release is 影视(FongMi)2.7.0 from 2024-12-22, followed by 海阔视界8.43 and 影视仓5.0.30, both from mid-2024. Those release entries are for third-party applications referenced by the README, not for software produced by this repository, so they say nothing about this project's own cadence. There is no versioned artifact here to upgrade.

Upgrading therefore means re-reading the README and re-copying URLs. If you have hardcoded a playlist URL into a device, you get whatever that upstream maintainer publishes; if they stop, your device keeps pointing at a dead endpoint until you notice. The README's advice to follow original publishers is the closest thing to an upgrade policy it offers.

The licence is not stated in the repository metadata, and no licence file is listed among the top-level entries. Without a stated licence, the compilation has no explicit terms, and the streams it links to are governed by whatever their publishers say, which the README does not document. Treat the list as a pointer, not as a distribution you can relicense.

Editorial conclusion

Adopt ngo5/IPTV if you already run TVBox, FongMi or a similar shell app and want a single page that lists IPV4 and IPV6 M3U playlists, VOD JSON endpoints and EPG URLs without hunting through Telegram channels. Skip it if you want a player, a self-hosted service or anything with an uptime guarantee: the repository ships no code for fetching or checking streams, and the README itself warns that many playlists are smooth only in specific regions. Before relying on it, open the raw README, confirm which rows are struck through, and run the listed playlists through iptv-checker on your own network, because the only quality signal this project offers is the maintainer's manual edit history.

Frequently asked questions

Is ngo5/IPTV an app I install, or just a list?

It is a list. The repository contains Instructions/, README.md, app/ and m3u/, and the README is the deliverable: tables of live M3U playlists, VOD JSON endpoints, EPG URLs and recommended player apps. You install one of the players it recommends and paste a source URL into it.

Should I pick an IPV4 or an IPV6 source from ngo5/IPTV?

It depends on your network. The live table labels every row as IPV4 or IPV6, and the README notes that many live sources are only smooth in specific regions. If your connection has no IPv6 route, use an IPV4 row such as the YanG-1989 gather playlist rather than an IPV6 one.

How do I know whether a source in ngo5/IPTV still works?

The repository gives no automated check. Rows are struck through when they are dead or withdrawn, but nothing records when that happened. The README recommends a separate tool, zhimin-dev/iptv-checker, for testing whether streams are actually alive.

Official sources

  1. Issues
  2. ngo5/IPTV on GitHub
  3. README
  4. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/ngo5-iptv.svg)](https://hysenlabs.com/projects/ngo5-iptv)