What Zalgo Text helps you do
Add or strip chaotic combining marks to create or undo glitch-style Zalgo text. The tool can both generate the effect and reverse it, which matters because the marks are hard to remove by hand. Intensity controls how many marks are stacked above and below each character.
Mark generation and removal run locally in your browser; nothing is uploaded.
How it works
These tools transform characters rather than meaning. Some map letters to other Unicode glyphs, some insert combining marks, and some encode bytes into a text-safe representation. The result is still text, so it can be copied into a document or chat, but the visual effect depends on the font and platform that renders it. Nothing is uploaded, and some transformations are not reversible; keep the original when that matters. The output is a snapshot of the pasted text, so changing the source afterwards does not update it.
How to use Zalgo Text
- Paste the text you want to make glitchy, or the glitchy text you want to clean.
- Choose to add or strip combining marks and set the intensity.
- Preview the result in the destination app.
- Copy the result.
When to use it
- Create creepy or corrupted text for a themed post.
- Strip combining marks from text that was pasted with unwanted decorators.
- Demonstrate how Unicode combining characters behave.
- Make a spooky label for a game or event.
- Clean up text that renders with overlapping marks.
- Show why combining marks can break line height.
When not to use it
- Do not use it for body copy or anything that must be readable.
- Do not use it for accessibility-critical text.
- Do not expect the transformation to be perfectly reversible.
Example
Adding marks to a single letter stacks diacritics above and below it, while stripping removes those marks back to plain text. A high intensity can make a line overlap the next one, and some apps clip the marks entirely. The plain text is the only reliable way to store the message.
What you can do with Zalgo Text
- Apply Zalgo combining marks to letters.
- Strip combining marks back to plain letters.
- Set the intensity from 1 to 8.
- Leave spaces and line breaks unchanged.
- Copy the glitchy or cleaned result.
- Run the transformation locally with no upload.
Example: preview the transformation before sharing
Paste a short sample and inspect the result in the place it will be used. A fancy style that looks right in one app can show as boxes or plain letters in another.
Check whether the transformation is reversible. Escapes, Morse and binary can be decoded; styled letters and Zalgo usually cannot be restored perfectly.
Copy the result and keep the original if the text will be edited later or read by a screen reader. Styled characters are separate code points, so a search for the plain word will not find them.
If the text is for accessibility, prefer plain characters. A screen reader may read styled letters one by one or skip the combining marks entirely.
If the output will go into a field with a character limit, count the characters before and after. Styled letters often use more code points than the plain form, so a caption that fit before may no longer fit.
For a reversible encoding, test the round trip on a short sample. Encode, decode, and compare; if the result differs, the tool is not the right one for that data.
Keep the plain source in a note next to the styled version. When the effect stops rendering or a reader cannot parse it, the plain text is the only accessible fallback.
What to know before you start
- Heavy Zalgo output can break line heights and renderers, and is often inaccessible.
- Stripping removes recognized combining marks but cannot recover characters that were replaced.
- The marks are random, so the same input does not produce the same output.
- Very long inputs are capped to keep the page responsive.
Common mistakes
- Applying a high intensity and making the text unreadable.
- Using Zalgo for a name or label that must be accessible.
- Expecting every renderer to show the marks.
- Assuming undo restores the exact original if other marks were present.
Troubleshooting
If the text looks unchanged, the renderer may not display combining marks.
If lines overlap, lower the intensity.
If undo leaves marks, they may come from a different source or script.
If the field rejects the text, it may allow only plain characters.
Related standards and documentation
- Styled letters are separate Unicode code points, not formatting; search and spell-check may not recognize them.
- Combining marks attach to the preceding character and can affect cursor movement and accessibility.
- Base64, binary and escapes are encodings, not encryption.
- Character counts can change after a transformation because Unicode code points differ from visible glyphs.
- Preview in the destination app.
- Some styles are one-way.
- Keep the original for editing.
- Prefer plain text for accessibility.