Skip to content
midgeDocs
HAR filesHow to export a HAR file in Microsoft Edge
HAR files

How to export a HAR file in Microsoft Edge

Export a HAR file in Edge from the DevTools Network tool, pick a sanitized or full export, and remove secrets before you share the file.

To export a HAR file in Microsoft Edge, press F12 or Ctrl+Shift+I (Command+Option+I on Mac) to open DevTools, select the Network tool, check Preserve log, reproduce the problem, and click the Export HAR (sanitized) button in the Network tool’s action bar. Edge saves a .har file that leaves out Cookie, Set-Cookie and Authorization headers by default.

That default does not cover everything. Tokens in URLs, passwords in request bodies and personal data in responses stay in the file. Clean it with the HAR sanitizer, which runs in your browser and never uploads the file, then check it in the HAR viewer. The steps below follow Microsoft’s Edge DevTools documentation. Edge updates often and labels can change, so if a name looks slightly different, choose the closest match.

Step 1: Open DevTools

Go to the page where the problem happens. Then open DevTools:

  • Press F12 or Ctrl+Shift+I on Windows and Linux.
  • Press Command+Option+I on Mac.
  • Click Settings and more (the three dots at the top right of the browser), then More tools, then Developer tools.
  • Right-click the page and choose Inspect.

If F12 does nothing, it may be turned off. In Edge, go to edge://settings/system and check the Use F12 key to open the Developer tools toggle in the Developer Tools section. The other methods work either way.

Step 2: Select the Network tool

Microsoft calls the panels in Edge DevTools “tools”. Click Network in the toolbar. If you do not see it, click the More tools button and choose Network from the list; tools that do not fit are moved there.

Edge records network requests while DevTools is open. The Stop recording network log button at the top left should be red, which means recording is on. If it is gray, click it, or press Ctrl+E (Command+E on Mac) with the Network tool focused.

Step 3: Set up the recording

In the Network tool’s action bar:

  • Check Preserve log. Without it, Edge clears the list on every page load, and the request you need often happens right before a redirect.
  • Optionally check Disable cache to see what a first-time visitor downloads, or if the problem might come from a stale file.
  • Leave throttling on No throttling unless the bug only appears on slow connections.

Then click the Clear network log button, or press Ctrl+L (Command+K on Mac) with the Network tool focused, so the file only contains the steps you are about to take.

Step 4: Reproduce the problem

Refresh the page if the issue appears during loading. Otherwise, perform the exact steps: click the button, submit the form, open the page that breaks. Wait until the error shows up.

Click a failing request to see its details. The Headers tab shows the status code and headers, Payload shows query parameters and form data, and Response shows what the server returned. Copy any error message into your report as well.

Step 5: Export the HAR file

You have two options for a sanitized export:

  1. Click the Export HAR (sanitized) button in the action bar at the top of the Network tool, and save the file.
  2. Or right-click any request in the Requests table and choose Copy, then Copy all as HAR (sanitized). This puts the HAR data on the clipboard instead of in a file.

Microsoft’s documentation notes that the export contains all requests that occurred since you opened DevTools, and that it does not save a single request or a filtered subset. If you want a smaller file, clear the network log right before you reproduce.

Name the file so it is easy to recognize later, for example upload-fails-edge-2026-11-10.har.

Exporting with sensitive data

The sanitized export leaves out Cookie, Set-Cookie and Authorization headers. Some investigations need them, such as a cookie that is never set or an authentication header that is rejected. To export everything:

  1. In DevTools, open Customize and control DevTools (the three dots inside DevTools), then Settings. The Preferences page opens.
  2. Scroll to the Network section.
  3. Check Allow to generate HAR with sensitive data, and close Settings.
  4. In the Network tool, click the export button and choose Export HAR (with sensitive data). The right-click Copy menu also gains Copy all as HAR (with sensitive data).

Send a full export only through the support channel that asked for it. Sign out of the app afterward; in most apps that ends the session, so the cookie in the file stops working. Then turn the setting off again.

What to remove before sharing

Even the sanitized export can contain:

  • Tokens in URLs, such as access_token, code or signed download parameters.
  • Custom headers with credentials, such as X-API-Key.
  • Request bodies with passwords or other form data you typed.
  • Response bodies with names, emails, addresses or tokens.

The HAR sanitizer handles these: auth and cookie headers, headers named like token, secret, key or session, sensitive URL parameters, password, token and card fields in bodies, JWTs, known API key formats and card numbers, with emails and phone numbers half-masked. It is rule-based, so a secret with an unusual name can slip through. Add your own field names and review the result. Our guide on removing sensitive data from a HAR file has a full checklist.

Check the file

Before sending, load the file back in:

  • In Edge, click the Import HAR file button in the Network tool’s action bar, or drag the file onto the Requests table.
  • Or open it in the HAR viewer, which works in any browser without uploading.

Make sure the failing request is there with its status and response. If the file is large, zip it before attaching.

Troubleshooting

The file is empty. DevTools was opened after the problem happened. Open it first, then reproduce.

The request you need is missing. A page load cleared the list. Check Preserve log and record again.

There is no Network tool in the toolbar. Look under the More tools button.

You only need one request. Right-click it, choose Copy, then Copy as cURL or Copy as fetch. These copy the request’s headers too, which can include cookies and tokens, so review them before pasting them anywhere shared.

Same steps as Chrome

Edge is built on Chromium, so if you already know Chrome’s Network panel, Edge’s Network tool will feel familiar. Our Chrome HAR guide covers the same flow with Chrome’s labels, and how to capture network traffic in Chrome goes deeper into filters and throttling, most of which also exist in Edge.

A lighter option for internal bug reports

Midge, a free bug-reporting extension, is built for Chrome. For bugs you report to your own team, it records your screen or takes a screenshot and attaches the technical details on one timeline, so nobody has to export anything. 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.

Frequently asked questions

Does Edge include cookies in a HAR export?

Not by default. Edge’s standard export is sanitized and leaves out Cookie, Set-Cookie and Authorization headers. A full export requires turning on Allow to generate HAR with sensitive data in the DevTools settings.

F12 doesn't open DevTools in Edge. Why?

Edge has a setting that can turn off the F12 shortcut. Use Ctrl+Shift+I instead, or open Settings and more, then More tools, then Developer tools.

Is Edge's HAR export the same as Chrome's?

Very close. Both browsers are built on Chromium and offer the same sanitized and with-sensitive-data options, though Microsoft calls the panel the Network tool and some labels differ slightly.

Is a sanitized Edge HAR file safe to share?

It is safer, but tokens in URLs, passwords in request bodies and personal data in responses can remain. Run it through a HAR sanitizer and check the result first.