TLDR
LinkedIn posts have no formatting toolbar — the composer is plain text. Unicode converters can fake bold and italics (with real accessibility and search costs — use sparingly). What always works: line breaks and short paragraphs, simple bullets (• – →), numbers, and a hook in the first ~200 characters before the "…see more" fold. Real typography lives in articles, newsletters, and document posts.
Why there's no bold button on LinkedIn
The post composer — the "Start a post" box — is a plain-text field. No bold, no italics, no headings, no hyperlink text; markdown-style *asterisks* render as literal asterisks. This isn't an oversight so much as a decision LinkedIn has held for years: posts are meant to read like writing, not like documents.
Rich text does exist on LinkedIn — just not in posts. Articles and newsletters have a full editor (headings, bold, links). Document posts render a PDF you designed, which means any typography you want. So the real question behind "how do I format a LinkedIn post" is: which of the three surfaces does your content belong on? For a short post, the answer is the plain-text tricks below. For anything that genuinely needs design, skip ahead to the document-post section.
Unicode bold and italics: the workaround
Every "LinkedIn text formatter" tool does the same thing: it swaps your letters for characters from unicode's mathematical alphabets — 𝗯𝗼𝗹𝗱 and 𝘪𝘵𝘢𝘭𝘪𝘤 lookalikes that are technically different characters, not styling. Because they're characters, they survive pasting into the plain-text composer.
The flow: type your text into a converter, copy the styled version, paste it into your post. That's the entire trick.
It has legitimate uses — a single emphasized word in a headline, a product name you want to pop. The mistake is treating it as formatting rather than as a character substitution with side effects:
Unicode "bold" is not bold — it's different letters. Screen readers announce 𝗯𝗼𝗹𝗱 as "mathematical sans-serif bold b, o, l, d" or skip it. LinkedIn search can't match the styled word. Devices missing the glyphs show ▯▯▯▯. A word of it is decoration; a paragraph of it locks part of your audience out of the post.
If you use it at all: one or two words, never numbers (styled digits break screen readers hardest), never your whole hook — the hook is exactly the text you want searchable and readable by everyone.
Formatting that always works
The reliable toolkit is smaller and better than the unicode hack:
- Line breaks. The Return key works in the composer and survives publishing. White space is LinkedIn's real bold: a blank line between every one-to-two-sentence paragraph is the difference between a post that gets read and a wall that gets scrolled past.
- Short first line. Only about the first three lines (~200 characters) show before the "…see more" fold. That's your headline slot — a specific claim or question, not a wind-up.
- Character bullets. The composer accepts plain characters as list markers: • for lists, → for cause-and-effect, – for asides. Type them (or paste from a note) and they render for everyone, screen readers included.
- Numbers and specifics. "3 mistakes" beats "some mistakes" in a feed skim. Digits are formatting — they create visual texture in plain text.
- Emoji, sparingly. One per section as a visual anchor works; a row of them per line reads as spam and gets announced, name by name, to screen-reader users.
A structure that reads well without any tricks
Plain text plus the toolkit above is enough for a professional-looking post. The pattern that consistently works:
Line 1 — the hook. One specific sentence that fits before the fold. A number, a tension, a result.
The body — one idea per paragraph. Two sentences max per paragraph, blank line between each. If you're listing, use • bullets — three to five items, parallel phrasing.
The close — one ask. A question for the comments, a link in the first comment, or a pointer at your profile. One ask; two asks compete.
Draft it wherever you like, but proof it in the composer: paste, check the fold position with the preview, and re-add any double line breaks the paste collapsed. Post length can run to about 3,000 characters, but the posts that perform rarely use half of that.
Links, hashtags, and mentions
Three more plain-text elements behave like formatting because they change how the post renders:
- Links. A pasted URL renders as a long raw string — there's no way to hyperlink a word in a post. You can delete the URL text after LinkedIn generates the link preview card, which keeps the card and loses the string. The "put the link in the first comment" tactic exists because of the raw-string ugliness as much as any reach theory; test both for your audience rather than trusting folklore.
- Hashtags. They render in blue and break up the text visually. Three to five relevant ones at the end of the post is the standard; a hashtag wall mid-paragraph reads as noise and interrupts screen-reader flow.
- @Mentions. Type @ and pick the person or company — the mention renders bold-ish and blue, the closest thing to native emphasis a post has. Mention only people who'd plausibly respond; tag-spraying for reach notifies ten people and impresses none.
When formatting isn't enough: use a document post
If you're fighting the composer — wishing for headings, brand colors, real typographic hierarchy — your content has outgrown the plain-text post. LinkedIn's answer to that is the document post: you upload a PDF, and LinkedIn renders its pages as swipeable slides in the feed. Inside those pages, typography is entirely yours — fonts, weights, color, layout — because you designed them.
That's the format behind every polished multi-slide post in your feed (the step-by-step upload flow is in our guide to posting a carousel on LinkedIn, and the six recurring structures that work are in our LinkedIn carousel examples breakdown). A document post also sidesteps every cost in this article: no unicode hack, no accessibility damage, no fold gamble — the design carries the hierarchy.
The trade is production effort: real slides at 1080×1350 instead of a minute of typing.
The short version
Format the post in plain text: hook before the fold, blank lines, • bullets, one emphasized word of unicode at most. When the content needs actual design, stop formatting text and ship a document post instead.
For that second path, xcarousel turns a topic, an article URL, or a PDF into designed slides — real typographic hierarchy, one type system across the set — and exports the LinkedIn-ready PDF at 1080×1350. The plain-text caption above it stays yours; this guide is everything that caption needs.