All lessons T
Frontend Utilities beginner 8 min

Clean Up Glitched Zalgo Text Before Sharing

Recognize heavy combining marks and keep decorative glitch text away from fragile contexts.

Scenario

Someone's status message renders as glitchy text that bleeds over the lines above and below it — H̵̛̹e̶̜͊l̸͚̍l̷̢͆o̶̩̓. That effect is Zalgo text: ordinary letters stacked with dozens of Unicode combining diacritical marks. It is not a font, not an image, and not corruption — just base characters carrying more combining marks than layouts expect. Knowing how it is built tells you where it will cause chaos: any field that measures, truncates, or indexes text.

Broken input

H̵̛̹e̶̜͊l̸͚̍l̷̢͆o̶̩̓

Goal

Use Zalgo Text Generator to understand the combining-mark mechanics — generate a controlled sample, see how intensity stacks marks — and make an informed call about where glitched text is safe to paste.

Tool sequence

  1. Open Zalgo Text Generator.
  2. Type Hello and generate at low intensity, then crank it up and watch the marks pile onto each base letter.
  3. Compare the output with the pasted status message — same mechanism: each visible letter is one base character plus stacked U+03xx-range combining marks.
  4. Note the practical consequence: the string's character count is several times its visible length, so length-validated fields, truncation, and moderation filters all behave unpredictably.
  5. Keep Zalgo for informal chat contexts; for emphasis that survives product surfaces, use Text Style Generator instead, and inspect any suspect string with ASCII / Unicode Explorer.

Checkpoint output

visible:    Hello  (5 glyphs)
actual:     H + 3 marks, e + 2 marks, l + 2 marks, l + 2 marks, o + 2 marks
length:     16 code points for 5 visible letters

The "glitch" is decorative combining-mark stacking — fine in a chat message, wrong for labels, IDs, form values, or anything that counts characters.

Common mistakes

  • Pasting Zalgo into fields that validate length or charset and shipping a confusing error to users.
  • Assuming the visual glitch is an image or font effect instead of real Unicode the backend must store.
  • Using decorative marks where accessibility matters — screen readers attempt to announce every combining mark.
  • "Cleaning" Zalgo by deleting visible letters when stripping the combining marks is what actually restores the text.

Related tools and lessons