CodeKitHubWhat Is This Tool?
A text obfuscator changes how text looks or is encoded without destroying the underlying meaning, so it can be reversed later. This is different from a code minifier or JS obfuscator, which rewrites and compresses actual program logic — this tool does not parse or execute code, so it is not a substitute for a real JavaScript/CSS build-tool obfuscator.
Three modes are offered here: Unicode lookalike substitution swaps ASCII letters for visually similar Unicode characters (like Cyrillic а for Latin a), which keeps text readable to a human eye but breaks simple substring/regex matching. ROT13 shifts each letter 13 places through the alphabet — a simple, well-known reversible cipher. Base64 re-encodes the text into a different character set entirely.
Why Use It?
- Three distinct obfuscation approaches in one tool — pick the one that fits.
- Every mode is fully reversible with the Deobfuscate button.
- Honest about scope: this is a text tool, not a JavaScript/CSS/HTML code minifier.
- Runs entirely in your browser — nothing is uploaded.
- No installation, no account, free to use.
How to Use
- Paste the text you want to obfuscate.
- Choose a mode: Unicode lookalike, ROT13, or Base64.
- Click Obfuscate to transform it, or Deobfuscate to reverse a previously obfuscated string.
- Copy the result.
Example
Input
Hello, World!Output
Hеllo, Wоrld!In Unicode lookalike mode, the H, e and o characters in this output are Cyrillic homoglyphs, not the Latin letters they appear to be — the text still reads correctly to a human but will not match a plain-text search for 'Hello, World!'.
Common uses
- Posting an email address or phone number online in a form that's readable but avoids simple scraper regexes.
- Sharing spoiler text or an answer key in a way that isn't instantly readable at a glance.
- Quick reversible encoding for casual use — not a substitute for real encryption.
- Testing how your own text-processing scripts handle homoglyph or encoded input.
Choosing a mode
Unicode lookalike substitution is the right choice when you want the text to still look correct to a human reader while defeating exact string matches — it's visually near-identical to the original but uses different underlying character codes. ROT13 is the traditional choice for spoiler-hiding: the scrambled result is clearly not the original text, and it's a widely recognized convention, so readers know to run it through a ROT13 tool if they want to reveal it. Base64 is the most "encoded-looking" option and is commonly used when you need a safe way to embed text inside a URL, JSON field, or system that doesn't handle special characters well.
Frequently Asked Questions
Does this obfuscate JavaScript, CSS, or HTML code?
No. This tool works on plain text only — it does not parse code syntax, rename variables, or minify. For real code obfuscation/minification you need a build-tool-level minifier that understands the language's grammar.
Is Unicode lookalike obfuscation secure?
No — it's a light obfuscation, not encryption. Anyone who runs the text back through this tool's Deobfuscate mode (or a similar homoglyph-reversal tool) can recover the original. Use it to dodge naive keyword filters or copy-paste scraping, not to protect sensitive data.
Why does ROT13 use the same button-logic for both directions?
ROT13 shifts each letter 13 places in a 26-letter alphabet, so applying it twice returns the original text. Obfuscate and Deobfuscate produce the same result in ROT13 mode.
Can Base64 mode handle non-English text?
Yes — the encoder handles full Unicode (accented letters, CJK characters, emoji) correctly by encoding the UTF-8 byte representation, not just ASCII.
Is my text uploaded anywhere?
No. All transformations run as local JavaScript in your browser; nothing is sent to a server.