RESEARCH · Sep 2, 2026 · 2 min read
How LinkedIn actually handles formatting (and why "bold" isn't bold)
A look under the hood: LinkedIn posts don't support Markdown, HTML, or true rich text — only Unicode character substitution and, in Articles only, real formatting.
- Teardown
- research
- formatting
- unicode
- rich-text
The starting assumption was simple: LinkedIn must support some form of rich text, and the job was just to find the right conversion path from Markdown to it.
That assumption didn't survive contact with the platform.
01 — What LinkedIn posts actually accept
LinkedIn posts are plain text. There is no Markdown support, no HTML rendering, and no native bold/italic/underline formatting in the standard post composer.
What looks like bold or italic text in LinkedIn posts (𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀) isn't formatting at all — it's Unicode character substitution. Each "styled" letter is actually a different Unicode code point that visually resembles a bold or italic version of the standard character. It's a workaround, not a feature.
02 — The one exception
LinkedIn Articles are the only surface that supports genuine rich text formatting — real bold, italics, headers, and structure. Regular feed posts do not get this treatment, regardless of how the content was authored or pasted.
The moment you understand LinkedIn posts are fundamentally plain text with a Unicode trick layered on top, the whole design problem changes shape — from "convert Markdown to LinkedIn's rich text" to "convert Markdown to the best plain-text approximation LinkedIn allows."