LinkedIn formats ·
How to write a long LinkedIn post (over 1,500 characters) that doesn't die at "see more"
A LinkedIn post is cut at roughly 210 characters on desktop and 140 on mobile with a "see more" that decides whether the reader continues or moves on. The maximum limit is 3,000 characters, and most long posts die not because of their topic but because they are written as if the "see more" did not exist. In 2026, with a saturated feed and the stylistic classifier rewarding retention above almost everything, one well built long post beats three short ones.
This article explains how to design a long post's architecture, where to place readable breaks, which topics call for 1,500 to 3,000 characters, and when the right answer is not a post but an article or a carousel.
By Sheena de PunkVoice · Edited by Mario Pérez
What the "see more" really decides
The first 140 characters (mobile) or 210 (desktop) are the part visible before the cut. LinkedIn calls it the post's above-the-fold portion and measures the expansion rate: how many people who see that portion tap "see more". Above 8% in your professional segment is high, below 3% is a signal that the first sentence does not promise enough.
The expansion rate feeds the dwell time classifier and the post's relevance score. A long post with low expansion gets distributed less than a short one of average quality, because the algorithm reads it as heavy content with no hook. A long post with high expansion and reading through to the end is the strongest signal you can give the algorithm, above even long comments.
That is why designing a long post starts before the post: in the first two sentences. If those two sentences do not hold up the rest, the rest does not matter. The operating rule is that the above-the-fold portion has to work as a standalone short post with a clear promise that there is more below.
The architecture of a long post in five blocks
The structure that performs consistently in posts between 1,500 and 2,800 characters has five blocks, each with a distinct function. Skipping any of them sinks the post; merging two into the same block loses the rhythm.
- Hook (1 to 2 sentences, around 200 characters): a concrete promise or a contradiction of the industry consensus. Close before the "see more" with a sentence that demands opening.
- Context (3 to 4 sentences, around 400 characters): who you are to speak on the topic, what situation brought you to it, why it deserves a long post rather than a tweet. Without context the hook looks like clickbait; with too much, the rhythm is lost.
- Core (around 50% of the post, around 1,400 characters): the substance. Data, the mechanics of the matter, three or four points numbered or developed. This is where the reader decides whether they learned something. If the core can be summarised in two sentences, the post did not need to be long.
- Counter-argument (2 to 3 sentences, around 300 characters): a legitimate objection to the core, treated seriously. It closes the reader's doubts and defuses comments that were going to say "but...". It separates a considered post from a loose opinion.
- Close (2 to 3 sentences, around 250 characters): a practical consequence or an open question inviting comments. Not a sales call to action, not a "what do you think?". A specific question your network genuinely has something to say about.
Readable breaks: why the nine line block kills
The LinkedIn feed renders the line breaks in the original post. A 2,500 character post presented as one compact block is unreadable on mobile, however excellent the content. Retention collapses within the first 400 characters.
The pattern that pays off in 2026 is blocks of one to three lines separated by a blank line. A three line paragraph is the maximum tolerable; four and up become a wall. Emoji at the start of a line work as bullets without being bullets (an arrow, an asterisk, a neutral symbol), but overusing them makes the post look like a landing page.
The practical rule is writing the whole post first, then running your eye over each block and asking: is this a paragraph or a wall? If it is a wall, break it in two at the natural full stop. The post takes up more screen, but all of the screen it takes up gets read.
Which topics call for a long post (and which call for something else)
Not every topic deserves 2,000 characters. The ones that do share three traits: there is a story or a mechanic to explain (not just an opinion), the reader will take away something applicable, and the angle justifies why you did not say it in less.
- Long post yes: a concrete case with an outcome and a lesson, analysis of an industry shift with data of your own, the deconstruction of a hard decision, an operational guide to a poorly documented process.
- Not a long post (better short): pure opinion, a hot take on the day's news, celebrating an achievement, saying thanks.
- Not a long post (better as a native carousel): content with a visual structure, a list of more than seven points, comparisons, a mini guide with screenshots.
- Not a long post (better as a LinkedIn article): a topic that needs more than 3,000 characters, content with footnotes and sources, exhaustive analysis you want cited externally.
Cadence and timing for long posts in your calendar
A profile publishing three times a week performs better with one long post every two or three posts rather than in every one. Alternating long with short generates a reading rhythm the classifier recognises as a varied profile and rewards with more consistent distribution.
The day matters too: long posts perform better on Tuesday, Wednesday and Thursday mornings, when the professional reader has room to read an extended text. Monday morning and Friday afternoon are short post territory, because the consumption mode is faster. Publishing the month's best considered long post on a Friday at 5pm is a predictable waste.
The long post as a serious format, not a wall of text
A long post is an editorial decision. It takes more time, more editing and more judgement than a short one, and in exchange it gives the profile a density the loose opinion feed cannot match. In 2026 the stylistic classifier rewards that density when it is well built and penalises it when it is only volume.
The operating rule is a single one: if the topic cannot hold five blocks with distinct functions, it is not a long post; it is two short posts or a carousel. The waste is not writing 2,500 characters, it is writing 2,500 characters that could have been said in 400.