How It Works Under the Hood
The inspector parses `.har` (HTTP Archive 1.2 JSON) files completely inside browser RAM, computes timing summaries (total transfer bytes, status buckets `2xx`/`4xx`/`5xx`, slowest endpoints), and runs a configurable multi-pass deep redactor over request headers, response `Set-Cookie` headers, `.cookies` arrays, query string parameters (`token`, `code`, `api_key`, `signature`), and optional JSON password/secret keys.
Step-by-Step Instructions
Drop a `.har` recording exported from Chrome, Edge, or Firefox DevTools ("Save all as HAR with content").
Review the summary metrics (Total Requests, Total KB, Slowest Request, Failed 4xx/5xx entries) and searchable waterfall table.
Verify Redaction Rules (Auth/Cookie headers, query secret params, custom header names, optional JSON body secret masking).
Click Download Redacted .har to save a cleaned `.har` file and inspect the Redacted Secret Count summary.
Key Features & Performance
- Never uploads `.har` files containing live session cookies to external analysis servers
- Scrubs `Authorization`, `Proxy-Authorization`, `Cookie`, `Set-Cookie`, `X-API-Key`, and `.cookies[]` arrays
- Redacts URL query secrets (`token`, `access_token`, `key`, `code`, `auth`, `sig`) consistently across `request.url` and `queryString`
- Supports custom user-specified header names (e.g., `X-Internal-Secret`)
- Interactive request explorer shows method, status, duration (`ms`), size, and URL safely
Methodology, Formulas & Technical Standards
Each HAR entry under `log.entries[]` is cloned non-destructively inside memory. Header/cookie matching is case-insensitive (`header.name.toLowerCase()`). Query parameter scrubbing parses URL search params cleanly and updates both `request.url` and structured `request.queryString[]` entries with `[REDACTED]`.
Common Real-World Use Cases
- Scrubbing session cookies and OAuth tokens before attaching a `.har` trace to a vendor support ticket or GitHub issue
- Auditing large single-page-app loads offline to identify slow third-party calls or oversized JSON/image payloads
- Finding unexpected `401`/`403`/`500` responses during QA reproduction sessions
- Sharing anonymized API debug logs safely across Slack or Jira
Worked Examples & Edge Cases
Sanitizing Bearer Auth & Query Token
Header: Authorization: Bearer eyJhbG... | URL: https://api.site.io/dl?token=sec_99&id=5
Header: Authorization: [REDACTED] | URL: https://api.site.io/dl?token=[REDACTED]&id=5
Non-secret query flags like `id=5` remain intact so engineers can still trace request parameters.
Custom Enterprise Header Scrubbing
Custom Headers: x-tenant-key, x-csrf-token
Matching custom headers replaced with `[REDACTED]` across every request/response entry.
Redaction summary reports total headers, cookies, query keys, and body keys scrubbed.
Limitations, Scope & Accuracy Notes
- • Custom proprietary auth tokens embedded inside plain-text HTML bodies or free-form non-JSON strings are not automatically recognized unless inside headers, cookies, query secret keys, or matching JSON keys.
- • Always quickly grep your downloaded `.har` file for highly specific custom strings (like a unique personal password) after redaction if dealing with ultra-sensitive incidents.
Local Browser Processing & Privacy
Traditional web converters upload your documents, snippets, or media files to remote servers. HAR Trace Inspector & Secret Redactor runs inside your browser tab:
Your input text and files are processed locally without uploading payloads to a processing server.
Microdeck does not log or store the files or inputs you paste into tool workspaces (normal static hosting/CDN requests still load page assets).
Working outputs stay in your browser tab and are released when you reset the tool or close the tab.
Frequently Asked Questions
Why should I NEVER upload an unredacted .har file to vendor support or online viewers?
Browser `.har` exports frequently record every `Cookie`, `Set-Cookie`, and `Authorization: Bearer` header in plain text, giving anyone holding the `.har` direct session-hijacking access.
Does this redactor strip `Set-Cookie` headers inside server responses too?
Yes. Both outgoing `Cookie` / `Authorization` headers and incoming `Set-Cookie` / `.cookies[]` arrays are scrubbed.
Will redacted `.har` files still open in Chrome DevTools Network panel?
Yes. We preserve standard HAR 1.2 schema structure (`log.entries`, timings, headers, queryString) while replacing only sensitive values with `[REDACTED]`.
Can I view response bodies inside the built-in table?
The built-in inspector focuses on summary timings, status filters, URLs, and redaction audit stats to keep rendering snappy even on 20 MB HAR files.
Explore Related Micro-Tools
cURL to Fetch, Axios, Python & Go Converter
Parse cURL commands offline into clean JavaScript Fetch, Axios, Python requests, or Go net/http code
CSV & Log PII Data Anonymizer
Mask, hash, or redact Emails, Phones, IPs, Cards & API tokens before sharing with AI
Offline Zero-Log JWT & Hash Inspector
Decode JSON Web Tokens and check expiration with 100% privacy