HAR to CSV / TXT
Analyze browser HTTP Archive (.har) network traces, URLs & status codes — 100% private client-side processing.
Active Converter
HAR to CSV / TXT: Auditing Chrome & Firefox Network Traces Without Leaking Session Cookies
Technical Anatomy of the .HAR 1.2 JSON Schema
Exported via Chrome, Edge, Firefox, or Safari DevTools (Network → Save all as HAR with content), an HTTP Archive (.har) is a structured JSON document rooted at {"log": {"version": "1.2", "entries": [...]}}. Each entry captures a single network transaction: request.method, request.url, response.status, response.content.mimeType, response.bodySize, and total elapsed time in milliseconds.
Because a single page load can fire 250+ requests and embed megabytes of base64 image bodies inside response.content.text, inspecting a raw .har file in VS Code is painful. Converting .har to CSV strips bloated response bodies and produces a crisp performance waterfall table you can sort by latency, HTTP 5xx errors, or payload weight.
Raw .HAR JSON Entry vs. Auditable Performance CSV
// Input: Chrome DevTools Network Export (checkout_slow.har)
{
"log": {
"entries": [
{ "request": { "method": "POST", "url": "https://api.shop.com/v2/pay" },
"response": { "status": 504, "bodySize": 182 }, "time": 10042.5 }
]
}
}
# Converted .CSV Output:
Method,Status,Time_ms,Size_Bytes,URL
"POST",504,10042.5,182,"https://api.shop.com/v2/pay"
Real-World Software & Hardware Ecosystem
Frontend performance engineers, QA testers, and technical SEO auditors export .har captures from Chrome DevTools, Firefox Developer Edition, Charles Proxy, Fiddler, Playwright, and WebPageTest, then open the CSV breakdown in Excel to spot third-party ad-script bottlenecks, failing CORS preflights, or uncached hero images.
Troubleshooting & Edge Cases
- Status Code
0or-1: A status of0indicates a request was canceled by the browser, blocked by an ad blocker/CORS policy, or dropped by a DNS/TLS timeout before the server replied. - Memory Size on Content-Heavy HARs: If you do not need response HTML/images inside the archive, use Chrome's Export HAR (sanitized) option to keep the file compact and automatically scrub sensitive cookies.
- Quick Error Filtering: Switch the output to Interactive Table mode and type
500,404, orPOSTin the filter box to isolate failing endpoints immediately.
HAR 1.2 Timing Phases Breakdown for Performance Debugging
| HAR Timing Key | Network Bottleneck Diagnosed |
|---|---|
| dns / connect / ssl | Slow DNS resolver, TCP handshake latency, or uncached TLS negotiation. |
| wait (TTFB) | Slow backend SQL query, cold serverless lambda, or origin server overload. |
| receive | Oversized unminified JS bundle or uncompressed hero PNG image. |
3-Step Slow-Page Triage Checklist
- Sort by
Time_msDescending: Immediately surface the top 5 slowest API calls or third-party ad scripts delaying Largest Contentful Paint (LCP). - Filter HTTP 4xx/5xx Errors: Type
404or500in Interactive Table view to catch broken assets and failing checkout endpoints. - Audit Total Transfer Weight: Sum
Size_Bytesin Excel to quantify mobile bandwidth cost per page load.
Frequently Asked Questions
A .HAR file is a W3C JSON snapshot (log.entries[]) of every HTTP/HTTPS request made by a browser tab—recording the HTTP method, full URL, status code (200, 404, 502), response MIME type, payload byte size, and millisecond timing breakdown (DNS, TLS, TTFB, download).
Raw .HAR JSON files easily reach 10–50 MB and are unreadable in text editors. Flattening log.entries into a CSV or Interactive Table lets you immediately sort by slowest response time (ms), filter 4xx/5xx error codes, or sum total transfer bytes by domain.
HAR captures record raw Authorization: Bearer tokens, session Cookie headers, and CSRF tokens from your logged-in browser session. Anyone with your .HAR file can hijack your account—so parsing .HAR strictly offline in your browser is essential.
Yes. Select Export .TXT to get a clean line-by-line summary of HTTP methods, status codes, timings, and URLs without sprawling JSON headers.