STREAMING ENGINEER CONSOLE

HLS AVERAGE-BANDWIDTH vs BANDWIDTH for transfer estimates

An HLS master playlist describes available renditions. It does not tell you how much time real viewers spend at each quality. The inspector turns each supported rendition into a separate transfer scenario, preserving that uncertainty.

Inspect an HLS master playlist

Start with a master playlist

Look for EXT-X-STREAM-INF entries followed by rendition playlist URIs. A media playlist instead lists segments, often with EXTINF tags. This tool supports master-playlist rendition analysis; it rejects media playlists rather than treating segment duration as a bitrate. Paste text directly: the inspector does not fetch the playlist's URLs.

#EXTM3U
#EXT-X-STREAM-INF:BANDWIDTH=1500000,AVERAGE-BANDWIDTH=1000000,RESOLUTION=640x360
low.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=4000000,AVERAGE-BANDWIDTH=3000000,RESOLUTION=1280x720
high.m3u8

Prefer average bandwidth when available

AVERAGE-BANDWIDTH describes an average for the variant; BANDWIDTH describes a peak requirement. The inspector prefers the average for transfer estimates. When it is absent, the peak becomes an explicitly labeled proxy, which can overstate typical transfer. Conflicting metadata, such as an average above the peak, produces a warning rather than hidden certainty.

Compare scenarios without adding them

For 10,000 plays lasting five minutes each, a 1 Mbps scenario implies 375 decimal GB. A 3 Mbps scenario implies 1,125 GB. These describe the same viewing time at different bitrates. Adding them would assume all of that viewing time occurred at both rates, which is not the usual adaptive-playback model.

Assumed rendition	Viewing minutes	Estimated transfer
1 Mbps average	50,000	375 GB
3 Mbps average	50,000	1,125 GB
1.5 Mbps peak proxy	50,000	562.5 GB

Build a weighted scenario only with evidence

If 70% of watched minutes genuinely occur at 1 Mbps and 30% at 3 Mbps, the weighted bitrate is 1.6 Mbps. For 50,000 watched minutes that gives 600 decimal GB before other overhead. Those percentages are an example, not a default or a measured audience. Use player analytics to obtain your own mix.

Export useful measurements safely

Playlist URLs may contain signed access tokens. The exported report omits rendition URIs and codec strings, and the parser does not fetch video segments or encryption keys. The report still describes your rendition configuration, so review it before sharing. Use the video delivery planner next to combine audience assumptions with library size and hosting capacity.

Load a local master playlist

Choose a UTF-8 .m3u8 or text file up to 500 KB, or paste the playlist. The inspector reads the local text only: it never fetches rendition URLs, encryption keys or media segments. After loading, choose Inspect to build the rendition table. If you edit the text while a file is loading, the newer text takes precedence.

Reproduce this example

At 10,000 plays of five minutes: 375 GB at 1 Mbps or 1,125 GB at 3 Mbps. These are alternative scenarios, not quantities to add. The playlist has no hosted video segments.

Load Two renditions at 1 and 3 Mbps average

Download two-renditions.m3u8 — synthetic data you can save or reference. The diagnostic samples contain no real addresses, credentials or hosted streams. Scenario CSVs document inputs; the calculators do not import CSV.

Common questions

Why does the inspector reject my M3U8?

It may be a media playlist, malformed text, or outside the supported size and attribute limits. Try the built-in master-playlist sample to compare its structure.

Does missing AVERAGE-BANDWIDTH make the estimate exact?

No. BANDWIDTH is used as a labeled fallback. Real average transfer may be lower, and playback overhead can change observed usage.

Does the tool contact URLs in my playlist?

No. It parses pasted text locally and exports measurements without the playlist URIs.

Try it with your own scenario

Inspect an HLS master playlist

The tool is free to use. Product inputs stay in the local browser workspace. Provider links, where present, are separate from the calculation.

References and scope

HTTP Live Streaming specification (RFC 8216)

Updated 2026-09-24. Examples are illustrative calculations, not measured customer outcomes. Provider prices and terms must be checked at purchase time.