Why Does My Underlined Text Look Broken? (And How to Fix It)

You generated some perfectly clean underlined text, copied it, pasted it into Instagram or WhatsApp — and now it shows up with gaps between the underline and the letters, or worse, as a row of empty boxes (□□□□).

Frustrating, right?

The good news: this is almost always a font rendering issue, not a problem with the text itself. Once you understand what's going on, you can fix it (or work around it) in seconds.

This guide walks through every reason underlined Unicode text can look broken, how to diagnose which one is hitting you, and what to do about each.

A 30-second crash course in how Unicode underline works

To understand why text breaks, you need to understand how it's built.

When you use a tool like Underline Text Generator, the tool doesn't actually create underlined letters. It takes each letter you typed and pairs it with a special combining character — most commonly U+0332 (combining low line) — that the system is supposed to render as a horizontal line beneath the letter.

So h̲ is technically two characters: the letter h plus the underline mark. Same for every other letter in your styled text.

For this to look right, three things have to happen on the device displaying the text:

1. The font being used must include glyphs for both characters
2. The text rendering engine must know to draw the combining mark on top of (well, under) the letter
3. The font's metrics — the spacing rules — must position the mark correctly

When any of these three fails, you get visual glitches.

Issue 1: Underline appears as separate boxes (□)

What you see: Instead of h̲e̲l̲l̲o̲, you see something like h□e□l□l□o□.

Why it happens: The font being used doesn't include the U+0332 combining low line glyph at all. The system's fallback is to show a generic "missing glyph" box.

Where it happens most:

• Older Android devices (Android 7 and below)
• Some custom-themed apps that override the system font
• Older Windows email clients
• Embedded WebViews in third-party apps

The fix:

• Best option: Update the device's OS or use the text on a more modern device
• Workaround: Use a different underline style. Some styles use more universally supported characters (like underscores between letters, or character-based "underlines" with hearts/dots/stars). Try the "alternative" styles in our generator.
• For your viewers: If your audience has old devices, mention they may see boxes — or just stick to plain text for important info

Issue 2: Underline is offset from the letters (floating below or to the side)

What you see: The underline mark appears, but it's clearly misaligned — too low, too far to the right, or sitting below where you'd expect.

Why it happens: The font has the U+0332 glyph, but the font's combining-mark positioning data is incorrect or outdated. This is most common in fonts designed before Unicode standardized combining-mark positioning rules (Unicode 9, released 2016).

Where it happens most:

• Older Android system fonts (Roboto pre-2017)
• Some bundled fonts in Microsoft Word and old Windows
• Custom decorative fonts on websites that don't include proper combining-mark metrics

The fix:

• Try a different underline style — thicker or stylized underlines (like the "double" or "extra thick" options) often have different combining characters that may render better
• If the issue is on a specific website you can't update, switch to a different stylization approach (like wrapping text in dashes: -h-e-l-l-o-)

Issue 3: Letters with descenders (g, j, p, q, y) overlap with the underline

What you see: Most letters look fine, but in g̲ or y̲, the underline crosses through the descending tail of the letter.

Why it happens: This isn't a bug — it's actually how combining underline is supposed to work in Unicode. The U+0332 mark is positioned at a fixed height below the baseline, regardless of letter shape. Letters with descenders extend below the baseline, so they intersect the underline.

This is the same reason the original <u> HTML tag looked ugly with descenders — and why CSS later introduced text-decoration-skip-ink to skip the underline through descenders.

The fix:

• This is largely cosmetic and most viewers won't notice
• If it bothers you: try a slightly lower underline style (some generators offer "low underline" variants) or switch to a "double underline" style which gives more visual breathing room
• Or simply rephrase to avoid words ending in descenders in the underlined portion

Issue 4: Spaces don't get underlined

What you see: h̲e̲l̲l̲o̲ w̲o̲r̲l̲d̲ — the underline disappears in the gap between "hello" and "world."

Why it happens: A space character (U+0020) followed by U+0332 has the combining mark applied to the space — but most fonts render the space as having zero width or no visible underline glyph. Some fonts treat the combining mark on a space as invalid and drop it entirely.

The fix:

• Most underline generators (including ours) handle this by not underlining spaces — which is actually the standard typographic convention anyway
• If you specifically want the underline to extend through spaces, use a different generator that uses non-breaking-space + combining-low-line, or a special "thick" underline style that uses dedicated underscoring characters

Issue 5: Underline disappears when copied to a different app

What you see: Text looks underlined in app A, but when you paste it into app B, the underline is gone.

Why it happens: Two possibilities.

Possibility A: App A was using HTML/markdown underline (like Discord's __hello__ or HTML's <u>hello</u>), and you copied the rendered display into a clipboard that stripped the formatting. App B receives just the plain word "hello" without any underline.

Possibility B: Some apps strip combining marks when text is pasted, especially if the app's input field has aggressive auto-correction or normalization. WhatsApp's About field has done this in some older versions.

The fix:

• For Possibility A: Generate proper Unicode underlined text from a tool like Underline Text Generator instead of copying rendered HTML/markdown. Unicode underline travels everywhere.
• For Possibility B: Try pasting again, and if it still strips, the destination app is broken. Try the same paste on a different device or app version.

Issue 6: Auto-correct breaks underlined words

What you see: You typed a sentence, pasted underlined text in the middle, and your phone's keyboard "corrected" the underlined word into a regular word.

Why it happens: Mobile keyboards run spell-check on your text after you paste. When they see h̲e̲l̲l̲o̲, they don't recognize it as a word — and they "fix" it by replacing it with their best guess at what you meant.

The fix:

• Paste your underlined text last, after you've finished typing the rest of the message
• Or temporarily disable auto-correct (most keyboards let you toggle it from a long-press of the spacebar or a quick keyboard settings screen)
• Or wrap the underlined word in something the keyboard won't auto-correct, like quotes: "h̲e̲l̲l̲o̲"

Issue 7: Text shows perfectly to me, but my friend sees boxes

What you see: On your phone, everything looks great. But when you ask a friend to check their phone, they screenshot you something that looks like □□□□.

Why it happens: Their device has an older OS or a system font that doesn't support combining low line. Common culprits: Android 6/7, very old budget Android phones, locked-down enterprise phones.

The fix:

• There's nothing you can do from your side — the text is fine; it's their rendering that's broken
• For mass communication (Instagram captions, WhatsApp broadcasts), assume 5–10% of viewers on older devices may see glitches and put your most important info in plain text

Issue 8: Underlined text looks fine on the website, broken in the screenshot

What you see: You paste underlined text into Instagram, looks great. Take a screenshot, send to a friend — the screenshot looks broken.

Why it happens: Screenshots capture exactly what your screen rendered. If your screen rendered correctly, the screenshot will too. If you're seeing a discrepancy, it's most likely:

1. The screenshot was taken at a moment when the text was still loading and Instagram was using a fallback font
2. You're viewing the screenshot on a different device than the one that took it, and the viewing device renders the screenshot differently (which shouldn't happen for image files — so this is rare)
3. You're confusing two different sessions (the underline got changed somewhere between)

The fix: Take a fresh screenshot. If the issue persists, it's a problem with how Instagram (or another platform) is rendering on your specific device — try clearing the app's cache and restarting.

Issue 9: The underline looks "off-color" or faded

What you see: The underline is there, but it's a different shade than the letters — usually slightly grayish or thinner.

Why it happens: Some fonts render the combining low line with anti-aliasing settings different from the main letter strokes. On certain displays, this makes the line look less crisp than the letters.

The fix:

• Use a thicker underline style (the "thick" or "extra thick" options in our generator) — these stack multiple combining marks for a heavier, more visible line
• This is mostly a perceptual quirk and viewers rarely notice unless they zoom in

Issue 10: Underlined text breaks when wrapped to a new line

What you see: A long underlined paragraph wraps to a new line, and the underline either disappears at the wrap point or carries over awkwardly to the next line.

Why it happens: Different platforms handle line-wrapping inside Unicode-styled text differently. Most handle it correctly, but some chat apps (Telegram on certain Android versions, some Reddit clients) have edge cases.

The fix:

• Avoid using long stretches of underlined text (it's also bad for readability)
• Insert manual line breaks before the wrap would naturally happen, so you control where the line splits

A practical rendering compatibility guide

Based on testing across major platforms in 2025–2026:

| Platform | Classic underline | Double | Wavy | Thick | Symbol-based | |---|---|---|---|---|---| | iPhone (iOS 16+) | ✅ | ✅ | ✅ | ✅ | ✅ | | Android 10+ | ✅ | ✅ | ✅ | ⚠️ | ⚠️ | | Android 7–9 | ✅ | ⚠️ | ⚠️ | ⚠️ | ❌ | | Windows 11 (Chrome/Edge) | ✅ | ✅ | ✅ | ✅ | ✅ | | Mac (Safari/Chrome) | ✅ | ✅ | ✅ | ✅ | ✅ | | WhatsApp Web | ✅ | ✅ | ✅ | ⚠️ | ⚠️ | | Discord (desktop) | ✅ | ✅ | ✅ | ✅ | ✅ | | Discord (mobile) | ✅ | ✅ | ⚠️ | ⚠️ | ⚠️ |

Legend: ✅ works perfectly • ⚠️ may have minor visual issues on some devices • ❌ frequently broken

What to do if nothing works

If you've tried multiple styles and none render correctly on the target platform:

1. Switch tactics. Instead of Unicode underline, try Unicode bold or italic — they're more universally supported.
2. Use markdown if available. On Discord, Slack, Reddit, and WhatsApp, native markdown formatting (**bold**, *italic*, __underline__) bypasses Unicode rendering issues entirely.
3. Combine with emoji separators. Use vertical bars or arrows (✦ Important Note ✦) to draw attention without relying on combining characters.
4. Test before posting. Always paste your styled text into a draft on the actual platform and check rendering before publishing publicly.

Frequently asked questions

Will Unicode underline get more reliable in the future?

Likely yes — newer Android versions, font updates, and OS patches improve rendering steadily. The reliability gap between iOS and Android has shrunk significantly since 2020.

Is there a "perfect" underline style that works everywhere?

The classic single underline (U+0332) has the widest support of any underline style. If reliability matters more than aesthetics, use that.

Are some underline characters better than others for accessibility?

Honestly, no — all combining-mark underlines cause issues for screen readers. If your text needs to be screen-reader friendly, use plain text and rely on platform-native bold/italic instead.

Can I report a broken rendering bug to Apple/Google/etc.?

Yes — Apple has Feedback Assistant, Google has the Android Issue Tracker, and Microsoft has Feedback Hub. Realistically, individual reports rarely lead to fixes for niche Unicode rendering issues, but it doesn't hurt.

Does using a different browser fix things?

Sometimes. Chrome, Firefox, and Safari each use slightly different text rendering engines. If a website displays Unicode poorly in one browser, try another. (This won't fix Instagram/WhatsApp app rendering — those are native apps, not browser-based.)

Try a different style, problem solved

Most "broken" underline issues are solved by switching to a different style. Our Underline Text Generator gives you 30+ styles in one place — so when one style breaks on a specific platform, you have plenty of alternatives to test.

If underline isn't cooperating at all, try our fonts generator for bold, italic, script, and 100+ other styles that often render more reliably across older devices.