Share the file, not the secrets
Logs, configs, and pastes carry credentials you never meant to hand over. Each tool here masks them — in your browser, before the file goes anywhere.
These pages are static files: there is no server behind them and no
upload. Every tool page ships a Content-Security-Policy of
connect-src 'none', so your browser itself refuses to let
the page send anything — to us or to anyone. You don't have to take our
word for it: open DevTools, watch the Network tab while you work, and see
that nothing leaves your device.
- .env & config scrubber Mask the values and keep the keys in a .env, YAML, TOML, INI, or JSON config before you share it. Open the tool →
- Access-log IP anonymizer Truncate or tokenize IPs (and mask other secrets) in an nginx/Apache log before you share it. Open the tool →
- CSV sample anonymizer Mask the PII columns in a CSV — emails, phones, names, cards, SSNs — with consistent tokens, so a data sample is safe to share with a vendor, a ticket, or an AI chat. Open the tool →
- curl command sanitizer Strip auth headers, cookies, and body credentials out of a copied-as-cURL command — and keep it runnable. Open the tool →
- HAR sanitizer + viewer Strip auth headers, cookies, tokens, and body secrets from a HAR file before you attach it to a ticket — then review it entry by entry. Open the tool →
- JSON redactor Redact secrets out of deeply nested JSON — API responses, exports, payloads — by key name and by pattern, with pretty-printed output. Open the tool →
- Log file redactor Mask emails, IPs, API keys, JWTs, and passwords in a log before you share it. Open the tool →
- Paste scrubber for AI chats Scrub keys, tokens, passwords, and emails out of a paste before it goes into an AI chat. Open the tool →
- Secret scanner (detect-only) Check a file for API keys, tokens, and passwords before you commit or share it. A findings report — nothing is changed, downloaded, or uploaded. Open the tool →
- Stack trace cleaner Strip usernames, local paths, and internal hostnames out of a stack trace before you share it. Open the tool →
Detection is pattern-based and best-effort — no scrubber can promise a clean file. Every tool shows a side-by-side preview of what changed and flags strings that merely look secret, so the final review stays yours. More on how this works →