Does the tool guarantee that no secrets remain?

No. Detection is best-effort and can miss secrets, encoded values, unusual field names, multiline structures, and personal data. Review the output manually before copying or downloading it.

Why did it remove the rest of a line or the remaining log?

A recognized sensitive assignment hides the rest of its line. If its value is missing, starts with an object or array, or has an unclosed quote, the remaining log is hidden conservatively. An unclosed PEM private-key block also hides the remaining log. This can remove harmless context and break JSON syntax.

Are the original logs stored or uploaded?

The tool does not upload or save log text or exact-text entries. Originals remain visible in the input area until cleared. Only the redacted preview is used by the copy and download actions.

Does exact-text matching support regex or ignore case?

Neither. Each non-empty line is a case-sensitive literal match, with spaces preserved. Entries need at least three characters. There can be at most 100 distinct entries and 10,000 characters in the list.

Log Redactor

Runs locally in your browser. Inputs are not uploaded or saved. Original log text stays visible here; do not paste it while screen sharing.

Original log (maximum 500,000 characters)Additional exact text to redact (optional, one case-sensitive value per line)

Exact-text entries are literal, not regex. Minimum 3 characters per entry; maximum 100 distinct entries and 10,000 characters total. Blank lines are ignored; spaces are significant.

Sensitive fields redact the rest of their line, so the output may no longer be valid JSON. An incomplete quoted, empty, or object-valued sensitive field, or an unclosed private-key block, hides the remaining log. Detection can miss secrets and can redact harmless text. It is not an anonymization guarantee.

Redacted preview

Paste a log, choose the patterns, and redact. Review the result before sharing it.

Output (manual review required)

Only the preview is copied or downloaded. Check for internal hostnames, customer IDs, addresses, opaque tokens, encoded data, and secrets under unexpected field names. Use exact-text entries for values the automatic patterns miss. Match counts can overlap.

Learn

Log Redactor Guide

About this tool

Replace common sensitive patterns with a fixed [REDACTED] marker before sharing log text. Patterns include sensitive-field lines, PEM private keys, URL credentials, JWT-like tokens, common email forms, IPv4, and IPv6. Add case-sensitive exact text for values the automatic patterns miss. Input processing stays in the browser without tool storage or upload.

Questions

Does the tool guarantee that no secrets remain?: No. Detection is best-effort and can miss secrets, encoded values, unusual field names, multiline structures, and personal data. Review the output manually before copying or downloading it.
Why did it remove the rest of a line or the remaining log?: A recognized sensitive assignment hides the rest of its line. If its value is missing, starts with an object or array, or has an unclosed quote, the remaining log is hidden conservatively. An unclosed PEM private-key block also hides the remaining log. This can remove harmless context and break JSON syntax.
Are the original logs stored or uploaded?: The tool does not upload or save log text or exact-text entries. Originals remain visible in the input area until cleared. Only the redacted preview is used by the copy and download actions.
Does exact-text matching support regex or ignore case?: Neither. Each non-empty line is a case-sensitive literal match, with spaces preserved. Entries need at least three characters. There can be at most 100 distinct entries and 10,000 characters in the list.