Corrupted text generator
The "data corruption" framing of the same effect — with a straight answer on how likely it is to actually render.
Controls the density of accent marks stacked above each character.
Controls the density of strikethrough-style marks. These are the marks most likely to render as boxes on old devices — keep this low if you need the text to be widely readable.
Controls the density of marks stacked below each character.
Style mockup, not a live embed — actual rendering can vary by device and app version.
Corruption you can actually predict
"Corrupted text" leans into the glitch-art, broken-file aesthetic rather than the horror-meme one — visually it's the identical Unicode combining-mark technique as glitch and zalgo text. The framing matters for one thing: if you want text that reads as "corrupted data," heavier "through" intensity (the strikethrough-style overlay marks) sells that look better than above/below marks alone.
That's also the setting most likely to actually break in a short field, which is exactly what the renderability badge under the output is tracking — it's an honest estimate, not a guarantee, based on how many marks are stacked per character.
Frequently asked questions
What is corrupted text?
Another name for glitch/zalgo text — Unicode combining marks stacked on normal characters to look broken or corrupted. Same technique, different framing.
Can corrupted text actually damage a file or app?
No. It is standard Unicode text; it cannot execute code or damage anything it's pasted into.
How do I make corrupted text without it getting cut off?
Check the renderability badge as you adjust the sliders — "safe" means low risk of trimming, "risky" means dial back the "through" slider first.