Don't like ads? Go Ad-Free Today 

HAR File Formatter & Request Inspector

DataDeveloperNetworking

ADVERTISEMENT · REMOVE?

INPUT

Auto Process

OUTPUT

Client Side

ADVERTISEMENT · REMOVE?

Guide

HAR File Formatter & Request Inspector

Drop in an HTTP Archive (.har) file exported from your browser’s DevTools and instantly see every request as a sortable, filterable waterfall — with full DNS, connect, SSL, wait, and download timings, plus the raw headers, body, and a ready-to-paste cURL command for any single request. Everything runs locally in your browser; the HAR never leaves your machine.

How to Use

Export a HAR file from your browser. In Chrome or Edge: open DevTools, switch to the Network tab, reproduce the page load or API call, then right-click any row and choose Save all as HAR with content.
Drop the .har file onto the upload area, or paste the JSON directly into the textarea.
Use the search box and the method/status/type dropdowns to narrow the request list.
Click any row in the waterfall to inspect its headers, request and response bodies, per-phase timings, and the equivalent cURL command.
Copy the cURL command into your terminal to replay the request outside the browser.

Features

Visual waterfall – Each request rendered as a stacked bar of blocked, DNS, connect, SSL, send, wait (TTFB), and receive phases, color-coded for fast scanning.
Multi-criteria filtering – Filter by URL substring, HTTP method, status tier (2xx, 3xx, 4xx, 5xx, failed), and content type (document, XHR, script, stylesheet, image, font, media).
Per-request inspector – Tabbed view of request and response headers, request body, response body (auto-prettified for JSON), per-phase timing breakdown, and a generated cURL one-liner.
Page load summary – Reads HAR pages entries to surface DOMContentLoaded and load timings alongside the request list.
Aggregate stats – Total transferred bytes, total content size, OK/error counts, and the elapsed time span across the filtered request set.
100% client-side – Parsing happens in your browser. No HAR data is uploaded to any server.

 FAQ

What is a HAR file?

HAR (HTTP Archive) is a JSON-based format standardized by the W3C Web Performance group. It captures a snapshot of a browser's network activity for a session, including every request and response, the headers exchanged, the request and response bodies, the timing of each phase of the connection, and metadata about the page being loaded. Browsers, performance monitoring tools, and proxies all support exporting HAR files so that traces can be shared across tools.
What do the waterfall timing phases mean?

A request is broken into seven phases. Blocked is time spent waiting in the browser queue or for an available connection. DNS is the time to resolve the host name to an IP. Connect is the TCP handshake. SSL is the TLS handshake on top of TCP for HTTPS requests. Send is the time taken to transmit the request bytes. Wait (also called TTFB, time-to-first-byte) is the gap between the request being fully sent and the first response byte arriving. Receive is the time spent downloading the response body.
Why is the waterfall a useful performance signal?

A waterfall lets you see the critical path of a page load at a glance. Long blocked or DNS phases hint at connection-pool or DNS-resolution issues. Long wait phases point at slow server-side processing or under-provisioned origins. Long receive phases point at large payloads or slow last-mile bandwidth. Stair-stepping bars where many requests start at the same offset reveal serial dependencies that could be parallelized, while a flat cluster of bars suggests a CDN or HTTP/2 multiplexing is doing its job.
Why does my HAR have empty response bodies?

Response content is optional in the HAR specification. Browsers typically omit binary payloads (images, fonts, video) and may truncate large text responses depending on DevTools settings. To capture full text bodies in Chrome, enable Preserve log and choose Save all as HAR with content. Even with content saved, fields such as cookies, authorization headers, and post bodies should be treated as sensitive — sanitize HAR files before sharing them publicly.