OpenReplay Logo
12k
12k

HAR file viewer

Inspect HTTP Archive files with DevTools-grade depth: headers, timings, payloads and response bodies.

Processed locally in your browser (unless shared)

About this tool

A HAR file is a JSON record of every network request a browser made — the standard way to capture and share a network session for debugging.

Drop in a .har export and browse requests like a Network tab: filter by status, sort by duration, and open full headers and bodies.

HAR files can contain cookies and tokens. This viewer parses everything locally — nothing is uploaded unless you explicitly create a share link, and even then the HAR is encrypted in your browser first, so we can never read it.

Frequently asked questions

How do I open a HAR file?

Drop the .har file onto this page and it opens instantly in your browser — no upload. You get a DevTools-style view: filter requests by status, sort by duration, and expand any request to read its headers, payload and response body.

What is a HAR file?

A HAR (HTTP Archive) file is a JSON record of every network request a browser made during a session — URLs, headers, timings, status codes and, optionally, response bodies. Browsers export it from the Network tab so you can capture and share a network trace for debugging.

How do I create a HAR file?

In Chrome DevTools’ Network tab, record the traffic, then right-click → "Save all as HAR with content". Firefox and Edge work the same way.

Are HAR files sensitive?

Often, yes — they capture cookies, auth headers and request bodies. This viewer never uploads your file on its own, and the optional share feature scrubs cookies, auth headers and token-like parameters by default before encrypting.

Why are response bodies missing?

Use "Save all as HAR with content" — the plain export omits bodies to keep files small.

Can I share a HAR file with someone?

Yes — load the HAR and click Share. The file is compressed and end-to-end encrypted in your browser; the decryption key stays in the link fragment, so our server only stores ciphertext it cannot read. Links expire after 24 hours and can be revoked, and sensitive values are scrubbed by default before sharing.