Understand the result
Average and peak describe different estimates
10,000 plays × 5 minutes at 1 Mbps → 375 GB The same viewing model at 1.5 Mbps → 562.5 GB
If the first report uses average bitrate and the second falls back to peak, the 50% increase is an estimation-basis change. It does not establish actual traffic growth. Rendition rows are alternative scenarios; do not add them together.
Compare like with like
Keep plays and watched time consistent. Match the same rendition and review whether each report uses average or peak bitrate. If multiple variants share a resolution, verify the correspondence manually. Confirm delivery changes with your own logs.
What this tool can and cannot tell you
Compare rendition alternatives without adding the rows. Average bandwidth is preferred; peak fallback is labeled. Compare two saved reports with matching plays and watched minutes. Unique resolution matching handles reordered rows; variant-number matching requires manual correspondence checks. Stream URLs are not exported; playback and actual transfer are not verified.
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.
Worked examples are synthetic. No customer outcome or saving is implied. Content by Orr Yoffe.