Clean your logs before you paste them into an AI
Paste a log, stack trace or config and get a copy without IP addresses, emails, passwords, tokens and customer IDs. Consistent placeholders like [IP-1] keep the log readable – nothing leaves your browser.
How it works
-
Add your log
Paste the log into the left box or open a
.log,.txtor.jsonfile. Large files work too. -
Check the settings
Choose what to hide – passwords and tokens, IPs, emails, IDs and more – and add your own words such as customer or project names.
-
Review the result
The cleaned log appears on the right. Every replacement is highlighted, and the same value always gets the same placeholder.
-
Copy or download
Copy the cleaned log into ChatGPT, Claude, a ticket or a chat, or download it as a file.
Use cases and examples
Debugging with ChatGPT, Claude or Copilot
You hit an error in production and want an AI to explain the stack trace. Paste the log here first: database passwords, bearer tokens and your users’ email addresses are replaced, the error message and the call stack stay intact.
Support tickets and GitHub issues
Maintainers and vendors often ask for “the full log”. Clean it here and attach it without exposing internal IPs, hostnames or API keys to a public issue tracker.
Sharing logs with colleagues and contractors
Not everyone in a chat channel should see customer data. Consistent placeholders keep the log useful for the conversation – [EMAIL-3] failed twice, [IP-1] caused the spike.
Example:
2026-11-17T09:15:44Z WARN 401 POST /api/login from 203.0.113.42 user=jane.doe@example.com
becomes
2026-11-17T09:15:44Z WARN 401 POST /api/login from [IP-1] user=[EMAIL-1]
Frequently asked questions
Is my log uploaded to a server?
No. The log is processed with JavaScript in your browser and never leaves your device. You can even disconnect from the internet after the page has loaded.
What does the log cleaner detect?
Passwords and secrets after keys like password=, token= or Authorization: Bearer, well-known API key formats (AWS, Stripe, GitHub, OpenAI, Slack, Google, JWT), credentials in URLs, IPv4 and IPv6 addresses, email addresses, user@host names, UUIDs and long IDs, labelled customer and order numbers, phone numbers, IBANs, card numbers and MAC addresses.
Why placeholders instead of just deleting the values?
An AI or a colleague still needs to see which request came from which client. With [IP-1] and [IP-2] the relationships stay visible while the real values stay private. If you prefer, switch to asterisks.
Are timestamps, ports and versions changed?
No. Timestamps, durations, ports, process IDs, version numbers, file names and stack traces stay as they are, so the log remains useful for debugging. Long commit hashes are kept by default and can be hidden too.
Does it find names?
Names of people or companies cannot be recognised reliably by patterns. Add them under “Also hide these words” – they are replaced everywhere, regardless of upper or lower case.
Is the automatic detection complete?
No tool catches everything. The log cleaner is a strong first pass; always skim the highlighted result before you share it.