# 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](/linkedin-text-formatter), [character counter](/linkedin-character-counter)
and [LinkedIn post previewer](/linkedin-post-preview). 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.

```text
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](https://www.linkedin.com/business/talent/blog/talent-acquisition/how-to-write-engaging-post-in-linkedin-feed)
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](https://www.linkedin.com/help/linkedin/answer/a525301) 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](/linkedin-character-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](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/little-text-format?view=li-lms-2026-10)
lists plain text, mentions and hashtags, not Markdown bold or italic elements.

LinkedIn's [article-editor help](https://www.linkedin.com/help/linkedin/answer/a522427/creating-articles-on-linkedin)
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](/linkedin-text-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](https://www.unicode.org/versions/Unicode17.0.0/core-spec/chapter-22/)
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](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/little-text-format?view=li-lms-2026-10)
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](https://www.linkedin.com/help/linkedin/answer/a523136/search-on-linkedin?lang=en) 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](https://www.linkedin.com/business/talent/blog/talent-acquisition/how-to-write-engaging-post-in-linkedin-feed)
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](https://www.linkedin.com/help/linkedin/answer/a525082/mention-people-in-your-posts) 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](https://app.flaghand.com/docs/drafts-and-media) explains that boundary. Typing `@[Name]` in a free
preview doesn't create a real LinkedIn mention.

## Links and their cards

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](https://www.linkedin.com/help/linkedin/answer/a525301) 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](https://www.linkedin.com/help/linkedin/answer/a525063/issues-sharing-urls-troubleshooting?lang=en)
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:

- It removes empty lines at the end of the visible preview. If the third line is a paragraph break, the preview can
  show only two lines; it doesn't pull a later paragraph up into that space.
- It leaves room for the **“… more”** button after the last whole word that fits on the last visible line. That
  button can hide words that would otherwise fit across the full width.
- Expanding the post reveals the remaining text. A post that fits needs no button.

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](/linkedin-post-preview), check desktop and phone, then expand it.
The [LinkedIn counter](/linkedin-character-counter) also marks the hidden portion using that same renderer. For a
version of the post on X, use the [X counter](/x-character-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.

- LinkedIn Help: [share articles or links](https://www.linkedin.com/help/linkedin/answer/a525301) — the 3,000-character
  limit, link entry and preview images.
- LinkedIn Help: [write and publish articles](https://www.linkedin.com/help/linkedin/answer/a522427/creating-articles-on-linkedin)
  — formatting controls belong to the article editor.
- LinkedIn Help: [mention people](https://www.linkedin.com/help/linkedin/answer/a525082/mention-people-in-your-posts)
  — selecting the member and mention restrictions.
- LinkedIn Help: [search on LinkedIn](https://www.linkedin.com/help/linkedin/answer/a523136/search-on-linkedin?lang=en)
  — manual hashtag searches, not a promise of reach.
- LinkedIn Help: [troubleshoot shared URLs](https://www.linkedin.com/help/linkedin/answer/a525063/issues-sharing-urls-troubleshooting?lang=en)
  — metadata, cache refresh and spaces in URLs.
- LinkedIn's [feed-writing guidance](https://www.linkedin.com/business/talent/blog/talent-acquisition/how-to-write-engaging-post-in-linkedin-feed)
  — paragraph spacing and capitalized hashtag words; editorial advice, not a Help Center layout specification.
- LinkedIn's [little Text Format](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/little-text-format?view=li-lms-2026-10)
  — supported text elements and newline-separated bullet example; developer documentation, not Markdown support.
- Unicode's [mathematical symbols specification, sections 22.2.2–22.2.3](https://www.unicode.org/versions/Unicode17.0.0/core-spec/chapter-22/)
  — distinct mathematical alphabets and compatibility mappings. The accessibility warning is not a claim that every
  screen reader fails; the search warning is not a measured LinkedIn ranking result.
- Flaghand's shared LinkedIn renderer and text counter — the measured 552 px cut, phone comparison and UTF-16 count.
  LinkedIn's help pages don't publish those implementation details.

[All guides](/docs/guides.md)