How to get a HAR file in any browser
How to get a HAR file in Chrome, Firefox, Safari and Edge: record in the Network panel, reproduce the issue, export, and clean it before sharing.
To get a HAR file, open your browser’s developer tools on the page with the problem, switch to the Network panel, turn on the option that keeps requests across page loads, reproduce the problem, and export the requests as a .har file. Chrome, Edge, Firefox and Safari all do this without extensions. The steps take about two minutes once you know where the buttons are.
Before you send the file, remove secrets. A HAR file records cookies, authorization headers, form data and response bodies, so it can be enough for someone to sign in as you. Run it through the HAR sanitizer, which works in your browser and does not upload the file, and check the result in the HAR viewer.
The short version for every browser
- Open the page where the problem happens.
- Open developer tools and select Network.
- Turn on the option that keeps the log across page loads.
- Clear the existing requests so the file only contains what matters.
- Reproduce the problem: reload, click, submit, whatever triggers it.
- Export the requests as a HAR file.
- Sanitize the file, then share it.
Below are the browser-specific steps. Each one links to a detailed guide you can follow with the browser open. Browser menus change between versions, so if a label differs slightly, look for the download or export icon in the Network panel toolbar.
Chrome
- Press F12 or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on Mac. You can also open the three-dot menu and choose More tools, then Developer tools.
- Click the Network tab.
- Check Preserve log.
- Reproduce the problem.
- Click Export HAR (sanitized)… in the Network panel action bar, or right-click any request and choose Copy, then Save all as HAR (sanitized).
Chrome’s default export leaves out Cookie, Set-Cookie and Authorization headers. If support specifically needs those, there is a setting to allow a full export. Details in how to export a HAR file in Chrome.
Firefox
- Press Ctrl+Shift+E on Windows and Linux, or Cmd+Option+E on Mac, to open the Network Monitor directly.
- Open the gear menu at the right end of the Network Monitor toolbar and select Persist Logs.
- Reload the page and reproduce the problem.
- From the same gear menu, choose Save All As HAR. You can also right-click any request and pick Save All As HAR.
Firefox’s documentation does not describe a sanitized export, so assume the file includes cookies and authorization headers. Details in how to export a HAR file in Firefox.
Safari
- Turn on developer features once: choose Safari, then Settings, open the Advanced pane and check Show features for web developers.
- Press Option+Command+I, or choose Show Web Inspector from the Develop menu.
- Select the Network tab and check Preserve Log.
- Reproduce the problem.
- Click Export in the Network tab, or press Command+S.
Safari records only the requests made since Web Inspector was opened. Details, including iPhone and iPad, in how to export a HAR file in Safari.
Edge
- Press F12 or Ctrl+Shift+I on Windows and Linux, or Command+Option+I on Mac. You can also open Settings and more, then More tools, then Developer tools.
- Select the Network tool.
- Check Preserve log.
- Reproduce the problem.
- Click Export HAR (sanitized) in the Network tool’s action bar.
Edge is built on Chromium, so its Network tool and HAR options closely match Chrome’s. Details in how to export a HAR file in Edge.
Before you start: get a clean recording
A HAR file is only useful if it contains the failing request. A few habits make that much more likely.
Open developer tools first. Browsers record network traffic only while developer tools are open. If you open them after the error, the request that failed is not in the log. Open the Network panel, then reproduce.
Keep the log across page loads. Sign-in flows, checkouts and payment pages often redirect several times. Without Preserve log (or Persist Logs in Firefox), each navigation wipes the list and the interesting request disappears.
Clear the list before you reproduce. A smaller file is easier to read and contains less personal data. Use the clear button in the Network panel, then perform only the steps that trigger the problem.
Reload if the problem happens on page load. If the bug appears when the page first opens, reload with the Network panel open so the initial requests are captured.
Don’t filter before exporting. In some browsers, the export only includes the requests currently shown. If you typed something in the filter box or selected a type such as Fetch/XHR, clear it first unless you want a partial file.
Note the time. Write down roughly when the error happened. Support teams can match that time against their server logs, and it helps them find the right entry in a long file.
Sanitized or full export?
Chrome and Edge give you a choice: a sanitized HAR that leaves out Cookie, Set-Cookie and Authorization headers, or a full export after you enable a setting. Firefox and Safari export everything they captured.
For most bugs, the sanitized version is enough. Send a full export only if the team asked for it because they are investigating a cookie or authentication problem, and only through their support channel. Even a sanitized export can still contain tokens in URLs, passwords in request bodies and personal data in responses. That is why we recommend running every HAR file through the HAR sanitizer before sharing it. It removes cookies, authorization headers, sensitive URL parameters, password and token fields, JWTs, API keys and card numbers, and lets you add field names that are private in your own app. Our guide on removing sensitive data from a HAR file explains what it checks and what it can miss.
Check the file before you send it
Open the exported file in the HAR viewer or import it back into the Network panel. Confirm three things:
- The failing request is there, with its status code and response.
- The file covers the whole flow, from the first page load to the error.
- No passwords, tokens or cookies are left after sanitizing.
If the file is large, compress it as a zip before attaching it. HAR files are text and usually compress well.
After you share it
If you recorded while signed in and sent a full export, sign out of the app once support has the file. In most apps this ends the session, so a cookie in the file stops working. Delete local copies you no longer need.
A shortcut for bug reports in Chrome
If you are reporting a bug to your own team rather than to a vendor’s support desk, a full HAR file is often more than you need. Midge, a free Chrome extension, records your screen or takes a screenshot and attaches the technical context automatically. 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. It does not replace a HAR file for every case, but for “the save button does nothing” it gives the developer the failing request and the console error in one link.
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
- Firefox DevTools: Network monitor toolbar
- WebKit: Web Inspector Network tab
- Microsoft Edge DevTools: Network features reference
Related guides
Frequently asked questions
Why does support keep asking me for a HAR file?
A HAR file shows every request your browser sent and what the server answered, with timings. It lets support see the failing request on your machine without a screen-sharing session.
Do I need to install anything to get a HAR file?
No. Chrome, Edge, Firefox and Safari can all export HAR files from their built-in developer tools. Safari needs its developer features turned on first.
My HAR file is empty or missing the error. What went wrong?
Browsers only record requests while developer tools are open. Open the Network panel first, turn on the option that keeps the log across page loads, then reproduce the problem and export.
Can I get a HAR file on my phone?
Not directly from mobile browsers. For Safari on iPhone or iPad you can connect the device to a Mac and use Safari’s Web Inspector, as described in our Safari guide.
Should I remove anything before sending it?
Yes. HAR files can contain cookies, tokens, passwords and personal data. Clean the file with a HAR sanitizer, check the result, and send it only to the team that asked for it.