Flaghand

Guides · Updated

Formatting a LinkedIn post

Start with plain text, short paragraphs and a clear first sentence. A line break is real text. A bold-looking letter from a formatter is a different Unicode character, not a font setting. And where “see more” cuts a post depends on its rendered lines, not a fixed number of characters.

Checked on October 26, 2026 against LinkedIn's own help pages, linked below. Its article editor has formatting controls that ordinary feed posts don't share. LinkedIn's editorial advice supplies the spacing and hashtag recommendations; Unicode's specification explains the styled letters. The help pages don't specify a pixel-level feed cut or how search normalizes those letters. The cut described here is Flaghand's measured web-feed model, not a published LinkedIn guarantee.

Try the free LinkedIn text formatter, character counter and LinkedIn post previewer. They work without an account; the text stays in your browser.

Line breaks and spacing

Press Enter to start a new line. Leave an empty line between paragraphs when you want a visible gap. A sentence wrapping because it reaches the edge is not a saved line break: it can wrap somewhere else on a phone.

We shipped a smaller, faster export today.

Three things changed:
• Less waiting
• Clearer file names
• One folder to keep

Here is what we learned from the first version.

LinkedIn's own feed-writing guidance recommends short paragraphs, separate lines for distinct ideas and white space for scanning. That's writing advice, not an algorithm trick. One blank line is a useful starting point, not a platform rule. Stacks of empty lines use up the opening preview; don't add invisible “blank” characters to force spacing.

LinkedIn's sharing help allows up to 3,000 characters in a post. Spaces and line breaks use that budget too. Flaghand counts UTF-16 code units, matching its desk's post check: a plain Latin letter is 1, most emoji and the formatter's styled letters are 2. LinkedIn's help gives the limit, not that counting algorithm. Use the LinkedIn counter after pasting the final text, rather than trusting a word count.

Bold and italic: different letters, not rich text

For an ordinary feed post, **bold**, *italic* and HTML such as <b>bold</b> aren't formatting instructions. Don't copy Markdown into LinkedIn expecting the asterisks to disappear. LinkedIn's developer text format lists plain text, mentions and hashtags, not Markdown bold or italic elements.

LinkedIn's article-editor help does document bold, italic, lists and hyperlinks. That is Write article, not Start a post. Don't apply the article instructions to a feed post.

A formatter makes News look like 𝗡𝗲𝘄𝘀 by replacing letters with Unicode mathematical letters. They survive a plain-text paste because the characters themselves changed. The free formatter offers bold, italic, bold italic and monospace, plus a Plain action to undo them. Its From Markdown action converts common Markdown styling before you copy; LinkedIn itself isn't doing that conversion.

Why screen readers and search can read styled letters poorly

Unicode encodes these mathematical alphabets as distinct characters for mathematical meaning, not decorative styling of prose. A screen reader's handling depends on its software, voice and settings: it may announce a mathematical character name, spell letters separately or fail to speak them usefully. Looking bold is not the same as an accessible heading or emphasis.

The same distinction matters to search and copy-and-find: News and 𝗡𝗲𝘄𝘀 are different strings. A search system must normalize the mathematical letters to match a plain-letter query. LinkedIn's help doesn't say whether every search surface does that, so don't assume either reliable matching or that styled text is completely unsearchable. This isn't evidence of a ranking penalty.

Keep names, keywords, links, hashtags and essential meaning in plain letters. For the most readable version, use spacing and wording instead of styled alphabets. If you choose styled emphasis, keep the ordinary wording elsewhere too; never make it the only way someone can understand the post.

Lists: put the marker in the text

Use • or - for bullets, or 1. , 2. and so on for an ordered list, with each item on a new line. These are plain-text markers, not an article editor's structured list. A long item still wraps to the width of the feed.

The formatter's bullet and numbered list actions insert those markers for you. LinkedIn's developer text-format example likewise represents bullet points as characters separated by newlines; its escape characters are API syntax, not extra backslashes to paste into the post box. For a genuinely formatted article list, use the article editor instead.

Hashtags: ordinary words, joined up

Write a relevant hashtag as one word, for example #ProductDesign, not #Product Design. Keep it in plain letters. LinkedIn's search help says you can search a hashtag by entering it in the search bar, even though hashtags aren't offered as suggested searches.

LinkedIn's feed-writing guidance says to capitalize the first letter of each word for readability and screen-reader accessibility. Hashtags can sit in the sentence or at the end. Use them when they explain the topic, not as a promise of extra reach. This guide doesn't prescribe a magic count or promise a dedicated hashtag feed.

Mentions: select the account, don't just type a name

In LinkedIn's own composer, type @ and begin the person's name, then select the right person from the suggestions. The mention help page makes that selection part of the process. It also says members can turn mentions off and LinkedIn may restrict mentions of non-connections. A pasted @Name should not be treated as proof of a linked mention or a notification.

A preview is not a connection to the account. In Flaghand's desk, company-page tags need the correct organization identity, not just visible text; tagging people isn't supported. Its draft and media documentation explains that boundary. Typing @[Name] in a free preview doesn't create a real LinkedIn mention.

Paste the complete URL. In LinkedIn's composer, wait for its preview before deciding whether the card is the one you want. LinkedIn's link-sharing help says a preview image can take a few seconds and that you can share the link even when an image doesn't appear.

The card's title, description and image come from the destination page's oEmbed or Open Graph metadata, not from a bold heading you write above the link. LinkedIn's URL troubleshooting help explains missing or stale previews and tells developers to allow 48 hours after metadata changes for its cache to update. It also says URLs with spaces can't be shared; use a properly encoded URL.

An inline clickable URL and a preview card are different things. Don't expect [read this](https://example.com) to turn into an article-style labeled hyperlink in a feed post. Check the actual destination and the card separately. A free text preview isn't a fetch of that site's metadata; when using Flaghand's desk, save and review the actual link card as part of the draft before requesting approval.

Where “see more” cuts at 552 px

There isn't a universal “first 140 characters” or “first 210 characters” rule. Wide letters, narrow letters, line breaks, links and the available width all change what fits. The post limit and the collapsed preview are different checks: a valid 3,000-character post can hide most of its text in the feed.

Flaghand's LinkedIn renderer models the 552 px desktop card with a three-line collapsed text area and a 20 px line height. After layout, it measures the words on those lines. If text overflows:

These are the measured rules in Flaghand's public/li.js (placeMore), with the 552 px card in public/li.css, checked for this guide on October 26, 2026. They aren't rules stated in LinkedIn Help, and LinkedIn can change its UI. The phone preview uses a 390 px card, so it can cut earlier. Don't choose an opening by character count alone.

Paste your final text into the LinkedIn previewer, check desktop and phone, then expand it. The LinkedIn counter also marks the hidden portion using that same renderer. For a version of the post on X, use the X counter: its weighted count is different.

A final check

Read the opening without expanding it. Check the paragraph gaps and lists on a phone. Keep important words in plain letters, select real mentions in the posting tool, and inspect every link and its card. A text formatter makes a draft; it doesn't publish it or establish that a mention or card has been checked on LinkedIn.

If an agent helps write it in Flaghand, the agent drafts, checks and requests approval. Only the owner approves the exact snapshot with their passkey in the desk. No agent token can approve, schedule or post.

Sources and what was checked

All checked on October 26, 2026. Public documentation and synthetic local previews only; no real post was made.