LinkedIn Text Formatter

Complete Guide to Formatting LinkedIn Posts

LinkedIn has no built-in bold, italic, or underline button. The workaround most people use (and the workaround this tool automates) is Unicode. Here is how it actually works, when to use it, and what the tradeoffs are.

Why LinkedIn blocks rich text

LinkedIn strips HTML and markdown from posts before publishing. The feed is rendered by the LinkedIn mobile app, the LinkedIn desktop site, and a handful of third-party embeddings, and none of them agreed on a common rich-text format. To keep posts consistent across surfaces, LinkedIn simply removes formatting tags. What survives is the raw Unicode string.

That single decision is why every LinkedIn formatter you have ever used converts your text to Unicode rather than applying CSS. The styled output is not really "bold" in the typographic sense. It is a different letter.

How Unicode Mathematical Alphanumerics work

In 2001, Unicode added a block called Mathematical Alphanumeric Symbols (U+1D400 to U+1D7FF) so mathematicians could write a bold vector or an italic variable inline without switching fonts. The block contains full A-Z, a-z, and 0-9 alphabets in these styles:

• Bold (serif): the original Mathematical Bold, looks like serif bold.
• Italic and Bold Italic: serif italic variants.
• Sans, Bold Sans, Italic Sans, Bold Italic Sans: the sans-serif family. Bold Sans (what this tool calls Math Sans Bold) is the style most people actually want, because LinkedIn's own UI is set in a sans-serif font. Serif bold letters look out of place.
• Script and Bold Script: cursive handwriting style.
• Fraktur: Gothic blackletter.
• Double-Struck: the "blackboard" style mathematicians use for real numbers, integers, and so on.
• Monospace: fixed-width, typewriter-like.

LinkedIn, Twitter, Facebook, and most other platforms render these characters as-is because they are ordinary Unicode, not formatting. This is why you can paste them anywhere LinkedIn accepts text: posts, comments, direct messages, headlines, the About section, article titles.

The UTF-16 character cost problem

LinkedIn's 3,000-character post limit is measured in UTF-16 code units, which is the same number JavaScript's string.length returns. Regular ASCII letters cost 1 unit. But every character in the Mathematical Alphanumeric Symbols block sits outside the Basic Multilingual Plane, which means it is encoded as a surrogate pair, which means each letter costs 2 characters against the 3,000 limit.

Underline and strikethrough work differently. They keep the base letter as a normal ASCII character and add a combining diacritic (U+0332 for underline, U+0336 for strikethrough) after it. That combining mark also costs 1 character, so every underlined or struck letter costs 2 characters too.

Only three styles stay 1:1 with the limit: Fullwidth (U+FF00 block, inside the Basic Multilingual Plane), Uppercase, and Lowercase. Everything else doubles your character spend.

This is why the rule "use formatting sparingly" is not just an aesthetic guideline. It is a math constraint. A 3,000-character post written entirely in Math Sans Bold becomes a 1,500-character post. The counter on this tool tracks the real cost live as you type.

When to use each style

• Math Sans Bold and Math Sans Bold Caps: hooks, calls to action, headlines, section breaks. The sans-serif match with LinkedIn's UI is the cleanest look.
• Math Sans Italic: inline emphasis, quoted speech, book or product titles.
• Bullet List, Radio List, Two-State Radio List: structured posts, progress updates, "here's what I shipped" style recaps. Radio-button lists perform well on posts that show before/after or done/pending states.
• Numbered List: step-by-step posts, ranked lists, listicles.
• Underline: sparingly, for a single keyword. Overuse looks noisy.
• Strikethrough: self-corrections, "don't do X, do Y" patterns.
• Script, Fraktur, Double Struck: decorative. Works for personal branding, logos, or attention-getting quotes. Use once or twice per post, never as body text.
• Fullwidth: novelty spacing effect. Good for a short hook or a one-word punchline.
• Uppercase and Lowercase: useful when pasting text you copied from somewhere with the wrong casing.

Platform compatibility

Unicode text works everywhere LinkedIn accepts text, including:

• Posts (feed, company pages, newsletters, articles)
• Comments on other posts
• Direct messages
• Your headline, About section, and custom pronouns
• Event and group descriptions
• Job post descriptions (though recruiters often avoid formatting here for ATS compatibility)

Rendering is identical on desktop web, iOS app, Android app, and the mobile web view. LinkedIn does not apply its own font substitution to these characters, so what you see in this preview is what your audience sees.

Accessibility, honestly

Unicode Mathematical Alphanumerics are not semantic bold or italic. They are different letters that happen to look bold or italic. Screen readers handle them inconsistently. Some read them character by character ("mathematical bold A, mathematical bold u, mathematical bold t..."), some skip them entirely, some read them as the underlying letter but without the bold emphasis. LinkedIn's own accessibility documentation discourages heavy use for this reason.

The practical answer is the one this tool's interface keeps repeating: use formatting for emphasis (a headline, a CTA, a single highlighted phrase), never for entire paragraphs or for information that matters to the meaning of the post. If a visually impaired reader would miss critical content because the screen reader skipped it, you have used the format wrong.

How this tool compares to the alternatives

Typegrow is the closest direct equivalent; it has been the default recommendation in LinkedIn creator circles for the past two years. This tool was built as a free, focused, no-upsell alternative with two features Typegrow does not ship: a UTF-16-aware character counter, and the two-state radio progress list.