Playlist workspace
M3U playlist merger
Combine M3U files in your chosen order. Optionally remove duplicate URLs or names, prefix source groups, and export one playlist with its metadata.
Your source
A new copy
Updated
The iiPTV playlist merger combines multiple M3U catalogues into one ordered file. Load the sources, choose whether repeated URLs or names should be removed, and review the resulting count before exporting. Optional source prefixes help distinguish groups that came from different inputs.
Use a playlist merger when you already have complete catalogues and want to retain their channel metadata. It is more reliable than copying entire files together, which can leave multiple headers and obscure where records came from. Merging changes the catalogue, not the availability or quality of the media it references.
On this page: load sources, choose matching, organize groups, follow an example, export safely, and questions.
Add sources to the playlist merger in order
Load files using the browser's File API, or paste two or more sources into separate inputs. Check that each one contains real channel records. A playlist merger cannot recover records that were absent from an incomplete download, nor can it turn a provider's HTML login page into a valid catalogue.
Arrange the sources deliberately before merging. When duplicate handling keeps the first matching record, the earlier catalogue supplies the surviving metadata. Put your preferred names and group labels first rather than assuming that the playlist merger will identify the best-maintained copy automatically.
Keep the originals somewhere you control. You may want to repeat the comparison with different matching options after reviewing a result. The playlist merger works with an in-memory copy and exports a new file; it does not synchronize changes back to the original publisher or overwrite local inputs.
Choose playlist merger duplicate rules
Match addresses when exact destinations matter
URL matching removes entries that point to the same exact address. It is a useful playlist merger option when several lists indexed the same source. Different signed URLs or alternate hosts remain different values, even when a person recognizes the same channel behind them.
Match names when labels are your criterion
Name matching compares catalogue labels rather than media identity. A playlist merger can therefore combine entries from separate hosts when their names match. Review regional, language and quality variants first: identical labels do not establish that the underlying programmes are interchangeable.
The URL and name options are separate choices in the playlist merger. Enabling broader matching can reduce the catalogue more aggressively. Inspect the resulting counts before exporting, and use the duplicate remover when you want a dedicated review of matching groups and retention choices.
Organize playlist merger source groups
The group-prefix option attaches the source number to group labels. This playlist merger setting helps when two providers both use a category such as News but you want to preserve their separate origins. A prefix is a catalogue label, not a claim about content ownership or quality.
Without prefixes, original group values stay with their retained records. News, NEWS and World News are not automatically equivalent. The playlist merger does not infer a common taxonomy. After export, the M3U editor can help you rename groups and arrange the surviving entries.
Check a playlist merger example
Suppose source one contains News One at address A and Sport One at address B. Source two contains the same address A under a longer title and another channel at address C. With exact URL removal enabled, the playlist merger keeps three records, including the first source's version of A.
With URL removal disabled, all four records remain. If only names are compared and the two A records have different names, they can both survive. This playlist merger example shows why the count depends on the selected rule rather than a hidden judgment about whether two streams look alike.
Addresses such as https://example.com/live/a.m3u8 are illustrative placeholders. Use your own authorized inputs for real work. A playlist merger does not test those addresses, refresh expired tokens or decide whether an alternative host will provide a working backup.
Review and export playlist merger results
The output is one extended-M3U catalogue with a single opening header and retained entries in the resulting order. The playlist merger carries channel metadata through its data model rather than preserving every byte of input formatting. Keep the originals if comments or uncommon custom conventions matter to another application.
Before downloading, compare the merged count and number removed with what you expected. A playlist merger result that is much smaller than anticipated deserves a second look, especially after name matching. Review a few entries from each source and confirm that useful backups or language variants remain distinguishable.
Inputs are bounded by iiPTV's 5 MiB and 10,000-entry import limits; combined work must stay within the supported dataset size. On-screen previews show a bounded subset for responsiveness. The playlist merger does not provide unlimited storage or a saved account library, so export useful work before refreshing the page.
Playlist merger questions
Does the playlist merger check which source is alive?
No. It combines records and applies matching rules. Use the stream checker for response evidence, or the playlist cleaner for a check-and-review pass. Unreadable cross-origin results should not be treated as proof of permanent failure.
Can I open the combined result immediately?
Yes. The player handoff transfers the accepted records once through browser memory. It does not place private addresses in an iiPTV navigation URL or save them persistently. Press Play and verify supported media separately from successful catalogue creation.
Is local merging the same as no network activity?
No. File transformations are local, while explicit remote imports, checking and playback contact their selected hosts. Ordinary page analytics and preferences are separate. The Privacy Policy explains these distinctions; never share a merged file publicly without reviewing its embedded credentials.