Log Sanitizer & Secret Redaction
Sanitize logs and JSON before sharing them. Detects and redacts emails, IPs, JWTs, bearer tokens, API keys, and passwords in your browser — nothing is uploaded.
Redaction rules
Choose which categories are replaced when you redact. Detection always shows all matches.
Custom field names
One field name per line. Matching JSON keys are replaced with [REDACTED_CUSTOM].
Recent Payloads
Payloads you format will appear here for quick access. Stored locally in your browser.
What this tool does
Paste a log, JSON payload, or webhook body, see which sensitive values were found, and redact them before you share it. Detection covers emails, IPv4 addresses, JWTs, Bearer tokens, and values held under credential-style key names such as api_key, token, secret, client_secret, and password. Structure stays intact, so the sanitized copy is still readable and still parses.
Privacy
Redaction runs entirely in your browser. Nothing is uploaded, logged on our servers, or sent to third-party APIs.
Use cases
- Sanitize a log before attaching it to a support ticket
- Redact API keys and tokens from an API response before pasting it in Slack
- Remove passwords and customer emails from a debug payload
What detection does not catch
Pattern matching finds the shapes it knows — emails, IPv4 addresses, JWTs, Bearer tokens, and credential-style key names. Vendor-specific formats, connection strings, internal hostnames, and customer identifiers are not recognised. How to sanitize logs before sharing them has the measured detection table and explains why redaction is not revocation.
Need additional detection patterns or custom redaction rules? Suggest a feature →
Guides for this tool
- Sanitize logs before sharingPasting a log into a ticket or Slack can hand over live credentials. What to remove, what automated detection reliably catches, and why redacting a copy does not undo an exposure.