Why LinkedIn strips your formatting (and how to fix it)
You just spent 20 minutes drafting a LinkedIn post using ChatGPT, Claude, or Gemini. You have good hooks, bolded keywords, and clean lists. You hit "Paste" into LinkedIn, and everything breaks.
All your bolding is gone, replaced by asterisks and symbols (**like this**).
Prefer to watch? Here's the 90-second walkthrough:
The problem: LinkedIn is plain text
Despite being a professional network, LinkedIn's standard text editor does not support rich text formatting. It does not understand the formatting symbols AI uses, so it just prints the asterisks instead of making the text bold.
The solution: special copy-pasteable text
The only way to get bold or italic text on LinkedIn is to use special copy-pasteable text formats. These are Unicode characters that happen to look exactly like bold letters.
Because they are actual characters (not formatting code), LinkedIn displays them correctly.
How to do it manually:
You can search for a "Bold Text Converter" online, type in your keyword, copy the bold result, and paste it back into your LinkedIn post. Doing this for every bold word in a 300-word post takes a while.
How to do it instantly:
We built AI Text Formatter to solve this problem.
- Paste your entire AI-generated draft into the tool.
- Toggle on "Keep bold".
- The tool finds every AI bold symbol (
**text**) and replaces it with the correct Unicode bold characters (𝘁𝗲𝘅𝘁). - Click "Copy Result" and paste directly into LinkedIn.
Your formatting will survive the paste, your hooks will stand out in the feed, and your audience will not be distracted by leftover AI symbols. Try it on your next post.
What actually survives where on LinkedIn
Not every corner of LinkedIn behaves the same, so here is the map:
- Feed posts: plain text only. Unicode bold, italic, and • bullets all render; markdown does not.
- Comments: same as posts — Unicode formatting works, which is a quiet way to make your comment stand out in a thread.
- Headline and About section: Unicode renders here too. A single bolded phrase in your headline is visible every time you comment anywhere.
- LinkedIn Articles: the one place with a real rich-text editor. If you are publishing an article, use the editor's own bold button — no Unicode needed.
- Messages: Unicode renders in DMs as well, but use it sparingly; heavy formatting in a direct message reads as salesy.
Bold is only half the job
The posts that perform are formatted around scannability, not decoration:
- The first two lines are the whole game. LinkedIn truncates posts behind "…see more" after roughly 200 characters. Your hook — often the only bolded line you need — has to land before that fold.
- White space beats walls. One- and two-sentence paragraphs with blank lines between them consistently out-read dense paragraphs, especially on mobile where most LinkedIn reading happens.
- Real bullets, not hyphens. AI drafts produce
-and*lists that paste as literal symbols. Convert them to clean • characters — the formatter does this with the "Keep bullets" toggle. - Watch the limit. Posts cap at 3,000 characters. Our editor shows a live LinkedIn character count so you trim before LinkedIn truncates for you.
The accessibility caveat
Honest downside: screen readers often announce Unicode bold letters individually, which makes fully-bolded paragraphs genuinely unpleasant for visually impaired readers. The fix is restraint — bold your hook and a handful of key phrases, and keep the substance of the post in regular characters. That also happens to be what reads best for everyone else.
Frequently asked questions
Does Unicode bold hurt my post's reach? There is no evidence LinkedIn downranks Unicode text — it appears constantly in high-performing posts. What hurts reach is unreadable formatting: all-bold walls and gimmicky script fonts get skipped by readers, and low dwell time is what the algorithm actually punishes.
Why does my bold text look different on some devices? Unicode bold comes from the Mathematical Alphanumeric Symbols block, and a small number of older devices render those code points with a fallback font — or as boxes. Keep names, numbers, and links in plain text so the message survives even in the worst case.
Can I use italics and strikethrough too? Yes — the same trick covers 𝘪𝘵𝘢𝘭𝘪𝘤, bold-italic, s̶t̶r̶i̶k̶e̶t̶h̶r̶o̶u̶g̶h̶, and u̲n̲d̲e̲r̲l̲i̲n̲e̲, all available from the toolbar in the formatter. Strikethrough is handy for the classic "old way ~~vs~~ new way" post structure.
By the way, the exact same Unicode trick works on Facebook, which also has no bold button for posts. See how to bold text in a Facebook post — or go straight to the Facebook post formatter.