Last updated October 11, 2026 · Report an error
Many plain-text contexts — chat apps, usernames, bios, comment fields — don't support rich-text underline formatting, so there's no button or markup that reliably underlines a word there. This tool works around that by inserting a Unicode combining low-line mark (U+0332) after every character, producing genuinely underlined-looking text using plain characters that display correctly almost anywhere, since the underline is baked directly into the text itself rather than relying on the receiving app to interpret formatting markup. It's a simple way to add emphasis to a word or short phrase in a context — like a social media bio, a plain-text chat message, or a username — where no native formatting option exists.
How it works
A combining low-line character (U+0332) is inserted immediately after each character in your text. Because Unicode combining marks are designed to render layered onto the preceding character rather than as a separate glyph, this produces a visible line beneath each character wherever the rendering software correctly supports Unicode combining marks, which is the case in nearly all modern software.
- Enter text.
- Click Calculate to see your results.
Examples
Emphasizing a word in chat
Typing "important" produces an underlined-looking version usable in a plain-text chat message with no rich-text formatting support, drawing the reader's eye to that specific word.
Underlining a name in a username or bio
Applying the effect to a name or handle in a social media bio is a common way to make it visually stand out from surrounding plain text without needing image editing.
Who should use it
- Emphasizing a word in a chat app or username.
- Novelty underlined social posts.
- Highlighting a name or handle in a bio.
Industry applications
- Social media/chat communication
Advantages
- Works in plain-text-only contexts.
- Real Unicode characters, copy-paste ready.
- Displays correctly on nearly all modern platforms.
Limitations
- May render less cleanly than native underline formatting where that's supported.
- Not always treated as identical to plain text by search/accessibility tools.
Common mistakes to avoid
- Using this where real Markdown/HTML underline is already available — native formatting usually looks cleaner and remains more accessible there.
- Applying the effect to long text, which can reduce readability compared to a short emphasized word.
- Assuming underlined text is indexed or read identically to plain text by search or accessibility tools.
Best practices
- Use specifically for plain-text-only contexts without rich-text formatting support.
- Reserve underlining for a single word or short phrase for the clearest emphasis.
- Test how your target platform renders combining marks before relying on this for something important like a username.
Tips
- If your platform supports HTML or Markdown, native underline formatting will usually render more cleanly.
- Keep underlined phrases short for the most legible effect.