What is a HAR file?
An HTTP Archive, or HAR, is JSON that records network requests made by a browser or another HTTP client. It can include URLs, timings, methods, response codes, headers, cookies, request payloads, and response content. That detail makes HAR useful for debugging performance and failed requests—and dangerous to share without review.
Sensitive information commonly captured
Authorization, proxy authorization, API-key, token, and session headers.
- Request and response cookies, including authenticated session values.
- Query parameters containing identifiers, search terms, email addresses, or tokens.
- Form fields and JSON request bodies containing personal data or passwords.
- Response bodies containing account details, internal configuration, or private API data.
This tool can redact those broad categories and shows a request summary without rendering response content.
Safe sharing workflow
- Reproduce only the minimum necessary action before exporting the HAR.
- Close unrelated authenticated tabs where practical.
- Enable conservative redaction, including both request and response bodies.
- Download the sanitized copy and search it again for names, domains, email addresses, IDs, tokens, and private hosts.
- Share only through the intended support channel and delete temporary copies when the case is complete.
Sanitizer limitations
Automatic matching cannot recognize every secret. Credentials may use product-specific header names or appear inside URL paths, filenames, compressed bodies, binary data, or ordinary-looking JSON fields. Redaction also reduces diagnostic detail, so a support engineer may ask for a smaller targeted capture instead.
Files are limited to 25 MB to avoid exhausting browser memory. Processing happens locally and MiniUtil does not receive the archive. Use the JWT Decoder to inspect token structure without verification, the JSON Formatter for ordinary JSON, or the Cache-Control Header Builder when debugging caching behavior.