HAR Sanitizer & Token Redactor

Strip live session cookies, Bearer JWTs, API keys, secret query parameters, and email PII from Chrome/DevTools .har captures locally before sharing.

Zero-Upload Guarantee:Processed 100% locally in your browser via WebAssembly & client-side JavaScript. Disconnect Wi-Fi and it still works.(Includes a synthetic 3-request checkout capture with mock secrets)
Drop a .har capture file here
Parses HTTP requests, timings, cookies, and auth tokens completely inside your browser tab.

What Gets Scrubbed from a Raw HAR Capture

An HTTP Archive (.har) capture is plain JSON containing every request and response recorded while a browser tab reproduced a bug. Unfortunately, attaching raw HAR logs to an issue tracker, vendor support ticket, or team Slack channel is one of the fastest ways to leak live production credentials: even after you close DevTools, the JSON still holds valid Cookie headers, Set-Cookie session grants,Authorization: Bearer ... JWTs, and password reset tokens.

This browser-only sanitizer never uploads your capture. It deep-clones the parsed HAR JSON in memory and runs five configurable passes with an itemized audit trail:

QA Workflow & Local CLI Alternative

  1. Click Try sample .har (with mock secrets) to verify the redaction audit log and toggle checkboxes, or drop your exported Chrome / Firefox / Edge .har file above.
  2. Review the Redaction Audit tab to confirm which entries matched, then spot-check theRequests & Safe cURL tab to copy sanitized reproducible curl commands directly into bug tickets.
  3. Download the cleaned *-sanitized.har JSON file safely from local memory.

If you automate log scrubbing inside a CI pipeline, you can also strip standard headers via jq:

# Minimal jq example: scrub Authorization & Cookie request headers (note: does not scan bodies/URLs)
jq '(.log.entries[].request.headers[] | select(.name | test("^(authorization|cookie|x-api-key)$";"i"))).value = "[REDACTED]"' raw.har > clean.har

Limitations & Spot-Check Guidance

Frequently Asked Questions

Why must you sanitize a HAR file before attaching it to Jira, GitHub, or Slack?

Browser DevTools exports every request header, response header, and cookie verbatim inside a .har JSON file. Anyone who opens an unsanitized HAR can replay your active session cookies, Bearer JWTs, or OAuth API keys until they expire.

Does the sanitizer preserve timing, HTTP status codes, and API error bodies needed for debugging?

Yes. Request URLs (minus sensitive query parameters), HTTP methods, status codes, timings, and non-secret JSON fields stay intact so engineers can still see the exact 4xx/5xx failure and payload structure.

Can regex-based sanitization catch every proprietary custom secret?

Automated rules handle standard Auth/API key headers, Cookies, common secret query names, JWTs, known provider token prefixes, and email addresses. Always review the Sanitized Output Preview tab when an application puts custom tokens inside non-standard header names or opaque binary strings.

Are generated cURL commands also scrubbed before copying?

Yes. Each request row builds its reproducible cURL snippet from the already-sanitized HAR entry, with single quotes shell-escaped and HTTP/2 pseudo-headers stripped.

Live · Offline

HAR Waterfall & Status Analyzer

Inspect captured HTTP entries locally, filter 4xx/5xx failures, sort slowest calls by latency, and check hosts.

Open tool
Live · Offline

HAR Request to cURL Converter

Select any API request captured in a .har log and generate a shell-escaped cURL command with optional token masking.

Open tool
Live · Offline

Parquet Viewer & SQL Inspector

Open .parquet files locally, inspect column schema & row groups, run SQL queries, and export CSV/JSON without uploading.

Open tool
Live · Offline

Parquet to CSV Converter

Select columns from local Apache Parquet files and export clean RFC-4180 CSV directly in browser memory.

Open tool