Skip to content
Part of: How-to format
General

Why Does Bold Text Work in My Caption but Not the Comment?

Bold survives in an Instagram caption but vanishes in the comment box because they are different input systems. Your bold is Unicode look-alike text; a comment, username or search field can strip non-standard characters. In a native-markdown chat app, the box wants that app's own bold syntax instead: a single asterisk on WhatsApp, double asterisks on Discord, and on Telegram the reliable native path is the highlight menu.

Shreyas Bagal·Jul 4, 2026·4 min

Bold survives in an Instagram caption but vanishes in the comment box because they are different input systems. Your bold is Unicode look-alike text; a comment, username or search field can strip non-standard characters. In a native-markdown chat app, the box wants that app's own bold syntax instead: a single asterisk on WhatsApp, double asterisks on Discord, and on Telegram the reliable native path is the highlight menu.

Key takeaways

  • A caption and a comment can run on different input rules inside the same app, which is why styled text works in one field and breaks in the other.
  • BoldlyType's bold is Unicode look-alike characters (e.g. 𝗕 = U+1D5D5), plain text that pastes anywhere — not a font file and not markdown.
  • Comment boxes, usernames, and search bars are locked-down fields that often strip non-standard characters; captions are the most permissive.
  • In native-markdown chat apps, use the app's own syntax, not pasted Unicode: a single asterisk on WhatsApp, double asterisks on Discord, and the highlight menu on Telegram mobile.
  • Telegram's typed **bold** auto-converts reliably only on Desktop and Web; on mobile the selection/highlight menu is the dependable cross-client route.
  • There is no public evidence that Unicode styling triggers a shadowban; the real cost is indirect, via accessibility and search.
Why Does Bold Text Work in My Caption but Not the Comment?
On this page

Definition

Because they are two different systems. Your bold "font" is Unicode look-alike characters. They paste and survive anywhere as plain text: captions, bios, display names. If it fails in a comment box, that field is either stripping non-standard characters or expecting the app's own markdown instead.

The confusing part is that both boxes look like they should behave the same. They don't. A caption and a comment can run on different input rules even inside the same app, and that one difference is why your styled text lands in one and breaks in the other.

What is actually in your "bold" text?

When you use a generator like BoldlyType, you aren't installing a font. You're copying real Unicode characters. The bold 𝗕 is code point U+1D5D5, a distinct character from the normal B (U+0042). These live in the Unicode "Mathematical Alphanumeric Symbols" block and cover only Latin letters and digits.

Because they're ordinary text characters rather than styling instructions, they travel with a copy-paste the same way an emoji does. That's why the same string works across Instagram, X, LinkedIn, TikTok and most bios. Nothing is being rendered. The characters simply are what they are. So when a field refuses them, the field is doing something to the characters, not to a font.

Why does the same text work in a caption but not a comment?

There are three common reasons a comment box (or reply, or search bar) rejects text a caption accepted:

ReasonWhat's happeningTypical symptom
The field strips non-standard charactersComment/username fields often allow-list a narrow character set for spam and safety reasonsYour text posts as blank, plain, or with characters dropped
The field is a plain-text-only inputSome inputs deliberately normalize everything to basic ASCIIBold pastes but shows as normal letters
You're in a native-markdown fieldThe box wants the app's own bold syntax, not UnicodeNothing styles, or your asterisks show literally
A length/validation limit tripsUnicode characters can count as multiple charactersText is cut off or the field rejects it

Captions are usually the most permissive field an app has, since they're built for expressive, long-form text. Comments, replies, display names and search boxes are more locked down, so they're where Unicode styling most often gets stripped. This is the same mechanism behind text showing up as empty boxes: the character exists, but that specific surface won't render or keep it.

Which fields most often strip or block styled text?

  • Instagram comments are noticeably stricter than captions, and styling frequently drops.
  • Usernames and display-name fields are heavily restricted on most platforms.
  • Search bars normalize input so a search still matches plain text.
  • In-app chat markdown fields, where bold is native markdown, expect the app's own syntax rather than pasted Unicode. This splits by app:
    • WhatsApp bold is a single asterisk on each side: *bold*.
    • Discord bold is double asterisks: **bold**.
    • Telegram typed **bold** (double asterisks) auto-converts reliably only on Telegram Desktop and Web. On mobile that typed-markdown conversion is inconsistent, so the dependable native path on every client is the selection/highlight menu (highlight the text, pick bold from the pop-up). See the full breakdown in our Telegram formatting guide and WhatsApp/Discord/Slack guide.

In those native-markdown boxes, pasted Unicode bold is unnecessary, and sometimes counter-productive, because it can trip accessibility and search. For a full walkthrough of building styled text that survives, see how to make stylish text.

Does using Unicode text where it doesn't belong cause problems?

It can, and this is the honest tradeoff. Unicode "font" characters are not read the same way as normal letters. Screen readers may announce them oddly, letter by letter, or skip them entirely, a real accessibility cost covered in are Unicode fonts accessible. Search and platform indexing can also treat "𝗯𝗼𝗹𝗱" as different from "bold," so styled keywords may not match queries.

On reach, there is no public evidence that Unicode styling itself triggers a shadowban, and no substantiated data for a secret penalty. What is real is the indirect effect. If a caption is unreadable to a screen reader or unsearchable, that can quietly cost you. Use styling for accents (a name, a heading, one line), not for whole blocks of body copy or every keyword.

How do I get the style to stick where it keeps breaking?

  1. Confirm the field, not the text, is the problem. Paste the same string into a caption or a note. If it works there, the comment box is stripping it.
  2. In native-markdown chat apps, use the app's own syntax. Single asterisk on WhatsApp, double on Discord, the highlight menu on Telegram mobile, instead of pasting Unicode.
  3. For strict fields, simplify. Try a lighter style (bold only), or fall back to plain text plus an emoji accent.
  4. Keep body copy plain. Style the hook or a name, and leave the rest readable and searchable.

You can test any of this in seconds with the bold text generator or the Instagram text formatter. Copy, paste into the target field, and see whether it survives before you post.

Ready to put this into practice?

Open a formatter

Sources

Spotted an error? Email hello@boldlytype.com — we update guides when platforms change and welcome corrections.

Frequently asked questions

Latest questions readers ask us about this topic.

Why does my bold text disappear only in Instagram comments?

Instagram's comment field is stricter than its caption field. Comment boxes commonly allow-list a narrow character set for spam and safety reasons, so non-standard Unicode characters get stripped or normalized to plain letters. The same string usually pastes fine into a caption or bio because those fields are more permissive.

Is BoldlyType text a font file or markdown?

Neither. It is real Unicode characters from the Mathematical Alphanumeric Symbols block — look-alike Latin letters and digits, like 𝗕 (U+1D5D5) instead of B (U+0042). Nothing is installed and nothing is rendered from markup; the characters travel with a copy-paste the way an emoji does.

Should I use Unicode bold inside WhatsApp, Discord, or Telegram?

No — those apps have native markdown, so use their own syntax. WhatsApp bolds with a single asterisk (*bold*) and Discord with double asterisks (**bold**). On Telegram, typed **bold** auto-converts reliably only on Desktop and Web; on mobile, highlight the text and pick bold from the pop-up menu, which works on every client.

Does using Unicode fancy text hurt my reach or get me shadowbanned?

There is no public evidence that Unicode styling itself triggers a shadowban, and no substantiated data for a secret penalty. The real risk is indirect: styled text can be unreadable to screen readers and may not match search queries, so keep it to accents like a name or a heading rather than whole captions.

How do I tell if the field or my text is the problem?

Paste the exact same string into a known-permissive field like a caption or a phone note. If it renders bold there but not in the comment box, the field is stripping it, not your text. For strict fields, simplify to a lighter style or fall back to plain text with an emoji accent.

Related in this series

See all in How-to format

Explore the topic cluster

More tools and guides across this topic cluster.

Get the next post.

Craft notes on writing for the internet. One short email, every other week. No spam.

Keep reading