Back to Shredder

Developer Mode ยท Log Sanitizer

Auto-Redact Secrets from Logs, Configs & Exports

Safe to share with support teams, post on GitHub, or include in bug reports. Log structure, timestamps, and messages are preserved exactly.

What Gets Redacted

PatternExample InputRedacted Output
IPv4 addresses
192.168.1.105xxx.xxx.xxx.xxx
Email addresses
admin@company.coma***@company.com
OpenAI API keys
sk-4eC39HqLyjWDar...sk-********************
AWS Access Keys
AKIAIOSFODNN7EXAMPLEAKIA****************
Bearer tokens
Bearer eyJhbGci0iJI...Authorization: Bearer ********************
Basic auth
Basic dXNlcjpwYXNzAuthorization: Basic ********************

Before / After

Before โ€” raw log with secrets
[14:23:07] INFO: DB connected
  host: 192.168.1.50:5432
[14:23:08] DEBUG: Stripe API call
  Authorization: Bearer sk_live_4eC39Hq...
[14:23:09] ERROR: Auth failed
  user: admin@acme.com
  from: 10.0.0.23
[14:23:10] WARN: Rate limit
  from: 203.0.113.45
After โ€” secrets redacted
[14:23:07] INFO: DB connected
  host: xxx.xxx.xxx.xxx:5432
[14:23:08] DEBUG: Stripe API call
  Authorization: Bearer ********************
[14:23:09] ERROR: Auth failed
  user: a***@acme.com
  from: xxx.xxx.xxx.xxx
[14:23:10] WARN: Rate limit
  from: xxx.xxx.xxx.xxx

Supported File Types

.log

Application Logs

Server, app, and access logs with timestamps and events

.json

JSON Configs

API responses, config files, and structured data exports

.env

Environment Files

.env and .env.local files with secrets and connection strings

.txt

Plain Text

Any unstructured text file containing sensitive patterns

.sql

SQL Exports

Database dumps that may contain email addresses or IPs in data

What Does NOT Change

โœ“Log structure & formatting
โœ“Timestamps & log levels
โœ“Message text & context
โœ“JSON keys & schema
โœ“Line numbers & order
โœ“Non-sensitive values

Only patterns that match known secret formats are replaced. Everything else is left exactly as-is.

Who Uses This

Support Escalation

Share application logs with third-party support or vendors without leaking internal IP ranges or credentials.

GitHub Bug Reports

Paste log output in public GitHub issues after sanitization โ€” no more accidentally committing API keys.

Security Audits

Hand off logs to security reviewers without exposing infrastructure topology or authentication tokens.

Config Export

Export application configs for documentation or peer review after redacting all credentials and endpoints.

Ready to sanitize a log file?

Drop any .log, .json, .env, .txt, or .sql file. Redacted in seconds, entirely offline.

Drag & Drop or Click to Upload

.log, .json, .env, .txt, .sql

100% Client-Side Privacy

All processing happens directly in your browser's memory. Your files are never uploaded to any server, guaranteeing zero data leakage. You can even use this tool offline.