Why this tool is useful
Reduce the chance of exposing an active session, bearer token, personal query value or captured form submission when a HAR must be attached to a bug or support ticket.
Local File Tools · runs locally
Private HAR Credential and Privacy Sanitizer
Create a safer HAR copy by redacting authorization, cookie, API-key and token fields, query values and optional captured bodies locally before sharing a support trace.
Ready. Your working data stays in this browser.
Files and capture streams stay on this device. Processing uses browser APIs only; nothing is uploaded to YTSave, the media API or a proxy. No server copy is created, stored or left to delete. The file picker is cleared when processing starts, and disposable worker memory is destroyed after completion or cancellation. Preview and generated-output memory is released when you clear the tool or leave the page.
How it works
The browser edits a parsed copy: recognized credential headers and cookie arrays are always redacted, URL and queryString values follow the selected policy, and body removal is explicit.
Practical example
Open an authenticated API trace, keep the default all-query and body-removal rules, review the redaction counters and download a .sanitized.har file for a support case.
Validation
The calculation is deterministic and explains validation errors instead of silently changing invalid input.
Privacy boundary
Input and output remain in this tab. Copy and download happen through browser APIs without a server upload.
Result passport
Every run reports its tool mode, timestamp and input/output size so transformed data can be audited.