Skip to main content

Generating a HAR File for Troubleshooting

Use these steps to record network logs so Support can diagnose technical or performance issues

Written by Elaine
Updated today

Support may request a HAR (HTTP Archive) file to help diagnose technical issues. This file records all network requests between your browser and our servers, allowing us to identify failed requests, slow loading times, or authentication errors.

Why is this needed?

  • Detailed Logs: Captures headers, cookies, and response data.

  • Error Tracking: Pinpoints the exact moment a request fails.

  • Performance: Identifies bottlenecks in asset loading or API calls.

Instructions by Browser

Google Chrome

  1. Open the page where the issue occurs.

  2. Click > More Tools > Developer Tools.

  3. Select the Network tab.

  4. Ensure the record button (top-left) is red.

  5. Check the Preserve log box.

  6. Click the Clear (crossed circle) icon to remove old logs.

  7. Reproduce the issue.

  8. Click the Export HAR (downward arrow) icon to save the file.

Mozilla Firefox

  1. Open the page where the issue occurs.

  2. Open the Tools menu > Web Developer > Network.

  3. Reproduce the issue.

  4. Right-click anywhere in the list of requests and select Save All As HAR.

Apple Safari

  1. Enable the Develop menu: Safari > Settings > Advanced > Show features for web developers.

  2. Go to Develop > Show Web Inspector.

  3. Select the Network tab.

  4. Reproduce the issue.

  5. Click Export in the top-right corner to save the HAR file.

Security & Privacy

IMPORTANT: HAR files record sensitive data, including session cookies, passwords, and personal information submitted while the recording is active.

  • Sanitization: We recommend using the Cloudflare HAR Sanitizer to strip sensitive tokens before sharing.

  • Secure Sharing: Do not post HAR files in public forums. Send them directly to Support via your active correspondence.


Sending the File

  • Compress: HAR files can be large. Please Zip or compress the file before attaching it to your email.

  • Naming: Give the file a descriptive name (e.g., Issue_Description_Chrome.har) instead of using the default URL name.

  • Console Logs: If possible, include a screenshot of any red error text found in the Console tab of your developer tools alongside the HAR file.

Did this answer your question?