M3U is fine for players but awkward for everything else. Converting to CSV lets you sort and bulk-edit a playlist in Excel or Google Sheets; converting to JSON gets it into an app or a database. Both convert cleanly back to M3U afterwards.
The input format is detected automatically, and you can override it if the guess is wrong.
Supported conversions
- M3U / M3U8 → JSON or CSV
- JSON → M3U or CSV
- CSV → M3U or JSON
- Plain lists of URLs are accepted as M3U input
How the formats map
- Every channel carries the same five fields: name, url, group, logo and epgId
- JSON output is an array of objects, one per channel
- CSV output follows RFC 4180, so names containing commas or quotes survive a round trip through a spreadsheet
- CSV input also accepts the M3U attribute names (tvg-name, group-title, tvg-logo, tvg-id) as column headers