Skip to content

HAR sanitizer

Remove cookies, tokens, passwords and card numbers from a HAR file before you share it. Everything happens in your browser.

or drop it here. Your file never leaves your browser.

How to sanitize a HAR file

  1. Choose your HAR file. Pick the .har file exported from the Network panel. It is processed in your browser and never uploaded.
  2. Add your own field names. Optional: list extra field names that are private in your app, such as customerRef.
  3. Check the summary. See how many headers, cookies, URL parameters and body fields were redacted.
  4. Download the sanitized file. Share the .sanitized.har file instead of the original.

Why HAR files need cleaning

A HAR file records every request your browser made, with full headers and bodies. That usually includes your session cookie, bearer tokens and whatever you typed into forms. Anyone with the file can often sign in as you. Read the full list of rules on our security page, or inspect the result in the HAR viewer.

Frequently asked questions

What does the HAR sanitizer remove?
Authorization and cookie headers, any header named like token, secret, key or session, sensitive URL parameters, password, token and card fields in request and response bodies, JWTs, API keys and card numbers anywhere in the file. Emails and phone numbers are half-masked.
Is my file uploaded?
No. Sanitizing happens in your browser with the same open redaction rules the Midge extension uses. Nothing is sent to a server.
Doesn't Chrome already sanitize HAR exports?
Recent versions of Chrome can export a HAR without cookies and authorization headers. Tokens in URLs, passwords in request bodies and secrets in responses usually remain. This tool checks those too.
Can it miss a secret?
It follows rules, so a secret with an unusual name and format may not be recognized. Add your own field names, and open the result in the HAR viewer to double-check before sharing.