Playlist workspace
M3U playlist cleaner
Check entries in your M3U playlist and review unavailable responses before removal. Keep uncertain results, make explicit choices and export a cleaned copy.
Your source
A new copy
Updated
The iiPTV playlist cleaner checks the addresses in an imported catalogue and helps you remove the entries you choose. It keeps inspection and deletion separate: first review the results, then make an explicit change and export a new file. Your original local playlist remains your backup.
A playlist cleaner is useful when an older list has accumulated missing resources or when a small subset repeatedly fails. It cannot establish permanent availability from a single request. Browser restrictions, temporary congestion and expired credentials deserve different responses from a clearly missing resource.
On this page: prepare a check, interpret outcomes, choose removals, follow an example, save privately, and questions.
Prepare a playlist cleaner session
Import a supported M3U file or paste the catalogue text, then verify the channel count and group labels. The playlist cleaner needs actual records, not a webpage containing a download link. If import fails before any channels appear, use playlist loading help before investigating media availability.
Start with a small authorized sample when the source is unfamiliar. A playlist cleaner sends direct requests to the selected hosts when you ask it to check. Those hosts may enforce connection limits, rate limits, geography or subscription rules, so a large test can produce different responses from an isolated request.
The check uses at most three concurrent probes and bounded response reading. You can stop a running operation rather than waiting for every entry. The playlist cleaner should leave unchecked records identifiable, because a canceled or incomplete check is not evidence that the remaining channels failed.
Interpret playlist cleaner outcomes
Separate evidence from assumptions
A readable success means that the source returned evidence this browser could inspect. A visible HTTP error supplies a status for that particular request. The playlist cleaner does not equate either result with a permanent judgment about a broadcaster, provider or subscription.
An unreadable response can reflect CORS restrictions rather than a missing stream. Timeouts and mixed-content blocks also leave uncertainty. The playlist cleaner retains unknown entries by default, making uncertainty visible instead of silently deleting channels that might work in another authorized environment.
A native application can use different codecs and request behavior. Its successful playback does not prove the browser should read the same source. MDN's CORS guide explains the cross-origin boundary that applies to this playlist cleaner and other browser tools.
Make playlist cleaner removal decisions deliberately
Review the failed or unknown rows before applying a removal action. The playlist cleaner gives you a working copy to edit, not permission to assume every unsuccessful probe is a dead channel. A useful source may simply require a renewed URL from its publisher.
When several entries from one host fail together, inspect the shared cause first. A playlist cleaner cannot restore a subscription, alter a region restriction or persuade a server to accept a different connection policy. Repeating a large check immediately can make a rate-limiting problem harder to interpret.
Remove only the records that fit your decision, then compare the retained count with the original. The playlist cleaner is different from the duplicate remover: an address can answer successfully and still appear several times. Decide separately whether those duplicates are mistakes or intentional backups.
Read a playlist cleaner example
Imagine four channel records. Two return readable HLS manifests, one returns an observable 404 and one cannot be inspected because the host does not grant cross-origin access. A cautious playlist cleaner session removes the confirmed missing record only after review, while retaining the uncertain entry for another comparison.
The result contains three records, not two. This playlist cleaner example illustrates why an unknown category matters: treating every unreadable source as dead would discard an entry without the evidence needed to justify that conclusion.
For a single suspicious address, use the stream checker instead of rerunning the whole catalogue. If a manifest responds but playback still fails, the HLS analyzer can inspect its declarations. Neither replaces testing actual supported media in the browser player.
Protect a playlist cleaner working copy
Local catalogue parsing and editing happen in browser memory. The playlist cleaner does not save a personal library on iiPTV's servers, but explicit source checks still reach the selected origins. Ordinary page analytics and preference storage are separate; the Privacy Policy explains those boundaries.
Import limits are 5 MiB and 10,000 entries, with a bounded on-screen preview. The playlist cleaner processes the accepted dataset rather than assuming that only the visible rows exist. For larger catalogues, prepare meaningful smaller copies and keep enough context to reconcile the results later.
Export before refreshing or closing the tab. A playlist cleaner result can contain private credentials in stream paths or parameters even after unwanted entries are removed. Store it appropriately and redact screenshots before sharing them. Cleaning a list does not turn its remaining addresses into public information.
Playlist cleaner questions
Does a playlist cleaner measure video quality?
No. A response check does not watch the programme, measure sustained throughput or verify every audio and video codec. An entry with a readable manifest can still buffer later. Use playback help when the failure happens after a channel has imported successfully.
Can a playlist cleaner fix a changed address?
It cannot discover the publisher's replacement automatically. Obtain the correct address from the source and update it in the M3U editor. Do not guess URLs or remove meaningful credentials merely to make a string look simpler.
What does Open in Player transfer?
It transfers the current accepted records once through browser memory. It does not save the playlist in persistent storage or place private source URLs in iiPTV's navigation address. You still press Play and need a compatible, accessible source; export a copy if you want to retain the result.