Back to scrubber Donate

Log Snail

Features + Q&A for privacy-first local log sanitization.

Tool Features

  • Scrubs sensitive data locally in your browser.
  • Web Worker processing to keep the UI responsive with large logs.
  • Detects and redacts emails, IPs, JWTs, tokens, passwords, API keys, cards, internal URLs, and auth headers.
  • Optional local AI analysis with WebLLM and WebGPU acceleration.
  • AI runs with no backend and no cloud API keys.
  • AI uses sanitized output by default and supports streaming responses.
  • Large logs are chunked before local AI analysis.
  • Per-rule toggles for controlled redaction.
  • One-click copy and download of cleaned logs.
  • Built for safe sharing to ChatGPT, Jira, GitHub, and support tickets.

Q&A

Does Log Snail upload my logs?

No. It runs fully client-side and does not send logs to a backend by default.

Can regex redaction miss secrets?

Yes, edge cases are possible. Log Snail is a strong first pass, but you should still review output before sharing externally.

Why use a local scrubber before ChatGPT or support?

It reduces accidental exposure of customer data, auth material, and internal infrastructure details in pasted logs.

How does LogSnail AI keep logs private?

The AI feature runs locally in your browser with a downloaded on-device model. No API key is required, and log text is not uploaded to a backend service.

Does AI analyze raw logs by default?

No. AI uses sanitized output by default. Raw mode is optional and gated behind an explicit local warning.

What if WebGPU is not available?

The AI panel shows a compatibility message and remains disabled, while the standard scrubber and export workflow keeps working normally.

How is model loading handled?

Model downloads show progress in the UI and are cached by the browser when possible for faster reuse.

Does card detection validate numbers?

Yes. Card-like strings are filtered with a Luhn checksum to reduce false positives.