Cursed text works by breaking a rule the text system relies on. Characters are supposed to carry a small number of marks; cursed text stacks dozens, and the letters spill out of their line. It is the only effect on this site that is deliberately misusing the system, and that is why it behaves so unpredictably.
Last updated: 30 August 2026 · COOLMOJI Editorial Team
132 cursed pieces to copy
Served byte for byte. Nothing here is normalised or cleaned on the way out — a tidied cursed character is just a plain character, so cleaning it would destroy the only thing it is.
Cursed & glitch
Creepy marks
Distorted
Bones
Witch & occult
Spikes
How the effect actually works
Unicode has a category of characters called combining marks. They do not stand on their own — they attach to the character before them. Accents work this way: an e plus a combining acute mark renders as é.
The system does not limit how many you can stack. Add forty marks to one letter and every one of them renders, piling above and below until the letter disappears inside them and the text bleeds into the lines around it.
So cursed text is not a font, an image or a glitch. It is ordinary text using a legitimate feature far past what anyone designing it expected. Everything strange about its behaviour follows from that one fact.
Three things platforms do to it
| What happens | Why | What you see |
|---|---|---|
| It renders fully | The platform passes text through untouched | The full effect, spilling between lines |
| Marks are stripped | The field removes combining marks deliberately | Plain letters. The effect is gone entirely |
| Line height is clamped | The layout caps how far text may spill | Marks cut off flat at the top and bottom |
All three are correct behaviour. Stripping is not censorship — a field that limits marks is protecting its own layout from text that would otherwise overlap the interface. The clamp is the most common on modern apps, which is why cursed text often looks stronger in a plain message than in a styled feed.
One consequence worth planning for: length. Every mark is a separate character, so a five-letter cursed word can be two hundred characters long. In any field with a limit, cursed text runs out of room almost immediately.
Where it is fine and where it is rude
This is worth saying plainly, because the same characters can be a joke or a nuisance depending on where they land.
Fine: your own posts, your own captions, a reply in a group that is playing along, anywhere the effect is the point and everyone can scroll past it.
Not fine: flooding a conversation so other people cannot read it. Marks that spill several lines up can cover other people’s messages, and doing that on purpose is disruption rather than decoration — most platforms treat it that way, and so do we in our terms of use.
Worth avoiding: a bio or display name. Screen readers announce each mark separately, so a cursed name can take a long time to read out and convey nothing. If people need to read a field to understand who you are, cursed text is the wrong tool for it.
The skull and gothic symbols give a similar mood without any of these problems, since they are single standalone characters.
FAQ
Why did my cursed text turn into plain letters?
The field stripped the combining marks. That will happen every time in that field — it is a rule, not a glitch.
Why is it cut off flat at the top?
The layout clamps line height so text cannot overlap the interface. The marks are all there; only the visible spill is limited.
Can cursed text break someone’s app?
Not really break, but extremely long stacks have caused slowdowns in some apps historically. Most modern platforms cap the number of marks they will render for exactly that reason.
Does it work in a username?
Almost never. Name fields are the strictest about combining marks, and the length inflation alone usually blocks it.
Is copying it going to mess up my clipboard?
No. It is ordinary text. Paste it into a plain note and it sits there like any other string.
