Free Log Redactor

Before you paste an error log into an AI chat or a support ticket, strip out the emails, tokens and passwords hiding in it — locally, in seconds, without uploading anything.

Privacy Level 1 — 100% local: your files never leave your browser

Redaction is pattern-based, not a guarantee. This tool catches the common shapes of secrets — emails, IPs, API keys, tokens, key = value secrets, credentials in URLs, Luhn-checked card numbers, private-key blocks and home-directory usernames. A secret in an unusual format can slip through, so read the redacted text once before you share it. The same secret always gets the same placeholder (for example, the same email is always [EMAIL_1]), so the log stays readable.

1. Paste your log

Or choose a log file (.log / .txt)

Log or config text

2. What to redact

Email addresses Replaced with [EMAIL_1], [EMAIL_2]…

IP addresses (IPv4 and IPv6) Times like 12:30:45 are left alone.

API keys, tokens, JWTs and key = value secrets Bearer tokens, GitHub / Stripe / AWS keys, api_key and password values.

Credentials inside URLs https://user:pass@host becomes https://[REDACTED-CREDENTIALS]@host.

Credit-card numbers Only numbers that pass the Luhn checksum are masked, so order IDs survive.

Home-directory usernames /home/jane/ and C:\Users\jane\ become [USER_1].

Custom terms to redact (one per line, optional)

Something not working?

Tell us what went wrong — it helps us fix the tool. Only what you type below is sent; your log never leaves your device. Please describe the pattern in general terms — do not paste the secret itself.

Need more power? Meet Log Redactor Pro

One-time payment. Yours forever. No subscription.

$29

single payment · lifetime updates included

Feature	Free	Pro
Emails, IPs, keys, tokens, card numbers, private keys	Yes	Yes
Custom terms and consistent placeholders	Yes	Yes
Saved redaction profiles per project	—	Yes
Batch-redact a folder of logs	—	Yes
Side-by-side diff of original vs redacted	—	Yes

Get Pro — $29 one-time

Frequently asked questions

Is my log uploaded?

No. Redaction runs entirely in your browser. If you use an AI chat afterwards, only the redacted text you paste there leaves your device — which is the whole point.

What exactly gets masked?

Emails, IPv4 and IPv6 addresses, Bearer tokens, JWTs, GitHub / Slack / Stripe / AWS style keys, values after api_key / password / secret / token labels, credentials embedded in URLs, private-key blocks, Luhn-valid card numbers, home-directory usernames, and any custom terms you add. Use the checkboxes to turn categories off.

Will it break my log's structure?

It tries not to. The same secret always becomes the same placeholder, key names and quoting are kept, and hosts in URLs are kept — only the secret part is replaced. Timestamps, log levels and stack traces are untouched.

Can I trust it completely?

No tool can. A secret written in a format no pattern recognizes (a custom token shape, a password split across lines) will survive. Always read the redacted output once before sharing, and rotate any secret you suspect already leaked.

Why are some numbers left alone?

Card masking requires the number to pass the Luhn checksum, and IP masking requires valid octets — otherwise order IDs, version numbers and times like 12:30:45 would be wrongly masked and the log would become unreadable.