iiPTV
Open player

Playlist workspace

M3U8 stream checker

Check IPTV and M3U8 URLs in your browser. Review response status, content type and timing, with uncertain requests kept separate from unavailable sources.

Your source

A new copy

Work in this tab

Add your source

Up to 5 MiB and 10,000 entries. For multiple files, the combined input is limited to 5 MiB and 20 files.

Files are processed in this tab. Remote imports and checks contact source hosts directly.

Checks request source hosts directly. A readable media response does not prove playback. CORS, timeouts and browser restrictions can leave a source unconfirmed.

Updated

The iiPTV stream checker tests whether a media address returns a response your browser can inspect. Paste individual URLs or import a playlist, then review each result before opening a stream. A successful request is useful evidence, but it is not a guarantee that every video segment, audio track or device will work.

Use this stream checker when a channel fails to start, a provider changes an address, or you want to compare several authorized sources. It separates readable responses from failures and uncertain browser restrictions, helping you choose a sensible next step without uploading your playlist to iiPTV.

On this page: start a check, read results, try a comparison, understand limits, protect sources, and questions.

Start a stream checker comparison

Enter one complete HTTP or HTTPS address per line, or select a supported playlist file. The stream checker combines the entries and avoids repeating a probe for the same address. Review the input count first: a short sample is easier to interpret than a large list from several unrelated hosts.

Start the check deliberately. Requests travel from your browser to the selected source, so that host can observe your connection just as it can during playback. The stream checker does not route media through an iiPTV relay, bypass a login, renew subscription tokens or change the remote server's policy.

For a readable HLS manifest, the HLS analyzer explains declared qualities and tracks.

Read stream checker results carefully

Readable success and HTTP failure

A readable success means the request returned usable information for this check. The stream checker can inspect HLS text when available; a direct media response is a different kind of evidence. Neither proves that your environment can decode the complete stream or maintain continuous playback.

A visible HTTP error gives a more specific starting point. A 404 indicates the requested resource was not found in that response. A 401 or 403 can involve authentication, authorization or a host restriction. Keep the actual status with your notes instead of summarizing every stream checker failure as an offline channel.

Unknown is a meaningful result

An unreadable response, timeout or mixed-content restriction does not prove permanent loss. Cross-origin permissions can prevent JavaScript from reading a source that another application can access. The stream checker reports uncertainty so you can check the publisher's documentation or compare in an authorized native player.

Use a small stream checker example

Suppose a playlist contains three entries: two point to the same HLS address, and a third points to a different MP4 resource. The stream checker should need two unique probes. This comparison distinguishes repeated catalogue entries from separate network destinations; it does not decide which channel name or group you should keep.

For a synthetic input, use https://example.com/live/master.m3u8 as a format example, not a working television channel. Replace it with an address you are authorized to inspect. Never assume that an example URL displayed in documentation has a live feed behind it.

If the first address answers and the second returns 404, compare the stream checker results with the original source record. A mistyped path, changed extension or expired signed link can explain a single failure. If many addresses share one host and all become unreadable together, investigate that common host before removing channels individually.

Know what the stream checker measures

Response time describes this request from this connection at this moment. The stream checker is not a bandwidth benchmark, global availability monitor or video-quality measurement service. A quick manifest response can still lead to slow segments, and a distant source can respond slowly while remaining usable.

Imports are limited to 5 MiB and 10,000 entries. Network probes use bounded concurrency, with at most three active requests, and read a limited response sample rather than downloading a full media file. The stream checker therefore gives a practical browser check without pretending to validate an entire broadcast.

HLS may reference additional manifests, segments and keys. Those resources can have different availability or permissions. See the playback troubleshooting guide when an address responds but the picture does not start. A stream checker cannot add a missing codec, transcode video or unlock protected content.

Protect source details during a stream checker session

Files and pasted entries are processed in browser memory. The stream checker contacts the requested source directly when you start a check; ordinary website analytics and preference handling are separate from playlist processing. Read the Privacy Policy for those boundaries rather than assuming that local file parsing means the page makes no network requests.

Treat signed links and credential-bearing paths as sensitive. Before sharing a screenshot, remove usernames, passwords, tokens and private addresses from results. A stream checker report sent to support should contain the browser version, visible status and a harmless reproducible sample whenever possible, not your complete subscription playlist.

Stream checker questions

Can a stream checker confirm picture quality?

No. It checks response evidence and readable metadata. Resolution labels and advertised bitrate describe the publisher's declarations, not an independent assessment of sharpness or buffering. Use the browser player for an actual supported-media comparison, press Play yourself and watch whether playback advances.

Why does a stream checker differ from another app?

A native app can have different codecs, request headers and cross-origin behavior. Your stream checker result applies to the browser environment used for the check. MDN's CORS explanation describes why readable access depends on the remote origin's permission.

Should I delete every failed entry?

Review the cause and repeat a small comparison first. The playlist cleaner is better suited to reviewing a full list and deliberately exporting the entries you choose to retain. Keep a backup so a temporary restriction does not become an irreversible catalogue edit.