HLS Media Playlist Timing Inspector

How to use HLS Media Playlist Timing Inspector

Inspect declared M3U8 media-segment durations, exact sequence numbers and byte ranges without fetching a stream. Resolve segment addresses against an explicit playlist URL and total decimal durations without binary rounding drift. Keep unmodeled HLS tags visible and distinguish source metadata from actual playback behavior.

1. Provide optional utf-8 media playlist, hls media playlist, playlist url used only for resolution.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 500 KB well-formed NFC UTF-8, no BOM or controls except CRLF/LF; 10,000 lines, 8,192 bytes per line and 2,000 media segments. Only selected media-playlist timing semantics for RFC 8216 compatibility versions 1–7 are modeled; master/multivariant playlists are refused.
• EXTINF uses at most six integer and nine fractional decimal digits and a comma before the optional title. Duration sums remain exact to the supplied nanosecond decimal precision; sum at most one billion seconds. Target-duration ties at exactly half a second are explicitly labeled.
• Sequence values and explicit byte-range lengths/offsets use unsigned 64-bit integers. Implicit byte offsets require the preceding byte range to resolve to the same HTTP(S) URI; this does not prove resources exist, are equal after redirects or contain enough bytes.
• Unmodeled EXT tags are listed by name, without parsing attribute lists or applying encryption, initialization-map, date/time, gap, I-frame or partial-segment semantics. A successful selected report is not a full HLS validator or player-compatibility verdict.
• The supplied playlist URL and media URI lines must resolve to HTTP(S) without embedded credentials. No stream, encryption key, image or linked playlist is requested or executed. URLs remain plain source/report text and may contain your own sensitive query parameters. Reports have a separate 500,000-character output cap.
• Inputs are processed on this device and are not automatically saved or uploaded.