Text Obfuscator
Professional-grade text scrambling, invisible steganography, and bot-resistant encoding tool. Includes Zalgo glitch generation, HTML entity masking for emails, and secure invisible ink techniques.
About
Obfuscation serves as a vital layer in digital privacy by transforming data into a format that resists immediate comprehension by unauthorized observers or automated bots. While encryption provides high-level security, obfuscation focuses on reducing the semantic value of text for scrapers and casual readers. This tool manages the complexity of character mapping, Unicode diacritic stacking, and zero-width steganography to ensure your data remains hidden in plain sight. Use the HTML Entity mode to shield email addresses from RegEx-based scrapers or the Invisible Ink protocol to embed hidden payloads within harmless cover text.
Technical constraints often dictate the choice of method. For instance, ROT13 is a simple Caesar cipher with a shift of 13, which is its own inverse. In contrast, Invisible Ink utilizes 2 distinct zero-width characters to represent binary states, allowing for the storage of n bits of data within a seemingly empty string or between the characters of a visible sentence. This prevents automated detection by standard text processors while maintaining the visual integrity of the host content.
text-security
steganography
zalgo-generator
email-obfuscator
rot13
base64-encoder
Formulas
The core logic for Invisible Ink conversion utilizes a binary mapping of characters into the zero-width Unicode space:
{
bit = 0 → \u200B (Zero Width Space)bit = 1 → \u200C (Zero Width Non-Joiner)
For ROT13, the transformation function f(x) is defined over the alphabet range 0-25:
f(x) = (x + 13)26 mod 26
Reference Data
| Method | Reversibility | Bot Resistance | Visual Change | Best Use Case |
|---|---|---|---|---|
| Base64 | Full (atob) | High (Logic-based) | Complete Scramble | Data transmission |
| ROT13 | Full (Shift 13) | Low (Known) | Complete Scramble | Spoiler protection |
| Invisible Ink | Full (Binary Map) | Very High | None (Invisible) | Watermarking, Secrets |
| HTML Entities | Full (Browser) | High | None (Rendered) | Email harvesting prevention |
| Zalgo / Glitch | None/Partial | Medium | Extreme Distraction | Aesthetic, Anti-OCR |
| Password Mask | N/A (Masking) | N/A | Asterisk Mask | UI demonstrations |
Frequently Asked Questions
Most modern search engines index all Unicode characters. While the text remains invisible to the human eye, the zero-width characters (\u200B and \u200C) are present in the DOM and can be parsed by bots if they are looking for steganographic patterns. It is a tool for privacy, not absolute cryptographic security.
Simple email scrapers look for the "@" symbol and a domain pattern. By converting "[email protected]" to "user@...", the source code no longer contains the literal string, but browsers will still render the clickable email correctly for human users.
Zalgo text relies on stacking diacritics. Some social media platforms or database systems may strip these characters to prevent UI breaking (as they can extend vertically beyond line height). It is best used for aesthetic effects on platforms that support full Unicode rendering.
Absolutely not. ROT13 is a trivial substitution cipher intended for hiding spoilers in forums. It offers zero security against intentional decryption and is only used to prevent accidental reading.