Zalgo Text and Combining Characters: How the Creepy Letters Work

Zalgo text looks like the letters are melting. They aren't melting. Each "letter" is a normal character with extra Unicode combining marks piled on top, underneath, or through the middle. The renderer tries to stack every mark on the same base. Layout engines were not designed for a stack of thirty tildes.

The meme name comes from Something Awful, mid-2000s: a creepypasta about a corrupted force that breaks text. The mechanism is older than the meme. Combining characters have been in Unicode for years so you can put an acute accent on a letter that didn't have a precomposed form. Zalgo just holds the accent key down until the line height screams.

Combining marks, without the horror poster

A base character occupies a slot. A combining mark is a character that says "draw me relative to the last base." é can be one precomposed character, or e plus a combining acute. Both can look the same. Zalgo is e plus a combining grave plus a combining tilde plus a dozen more, some meant to sit above, some below.

Wikipedia's combining character page is the sober version. Blocks like Combining Diacritical Marks (U+0300 and friends) are the pantry. Generators pick randomly from that pantry. That's why two Zalgo outputs never match. There isn't a canonical "cursed A."

Our cursed text generator is that pantry with a slider for how mean to be. Crank it and you'll overflow a comment box. That's not a bug in your phone. That's the stack getting taller than the line.

Why apps panic

Line height is a guess. A paragraph style says "lines are 20px." Combining marks paint outside that box. They overlap the comment above yours. They can hide a button. They've been used as a nuisance, which is why some apps strip combining marks on the way in. That's the sanitizer failure from the missing-glyph article, aimed specifically at this trick.

Search and names also hate it. A username with thirty marks is a moderation headache and a copy-paste landmine. I'd keep Zalgo in a joke comment, not in a handle, not in a price, not in anything a screen reader has to finish this year.

Readers may announce every mark. "Lowercase z, combining long stroke overlay, combining grave, combining candrabindu…" You will lose friends.

Zalgo isn't a font, either

Same sermon as cursive. You're not applying a typeface named Cursed. You're inserting extra code points. Copy the result and the marks travel with the letters. Paste into an app that strips them and you're back to plain zalgo, sorry, plain zalgo without the drip. The drip was the marks.

Some "glitch fonts" on other sites are images or private-use glyphs. Those won't even paste as text. If it doesn't survive Notes, it isn't this trick.

When I'd still use it

A one-word joke. A Halloween graphic where the overlap is the point. A test to see whether a form sanitizes input (on a site you own, please). I wouldn't put it in a client pitch. I wouldn't put it in a push notification. Notifications have even worse line boxes than comments.

If you want chaos that still sorts and searches, leet is gentler. Different decade, different mess. See leet history. If you want letters that merely look styled, use math bold and accept tofu risk, not a combining-mark bomb.

Precomposed vs stacked, because it matters

é as a single character (U+00E9) is boring and safe. e plus combining acute is two code points that usually look identical. Normalization (NFC vs NFD) can rewrite one into the other without you noticing. Zalgo is NFD's chaotic cousin: so many marks that no normalizer will fold them back into a single Latin letter, because there is no precomposed "letter plus fifteen graves."

That's useful if you're testing a form. Throw a modest stack at the input and see whether your database stores it, whether your email client clips it, whether your PDF library panics. Do that on a staging box. Production comments don't need your QA hobby.

Copy length also lies, because a "five letter" zalgo word can be 80 code points, and some fields say 50 characters when they mean 50 code points, so your cute nickname won't save even if the preview looked short. That's not Instagram being evil. That's a length check that can't see glyphs, only the tape of marks you stacked because the meme told you more drip equals more cursed. Throw a modest stack at a form you own if you're testing sanitizers. Production comments don't need your QA hobby, and neither does a group chat whose layout is already one overlapping comment away from hiding a reply button.

Common Questions

Will this break someone's phone? It can wreck a layout. It shouldn't brick a device. Still a rotten thing to drop in a huge group chat.

Is there a "safe" amount of Zalgo? A couple of marks can look like a weird accent. Past a handful, you're in meme territory and in clip-overflow territory.

Can I reverse it back to clean text? Strip combining marks, keep the bases. Many converters have a "remove diacritics" idea. Ours is a generator, not a janitor. Notes and a regex will do it if you're desperate.

Why does it look different in two apps? Mark positioning is font-specific. One font stacks neatly. Another sprays. Same string, different drawings, like every other Unicode toy on this site.

The creepy look is extra marks, stacked until the line gives up. Fun in a caption. Rude in a form field. Unicode didn't build it for horror. The internet noticed the stacking and went for it.