LinkedIn formatting not working

Quick steps

1. Work out which of the three failures you have: styled characters rejected, blank lines collapsing, or Markdown showing up literally.
2. For a rejected headline or About section, strip the styling — those fields validate their characters and no workaround makes them accept it.
3. For collapsing spacing, paste on desktop and use a single blank line between paragraphs rather than several.

Three different problems get called the same thing

“LinkedIn formatting not working” covers three unrelated failures, and the fix for one makes the others worse. Identify yours first.

Styled characters are rejected outright, with a save error. That is field validation and it is deliberate.

Your spacing disappears — the post looked right in the composer and arrives as a wall of text. That is line-break handling, and it differs between desktop and mobile.

Asterisks and hash symbols appear literally in the feed. That is Markdown, and LinkedIn has never supported it.

Why the headline refuses styled characters

The headline field validates what you type and rejects the mathematical alphabet with an “invalid characters” error. No amount of retrying or switching styles gets past it, because it is a rule rather than a rendering problem.

Practitioners have reported the same block extending to the About summary, with existing styled text being converted back. LinkedIn has not published anything confirming that, so treat it as likely rather than certain — and test your own profile while logged out before relying on it.

This is worth being relaxed about. The headline is the single most valuable plain-text field you own: it appears in search results, connection requests, and every comment you leave, and only the first 60 to 70 characters are visible in most of those places. Styled characters would have made it unmatchable in search anyway.

Posts and comments are a different matter. Those accept styled characters and always have.

Why your line breaks vanish

The desktop composer keeps a single blank line between paragraphs reliably. Beyond that, behaviour varies: the mobile app frequently discards extra blank lines, and comments do not support blank lines at all — a paragraph break you type in a comment will close up.

Pasting is the usual trigger. Text copied from Google Docs, Notion, Word, or the iOS Notes app carries its own paragraph markers, and LinkedIn does not always translate them into the breaks it would have created itself. Pasting into a plain-text editor first, then copying again, strips the markers and fixes most cases.

Use one blank line, not three. Runs of blank lines are the first thing to be collapsed, so a post built on double and triple gaps is the most fragile kind.

The workaround people reach for is an invisible character: put a zero-width or blank character on the otherwise-empty line so the line is no longer empty and survives. It works, but it is worth knowing the cost — a screen reader may announce the character, and it counts against your 3,000. Our invisible character tool explains which blank characters actually survive a paste.

There is also a long-running bug in the About section where your own formatting looks correct to you and renders as a single block to visitors. If the spacing is right in your editor and wrong for everyone else, check it in a logged-out browser window before rewriting it.

Why Markdown appears literally

LinkedIn does not read Markdown in posts, comments, headlines, or the About section. The only place with genuine rich text is the article editor, which has its own toolbar.

This catches people out most often with AI-drafted posts. ChatGPT, Claude, and Gemini reply in Markdown, and the chat window renders it — so you see bold text, not the asterisks producing it. The text on your clipboard still contains them, and LinkedIn prints them.

The same applies to hyphen bullets. A line starting with “- ” stays a line starting with a hyphen; LinkedIn will not turn it into a list. Real lists in the feed are literal bullet characters such as •.

Our ChatGPT to LinkedIn formatter converts a Markdown draft in one paste, and tells you what it had to change — tables and code blocks lose the most.

Fixes that do not work

Retrying the headline. The validation is not intermittent.

Switching to a different styled alphabet. Fraktur and double-struck are rejected the same way, and they are also the two most likely to render as empty boxes on Android when they are accepted.

Pasting HTML. There is nowhere in a LinkedIn post that interprets tags.

Trusting the composer preview. The composer is not the feed. Mobile truncates earlier and treats spacing differently, which is why our formatter shows a desktop and a mobile fold separately.