Log redactor
Keep the error. Remove the details you did not mean to share.
Prepare logs for a bug report, support ticket or AI conversation. Replace common credentials, emails and network addresses with repeatable placeholders, then review the result yourself.
Runs in this browser. No log upload. No account.
How to redact logs without losing the problem
- Paste only the part needed to reproduce the error. Include the failing request and nearby context, not an entire production dump.
- Keep the detection rules on. Add customer names, internal hostnames, file paths and any secrets the patterns might miss as custom terms.
- Choose Redact locally. Repeated matches receive the same placeholder so you can still follow one address or credential across lines.
- Review the result, then copy or download it. Check request bodies, cookies, query strings, document excerpts and free text yourself.
Timestamps, error messages and ordinary numeric values are left in place where possible. The fictional sample is an authored example, not a real incident or a generated AI answer.
What it looks for — and what it can miss
The credential rule recognizes common labeled secrets, Bearer tokens, selected API-key shapes, URL credentials and PEM private-key blocks. Address rules look for common email and IP formats. These checks are deliberately limited: an unlabeled secret, unusual encoding or personal detail written in a sentence can remain unchanged. False matches are possible too.
This is a review aid, not a security audit, compliance certification or irreversible anonymization method. If a real secret has already been shared, redacting this copy does not revoke it. Rotate the affected credential through its issuer.
Need help understanding the error?
Mother can help reason through logs you choose to provide. Review and copy the redacted result yourself first. Opening Mother does not transfer anything from this tool; you decide what to paste and send.
Try a fictional debugging request in MotherEditable draft only. No automatic send. Mother sends submitted prompts and relevant context to its model provider and stores saved chats on the server. Anonymous access does not mean end-to-end encryption.