Style Text · browser-local

Zalgo Text Generator

Create the glitchy, dripping zalgo look by stacking Unicode combining marks on each character. GlyphSift caps the number of marks per character so results stay bounded and reproducible.

Index state
eligible
Reviewed
2026-08-24
Input limit
5,000 graphemes
11 graphemes11 code points11 bytes
Intensity

Higher intensity adds more combining marks and can be harder to render or read.

Live result

Zalgo Text Generator

c̤̖̀̈ǖ̥́r̥̗̊̆s̰̣̆̂ẹ̋̇̃d̤̖̃̀ t̥̗́̊ḛ̊̆̂x̰̣̋̇ṫ̤̃̀

Good fit

Use this tool when

  • You want a decorative glitch effect for a short label.
  • You accept reduced readability for style.
  • You want a controlled, capped amount of distortion.

Keep the original

Avoid it when

  • The text must remain readable or accessible.
  • You are trying to evade moderation or filters.
  • The destination limits combining marks.
01

Reviewed truth vectors

Examples that expose the edge cases

Inputcursed
Outputcursed with stacked combining marks

Each letter gains a capped set of marks.

Inputhi
Outputhi with marks above and below

Intensity controls how many marks are added.

Inputa b
Outputspaces are left unmarked

Whitespace is skipped to keep word gaps.

02

Transparent implementation

How it works

  1. 01

    Skip whitespace and keep each base character.

  2. 02

    Append a capped number of combining marks chosen by position.

  3. 03

    Increase or decrease the count with the intensity control.

03

Known limitations

What the result cannot promise

Heavy stacking can be hard to render or read.

Some platforms strip or limit combining marks.

It is decorative and should not be used to bypass moderation.

04

Questions before copying

Frequently asked questions

Why is it capped?

A per-character limit keeps output bounded, reproducible, and safe for rendering, unlike uncapped zalgo generators.

Is the output random?

No. Marks are selected by character position, so the same input and intensity always give the same result.

Can it hide text from filters?

It is a visual effect, not an evasion tool, and many systems normalize or strip the marks.

05

Experience, expertise & trust

How we verify this tool

GlyphSift EditorialText-engine authors & reviewers

The GlyphSift Editorial team designs the deterministic text engine, writes each tool's examples against real Unicode edge cases, and reviews every claim before a page becomes eligible for indexing. We build and test the software we document; we do not outsource the copy to generic content mills.

Each tool page is reviewed against the same six input classes the engine is tested with — ASCII, emoji, combining marks, non-Latin scripts, empty input, and 5,000-grapheme input — and cannot become eligible if it is only a parameter variation of another page.

Automated evidence

  • Tool-contract & coverage suite30 deterministic cases

    tests/tools-30.test.mjs mirrors the ToolRunner dispatch and asserts every registered engineId returns the contracted output shape, plus a coverage guard so no tool silently drops characters.

    Run in: node --test after a production build (vinext build)
  • Rendered-HTML suite12 deterministic cases

    tests/rendered-html.test.mjs renders the deployed server bundle and asserts the Unicode-version manifest and each wave's tool markup are present in the server-rendered HTML.

    Run in: node --test against the built dist/server bundle
  • Transform & cleanup suite21 deterministic cases

    tests/transform-cleanup.test.mjs exercises each deterministic cleanup and transform action against whitespace, duplicate, ordering, casing, and HTML-to-text edge cases.

    Run in: node --test, no network, no randomness

Standards this tool follows