HAR File Viewer
Open a HAR file from the browser's network panel, filter requests by URL or status, see sizes and timings, and copy any request as curl with secrets redacted.
Free · No sign-up · Your inputs stay in your browser
Input
View a HAR file
Output
4 requests, 114 KiB
This capture contains Cookie or Authorization headers.
| # | Method | Status | URL | Size | Time |
|---|---|---|---|---|---|
| GET | 200 | https://example.com/ | 17.8 KiB | 182 ms | |
| GET | 200 | https://example.com/_next/static/chunks/main.js | 95.9 KiB | 41 ms | |
| POST | 502 | https://example.com/api/subscribe | 0.5 KiB | 1204 ms | |
| GET | 404 | https://example.com/favicon.ico | 0.0 KiB | 12 ms |
Request 1 as curl
curl -X GET https://example.com/ \ -H 'Accept: text/html'
A HAR file records every header, including cookies and Authorization tokens, and often request bodies with passwords in them. That is why it should be read here or in DevTools and never attached to a public ticket without scrubbing it.
Runs in this browser. Nothing you paste is sent to a server.
About this tool
Method, assumptions, practical next steps, and limits.
HAR files contain secrets
A HAR export records every header and often every request body: session cookies, bearer tokens, CSRF tokens, passwords typed into forms. Support teams ask for them and people attach them to tickets, which is how session tokens leak. Viewing one here keeps it on your machine; before sharing one, remove the sensitive headers or use the browser's sanitised export option where it exists.
Making one
In Chrome and Firefox DevTools, open the Network panel, reproduce the problem with Preserve log on, then right-click and save all as HAR. The format is a JSON document described in the HAR 1.2 draft specification.