---
title: "Share a HAR file without handing over a session | Proofline"
description: "A HAR file is the most complete browser evidence you can send, and it can carry session cookies, tokens and personal data."
url: https://proofline.sh/learn/share-har-file/
---

[Learning center](/learn/)

# Share a HAR file without handing over a session

A HAR file is the most complete browser evidence you can send, and it can carry session cookies, tokens and personal data. Chrome's default export removes some of that, so send the smallest file that answers the question.

Data leaks The Proofline team November 20, 2026 4 min read

## What a HAR file contains

A HAR file is JSON. For each request it holds the URL, method, headers, query string and body, and for each response the status, headers, timing and often the body. [Network panel: export requests](https://developer.chrome.com/docs/devtools/network/reference)

Since Chrome 130, the Network panel's export offers two forms: `Export HAR (sanitized)`, the default, and `Export HAR (with sensitive data)`, available after you turn on **Allow to generate HAR with sensitive data** in DevTools' Network preferences. Chrome's documentation describes the default export as excluding sensitive information _such as_ `Cookie`, `Set-Cookie` and `Authorization` headers. [Chrome DevTools: HAR export options](https://developer.chrome.com/docs/devtools/network/reference) · [Chrome 130 DevTools changes](https://developer.chrome.com/blog/new-in-devtools-130)

That still leaves a lot in the file.

| What | Removed by the default export? | Why it matters |
| --- | --- | --- |
| `Cookie`, `Set-Cookie`, `Authorization` headers | Yes | Session and API credentials |
| Tokens in URLs, such as `?token=` or `#access_token=` | No | Anyone with the URL may be able to use the token |
| Request bodies, such as login forms, search terms and profile edits | No | Passwords, personal data, payment details |
| Response bodies, such as account pages and API results | No | Personal and business data |
| Custom auth headers, such as `X-Api-Key` | Not by the headers named above | Credentials the export does not recognize |

## Two reasons to send a HAR, and what each needs

| The receiver needs | Send |
| --- | --- |
| Timing, ordering or redirect chains | A HAR filtered to the relevant requests, or a waterfall screenshot with URLs and times |
| The content of one request and response | That request only, as a curl command with credentials replaced, and the response's status, headers and the relevant part of the body |

Most bug reports need the second. A single request copied with **Copy as cURL** shows the receiver exactly what was sent and leaves out everything else the session did. The [curl replay guide](/learn/replay-browser-request-curl/) covers copying it.

When ordering matters across many requests, such as a [race between responses](/learn/stale-search-results-race/) or a [chunk loading failure](/learn/chunk-load-error-after-deploy/), a HAR is the right format. Filter the Network panel first, then use `Copy all listed as HAR (sanitized)` or the matching save option, so only the filtered requests go into the file. [Copy and save options](https://developer.chrome.com/docs/devtools/network/reference)

## Check the file before sending it

1.  **Reproduce with a test account** when you can, so the file holds no real user's data.
2.  **Search the file** for the values you know are sensitive: the account's email address, the session cookie's name, `token`, `key`, `password`, `secret` and `bearer`.
3.  **Replace values, not keys.** Change `"value": "eyJhbGciOi…"` to `"value": "TOKEN_REMOVED"` so the receiver still sees which header or field was present.
4.  **Remove response bodies you do not need.** A HAR viewer still shows status and timing without them.
5.  **Say what you changed** in the report, so the receiver does not chase a missing header.

If a credential was in the file before you noticed it, end that session by logging out, or rotate the key, instead of only editing the file. Copies may already exist in a ticket system or chat history.

## Worked example: a support ticket that needed one request

This example is fictional. A customer reports that saving a profile fails with "Something went wrong" and offers to send a HAR file of their whole session.

The support engineer asked for the failing request instead. The customer's Network panel showed `PATCH /api/profile` returning `422` with `{"error":"phone_format","field":"phone"}`. The request body contained the customer's full address and phone number.

The report said: _`PATCH /api/profile` returns `422 phone_format` for a phone number with a leading `+` and spaces. Request body fields other than `phone` removed; the phone value replaced with the format `+NN NNN NNNNNNN`._ The engineer had the deciding observation and the customer's personal data stayed out of the ticket. A full HAR would have carried the address, the session's other requests, and any tokens in their URLs.

## What to put in the report

-   Which requests the file or excerpt covers, and why.
-   How it was exported: default, with sensitive data, or copied per request.
-   What you removed or replaced.
-   Whether a test account was used.

## Questions

### Is the default Chrome export enough on its own?

It removes the credential headers Chrome names, and leaves URLs, bodies and other headers. For many requests that is fine, but you need to check the file for your own application's tokens and data before sending it.

### Can I open a HAR file to check it?

Yes. It is JSON, so a text editor or `jq` works. Chrome's Network panel can also import a HAR file, which shows it as a request list. [Import HAR files](https://developer.chrome.com/docs/devtools/network/reference)

### Do other browsers export HAR files the same way?

Firefox and Safari also export HAR files from their network tools. Their options for removing credentials differ, so check the file the same way whichever browser produced it.

Return to the [method for browser bug reports](/learn/browser-bug-report-evidence/) for the other symptoms in this collection.

## One month of free code review.

New organizations get one calendar month of hosted code review for private and public GitHub repositories. No card or cloud connection required. [Eligibility and fair-use terms](/free-code-review/).

[Start free with GitHub](https://proofline.sh/orgs/plan?offer=free_month)

## Related reading

-   ### [Turn a browser symptom into a bug report another engineer can act on](/learn/browser-bug-report-evidence/)
    
    Network outages The Proofline team November 20, 2026 7 min read
    
-   ### [Browser or server? Replay the failing request outside the page](/learn/replay-browser-request-curl/)
    
    Network outages The Proofline team November 20, 2026 5 min read
