String Obfuscator

Obfuscation is not encryption — know which one you actually need

This comes up constantly. Obfuscation makes text harder to read; it doesn't make it impossible to recover. Base64 encoding, Caesar shifts, character substitution — all of these can be reversed by anyone who recognises the method. They're not secrets. If you need actual confidentiality, use the Encrypt/Decrypt tool instead, which applies a real cipher that requires a key. Obfuscation is useful for different things: reducing the readability of leaked logs, making copy-paste abuse slightly harder, adding a simple layer before content that doesn't need strong security, or generating placeholder-style strings that look scrambled but aren't sensitive.

Log scrubbing is probably the most practical use for this

If you're shipping logs somewhere and want to make email addresses, usernames, or internal IDs harder to read at a glance without stripping them entirely, running them through a reversible obfuscation method keeps the log data useful while reducing the exposure from accidental visibility. It won't stop a determined person from recovering the originals — again, not encryption — but it adds enough friction that casual viewing doesn't expose user data. The other common use is source code that you want to distribute but make slightly less readable. Obfuscated code is still executable; it just takes more effort to follow. Real minifiers and code obfuscators do a much more thorough job, but for strings specifically, this tool gives you quick output without installing anything.