How to view a HAR file and read what's inside
Open a HAR file in a free HAR file viewer or browser DevTools, find failing requests fast, and read the waterfall and timing breakdown.
To view a HAR file, open it in a HAR file viewer such as the free Midge HAR viewer, which reads the file in your browser without uploading it, or import it into the Network panel of Chrome, Edge, Firefox or Safari. Either way you get the same kind of table you see in DevTools: one row per request with its status, type, size, time and a waterfall bar, plus the headers, payload, response and timings when you click a row.
Reading it is mostly about two questions: which request failed, and where the time went. Start by filtering for errors and API calls, then use the waterfall and the timing breakdown to see whether the delay was in the network, the server or the download.
Ways to open a HAR file
In a HAR viewer in your browser
The HAR viewer is the quickest route when you received a file from someone else. Choose the file or drop it on the page. The viewer parses it with JavaScript in your browser, so the contents are not sent anywhere, which matters because HAR files often contain cookies and tokens. Large files stay responsive because parsing happens in a background worker and the table only draws the rows on screen.
You can filter by type (All, Fetch/XHR, WS, JS, CSS, Img, Media, Font, Doc, Other), search by URL, and keep only errors.
In Chrome or Edge DevTools
- Open DevTools with F12 or Ctrl+Shift+I (Cmd+Option+I on Mac).
- Select the Network panel.
- Click Import HAR in the action bar, or drag the
.harfile onto the request table.
The Network panel then shows the imported requests as if you had recorded them, including initiators. This is handy if you already know DevTools well.
In Firefox
Open the Network Monitor with Ctrl+Shift+E (Cmd+Option+E on Mac), open the gear menu at the right end of its toolbar, and choose Import HAR.
In Safari
Open Web Inspector with Option+Command+I, select the Network tab and click Import, or drag the file onto Web Inspector. Imported files can be viewed one at a time. Safari needs developer features turned on first; see how to export a HAR file in Safari.
Other options
Google also offers a HAR Analyzer web tool, which Microsoft’s Edge documentation links to. Before you open a file that contains secrets in any online tool, check how it handles uploads, or sanitize the file first with the HAR sanitizer.
Because a HAR file is JSON, you can also search it in a text editor or query it from the command line. That is useful for very large files or for scripting. With jq, the first command below lists every request that returned an HTTP error, and the second shows the ten slowest requests:
jq -r '.log.entries[] | select(.response.status >= 400) | "\(.response.status) \(.request.method) \(.request.url)"' session.har
jq -r '.log.entries | sort_by(-.time) | .[:10][] | "\(.time | floor) ms \(.request.url)"' session.har
Reading the request table
Each row is one request. The columns you will use most:
- Name: the last part of the URL. Hover or click to see the full address.
- Method: GET, POST, PUT, DELETE and so on.
- Status: the HTTP status code. 2xx means success, 3xx a redirect, 4xx a problem with the request (missing auth, not found, validation), 5xx a server error. A status of 0 or an empty status often means the request never got a response: it was blocked, cancelled or failed at the network level.
- Type: document, script, stylesheet, image, fetch or XHR, WebSocket and so on.
- Size: how many bytes came back.
- Time: total time from start to finish.
- Waterfall: when the request started and how long it took, relative to the others.
Find the failing request first
Most HAR files are opened to answer “what broke?”. A quick routine:
- Filter to Fetch/XHR. These are the app’s API calls, and most application bugs show up here.
- Turn on errors only, or sort by status. Look for 4xx and 5xx codes.
- Click the failing request and open Response. Many APIs return a readable error message or an error code.
- Open Headers and check the request URL, method and the important headers. A 401 might come from a missing
Authorizationheader; a CORS failure shows up as missingAccess-Control-Allow-Originheaders in the response. - Open Payload to see what was sent. Validation errors (400 or 422) usually trace back to a field in the body.
- Note the request ID if the response includes one. Server teams can search their logs for it.
Do not stop at the first red row. A 404 for a favicon is noise; a 500 from /api/checkout right before the user saw “Something went wrong” is the story.
Reading the waterfall
The waterfall shows every request as a horizontal bar on a shared timeline. Patterns to look for:
- One long bar. A single slow request that holds up the page. Click it and check the timing breakdown.
- A staircase. Requests that start only after the previous one ends. This usually means a chain of dependencies, such as an API call that waits for a script, which waits for another script.
- Many bars starting late together. Requests waiting in a queue for a free connection. Browsers limit simultaneous connections to one server; Firefox’s documentation gives six as its default.
- A long gap with no requests. The browser was busy doing something other than networking, often running JavaScript.
- Repeated identical requests. A retry loop or a component that fetches the same data several times.
Reading the timing breakdown
Click a request and open Timing. The HAR format stores these phases, in milliseconds:
| HAR field | What it measures | Chrome’s label (roughly) |
|---|---|---|
blocked | Waiting in a queue before the request could start | Queueing, Stalled |
dns | Resolving the host name | DNS Lookup |
connect | Opening the connection, including TLS when ssl is present | Initial connection |
ssl | The TLS handshake (also counted inside connect) | Part of Initial connection |
send | Sending the request | Request sent |
wait | Waiting for the first byte of the response | Waiting (TTFB) |
receive | Downloading the response | Content Download |
A value of -1 means the phase did not apply. dns and connect are usually -1 when the browser reused an existing connection. The request’s total time is the sum of the phases that are not -1.
How to interpret them:
- High
waitpoints at the server or anything between you and it: a slow database query, a cold start, a busy upstream service. This is the most common cause of a slow API call. - High
receivepoints at a large response or a slow connection. Check the size. - High
blockedmeans the request sat in a queue. Too many requests to one host at once is a common reason. - High
dnsorconnecton many requests suggests a network problem on the user’s side, a VPN or proxy, or a server far away.
A worked example
Imagine a customer says the billing page takes ten seconds to load. You open their HAR file, filter to Fetch/XHR and sort by time. One request, GET /api/invoices?limit=500, took 9.4 seconds. Its timing shows wait at 9.1 seconds and receive at 0.2 seconds. The server spent nine seconds before sending the first byte, so the fix belongs on the backend, probably in how invoices are queried. Without the HAR file, the same report could easily have turned into a week of guessing about the customer’s network.
Before you forward the file
If you are passing a HAR file to someone else, sanitize it first with the HAR sanitizer and check the result in the viewer. Our guide on removing sensitive data from a HAR file explains what to look for.
When you need more than the network
A HAR file shows requests and responses, but not the console error that followed or what the user clicked. Midge, a free Chrome extension, puts those on one timeline with a screen recording or screenshot. Every recording includes console logs, network requests, user actions and device info. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device.
Official documentation
The browser steps above were checked against these pages on November 10, 2026. Browser menus change between versions, so the official pages are the place to look if a label has moved.
- Chrome DevTools: Network features reference (Import HAR, Timing tab)
- Firefox DevTools: Network request details
- WebKit: Web Inspector Network tab
- HAR 1.2 specification draft (timings object)
Related guides
Frequently asked questions
What program opens a HAR file?
Any modern browser can. Import it into the Network panel of Chrome, Edge, Firefox or Safari, or open it in a HAR viewer web page. Since it is JSON, a text editor can open it too, but it is hard to read that way.
Is it safe to open a HAR file in an online viewer?
It depends on the viewer. HAR files often contain cookies and tokens, so use a viewer that reads the file locally in your browser, like the Midge HAR viewer, or sanitize the file first.
What does a -1 timing mean in a HAR file?
It means the phase did not apply to that request. For example, DNS and connect are -1 when the browser reused an existing connection.
Which number tells me the server was slow?
The wait time, shown as Waiting (TTFB) in Chrome. It measures how long the browser waited for the first byte of the response after sending the request.