The steps
- Open developer tools on the page that has the problemPress F12, or Ctrl+Shift+I (Windows, Linux) or Cmd+Option+I (Mac). In Safari, turn on developer features first (see the Safari steps).
- Open the Network tabChrome, Edge and Safari call it Network. Firefox calls it Network Monitor (Ctrl+Shift+E, or Cmd+Option+E on a Mac).
- Keep the log and clear old requestsTurn on Preserve log (Persist Logs in Firefox) so requests survive reloads and redirects, then clear the list so the file only holds what you are about to record.
- Reproduce the problemReload the page if the problem happens on load, then repeat the clicks that fail. Stop as soon as the problem has happened.
- Export the HAR fileIn Chrome and Edge use Export HAR (sanitized). In Firefox use Save All As HAR. In Safari use Export. Save the file somewhere you can find it.
- Open it in HAR PlaygroundDrop the file on HAR Playground to see the failing, slow and insecure requests. Nothing is uploaded, because the analysis runs in your browser.
Steps for each browser
| Browser | Where the export is | Removes cookies and auth headers? |
|---|---|---|
| Chrome | Network tab, Export HAR (sanitized) | Yes, by default since Chrome 130 |
| Firefox | Network Monitor, settings menu, Save All As HAR | No sanitized option. Redact before sharing |
| Edge | Network tool, Export HAR (sanitized) | Yes, by default |
| Safari | Web Inspector, Network tab, Export | No sanitized option. Redact before sharing |
Before you share the file
A HAR file can hold cookies, tokens and personal data. Run it through the HAR sanitizer first, or read what a HAR file contains to see what to look for.