When do you need a HAR file?
A HAR (HTTP Archive) file is a recording of every network request your browser makes while you use a page. When you report a bug that only shows up in the browser — a page not loading, a button doing nothing, data displaying incorrectly — the support and engineering teams often need a HAR file to see exactly what the browser asked for and what it got back. Attaching a HAR to your ticket dramatically shortens the debug time.
This guide walks through recording a HAR in Google Chrome in about 60 seconds.
Quick summary
Open Chrome DevTools (F12 or right-click → Inspect).
Click the Network tab.
Make sure the record dot (●) is red: Chrome is now recording.
Reproduce the bug in the same tab.
Right-click any row in the Network panel → Save all as HAR with content.
Attach the downloaded
.harfile to your support ticket.
Full walkthrough
Step 1: Open Chrome DevTools
On the page where the bug happens, right-click anywhere and choose Inspect. Or just press F12 (Windows/Linux) / Cmd + Option + I (macOS).
Step 2: Click the Network tab
At the top of the DevTools panel, click Network. This is where every request the page makes will be logged.
Step 3: Confirm recording is ON, then reproduce the bug
The round dot at the top-left of the Network panel should be red (●): that means recording is active. If it's grey, click it once to start.
Now do the exact thing that triggers the bug: click the broken button, submit the form, load the page that fails, etc. You'll see requests appear in the list as they happen.
Step 4: Save as HAR
Once you've reproduced the bug, right-click any row in the Network list and choose Save all as HAR with content. Chrome will download a .har file to your Downloads folder.
Step 5: Attach the .har file to your ticket
Open your support ticket (or your reply email) and attach the .har file. That's it: the engineering team can now replay exactly what your browser saw.
Full 5-step walkthrough (animated, 5 seconds)
Tips and gotchas
The HAR contains real data. Any cookies, auth tokens, form values, or personal info that were part of the requests are inside the file. Don't post HAR files publicly — attach them to your Jira ticket where access is controlled.
Reproduce the bug AFTER DevTools is open. Requests that happened before you opened DevTools are not captured.
Use "Preserve log" if the bug involves a page redirect or reload. Without it, the log clears on navigation.
HAR files can be big (several MB is normal). If your ticket system rejects the upload, zip the file first.
Firefox and Edge have the same feature: same shortcut (F12), same Network tab, same "Save All As HAR" right-click option.
Need help?
If any step above is confusing or the file won't download, ping the Customer Support Engineering team in Slack — we'll walk you through it live.