Skip to main content
When troubleshooting issues, our support team may ask you to provide a HAR (HTTP Archive) file. This file captures all network requests made by your browser, helping us diagnose problems more effectively.

​
What is a HAR file?

A HAR file is a JSON-formatted log of your browser’s network activity. It records all HTTP requests and responses, including headers, cookies, timing information, and response content. This data helps identify issues like failed API calls, slow responses, or unexpected errors.
HAR files contain sensitive data including cookies, authentication tokens, and page content. Before sharing, consider using a HAR sanitizer to remove sensitive information.

​
Generating a HAR file

  • Chrome
  • Firefox
  • Safari
  • Edge
  1. Open Chrome and navigate to the page where the issue occurs
  2. Press F12 or right-click and select Inspect to open Developer Tools
  3. Click the Network tab
  4. Ensure the record button (red circle) in the top-left is active
  5. Check Preserve log to keep logs across page navigations
  6. Click the clear button (circle with a line) to remove existing logs
  7. Reproduce the issue
  8. Right-click anywhere in the network log and select Save all as HAR with content
  9. Save the file to your computer

​
Capturing console logs

In addition to HAR files, browser console logs can provide valuable debugging information.
  • Chrome/Edge
  • Firefox
  • Safari
  1. Open Developer Tools (F12)
  2. Click the Console tab
  3. Right-click in the console and select Save as to export logs, or take a screenshot of any errors

​
Sending HAR files to support

Before sending your HAR file:
  1. Rename the file - HAR files often use the page URL as the filename, which can trigger spam filters. Use a descriptive name like dynamic-issue-har.har
  2. Compress the file - HAR files can be large. Zip or compress the file before sending
  3. Remove sensitive data - Consider using a HAR sanitizer to strip cookies and tokens
Share the HAR file with our support team via Slack in the #bug-report channel, or attach it to your support ticket.