IPTV Dead Stream Checker

Run browser-based reachability checks for authorized URLs, review elapsed time, and remove entries that time out.

Why use a local M3U stream validator?

A selected playlist file is parsed in browser memory, then the checker contacts each unique URL directly from your device. This avoids uploading the playlist to an M3U Studio checking server, but it does not make the network test private from the destination host. That host may receive your IP address and request headers.

Key Features of the Stream Tester

  • Elapsed-time hints: Measure how long the browser fetch takes to resolve or time out.
  • Configurable Concurrency: Speed up validation with parallel requests.
  • One-Click Cleaning: Clean all dead feeds from your playlist with a single action.
Interactive Tool Workspace

How to interpret a result

An online or slow label means the browser request resolved before the configured timeout. With mode: no-cors, the response can be opaque: M3U Studio cannot read its HTTP status, authenticate the media, inspect an HLS manifest, verify codecs, or confirm that later segments will play. A dead result can also be caused by a browser policy, mixed-content blocking, a temporary network error, rate limiting, or a host that rejects browser requests.

Safer testing workflow

  1. Keep the original file.
  2. Start with low concurrency to avoid sending a burst of requests.
  3. Test only URLs you are authorized to access.
  4. Confirm questionable results in the intended player and network.
  5. Export a cleaned copy instead of overwriting the source.

For syntax problems rather than network reachability, use the M3U validation guide. For file anatomy, see M3U file structure.