How-to guide
How to record a HAR file in Chrome
To record a HAR file in Chrome, open DevTools (F12), go to the Network panel, turn on Preserve log, reproduce the problem, then click Export HAR to save the file. It takes a couple of minutes. If you'd rather not open DevTools, Browser Support Kit by URLflows, a free Chrome extension, records one from a button on your toolbar.
What a HAR file is
A HAR file (short for HTTP Archive) is a recording of what your browser sent and received while you used a site: every address it asked for, how the site answered, how long each step took, and which requests failed. It's a text file whose name ends in .har.
Support teams ask for one because it shows exactly where things went wrong, which is often hard to put into words or a screenshot.
Because it's a full recording, a HAR file can also contain private things: the pages you opened, what you typed into forms, and the cookies and sign-in tokens that keep you logged in. Someone holding those could act as you on that site. The steps below keep that in check.
Before you start
- Know how to make the problem happen. A short recording is easier to read and holds less.
- Use one tab. Open the page with the problem and do everything in that tab, the one you'll record.
- Close what you don't need. Close other tabs and windows, especially ones signed in to other accounts, so nothing unrelated gets mixed in.
- Sign out first if signing in is the problem. That way the recording catches the whole sign-in.
Record a HAR file with Chrome's DevTools
DevTools is the set of developer tools built into Chrome. You only need one part of it, the Network panel.
- Open the page with the problem in Chrome.
- Open DevTools: press F12 or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on a Mac. You can also open Chrome's three-dot menu and choose More tools → Developer tools.
- Click the Network tab at the top of DevTools.
- Turn on Preserve log, so the recording keeps going when the page reloads or moves to another page. If the support team asks for it, turn on Disable cache too, so the browser loads everything fresh instead of using copies it saved earlier.
- Check the round record button at the top left of the panel. It should be red, which means it's recording. If it's gray, click it once.
- Click the clear button next to it (a circle with a line through it) to empty the list, so the file holds only what you're about to do.
- Reproduce the problem: reload the page, click the button that fails, submit the form. Keep DevTools open the whole time, because it records only while it's open.
- When the problem has happened, click Export HAR, the downward arrow in the bar at the top of the Network panel, and save the file.
Since Chrome 130, that button saves a sanitized file by default, labeled Export HAR (sanitized). It leaves out the Cookie, Set-Cookie and Authorization headers, the parts of each request that keep you signed in. That's the right file for most support requests.
If the support team specifically asks for the full file, open DevTools' settings (the gear icon), turn on Allow to generate HAR with sensitive data under Preferences → Network, then press and hold the export button and choose Export HAR (with sensitive data). Only do this when they ask.
Record a HAR file with Browser Support Kit
If DevTools feels like a lot, Browser Support Kit puts a HAR recorder one click from your toolbar. It's free, forever, with no account to create.
- Install Browser Support Kit and pin it to your toolbar.
- Open the page with the problem.
- Click the Browser Support Kit icon, then HAR file for support under Support.
- Press Start recording. A banner stays on the page while it records, and Chrome shows its own bar saying the browser is being debugged.
- Reproduce the problem in the same tab.
- Open the panel again and press Stop and save.
The file goes to your Downloads folder, with a summary of what it holds. Cancel recording stops without saving anything. Browser Support Kit doesn't send the recording anywhere: it stays on your computer until you share it.
Chrome shows the debugging bar because it only lets an extension see a tab's network traffic through its debugger. Browser Support Kit attaches it to that one tab while you record, and detaches it when you stop or cancel. If you close the bar yourself, the recording stops without saving, so start again.
Support teams often ask for a page's console errors as well, the error messages the page reports behind the scenes. Console errors, also under Support, records them and copies them for your ticket. Web developers who want more can use DevTools+ by URLflows, whose Record a HAR file tool includes response bodies in the file.
Share it safely
- Send it only to the support team that asked, through their own ticket, upload page or secure link. Don't post it in a public forum, a group chat or a shared folder.
- Treat even a sanitized file as private. Sanitizing is aimed at the sign-in headers. Assume the rest of the recording, such as the pages you opened and anything you typed into a form, is still in it.
- Send the full file only when asked. If you did send one, signing out of that site afterward is a sensible precaution.
- Delete your copy once the problem is solved, and empty the trash.
Common questions
- Does this work in Edge, Brave or another browser? Edge and other Chromium-based browsers have the same developer tools, so the steps are nearly identical. Browser Support Kit installs in Chrome, Edge, Brave, Opera, Arc and Vivaldi from the same Chrome Web Store listing. There's no Firefox or Safari version.
- I'm on a Mac. Press Cmd+Option+I to open DevTools, or use Chrome's menu. Everything else is the same.
- The file is huge. That's normal for a busy page. Clear the list just before you reproduce the problem, and stop once it has happened. If the support team's upload has a size limit, ask them whether a zipped file is fine.
- The file is empty or doesn't show the problem. DevTools records only while it's open, so open it before you reproduce the problem, check the record button is red, and keep Preserve log on if the page reloads. With Browser Support Kit, reproduce the problem in the tab you started recording in, and press Stop and save rather than closing Chrome's debugging bar.
- Browser Support Kit does nothing on this page. Chrome keeps extensions out of
chrome://pages, the Chrome Web Store and other internal pages. Use DevTools there.
Related guides
See Record a HAR file for support for more on the recorder, and pair it with a page's console errors. Privacy & permissions explains how the debugger permission is used, and Troubleshoot common issues covers the debugging bar and pages a tool can't run on.