HLS analyzer

Updated 2026-10-15

The iiPTV HLS analyzer reads an HLS manifest and turns its text declarations into an understandable report. It distinguishes master playlists from media playlists and shows information such as variants, codecs, tracks, segment timing and encryption signaling. It inspects the manifest rather than downloading and decoding the video.

An HLS analyzer is useful when a source responds but the offered qualities, audio options or playlist structure are unclear. Load a manifest file, paste its text or enter an authorized manifest URL. Remote requests go directly from your browser to the source, so normal cross-origin permissions still apply.

On this page: analyze a manifest, inspect variants, read timing, compare an example, understand boundaries, and questions.

Use the HLS analyzer with the correct input

Load actual manifest text or its address, usually ending in .m3u8, rather than a website page that embeds a player. An HLS analyzer needs readable playlist text. A login page or HTML error returned with a successful HTTP status does not become an HLS playlist because its URL contains the expected extension.

Run the analysis and check the reported manifest type first. A master playlist describes available renditions and related tracks. A media playlist describes the segments for one rendition. The HLS analyzer cannot invent a full adaptive ladder from a media playlist that does not contain it.

If the request cannot be read, use the stream checker to separate response problems from manifest interpretation. Keep the URL private if it contains a subscription identifier. Repeated analysis will not repair expired credentials, change an HTTP origin into HTTPS or grant cross-origin permission.

Read HLS analyzer variant information

For a master playlist, review resolution and bandwidth together. The HLS analyzer displays what the publisher declares; it does not measure the compressed video or verify the number of pixels in a segment. A larger advertised bandwidth is not proof of a better source, especially when variants use different codecs.

Codec strings can describe video and audio within the same attribute. The HLS analyzer keeps those declarations visible because a browser may understand the container while lacking a decoder for one track. Device support also depends on the browser, operating system and available media capabilities.

Audio and subtitle groups

Alternative tracks can have names, languages and group identifiers. Use the HLS analyzer to see whether the manifest declares them before assuming that a player has hidden an option. A listed subtitle track is metadata evidence; its separate resource can still fail when requested by an actual player.

Frame rate and relative variant addresses provide useful context too. The HLS analyzer reads a manifest's structure, while a playback test must still request the chosen rendition and its resources. Use Compatibility to keep supported player behavior distinct from a complete HLS specification.

Read HLS analyzer media timing

A media playlist can declare a target duration and individual segment durations. The HLS analyzer uses these values to describe the listed window. For a live source, that window can change as the publisher adds new entries and removes older ones, so record when you inspected it.

A playlist ending with an end marker differs from an ongoing live window. Encryption tags describe how a stream signals protection; they do not demonstrate that a key is available to you. The HLS analyzer does not fetch encryption keys, remove protection or offer a DRM access service.

The protocol definitions are documented in RFC 8216. This HLS analyzer is a practical inspection aid, not a complete conformance certification. A valid-looking text file can still point to missing, inconsistent or unsupported media resources.

Interpret an HLS analyzer example

Imagine a master that lists a 640×360 variant at 800,000 bits per second and another at 1280×720 with a larger declared bandwidth. An HLS analyzer helps you recognize two available choices. It cannot conclude which one your connection will sustain without a separate playback comparison.

Now imagine a media playlist with two segments lasting six and four seconds. Its listed duration is ten seconds, even if a target-duration tag says six. The HLS analyzer should keep those concepts separate: a target is not the total programme length, and a live window is not necessarily the complete broadcast.

Understand HLS analyzer privacy and limits

Inspection requests run in your browser against the chosen origin. The HLS analyzer does not use an iiPTV proxy to bypass permissions. CORS failures and mixed-content restrictions can prevent a report even when the source works in a native application; that difference is not evidence that its manifest is malformed.

Response reading is bounded to prevent an unexpectedly large resource from occupying the tab. The HLS analyzer does not fetch video segments or keys to complete the report. General playlist imports elsewhere in iiPTV are limited to 5 MiB and 10,000 entries; those catalogue limits are separate from a manifest's media timeline.

HLS analyzer questions

Does the HLS analyzer support DASH?

This report is for HLS text manifests. A DASH .mpd document uses another structure. The stream checker can inspect response availability, but changing a filename does not convert DASH to HLS or add a player decoder.

Does a clean HLS analyzer report prove playback?

No. Try supported media in the iiPTV player and press Play. A later rendition, segment or codec can fail after the outer manifest loads. Playback help explains that sequence without confusing successful import with successful decoding.

Can I share the raw manifest?

Review and redact it first. Variant, key and segment addresses can contain private tokens. Share only the minimum harmless example needed to explain a problem, and retain the source privately if you need to compare later changes.