HAR File Viewer
Open .har captures from Chrome / Firefox DevTools. Filter, inspect headers and bodies. Local-only.
published
- [FREE]
- [NO_SIGNUP]
- [NO_UPLOAD]
A HAR file viewer parses HTTP Archive captures in your browser. Every request that crossed the wire during a DevTools session — URL, method, status, timings, headers, bodies — laid out as a table you can filter and drill into.
Why bother
HARs are how front-end bugs travel between people. Someone hits a flaky 500, captures the network tab, and shares the .har. You drop it here and see what the browser actually sent and received — no need to reproduce on your machine.
Privacy
The file is read with FileReader and parsed in JavaScript. No backend, no upload. The list of requests, headers, and bodies stays in your tab.
Frequently asked questions
What is a HAR file?
HTTP Archive — a JSON dump of every network request your browser made. Chrome, Firefox, Edge, and Safari can all export one from DevTools → Network. Useful for sharing a bug repro without screen-share.
Does the file get uploaded?
No. The viewer reads the file with the FileReader API and parses it in your tab. The file never leaves your browser.
How do I capture a HAR in Chrome?
Open DevTools (F12) → Network tab → reload page → reproduce the issue → right-click any request → Save all as HAR with content.
Why are some response bodies empty?
HAR captures are optional about including response content. If "Save all as HAR with content" was used, bodies are present; "Save all as HAR" omits them. Binary responses (images, fonts) are base64-encoded if included.
Do HARs contain secrets?
Yes. Auth headers, cookies, and request bodies are recorded verbatim. Scrub before sharing — DevTools has a "Sanitize" option in some browsers, or use a redaction script.