Skip to developer tool
DEVELOPER TOOLKIT INSPECT & UNDERSTAND

HAR Viewer & Network Log Analyzer

Understand a network capture. Find slow requests, inspect HTTP errors and review the data your browser recorded, all in one local workspace.

No uploads · No account · No request replay

BUILT FOR THE DETAILS
  1. 01Add your input
  2. 02Explore the network log
  3. 03Review request details
Explore all developer tools

Explore a captured network session

Local files · No request replay

Up to 25 MiB and 10,000 requests. HAR files can contain account tokens, cookies and private response data. This viewer keeps the capture in memory on this page.

How to inspect a HAR network capture

  1. Export a HAR file from your browser's Network panel, then choose it here. Use the sample to explore the viewer before loading your own capture.
  2. Search requests, choose a host or status group, and sort by start time, duration or response body size. Requests are displayed in pages of 100.
  3. Select a request to inspect its recorded URL, request and response headers, query parameters, timing phases and captured text bodies.
  4. Download a summary of the filtered requests or clear the workspace when finished.

What the timing and size fields mean

Durations use each entry's recorded total time in milliseconds. The capture span runs from the earliest recorded request start to the latest known request end; overlapping requests are not added together. Missing or negative HAR values remain unknown. Status 0 means no HTTP response was recorded and is separate from HTTP 4xx/5xx errors.

SSL time is included within connect time in HAR, so it is not an additional sequential phase. Body size is the response body size as recorded, which may be zero for cached responses. Decoded content size appears separately in request details. Neither value is a complete packet-level bandwidth measurement.

Local text previews

Captured text, JSON, XML, JavaScript, form-encoded text and SVG are displayed as plain text. Base64 text bodies are decoded as UTF-8 with a bounded preview. Binary bodies are not rendered. Missing bodies cannot be recovered from a HAR that did not capture them.

Supported files and limits

This viewer reads HAR-style JSON with a log.entries array, including typical HAR 1.2 browser exports and a UTF-8 byte-order mark. It is a practical viewer rather than a complete schema validator. Entries without a request URL or method are skipped and counted. Browser-specific extension fields are ignored.

The file limit is 25 MiB, with up to 10,000 entries and a 15-second worker parsing deadline. Long URL and metadata fields are bounded for display. Headers and query parameters show up to 200 pairs, names up to 256 characters and values up to 4,096 characters. Body previews show at most 65,536 characters with bounded base64 decoding. Large captures should be exported in smaller sessions.

Privacy and export scope

The viewer does not upload the HAR, replay its requests, contact captured hosts or save capture contents in browser storage. It holds the normalized capture in page memory until replaced, cleared or the page is left. Downloaded summary JSON contains only request indices, hostnames, methods, statuses, durations and size fields; it is not an anonymization tool.

Field semantics follow the HAR 1.2 specification.

Frequently asked questions

Will this send my captured API requests again?

No. This is an offline log viewer. It does not fetch recorded URLs or replay traffic.

Why is a body, size or timing missing?

Browser exports can omit response bodies and fields, especially for cached or failed requests. Unknown values stay unknown; the viewer does not estimate missing data.

Can I use this to remove every secret from a HAR?

No. The summary export omits URLs, headers, queries and bodies but retains hostnames and request metrics. Full HAR redaction and sharing are outside this tool's scope.

Continue your workflow

Read captured traffic without replaying it

Open a supported HAR and inspect its normalized requests and timing fields. Use smaller captures when source logs exceed the page’s bounds.

Scope of this workflow

Unknown capture fields stay unknown. Summary exports are not full anonymization, and this page does not replay captured requests or query their hosts.

HTTP Header Analyzer — Local Response Review · All developer tools · Privacy policy · Contact PixelOkay