HAR Viewer
BetaInspect a HAR file in your browser. Review request method, URL, status, size, and time, then copy one selected request as a controlled cURL command for review.
- Free, no sign-up
- REST + MCP
- Updated
- Reviewed by Olgun Ozoktas
The HAR file stays in your browser. Analytics and ads may load on the page.
HAR input
Limit 20 MB of text.
How to inspect a HAR file
-
Export a HAR
In the browser network panel, save the log as HAR. -
Paste or drop
Drop the file or paste the JSON into this page. The limit is 20 MB. -
Inspect entries
Read method, URL, status, size, and time. The page does not render HAR as HTML. -
Copy cURL
Select one row and copy it as a cURL command.
Common Use Cases
Slow Request Review
Failed API Inspection
Request Reproduction
Network Log Handoff
Why use this HAR viewer
A HAR file records browser network activity as JSON. FindUtils HAR Viewer reads that data and lists each request with its method, URL, response status, size, and recorded time.
Selecting an entry creates a cURL command from the recorded request. The command can include request headers and body data, but it excludes browser cookies and several connection-specific headers. Review the command before you run or share it.
Parsing stays in your browser, and the page does not render recorded HTML or replay requests. Use the HAR to cURL tool for a conversion workflow, or use the HTTP Request Builder for a controlled public-endpoint test.
How it compares
Browser network panels are best during a live session. FindUtils HAR Viewer opens a saved log and creates cURL for one selected request, but it does not show response bodies or replay traffic.
A dedicated network client can send and organize requests, while this viewer only reads the supplied archive. Use cURL to Code when you need to turn the reviewed command into application source.
HAR Review Tips
- Remove passwords, tokens, cookies, and personal data before you share a HAR file.
- Keep the input below the 20 MB text limit.
- Select the exact request row before you copy cURL.
- Review the generated cURL before you run it because request headers or body data can be sensitive.
- Use a different tool when you need response body inspection or request replay.