- Does LinkedIn support markdown? What happens when you try it
- So how does LinkedIn bold and italic text work
- The uncomfortable bit nobody wants to say out loud
- What LinkedIn does support natively, without any Unicode trickery
- Step by step: getting formatted text into a normal LinkedIn post
- Where this trips people up in practice
- A word on other platforms, since the confusion spreads
- My actual take, after years of testing this
- Frequently asked questions
The short version: No, LinkedIn does not support markdown syntax in the post composer, so typing asterisks or underscores around a word just leaves the asterisks sitting there looking daft. What LinkedIn does support is Unicode formatting, which is a different technical trick that produces bold and italic text without any actual markdown parsing happening at all.
More on this here: linkedin profile view daily limit.
I found this out the hard way about six years ago, sat in a coffee shop in Windsor trying to make a headline pop in a post about a client launch. I typed **this is important** the way I would in Slack or Notion, hit post, and what appeared on screen was, quite literally, asterisks either side of the words. No bold. No italics. Just a slightly embarrassing set of stars sitting there like I'd forgotten to finish formatting my own sentence. That's the moment most people discover the truth about LinkedIn and markdown, usually in public, usually right before they hit publish.
Does LinkedIn support markdown? What happens when you try it
Markdown is a lightweight formatting language built by John Gruber back in 2004, and it's become the default way people write on platforms like GitHub, Reddit, Notion, and Slack. You wrap text in asterisks for bold, underscores for italics, hashes for headers, and the software behind the scenes converts that plain text into styled text. LinkedIn's composer does none of that conversion. It treats your asterisks as characters, full stop.
So when you write:
- bold text in the box, it stays as asterisks and letters
- a hash symbol at the start of a line does nothing except sit there
- a dash followed by a space does not become a bulleted list, it just looks like a dash
This trips up a lot of people who write on multiple platforms, because your brain gets trained on one syntax and you forget every platform doesn't play by the same rules. I've watched clients paste a whole markdown-formatted brief straight into LinkedIn and publish it without checking, and the result is a wall of hashes and underscores that reads like a ransom note written by a bot.
So how does LinkedIn bold and italic text work
Here's the bit almost nobody explains. Those bold headlines and italic phrases you see scattered through LinkedIn feeds are not created using LinkedIn's own formatting tools, because LinkedIn's own formatting tools for body text are, frankly, non-existent. What people are using is Unicode.
Unicode is the international standard that assigns a number to every character your computer can display, and crucially, it includes entire alternate alphabets that look bold or italic but are technically completely different characters to the regular alphabet. A normal capital A and a "bold" Unicode capital A are not the same character with a style applied, they're two entirely separate symbols that happen to look related. When you type your text into a Unicode text generator and it spits out something that looks bold, what's really happened is every letter has been swapped for its bold Unicode twin.
That's why it works everywhere, including LinkedIn, Twitter and Instagram bios, and even some email subject lines. It's not a formatting instruction the platform is reading and rendering, it's just plain text made of unusual characters, and LinkedIn displays plain text the same way it displays any other plain text, bold twins included.
The tools people use
There are free Unicode text generator sites (I won't name and link one, since they come and go, but searching "bold text generator" brings up several) where you type your sentence, it shows you a bold version and an italic version using these swapped characters, and you copy and paste the result straight into your LinkedIn post box. No plugin, no LinkedIn feature, no markdown. Just character substitution.
A few practical notes from using this for years:
- Not every character has a bold or italic Unicode twin, so numbers and some punctuation sometimes stay in the regular font, which can look slightly patchy
- Screen readers can struggle with Unicode substitutes, because to assistive technology, a bold Unicode letter isn't recognised as the letter it visually resembles, so heavy use can hurt accessibility for visually impaired readers
- LinkedIn's own algorithm reads this text fine for ranking purposes since it's still valid text, but it doesn't get any kind of formatting boost or penalty either way from LinkedIn itself
The uncomfortable bit nobody wants to say out loud
Here's what most guides on this topic skip past. Bold text on LinkedIn does not consistently improve engagement, and in a lot of cases it makes posts look worse, not better. I've tested this across client accounts for years, alternating plain text posts against heavily bolded ones with the same content, same posting time, same hook structure. The plain text version won more often than it lost. Not always, but often enough that I stopped recommending bold Unicode as a default tactic around 2023. The reason is simple once you see it: readers have gotten wise to the "bold first line, italic subheading, bullet list of Unicode arrows" template that flooded feeds for a couple of years, and it now reads as slightly try-hard, the LinkedIn equivalent of a PowerPoint slide with too many fonts. A good hook in plain text still outperforms a mediocre hook wrapped in fake bold. Formatting is a garnish, not a substitute for a sentence worth reading.
That doesn't mean never use it. A single bold line to break up a long post, or one italic aside for tone, still earns its place. Bolding your entire opening paragraph, every single time, on every single post, is the bit that stops working.
What LinkedIn does support natively, without any Unicode trickery
It's worth being precise here, because LinkedIn isn't a total formatting wasteland, it's just far more limited than people expect.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
- Line breaks: pressing enter creates a genuine line break, and this is the single most useful formatting tool you have for readability
- Bullet points using the actual bullet character: LinkedIn's composer has no bullet button, but you can paste a real bullet symbol (•) at the start of a line and it displays as a proper bullet, no Unicode trickery needed
- Emoji: fully supported and rendered natively, and used well they do more visual work than fake bold ever will, arrows and checkmarks especially
- Hashtags: functional and clickable, part of LinkedIn's native system, unlike markdown-style tags on other platforms
- @ mentions: fully native and will notify the tagged person or page
Where LinkedIn Articles differ slightly from regular posts: if you're publishing a long-form LinkedIn article rather than a standard post, the article editor gives you a proper toolbar with real bold, real italic, real headers, and real bullet lists, no Unicode swapping required. That's the one corner of LinkedIn where actual rich text formatting exists. It's a completely separate publishing format from the newsfeed post box, which confuses a lot of people who assume "LinkedIn" behaves the same everywhere on the platform. It doesn't. If you're weighing up whether to run a newsletter on LinkedIn versus regular posts, the newsletter format sits closer to the Articles editor, with proper formatting tools built in.
Step by step: getting formatted text into a normal LinkedIn post
- Write your post in a plain document first, focusing entirely on the sentence structure and the hook, not the formatting
- Decide on no more than two or three words or short phrases that need visual weight, not entire paragraphs
- Search for a free bold text generator or italic text generator, paste in only those specific words
- Copy the Unicode result and paste it back into your draft in place of the plain text
- For lists, manually copy a real bullet character (•) or use short dashes with a space after them, then a line break after each item
- Preview the post in LinkedIn's composer before publishing, because Unicode characters occasionally render differently across desktop and mobile, and what looks fine on your laptop can look cramped on someone's phone
- Read the whole thing back as if you're a stranger scrolling fast, and cut any bold that isn't doing real work
Where this trips people up in practice
A client of mine, a coach who'd built a decent following posting daily (a habit worth thinking through carefully, and I've written before about what happens when you post on LinkedIn every single day), came to me convinced her engagement had dropped because LinkedIn had "turned off formatting." What had happened was she'd started copying entire posts from a Notion doc where she'd used real markdown headers and bullet syntax, and none of it converted, so her posts were arriving as raw hash symbols and dashes. LinkedIn hadn't changed anything. She'd just started drafting somewhere with a different set of rules and never checked the paste. The fix took ten minutes: draft in plain text or draft directly in LinkedIn's box, strip any markdown before pasting, and use Unicode bold sparingly on the hook line only. Her engagement recovered within two weeks, not because of formatting, but because the posts stopped looking broken.
This is also worth knowing if you're outsourcing content work. If you've hired a virtual assistant to help draft or schedule your LinkedIn posts, it's worth explicitly telling them LinkedIn doesn't read markdown, because most scheduling and drafting tools they'll be familiar with (Notion, Google Docs, Trello) do support it, and the mismatch causes exactly the broken-post problem above more often than you'd think.
A word on other platforms, since the confusion spreads
If you're moving content between platforms, it helps to know none of the main social networks read markdown natively in their standard post composer, LinkedIn included. Facebook doesn't render it either, which matters if you're repurposing the same draft across networks; I've covered the specifics of writing well for that particular feed in a piece on blogging on Facebook without feeding an algorithm that doesn't return the favour. Google Docs, by contrast, does support real formatting tools including proper headers and bullet lists you can build from templates, which is one reason I still draft long posts there before moving anything over, and if you've never used its built-in templates, it's worth knowing Google Docs has a surprising amount of free template support baked in already for structured documents.
My actual take, after years of testing this
Use Unicode bold on one line, maybe two, per post, and only where the emphasis earns its place. Skip it entirely on lists longer than four items, because the visual noise of bold Unicode bullets stacked on top of each other is harder to skim than plain text, not easier, whatever the "engagement hack" threads tell you. And if you're drafting anywhere other than LinkedIn's own box, strip your formatting before you paste, every single time, because the ten seconds that takes is cheaper than publishing a post full of stray asterisks in front of people who might be deciding whether to hire you.
Related reading: linkedin work anniversary posts.
Frequently asked questions
Can you use markdown in LinkedIn comments as well as posts?
No, comments follow the exact same rules as posts. Asterisks, underscores, and hashes typed as markdown syntax will show up literally in comments too, so the Unicode bold and italic trick is your only workaround there as well.
Why does my bold LinkedIn text look normal on some phones?
Because Unicode bold characters rely on specific font support, and a small number of older devices or default system fonts don't render every bold or italic Unicode character, so it can fall back to displaying as a plain or slightly odd-looking character on those setups.
Does LinkedIn punish posts that use Unicode bold text?
No, there's no evidence LinkedIn's algorithm treats Unicode-formatted text differently for reach or ranking, since it still reads as valid text characters. Any engagement difference you notice comes down to how readers respond to the look of the post, not a platform penalty.
Is there a way to get real markdown formatting on LinkedIn at all?
Only inside LinkedIn's Articles and Newsletter publishing tools, which use a proper rich text editor with genuine bold, italic, headers, and bullet lists built in. Standard newsfeed posts and comments never get this, only the long-form publishing format does.
Run a business, a brand or a blog? I feature tools, products and expert guest posts for an audience of 15,000. See how it works