String Obfuscator

About String Obfuscator

Available Obfuscation Methods

Method	How It Works	Example (input: "Hello")	Reversible?
ROT13	Shifts each letter 13 positions in the alphabet	Uryyb	Yes - applying ROT13 twice returns the original
Base64	Encodes bytes as ASCII characters (A-Z, a-z, 0-9, +, /)	SGVsbG8=	Yes - standard decode
Reverse	Reverses the entire string character by character	olleH	Yes - reverse again
Leetspeak	Replaces letters with visually similar numbers/symbols	H3ll0	No - multiple letters map to the same symbol
Morse code	Converts to dots (.) and dashes (-) with spaces between letters	.... . .-.. .-.. ---	Yes - standard decode
Upside-down	Maps characters to Unicode equivalents that look flipped	ollǝH (reversed and flipped)	No - some characters have no upside-down equivalent
Zalgo	Adds combining Unicode characters above and below letters	H̷̢e̸̛l̵̢l̶̡o̸̧ (with stacking diacritics)	No - original character positions are preserved but cleanup varies

How ROT13 Works

ROT13 is a simple letter substitution cipher that shifts each letter 13 positions forward in the alphabet. Since the English alphabet has 26 letters, applying ROT13 twice returns the original text - the same function both encodes and decodes.

Original	A	B	C	D	...	M	N	O	P	...	Z
ROT13	N	O	P	Q	...	Z	A	B	C	...	M

ROT13 is not encryption - it provides zero security. It is used to hide spoilers on forums, obscure puzzle answers, and prevent accidental reading of text that someone might not want to see immediately. Usenet newsgroups popularised it in the 1980s for exactly this purpose.

Leetspeak Character Substitutions

Leetspeak (1337 5p34k) originated in 1980s hacker and bulletin board culture. It replaces letters with visually similar numbers and symbols. There is no single standard - different communities use different mappings.

Letter	Common Replacements	Letter	Common Replacements
A	4, @	N	|\|
B	8, |3	O	0
E	3	S	5, $
G	6, 9	T	7
I	1, !	L	1, |

Morse Code Basics

Morse code represents each letter as a sequence of short signals (dots) and long signals (dashes). Developed by Samuel Morse and Alfred Vail in the 1830s for telegraph communication, it is still used today in amateur radio, aviation emergency signals, and accessibility devices.

Character	Morse	Character	Morse	Character	Morse
A	.-	J	.---	S	...
B	-...	K	-.-	T	-
C	-.-.	L	.-..	U	..-
D	-..	M	--	V	...-
E	.	N	-.	W	.--
F	..-.	O	---	X	-..-
G	--.	P	.--.	Y	-.--
H	....	Q	--.-	Z	--..
I	..	R	.-.	SOS	...---...

SOS (...---...) is the universal distress signal. It was chosen not because the letters stand for anything, but because the pattern is easy to transmit and recognise.

Obfuscation vs Encryption

None of the methods in this tool provide security. They are encoding and transformation methods, not encryption.

Property	Obfuscation (this tool)	Encryption (e.g., AES-256)
Security	None - anyone who knows the method can reverse it	Strong - requires the correct key to decrypt
Purpose	Hide text from casual viewing, fun, creative effects	Protect sensitive data from unauthorised access
Key required?	No	Yes - a secret key or key pair
Examples	ROT13, Base64, leetspeak	AES, RSA, ChaCha20

For actual encryption, use the dedicated encryption tool which implements AES-256-GCM. For binary encoding of text, the text to binary converter shows the raw binary representation. For decorative Unicode text styles, the fancy text generator offers bold, italic, and script variations. Everything runs locally in your browser.

How Base64 Encoding Works

Base64 groups three input bytes (24 bits) into four 6-bit chunks, then maps each chunk to one of 64 ASCII characters (A-Z, a-z, 0-9, +, /). The output is roughly 33% larger than the input. The trailing `=` characters pad the result to a multiple of four when the input length is not divisible by three.

Worked example (encoding "Hi"): The two ASCII bytes are 0x48 (H) and 0x69 (i), giving binary `01001000 01101001`. Split into 6-bit groups this is `010010 000110 1001`, padded to `010010 000110 100100` = decimals 18, 6, 36. Mapping those to the Base64 alphabet gives S, G, k. Because there are only two input bytes, one `=` is appended, producing `SGk=`.

Base64 was first standardised in RFC 1421 (1993) for Privacy-Enhanced Mail and is now defined by RFC 4648. It is the standard way to embed binary data inside text-only formats - data URLs in HTML, attachments in MIME emails, tokens in JSON Web Tokens, and the `Authorization: Basic` HTTP header all use it. It is not a security mechanism; anyone can decode a Base64 string in a browser console.

Morse Code in Modern Use

Morse code is still legally recognised for emergency signalling and remains in active use by amateur (ham) radio operators worldwide. The International Telecommunication Union dropped the Morse proficiency requirement for amateur licences in 2003, but hams continue to use it because Continuous Wave (CW) transmissions punch through noise that would render voice unintelligible - a 5 watt CW signal can cross oceans when the same power in SSB voice would be lost.

The US Federal Aviation Administration still uses Morse identifiers for VOR and NDB aviation navigation beacons - pilots listen for the three-letter Morse ID to confirm they have tuned the correct station. The United States Coast Guard ceased monitoring the 500 kHz maritime distress frequency in 1995, but SOS (...---...) remains the universal signal taught in every survival course. The signal has no literal meaning: it was chosen in the 1908 Berlin Radiotelegraphic Convention because its nine-element pattern is easy to send under stress and instantly recognisable even to an untrained listener.

Why Do Zalgo and Upside-Down Text Work?

Both effects exploit Unicode's combining characters and its enormous supplementary character blocks. Zalgo stacks combining diacritics (Unicode categories Mn - Mark, Nonspacing) above and below a base letter. These marks are designed for languages like Vietnamese, Yoruba, and Ancient Greek where a letter can legitimately carry multiple accents, but they have no limit on how many can attach to one base, which is what produces the glitchy overflow look.

Upside-down text works differently. Instead of combining marks, it maps each Latin letter to a different Unicode codepoint that happens to look like the original letter flipped 180 degrees. Lowercase `a` becomes `ɐ` (U+0250, the IPA symbol for the near-open central vowel), `e` becomes `ǝ` (U+01DD), and so on. The tool then reverses the string so the sentence reads correctly when the screen or page is physically flipped.

Because these effects rely on Unicode codepoints rather than images, they copy-paste cleanly into most apps. Platforms that strip or normalise Unicode (older SMS gateways, some corporate email scanners) may display tofu boxes instead. Zalgo text in particular can break screen readers and accessibility tools, so avoid it in any content that needs to be read aloud.

Common Mistakes and Edge Cases

Mistake	What goes wrong	Fix
Treating ROT13 as security	Anyone can reverse it in seconds - it is only a spoiler shield	Use AES or similar for real secrets
Losing padding from Base64	Decoders reject strings whose length is not a multiple of four	Add trailing `=` characters until length mod 4 is zero
Assuming Base64 hides data	Every browser and scripting language decodes it natively	Encrypt first, then Base64 if a text-only transport is needed
Using leetspeak as a password filter bypass	Modern password blocklists expand leet variants automatically	Use a passphrase with real length, not a leet-translated weak word
Morse without prosigns	Decoders split on single spaces - word gaps need `/`	Use `/` between words, single space between letters
Zalgo in usernames or filenames	Many systems strip combining marks or reject the input	Limit zalgo to display text, not identifiers

Where These Methods Are Actually Used

ROT13 appears in Reddit spoilers, puzzle communities, and the Unix `tr 'A-Za-z' 'N-ZA-Mn-za-m'` one-liner that ships on most systems. Base64 is everywhere: MIME email attachments, data URIs in HTML (<img src="data:image/png;base64,...">), JWT headers and payloads, the `Authorization: Basic` HTTP header, and PEM-formatted TLS certificates. Leetspeak survives in hacker culture and gamer usernames but has faded in mainstream use. Morse lives on in amateur radio, aviation beacons, and as a fallback for locked-in patients who can blink dots and dashes. Upside-down and zalgo text are almost entirely decorative - memes, creepy profile names, and the occasional art project.

If you are comparing or transforming text in other ways, the case converter handles camelCase, snake_case, and title case, and the Base64 encoder/decoder is a dedicated tool for file-safe Base64 with padding controls. For a stricter security discussion of why obfuscation is not encryption, Cloudflare's learning centre and OWASP's cryptographic storage cheat sheet are the clearest primary references.

Sources

• IETF RFC 4648 - Base16, Base32, and Base64 Data Encodings
• ITU-R M.1677 - International Morse Code Standard
• FCC - Amateur Radio Service
• Unicode Standard Annex #15 - Unicode Normalization Forms
• FAA Aeronautical Information Manual - Navigation Aids
• OWASP - Cryptographic Storage Cheat Sheet