Glitch & Zalgo Text Generator: Cursed Text to Copy-Paste

TL;DR A glitch text generator doesn't swap your letters for fancy look-alikes — it stacks non-spacing Unicode combining marks on top of your normal letters so they drip above and below the line. Pure Zalgo maxes that out for a chaotic, unreadable "cursed" look; light glitch uses a few marks for subtler distortion. It copy-pastes, but it inflates your character count, gets stripped or filtered on some platforms, and is unreadable to screen readers — so keep it decorative.

You wanted the dripping, half-corrupted "cursed" text — the kind that looks like the comment section glitched out — and you want to copy-paste it into a bio, a username, or a caption. A glitch (or Zalgo) text generator does exactly that, and below you'll find real copy-paste samples plus the part most pages skip: how it actually works under the hood, and exactly where it breaks. The short version is that glitch text behaves very differently from a normal fancy text generator, and that difference decides where it'll survive and where it'll fall apart.

What glitch and Zalgo text really are

Most "fancy fonts" you've seen work by substitution: you type hello and the tool hands back 𝒽𝑒𝓁𝓁𝑜, where each letter has been swapped for a different Unicode character that was drawn to look cursive or bold. (That's the mechanic behind the main text generator, and the how bold text generators work explainer walks through it.)

Glitch and Zalgo text do not work that way. Your normal letters stay exactly as they are. The generator stacks extra characters called combining diacritical marks on top of each one. These are the same accent marks used legitimately in everyday text — the acute over the e in café, the tilde over the n in señor, the dots over the u in über. In a glitch generator, though, the base stays as a plain letter and the marks pile on separately. They come mostly from the Unicode Combining Diacritical Marks block, U+0300–U+036F, which holds exactly 112 marks. Heavier generators reach larger stacks by also pulling from related blocks — Combining Diacritical Marks Supplement (U+1DC0–U+1DFF) and Extended (U+1AB0–U+1AFF) — for a few hundred marks in total.

The key property: a combining mark is non-spacing — in Unicode terms its category is Mn, with zero advance width (not to be confused with the separately named "zero-width" characters like U+200B). It doesn't take its own cell — it attaches to the character right before it and overlays it. So when a generator piles five, ten, or twenty marks onto a single letter, they all accrete above, through, and below that one letter, spilling past the baseline. Zalgo generators pull from marks that render above the letter, through the middle, and below it, and apply all three at once to get the "dripping in every direction" look. (Those neat up/mid/down buckets are how generator sites describe their sliders, not an official Unicode taxonomy — the standard just defines the block, and each mark's real position is set per-character.)

So the one fact to remember: fancy fonts replace your letters; glitch and Zalgo add marks on top of them. Your base word is still sitting there underneath as plain ASCII — which, as we'll see, is exactly why some filters miss it and others catch it. (Some "mixed" glitch generators do also swap in accented look-alikes, so if you specifically need the base letters intact, paste a sample into a decoder or just check it character by character.)

Glitch vs. Zalgo: a spectrum, not two things

"Glitch text" is the umbrella term. Zalgo is the extreme end of it.

• Pure Zalgo maxes out the stacking for chaos. Because Unicode doesn't cap how many marks attach to one letter, the accents pile so high and deep they overflow the line and collide with the text above and below. The result is intentionally unreadable — the "He comes" / cursed-summoning aesthetic. (Zalgo started in the mid-2000s as an internet meme tied to a Lovecraftian creepypasta deity.)
• Light glitch uses just one or two marks per letter for a subtler "digital distortion" or hacker look that stays mostly legible.
• Mixed glitch generators often blend in other tricks too — strikethrough/overlay marks, swapped variant or upside-down letters, full-width vaporwave characters. Some of these survive platforms better than full Zalgo.

Copy-paste glitch & Zalgo examples

Here are real, paste-ready samples. Every one of them is a plain ASCII word with combining marks stacked on top — nothing in the base layer has been swapped out. They'll render differently depending on your device and app — that inconsistency is the whole story of this style, so treat these as a preview, not a guarantee.

Heavy Zalgo (cursed / dripping):

c̴̘̱̙̦̋̄̒͒ų̴̨̘̘͐́̾̇r̴̲̙̠̹̈̂͂̓ş̸̗̠̗͒͐́͐e̵̱̙̲̤͂̄̊̓d̸̲̹̞̦͂͗̆̃

Medium Zalgo (still legible underneath):

h̻̘̃͂e̳̞͐́ḻ̨̽͗l̩̲ͯ̋o̤̠̔̌

Light glitch (subtle distortion):

ğ̻l̠ͯî̲t̰̊c̥̽h̩ͣ

Strikethrough glitch (overlay marks):

g̶l̶i̶t̶c̶h̶

Paste the heavy one into a notes app and try to delete it — you'll see it takes several backspaces to clear a single visible letter. That's every stacked mark being its own character, which is also the root of the next problem.

Where it breaks (read this before you paste)

Glitch text is fun, but it has sharp edges. Here's the honest list.

It wrecks your character count. Every combining mark is a separate Unicode code point, and each one counts against length limits. A 6-letter word with heavy Zalgo can balloon from 6 to 80-plus characters — the "cursed" sample above is already 60. That overflows short fields fast, and Discord is the clearest case to be precise about. Your Discord display name / server nickname has a 32-character cap and does accept Unicode, so heavy stacks blow past it and get rejected or truncated. Your Discord @username, since the 2023 username change, only allows lowercase a–z, 0–9, . and _ — so it rejects combining marks outright on a character-class basis; there's no "truncation," it simply won't take them. This is the same character-inflation trap covered in how fancy text inflates your character count.

It gets stripped, capped, or normalized. Behavior is platform-dependent and inconsistent. Discord renders heavy stacks in messages and nicknames. Other surfaces cap how many marks they allow per glyph, strip the marks, truncate the string, flag extreme Zalgo as spam, or normalize input so heavy stacks get cut down — Reddit, for instance, actively normalizes and trims excessive combining marks in titles and comments as part of its anti-abuse handling, so don't count on full Zalgo surviving there. Instagram falls somewhere in between and is worth testing. There's no reliable published per-platform number, so test before you commit. Lighter glitch with fewer marks is far more reliable than full Zalgo, which is the most likely to be stripped, capped, or filtered.

It can show as boxes. On older devices or in apps with limited bundled fonts, a character the device can't draw falls back to an empty box (□), nicknamed "tofu." That's a separate issue from stripping — the character arrived intact, the device just has no glyph for it. We cover that fully in why fancy text shows as boxes.

It's effectively unreadable to screen readers. This is the most important caveat, and the reason to keep glitch text decorative. Screen readers handle stacked combining marks very poorly: depending on the software, a reader may try to pronounce each individual mark (producing nonsense), spell the underlying text out letter-by-letter, or skip the affected text entirely. There's no version of heavy Zalgo that reads cleanly aloud. So never put meaningful information — your name, what you do, dates, prices, or links — inside glitch text; keep all of that in plain text and use glitch styling only as decoration around it. Our accessibility page covers how styled Unicode behaves with assistive tech in more detail.

Is it safe?

Yes. The combining marks Zalgo uses are perfectly valid, standard Unicode characters — the same ones used for ordinary accents — not malware or "broken" code, so pasting them is safe for you. The honest caveats above are about how the text behaves, not about your security. (There's an old class of crafted-Unicode "text bomb" bugs — like the 2015 iOS "Effective Power" crash — but those were specific parser bugs that got patched, not a property of ordinary Zalgo today.)

How to use glitch text without it backfiring

The whole point of glitch and Zalgo text is the look, so use it where the look is the only job:

• Decoration around plain text, never instead of it. Frame a plain-text bio line with a few glitch characters; don't run your handle, link, or call-to-action through the generator.
• Lean light, not full Zalgo. One or two marks per letter survives more platforms, stays legible, and is gentler on character counts. Save maxed-out Zalgo for places you control and have tested.
• Check the length before you post. Because every mark counts, paste your styled text into the character counter so you know the real length before a field cuts it off mid-word.
• Paste-test in the exact field. A nickname field, a message box, and a username field all behave differently. What renders in a Discord message may be rejected in a username. Test in the real spot before you save.

Do that, and glitch text stays what it's good at: a fun, cursed, deliberately broken-looking effect — without quietly breaking the parts of your profile that actually need to work.