database
A collaborative, community-maintained CSV-based database of TV channels designed for IPTV applications. Data is stored in simple spreadsheet-compatible files and exposed via an API, making it accessible for both manual editing and programmatic consumption.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | iptv-org/database |
| Owner | iptv-org |
| Primary language | JavaScript |
| License | Unlicense — OSI-approved |
| Stars | 1.5k |
| Forks | 578 |
| Open issues | 223 |
| Latest release | Unknown |
| Last updated | 2026-07-08 |
| Source | https://github.com/iptv-org/database |
What database is
JavaScript-based project that manages TV channel metadata in CSV format within a /data folder, with CI/CD automation (update workflow) and API layer provided by the separate iptv-org/api repository. All data is public and version-controlled via Git.
Get the database source
Clone the repository and explore it locally.
git clone https://github.com/iptv-org/database.gitcd database# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Data validation and schema enforcement are the responsibility of consumers; no formal schema definition or type validation is embedded in the repository.
- Channel URLs and metadata can become stale; plan for periodic reconciliation, health checks, and user-reported corrections workflows.
- CSV format is simple but lacks native support for nested or complex relationships; consider transformation to a normalized database on ingestion.
- The separate API repository (iptv-org/api) is the canonical integration point; direct CSV consumption requires manual sync and parsing.
- 223 open issues suggest active discussion but potential backlog; review issue tracker for known data quality or coverage gaps relevant to your region/channels.
When to avoid it — and what to weigh
- Proprietary or Licensed Content Requirement — If your application requires exclusive, commercially licensed channel data or DRM-protected metadata, this crowdsourced model may not align with rights management needs.
- Real-Time Guarantee SLAs — Channel URLs, availability, and metadata depend on community maintenance; no formal SLA or guarantee exists that data is current or error-free at any given moment.
- Closed or Privacy-Sensitive Deployments — All data is public under Unlicense; unsuitable for internal-only or privacy-critical applications where openness conflicts with governance.
- High-Volume Transactional Backend — CSV files are not designed for ACID transactions or concurrent write-heavy workloads; better suited for read-heavy reference data than operational databases.
License & commercial use
Licensed under The Unlicense, which places all data and code in the public domain with no restrictions. Anyone may use, modify, or distribute for any purpose without attribution or permission.
The Unlicense explicitly permits commercial use without restriction or attribution. However, verify that channel metadata and URLs themselves do not infringe third-party intellectual property rights; the license covers only the database structure and compilation, not the underlying broadcast or content rights.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
All data is public and user-editable via pull requests, creating potential for malicious or incorrect URLs, channel impersonation, or typosquatting. Implement client-side validation, sanitization, and user feedback mechanisms before displaying URLs. No authentication or rate-limiting info provided; review iptv-org/api documentation for API-level protections.
Alternatives to consider
Gracenote or TVmaze APIs
Commercial metadata services with guaranteed data quality, real-time updates, and legal indemnity; suitable if licensing budget exists and proprietary data rights are required.
In-house curated database
Full control over data, validation, and SLAs; eliminates dependency on community maintenance but requires dedicated team and ongoing channel verification.
XMLTV or m3u aggregators
Alternative crowdsourced formats for IPTV playlists and EPG; may offer different community or geographic coverage, but similar quality variability and maintenance constraints.
Build on database with DEV.co software developers
Evaluate iptv-org/database for your IPTV platform. Confirm data quality, freshness, and copyright compliance for your use case before production integration.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
database FAQ
Can I use this data commercially?
How often is the data updated?
Can I contribute or correct channel data?
Is there a formal schema or data validation?
Custom software development services
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If database is part of your open-source databases roadmap, our team can implement, customize, migrate, and maintain it.
Ready to build on crowdsourced channel data?
Evaluate iptv-org/database for your IPTV platform. Confirm data quality, freshness, and copyright compliance for your use case before production integration.