Skip to main content

MRSS Feed Validator and HLS Playlist Inspector

Enter a feed URL, a live stream playlist URL, paste XML or playlist text, or upload a file. See recent videos, categories and tags, the last 30 days of publishing activity, and for an HLS stream the live window, the items in it, and every field the manifest carries. This checks the feed or playlist contents, not acceptance by a specific platform.

A feed URL and an .m3u8 playlist URL both work here; the response decides which inspector runs. A VideoNest channel URL such as https://videonest.co/live/<channel>/channel.m3u8 or https://<channel>.videonest.co/live/master.m3u8 also brings in that channel's schedule: the current title, each item's runtime, and what is coming next. VideoNest channel hosts are read directly, and other stream hosts are read when their policy allows it. Remote fetch stays limited to pre-approved public hosts plus VideoNest's own channel hosts, so this tool never becomes an open proxy. Any feed or playlist can be pasted or uploaded, which keeps the inspection fully in your browser.

Use this for any feed or playlist, including hosts outside the fetch allowlist. The text stays in your browser. Thumbnail requests may contact image hosts.

The file is read entirely in your browser as UTF-8. Nothing is uploaded.

What this snapshot shows

The inspector reads one feed, at one moment in time, and reports exactly what it contains. Field names, namespace URIs, durations, and dates are the observed values, not inferences.

Complete field inventory

Every element and attribute, including namespace-qualified and unknown extension fields, with counts. Counts cover the complete feed. Inventory samples are shortened for scanning; expand an item or view raw XML for full values.

Durations, by source

Media RSS media:content durations are seconds. Podcast itunes:duration is clock time. Alternative renditions are never summed.

Publishing cadence

Oldest and newest published dates among this snapshot's dated items, plus undated and future-dated counts. A single fetch measures this snapshot, not refresh frequency.

Warnings, not judgments

Malformed XML, missing expected fields, and coverage gaps are flagged as warnings. This tool never claims a feed is valid or will be accepted by a platform.

HLS playlist readings

An .m3u8 stream is read as a master playlist first, then its rendition playlist. The report lists the live window, the item boundaries, titles and cue markers inside it, the runtime observed for each item, the rendition ladder, and the exact tag inventory. A VideoNest channel URL is also read with its channel schedule, which adds the current title and the upcoming queue.

What a playlist cannot carry

A playlist carries no description and no list of upcoming items, and those panels say so explicitly instead of inventing values. A title is reported only from a field that really holds one: the #EXTINF title text, #EXT-X-SESSION-DATA, or a channel schedule endpoint. Every value in the report names the endpoint it came from.

Questions

Paste the feed URL, paste the raw XML, or upload the feed file. The inspector parses the feed in your browser and lists every field and attribute it finds, with item details, durations, and publishing cadence from a single snapshot.
It inventories channel and item fields, preserves namespace-qualified and unknown extension fields with their attributes, reports media:content and podcast durations, and summarizes published dates from the snapshot. It warns when XML is malformed or expected fields are missing.
No. This is a diagnostic snapshot of what is in a feed. It does not verify a feed against any platform's spec and gives no guarantee a platform will accept it. Coverage and duration figures describe this snapshot only.
Recent entries can load thumbnail images from hosts permitted by the page image policy; when a host is not permitted, the image is requested once more through this site's own image route, which fetches first-party thumbnail hosts only. The inspector does not play video or execute feed markup. Other fields are displayed as text. Thumbnails and their links point at the item's media source so readers can reach the actual video.
No. Feed URLs are sent to a same-origin fetch route that returns no-store responses and never caches feed URLs or bodies. When you paste or upload, the XML is processed in your browser; thumbnail requests may contact image hosts.
Remote fetching is limited to pre-approved public feed hosts and VideoNest's own channel hosts, so the tool never becomes an open proxy. Any feed can be pasted or uploaded instead, which keeps things fully local.
Yes. Enter a stream playlist URL such as https://yourchannel.videonest.co/live/master.m3u8. The inspector reads the master playlist, follows its first rendition playlist, and reports the live window, the items inside it, cue markers, per-item runtime, the rendition ladder, and the full tag inventory. A playlist can also be pasted or uploaded, which works on any host.
It depends on the playlist. The title is carried when the producer writes it into the manifest: VideoNest's canonical channel playlists put the current title in #EXTINF text, and anything written into #EXT-X-SESSION-DATA is surfaced with its field name. Upcoming items are not in a playlist at all, because it publishes segment paths only up to the newest completed segment, so a VideoNest channel URL is read together with that channel's JSON schedule, which carries the upcoming queue, each item's runtime, and start times. A description is not carried anywhere, and the report says so rather than inferring one. The inspector never fetches or plays video segments, only manifest and schedule text.

Ready to distribute everywhere

Your content, delivered on time and in the right format, to every destination. No manual submissions and no spec guesswork.

Get Started Today

Book a demo

The MRSS Feed Inspector and HLS playlist reader is an independent diagnostic tool. It reflects a snapshot of a feed or playlist at inspection time and is not affiliated with, endorsed by, or a guarantee of acceptance by any platform. It has no universal validation claim.