ChatGPT to LinkedIn formatter
Paste Markdown from ChatGPT, Claude, or Gemini. Get LinkedIn-ready bold, headings, and bullets—em dashes tidied. Not a post writer or hand formatter.
What this conversion changed
- 1 table flattened. LinkedIn has no tables. Each row is now one line with cells separated by a middle dot. Anything wider than three columns is usually better as a screenshot or a carousel.
- 1 heading became bold lines. LinkedIn has no heading levels, so an H2 and an H4 both come out as one bold line. If the structure mattered, use blank lines and shorter sections instead of nesting.
Punctuation tidied
- Em dashes: 3 → -
3 runs of text became styled Unicode characters. Those are not real bold — they are different letters that happen to look bold, so they will not match a LinkedIn or Google search for the plain word. Keep your keywords, hashtags, and name in ordinary letters.
What gets converted
| Markdown in | LinkedIn out | Notes |
|---|---|---|
**bold** | 𝗯𝗼𝗹𝗱 | Sans-serif bold, the most reliable styled alphabet. |
*italic* | 𝘪𝘵𝘢𝘭𝘪𝘤 | Sans-serif italic. Underscores work too. |
## Heading | Bold line | LinkedIn has no heading levels, so every depth looks the same. |
- item | • item | A real bullet character, because Markdown lists do nothing. |
1. item | 1. item | Kept as digits — already the most readable option. |
[text](url) | text (url) | Link syntax does nothing here. LinkedIn auto-links a bare URL. |
> quote | “quote” | No blockquote styling exists, so quotation marks stand in. |
`code` | 𝚌𝚘𝚍𝚎 | Monospace characters — the look, not a real code block. |
| Tables | One line per row | Cells joined with a middle dot. Lossy by necessity. |
Line breaks are the other half of the problem
Formatting is not usually what ruins a pasted AI draft — spacing is. LinkedIn treats blank lines inconsistently: the desktop composer keeps a double return, the mobile app often discards extra blank lines, and comments do not support them at all.
This converter collapses runs of three or more newlines to a single blank line, which is the spacing LinkedIn preserves most reliably, and removes the non-breaking and zero-width spaces that models sprinkle through prose. If your spacing still collapses after pasting, the LinkedIn formatting troubleshooting guide covers the invisible-character workaround and when it is worth using.
What this does not do
- It does not write the post. There is no model here and no generated text — it converts what you already have.
- It does not make text undetectable as AI-written. Removing em dashes changes punctuation, not the writing underneath. Any tool selling detector evasion is selling a guess.
- It does not create real formatting. Converted bold is a set of substitute characters. That is the only mechanism LinkedIn allows, and it comes with the screen reader trade-offs attached.
- It does not keep a copy. Nothing is uploaded and nothing is stored.
If you need to go the other way — someone sent you styled text and you want plain letters back — use convert fancy text to normal.
Frequently asked questions
Why does my ChatGPT text look broken when I paste it into LinkedIn?
Because the assistant replied in Markdown and LinkedIn does not read Markdown. The chat window renders **bold** as bold, so you never see the asterisks — but the text you copied still contains them, and LinkedIn shows them literally. Headings become ## in the feed, and hyphen bullets stay hyphens.
Does Markdown work on LinkedIn at all?
No. Not in posts, comments, headlines, or the About section. The only place with genuine rich text is the article editor, which has its own toolbar. Everywhere else, formatting has to be characters, which is what this converter produces.
What happens to tables?
Each row is flattened to a single line with cells separated by a middle dot, because LinkedIn has no table support of any kind. For anything wider than three columns that is a poor result no matter what the tool does — a screenshot or a document carousel will read better.
Why does it change em dashes?
Em dashes are the most-cited giveaway that text came out of a language model, and they are the one artefact people most often want gone. You can switch the replacement to a comma or keep them. This is about tidying punctuation, not about defeating AI detectors — those do not work by counting dashes, and no tool that claims otherwise is telling you the truth.
What else does it clean up?
Curly quotes and apostrophes become straight ones, the single-character ellipsis becomes three periods, en dashes become hyphens, and non-breaking and zero-width spaces are removed. Invisible characters matter more than they sound: they survive a paste and can make a line break in an unexpected place. Every change is counted in the readout so you can see what happened.
Can I strip the Markdown instead of converting it?
Yes — switch to “Strip it to plain text”. You get the structure without any styled characters: clean prose, bullet characters for lists, and no Unicode substitution at all. That is the better choice for accessibility, and for anywhere the text needs to stay searchable.
Are my drafts sent anywhere?
No. The conversion is JavaScript running in your browser. Nothing is uploaded, there is no account, and unposted drafts do not leave your device — which is not something you can say about extensions and scheduling tools that need a login.
Should I convert the whole post to styled characters?
No. A post that is entirely styled characters is slower to read, invisible to LinkedIn search, and awkward on screen readers that do not normalise. The useful pattern is a styled first line and plain body text, which is what “Headings become bold” gives you by default.