Skip to content

Character limits & Unicode compatibility

Published September 23, 2026

The tightest real constraint on every platform this site has a generator for, in one table, plus what Unicode normalization actually does to combining marks.

Every platform below counts "characters" differently — most count raw Unicode code points (so every combining mark this generator adds counts individually), a few are limited by display width instead of a strict count. This table is one place to check the tightest field on each platform before you commit heavy glitch intensity to a username, bio, or post. Each platform's own page has the full field-by-field breakdown, formatting tips, and FAQs.

PlatformTightest fieldLimit
InstagramInstagram Bio150 chars
DiscordDiscord Nickname32 chars
WhatsAppWhatsApp Status700 chars
TikTokTikTok Bio80 chars
FacebookFacebook Bio101 chars
MinecraftSign Line15 chars
RobloxRoblox Display Name20 chars
X (Twitter)X Bio160 chars

What is Unicode normalization, and does it affect glitch text?

Some platforms — X (Twitter) is the clearest documented example — normalize text to Unicode Normalization Form C (NFC)before counting or storing it. NFC's job is narrow: it recomposes a base letter followed by a single combining accent into one precomposed character, so "e" + a combining acute accent becomes "é" as a single code point instead of two.

That doesn't do anything to glitch or zalgo text. There's no precomposed Unicode character for "a letter with a dozen combining marks stacked on it" — normalization has nowhere to fold those marks into, so they pass through untouched. Practically: normalization doesn't make heavy glitch text safer to use in a tight field, and it doesn't strip the effect either. See Unicode combining characters for how the marks themselves work.

Frequently asked questions

Which platform has the tightest character limit for glitch text?

Minecraft signs and Roblox display names are the tightest — 15 visible characters per sign line and 20 code points for a display name, respectively. Both are far more restrictive than a bio or post field, so keep intensity low if you're glitching text for either.

Why does the same glitch text fit in one app but get cut off in another?

Because every field counts length differently. Most apps count by raw Unicode code point, which is what this generator's renderability badge estimates against — but display-width-limited fields like Minecraft signs can clip text well before you hit any code-point limit, since they cap how much fits visually, not how many characters you typed.

Does Unicode normalization strip or merge glitch text's combining marks?

No, for the same reason across every platform that normalizes text: NFC normalization only recomposes a base letter plus one accent into a single precomposed character (like é). There's no precomposed form for a letter with a dozen combining marks stacked on it, so heavy glitch/zalgo marks pass through normalization unchanged and each still counts individually toward whatever limit applies.