You typed a word into a generator, the preview showed tall, layered letters, and then you pasted it into a bio, a chat, or a document. What you got was empty boxes, plain letters, or a smear of marks crowding the line above. When stacked text looks broken after paste, the text itself is usually fine. The characters are still there. What changed is how the app, the font, or the input field you pasted into handles Unicode combining marks. This guide explains why that happens and walks through seven fixes, starting with the most common causes.
Why Stacked Text Looks Broken After You Paste It
Stacked text looks broken after paste because it is not an image and it is not a special font. It is a normal letter followed by several Unicode combining marks, and every app decides on its own how many of those marks to draw, which font to draw them in, and whether to keep them at all. The generator preview shows the best case. The place you paste into shows what that app can actually handle.
The Unicode Standard includes a block of combining diacritical marks, running from U+0300 to U+036F, that was built to add accents to letters in many languages. A stacked text generator reuses those marks. It places several of them after each base letter, and the renderer draws them one above the other, which creates the tall, layered look. Normal accents use one or two marks. Stacked text uses more, and that extra height is where most problems begin.
Because the result depends on the destination, the same string can behave in three different ways. Some apps show the full stack. Some trim it to a fixed number of marks. Some remove the marks entirely and leave only the plain letters. On top of that, the font in use and the line spacing of the field can change what you see even when every mark survives the paste.
The table below matches what you see with the most likely cause, so you can jump to the right fix.
| What you see after pasting | Most likely cause | Fix to try |
|---|---|---|
| Plain letters with no marks | The field removes combining marks | Fix 1 |
| Empty squares or question marks | The font has no glyphs for the marks | Fix 2 |
| Marks cut off at the top, or overlapping the line above | Tight line height or a clipped container | Fix 3 |
| Missing letters or a shortened result | Incomplete copy | Fix 4 |
| Text cut off or rejected at a limit | Marks count toward the character limit | Fix 5 |
| Odd size, color, or spacing around the text | Hidden formatting came along with the paste | Fix 6 |
| Looks right in one app and wrong in another | Different rendering support | Fix 7 |
Fix 1: Check Whether the Field Strips Combining Marks
If your pasted text shows plain letters with no marks above them, the field you pasted into is almost certainly removing combining marks. This is common in username fields, search boxes, and form inputs, where the platform wants clean, predictable text. The marks are discarded on paste, and nothing you do to the text itself will bring them back in that field.
The quickest way to confirm this is to paste the same stacked text into a second, unrelated place, such as a notes app or a message to yourself. If the marks appear there, the original field is the problem. If they disappear in both places, the problem is more likely the copy step or the font, which the next fixes cover.
When a field strips the marks, the practical choices are limited. You can move the stacked text to a field that accepts it, such as a bio or a caption instead of a username, or you can switch to a different text style that does not depend on combining marks. Another detail worth knowing is that a name made of stacked characters is hard to type back in by hand. If you use it as a login or a searchable handle, you may not be able to enter it again later.
Fix 2: Switch to a Font That Supports Combining Marks
When stacked text shows up as empty squares or question marks, the font in the destination does not have the glyphs it needs. Operating systems usually substitute another font when a character is missing, but if no installed font covers the mark, you get a placeholder box instead of a mark.
Support also varies in quality, not only in presence. Some fonts include the marks but position them poorly, so the stack leans sideways or sits too close to the letter. A body font that looks great for ordinary writing may handle a tall column of marks worse than a plain system font.
Here is how I usually approach it:
- Change the font of the destination to a common system font and paste again.
- On a website or a design tool, check whether a custom font is being forced onto the field, since a fixed font family blocks the usual fallback behavior.
- Open the same text on a second device. If it renders on a phone but not on a desktop, or the other way around, the difference is the fonts installed on each device.
If squares still appear after a font change, the destination likely cannot render the marks at all, and Fix 7 is the better route.
Fix 3: Add Line Height So the Marks Stop Being Clipped
If the top of your stacked letters is cut off, or the marks overlap the line above, the line height or the container is too tight for the stack. Combining marks extend above the normal height of a letter, and a field that assumes standard text height has no room for them.
This shows up in a few predictable ways. A single-line input can clip anything that rises above its box. A word processor set to an exact line spacing, rather than automatic spacing, can slice off the tops of tall characters. A web page or app with a fixed line height and a hidden overflow setting does the same thing. In a long paragraph, tall stacks from one line collide with the line above and make the whole block hard to read.
What works in practice:
- In a word processor, change line spacing from an exact value to single or multiple, so the line can grow with its content.
- In a field you control, such as a page builder, increase the line height and the padding above the text.
- Place stacked text on its own line with space above and below it, instead of inside a dense paragraph.
If the field belongs to someone else, such as a social platform, you cannot change its spacing. In that case the better fix is to reduce how tall the stack is, which Fix 5 covers.
Fix 4: Copy the Whole Result So No Marks Get Left Behind
An incomplete copy is a quiet cause of broken stacked text, and it produces results that look like a rendering problem when they are really a clipboard problem. If the last word is missing, or the final letters have no marks, the selection probably stopped short.
Manual selection is the usual culprit, especially on touch screens, where dragging the handles to cover a long string of letters and marks is easy to get slightly wrong. Selecting by hand also makes it possible to miss a trailing mark at the end of the text.
The more reliable path is to regenerate the text and use the copy button rather than selecting it yourself. A stacked text generator that offers a one-click copy places the entire string on the clipboard in one step. After copying, paste it into a notes app first and check that the first and last letters both carry their marks. Then paste it into the final destination.
It also helps to paste once and avoid editing the stacked text afterward. Deleting or retyping a letter in the middle of a stacked word can separate a base letter from its marks or leave marks attached to the wrong character. Fixing the source text in the generator and copying again is cleaner than repairing the pasted version.
Fix 5: Lower the Mark Count When Character Limits Apply
Stacked text can fail at a character limit because every combining mark counts as its own character in many counters. A short word with several marks on each letter can use far more of the limit than its visible length suggests. A nine-letter word with five marks on every letter becomes 54 characters, even though it looks like nine.
This matters most in places with tight limits, such as a 150-character bio or a short display name. When the limit is exceeded, the app may reject the paste, cut the text at the limit, or trim the string in the middle of a stack. A cut in the wrong place leaves the last letters bare or damaged, which looks broken even though the cause is simply the count.
You can work with this in three ways:
- Shorten the text. A single word or a short name in stacked style often reads better than a full sentence.
- Use a lower intensity if the generator offers one, so each letter carries fewer marks.
- Keep the stacked part to the one element you want to stand out, and write the rest of the line in plain characters.
A shorter, lighter stack also solves several other problems at once. It fits in the field, it clips less, and it overlaps neighboring lines less.
Fix 6: Paste as Plain Text to Remove Hidden Formatting
When stacked text arrives with a strange size, color, or spacing, the extra formatting came along from the source. Pasting as plain text removes that formatting and leaves only the characters, which is all that stacked text needs to work.
This happens most in word processors, email editors, and website builders, where a normal paste can bring along font settings from wherever the text was copied. Those settings can override the font of the destination, change the line spacing, or add styling that interacts badly with tall marks.
Most editors offer a paste without formatting option. On many desktop systems the shortcut is Ctrl+Shift+V on Windows or Cmd+Shift+V on a Mac, and some editors also list it in a Paste Special menu as unformatted text. After pasting this way, set the font and the spacing in the destination itself, so the field controls the look rather than the clipboard.
This fix is cheap to try and it never makes things worse, so it is worth doing before spending time on the more involved changes.
Fix 7: Match the Style to the Platform When Support Is Limited
If stacked text works in some apps and fails in others, the failing apps do not support a tall stack of combining marks, and the right fix is to change the style, not to keep adjusting the paste. Platforms differ in how many marks they allow per character, and no setting on your side overrides that.
There are a few sensible fallbacks. Use a lower mark count so the text stays inside whatever limit the app applies. Choose a different style that uses single characters instead of combining marks, such as bold or small caps, since a single character is less likely to be trimmed or stripped. Or place the stacked text in an image when the design matters more than the ability to copy and edit it as text.
Accessibility deserves a mention here as well. Screen readers may read each combining mark aloud or handle the text unpredictably, so a heavily stacked name can be hard for some people to follow. For anything people need to read, search for, or act on, such as a contact line or a call to action, plain text is the safer choice. Keeping stacked text for decoration, and keeping essential information in standard characters, avoids most of the trouble.
How to Test Stacked Text Before You Post It
The simplest way to avoid broken stacked text is to test a short sample in the destination before you commit to the final version. Five or six letters are enough to show whether the marks appear, whether they clip, and whether the font supports them.
A short routine I find useful:
- Generate a small sample with a Unicode stacked text generator and copy it with the copy button.
- Paste it into the real destination field, and check the first and last letters.
- View the result on both a phone and a desktop screen if the content will be seen on both.
- If the sample works, generate the full text at the same intensity and paste it in the same way.
Testing on more than one device matters because rendering depends on the fonts and the software of the device showing the text, not only the one that created it. Something that looks right on your screen can still look different to a reader on another phone or browser, and a short test catches the obvious cases.
What to Do When Stacked Text Is Still Not Displaying Correctly
If you have tried each fix and the result still looks wrong, the destination probably cannot render stacked text well, and the best option is to simplify. Reduce the number of marks, shorten the text, or choose a style that relies on single characters instead.
It helps to remember what stacked text is. It is a visual effect built from characters that were designed for accents, pushed well past their normal use. Apps are not required to support that, and many handle it inconsistently. Treating the effect as optional decoration, with a plain version of the text ready as a fallback, keeps your content readable wherever it lands.
The pattern across all seven fixes is the same. Find out where the break happens, whether in the field, the font, the spacing, the copy, the character limit, or the formatting, and change that one thing. Most cases where stacked text looks broken after paste turn out to be one of these causes, and the table near the top of this guide points to the right one in a few seconds.
