Recover HAR response files
Recover response bodies already captured in a local HAR file, with a clear report of missing content.
- 1Add input
- 2Review and run
- 3Get your result
Tool input and files are processed in this browser without being uploaded.
Before you start
Turn captured HAR response bodies into local files and a ZIP. Base64 payloads recover their exact recorded bytes; ordinary response text is saved as UTF-8. Missing bodies and bodyless statuses stay visible in the report.
How to use this tool
- Choose a HAR export that includes response bodies, or paste its JSON.
- Review recovered and omitted entries, byte provenance and safe filenames.
- Download the resource ZIP and complete reports. Duplicate URLs remain separate entries.
Supported inputs and limits
One UTF-8 HAR file up to 10 MiB or pasted JSON up to 1 MiB; up to 5,000 entries, 2,000 recovered bodies, 10 MiB per body and 30 MiB total recovered bytes. Duplicate JSON keys and corrupt declared Base64 are rejected.
Only content.text already in the recording is used. No URL is fetched. 204/304, missing content.text and unsupported encodings are reported as omitted. Plain text is explicitly UTF-8 reserialization and may differ from original wire bytes. Report URLs omit credentials, query and fragment; headers and cookies are excluded. Reports are still private local artifacts.
Worked example
Example input
HAR with one 5-byte Base64 body, UTF-8 text 合同 plus newline, an empty captured body, a missing body and a 304.
Example options
{}Example output
5 entries, 3 recovered files, 2 omitted entries, 12 recovered bytes; no URLs fetched.
When something does not work
Export HAR with response content when available. Missing body entries cannot be reconstructed from URLs. Fix malformed HAR or bad declared Base64, and reduce records when budgets are exceeded.
Frequently asked questions
Will it download missing bodies from the internet?
No. It uses only captured content.text. Missing data remains an explicit report entry.
Are text responses byte-identical?
Canonical Base64 responses preserve recorded payload bytes. Unencoded response strings are saved as UTF-8, which is not a claim about original transport encoding.
What happens to repeated URLs?
Each captured entry has its own index and unique download name. Resources are not overwritten merely because their URL repeats.
Documentation & further reading
Related tools
QR code maker
Turn a link or a little text into a QR code.
UTM link builder
Add your campaign details without the guesswork.
Meta tags generator
Fill in page details and copy the resulting meta tags.
robots.txt generator
Build a robots.txt file from the crawl rules you choose.