EVIDENCE FOR YOUR NEXT WEB DECISION

HTTP Transfer Size Breakdown

Separate headers, encoded bytes and decoded bytes from imported resource records.

Worked exampleBrowser processingUseful downloads

A clear result starts here

Add your input or try the worked example.

Using HTTP Transfer Size Breakdown

Separate headers, encoded bytes and decoded bytes from imported resource records.

Use Try example to explore http transfer size breakdown, or enter your own har json or resource csv.
Review the input format and the scope note before processing.
Choose Review input and inspect the result, including any review flags or unsupported cases.
Use the relevant download buttons to keep your result. CSV and report JSON preserve the available findings; original files are not changed.

Example

HAR JSON or resource CSV: url,headers,encoded,decoded
/app.js,450,12000,42000
/style.css,320,3000,15000
/cached.png,0,0,8000
/unknown,-1,-1,500

Questions & answers

What does HTTP Transfer Size Breakdown do?

Separate headers, encoded bytes and decoded bytes from imported resource records.

What input does this tool support?

HAR JSON or resource CSV: CSV columns: url,headers,encoded,decoded. HAR: log.entries[].response sizes.

What should I check before using the result?

Analyzes supplied resource records. HAR -1 means unknown; zero transferred bytes may reflect cache or an empty response. Compression savings exclude headers.

Can I keep or share the result?

Yes. Use the result-specific downloads, CSV where available and report JSON. Downloads can contain your supplied information, so review the content before sharing. Processing runs in this browser; public pages also include the site’s approved advertising and optional analytics.