Stylish Text Changed After You Pasted It? Find the Cause
Stylish text changes after pasting for four reasons. We ran all 104 TextStylish styles through Unicode normalisation: 15 turn fully plain, 62 are untouched. Plus 118 paste-proof decorations.
Stylish text changes after you paste it for one of four reasons: the app converted it back to plain letters, the app removed some characters, a right-to-left character flipped the layout, or the copy never reached the clipboard. Each one looks different, so start by matching what you see.
Checked by the TextStylish editorial team on 16 September 2026 by running all 104 generator styles through Unicode normalisation (NFKC) and character-category tests. Method and sources are at the end.
Match the symptom to the cause
| What you see after pasting | Cause | What works |
|---|---|---|
| Styled letters became ordinary letters | The field applied Unicode normalisation (NFKC) | Use one of the 62 styles NFKC leaves alone, or style the message instead of the name |
| Strikes, underlines or glitch marks vanished | The field removed combining marks | Pick a style with no combining marks |
| Brackets or symbols moved to the wrong side | A right-to-left character changed the display order | Remove that one character |
| Empty boxes on someone else’s screen | Their phone has no font for it — not a paste problem | See why stylish text shows boxes on another phone |
| Nothing appeared | The copy did not reach the clipboard | Tap the page once, then copy again |
Why stylish text turns into plain letters after pasting
Stylish text turns plain when the app runs NFKC normalisation, a Unicode rule that maps “compatibility” characters — such as 𝓐 MATHEMATICAL BOLD SCRIPT CAPITAL A — back to the ordinary letter they imitate. Apps use it in usernames and search so that two names that look identical cannot belong to two different accounts.
We ran every style in the generator through NFKC with the name “Aisha”. The result splits the 104 styles into four groups:
| What NFKC does | Styles | Examples (before → after) |
|---|---|---|
| Styling removed completely | 15 | Cursive Script 𝓐𝓲𝓼𝓱𝓪 → Aisha · Old English · Bubble · Full Width · Double Struck · Bold Sans |
| Letters become plain but differ from what was typed (case, spacing or marks) | 23 | Cursive Underline 𝓐̲𝓲̲𝓼̲𝓱̲𝓪̲ → A̲i̲s̲h̲a̲ · Squared 🄰🄸🅂🄷🄰 → AISHA · Tiny Letters ᵃⁱˢʰᵃ → aisha |
| Not changed at all | 62 | Small Caps ᴀɪsʜᴀ · Upside Down ɐɥsᴉɐ · Runic ᚨᛁᛊᚺᚨ · Heart Trail A♡i♡s♡h♡a · all accent styles |
| Already plain letters (case styles) | 4 | Title Case · Sentence case · PascalCase · Reversed Words |
The pattern is simple: styles built from the Mathematical Alphanumeric Symbols block, the circled letters and the full-width letters are exactly the characters NFKC was designed to fold. Small caps, phonetic letters and runes are real letters of their own, so NFKC has nothing to fold them into.
CURSIVE SCRIPT
𝓐𝓲𝓼𝓱𝓪
SMALL CAPS
ᴀɪsʜᴀ
HEART TRAIL
A♡i♡s♡h♡a
Try your own name in the box above: the first line is the kind that turns plain in a normalising field, the second and third are the kind that survive. This matters most for names — our page on font styles for a name covers which fields in Instagram, WhatsApp and Facebook accept styled names at all.
Why parts of your stylish text disappeared
When strikes, underlines or glitch effects vanish but the letters stay, the app removed combining marks. A combining mark is a separate Unicode character that draws on top of or below the letter before it, so an app can delete it without touching the letter.
36 of the 104 styles depend on combining marks, including Strikethrough, Underline, Glitch, Heavy Glitch, Bold Strikethrough and every accent style. Those are the styles to avoid for a field that strips marks. Two other invisible characters get removed just as often:
- Invisible spacers such as U+3164 HANGUL FILLER, used by the Hidden Spacer style. Many name fields trim or reject them.
- Variation selectors (U+FE0E and U+FE0F), which tell a phone whether to draw a symbol as text or as a colour emoji. Remove one and ❤️ can become a plain black ❤.
118 decorations that nothing in a paste can change
Every item below passed four tests on 16 September 2026: NFKC leaves it unchanged, it has no combining marks, it has no invisible or format characters, and it contains no right-to-left characters. There is nothing in them for a field to fold, strip or reorder. Tap to copy.
Stars and moons 24
Hearts and flowers 22
Name frames 20
Kaomoji 34
Dividers for a bio 18
Correction: an earlier version of this list included five items that failed the fourth test — one began with an invisible U+200F RIGHT-TO-LEFT MARK and four contained Syriac or Arabic characters. They could make a decoration jump sides, so they were replaced.
Why a decoration jumps to the other side of the name
A decoration jumps sides when the line contains a right-to-left character. Unicode’s bidirectional algorithm lays out neutral characters — brackets, stars, dashes — according to the strongest direction around them, so one Arabic, Hebrew or Syriac letter, or an invisible RIGHT-TO-LEFT MARK, can move a bracket from the end of a name to the start.
The text itself is not reordered. Copy it back out and every character is where you put it; only the display changed. To fix it, rebuild the line one piece at a time and remove the piece where the layout jumps. Of 6,231 decorations we checked from our source pool, 169 contain a right-to-left character, so this is not rare.
When nothing pastes at all
If the paste is empty, the copy never happened. Browsers only allow a page to write to the clipboard after a real tap or click, and only over a secure connection. Tap the page once, then press Copy again. If it still fails, long-press the result, select it, and copy it by hand.
Once it pastes, check it in the real field before you save — a name box and a message box in the same app can behave differently. Build and compare versions on TextStylish, then keep the one that survives.
Short answers
Did the generator send broken text?
No. The copy button sends the exact characters shown on the page; we do not normalise them. Any change happens in the app you paste into.
Can I stop an app from converting my stylish text?
No. Normalisation runs on the app’s servers when the text is saved. Choose a style NFKC does not change, or put the styling in a field that keeps it.
Why does search still find me after my name turned plain?
Because the same normalisation that removed the styling also makes the name match ordinary typing. We explain the trade-off in what stylish text does to search.
Method: NFKC and character categories computed with the Unicode normalisation algorithm on the exact output of the TextStylish generator for “Aisha”; right-to-left detection uses the Unicode Bidi_Class property (R and AL). References: Unicode Normalization Forms (UAX #15) and Unicode Bidirectional Algorithm (UAX #9).
