HAR File Viewer and Sanitizer
Open a HAR file you own or have the right to inspect. Free, with no sign up. Your file stays in this browser; nothing is uploaded.
Or drop it here.
| Method | Status | Host | Path | Type | Size | Time |
|---|
Clean it before you share it
Makes a copy without cookies, login headers and secret-looking values. The file you opened is not changed.
How to save a HAR file
Chrome or Edge
- Press F12 and open the Network tab.
- Reload the page and do the steps you want to record.
- Click the download arrow (Export HAR) above the request list.
Firefox
- Press F12 and open the Network tab.
- Reload the page and do the steps you want to record.
- Right-click any request and choose Save All As HAR.
A HAR file can hold your login cookies. Open only a HAR file you own or have the right to inspect, and clean it before you send it to anyone.
How to use this tool
Drop a HAR file you own or have the right to inspect, or try the sample. Filter the requests, hover the waterfall, click a row to read it. Press Make a cleaned copy to save a version without cookies and tokens.
Frequently asked questions
Is my HAR file uploaded?
No. The file is read and cleaned inside your browser. This page makes no network call with it, and the cleaned copy is built on your device.
What does the cleaned copy remove?
It drops Cookie, Set-Cookie, Authorization and Proxy-Authorization headers and every cookie list. It replaces the values of headers, query parameters, form fields and JSON keys whose names contain token, key, secret, password, session, auth, sig, jwt, csrf, xsrf, credential, bearer or otp with REDACTED. The page shows how many of each it removed.
Is a cleaned HAR safe to share?
It is safer, not guaranteed safe. A secret under an unusual name, an ID in a URL path, or personal details in a page body can stay. Search the cleaned file for anything private before you send it.
What is a HAR file?
HAR stands for HTTP Archive. It is a JSON file a browser saves from its network panel. It lists each request with its URL, headers, timings and often the response body, so it can hold login cookies and tokens.
What do the waterfall colours mean?
Each bar is one request, placed where it started on the page timeline. Its parts are time spent blocked or queued, the DNS lookup, connecting, sending, waiting for the first byte, and receiving the response. A part the browser did not record is left out.