How to redact logs and JSON before sharing
Bug reports, support tickets and forum posts often need a log or a config. Those files tend to hold customer emails, IP addresses, session cookies and live API keys. The text redaction tool masks them and keeps the file usable.
Steps
- Paste the text or open a .log, .txt, .csv, .json, .jsonl, .xml, .yaml, .toml, .ini or .env file.
- Allow the scan to find emails, phone numbers, IPs, card numbers, keys and tokens.
- Add your own terms under "Always redact": internal host names, customer IDs, project code names.
- Pick a style. "Black out" keeps each line the same length, which helps with aligned columns. "Replace with label" makes the result easier to read.
- Download the result.
Valid output
JSON and XML stay parseable: quotes, brackets and tags are untouched, and a redacted JSON number turns into a string. YAML and .env files keep their keys, so a reader can still see which setting held the secret.
What to look for
- Authorization headers, bearer tokens, cookies and signed URLs.
- Connection strings with a password inside.
- Email addresses and user IDs in request paths.
- Client IP addresses and device identifiers.
- Stack traces with home directory paths that include a user name.
Rotate leaked secrets
If a key or password was already posted somewhere, redacting the copy you share next does not undo the leak. Revoke the key and issue a new one.