Skip to main content
A HAR (HTTP Archive) file is a recording of every network request your browser made while you were using the app. When a page won’t load, a chart stays blank, or something fails with no visible error, a HAR usually tells us exactly which request broke and why — often turning a multi-day back-and-forth into a same-day fix. Send one whenever the problem looks like a loading, timeout, or network failure. For questions about Ana’s answers or query results, a chat URL is more useful than a HAR.
A raw HAR file contains your session cookies, authentication headers, and the full contents of every response — including your data. Anyone who obtains it can potentially act as you. Always use your browser’s sanitized export if it offers one, and only send HAR files to TextQL through the channels below.

​
Record the file

Start recording before you reproduce the problem — a HAR only captures traffic while DevTools is open.
1

Open DevTools

Press F12 on Windows and Linux, or Cmd+Option+I on macOS, then select the Network tab.
2

Enable Preserve log

Check Preserve log so the recording survives page reloads and redirects.
3

Clear existing requests

Click the Clear icon. This drops unrelated traffic and keeps the file small enough to email.
4

Reproduce the issue

Repeat the exact steps that caused the problem. Wait for the error to appear.
5

Export

Right-click anywhere in the request list and choose Save all as HAR with sanitized content. This strips cookies and authorization headers. If you only see Save all as HAR, your browser is older — use it, then sanitize the file yourself.

​
Important: Sanitize sensitive information before sharing

Before sending a HAR file to anyone, it is critical to inspect it for sensitive information. HAR files are plain text files that capture everything your browser sends and receives, which can include:
  • Passwords
  • API keys
  • Authentication tokens and session cookies
  • Personal information you entered into forms (names, addresses, phone numbers, etc.)
To sanitize your file, open it in a text editor (like Notepad, VS Code, or TextEdit) and use the Find and Replace function to search for any sensitive data. Replace these values with a placeholder like [REDACTED] to ensure you don’t expose confidential information.
This matters most in Firefox and Safari, which have no sanitized export — their HAR files include cookies and auth headers exactly as recorded. Until it’s sanitized, treat the file as a credential: send it through the in-app form below, never a public forum or a third-party file host. If you work with regulated data, consider changing your password afterwards.

​
Send it to us

Report it in the app. Click the ? button in the bottom-right corner of app.textql.com, describe what went wrong, and attach the .har file alongside any screenshots. Files up to 30MB are accepted. This is the best route for two reasons: your account, organization, and the page you were on are attached automatically, and credentials are stripped from the file before it is stored — so a file exported from Firefox or Safari is cleaned up even if you skipped the step above.

​
What we redact automatically

On upload, we replace these values with [REDACTED BY TEXTQL] wherever they appear in the file — as a request header, a response header, a query parameter, or a form field: We also empty the parsed cookies arrays that browsers write alongside the raw cookie headers.
Review the file yourself before uploading. The list above is matched by exact name, and it covers credentials only — not your data. These are not touched:
  • Response bodies, including query results and anything else the API returned
  • Raw request bodies, such as a JSON payload posted to an endpoint
  • URLs and query strings, apart from parameters matching a name above
  • Auth headers with non-standard names, such as X-Session-Token or Api-Key
If the traffic you captured includes regulated or sensitive data, open the file and check it before you upload.
Along with the file, tell us:
  • Roughly what time you reproduced the issue. HARs can hold thousands of requests, and a timestamp helps us find the right one quickly.
  • What you were trying to do, and what you expected to happen instead.
  • The chat or page URL where the error occurred.