LinkedIn see more fold: the character count, and why it is not one number

LinkedIn cuts your post at roughly 210 characters on a desktop feed and roughly 140 characters in the mobile app, and neither number is fixed. The truncation is applied after about three rendered lines of text, not after a set number of characters, so the count moves with screen width, font size, and where your line breaks fall. That is why published figures disagree: 140, 200-210, 210, 215 and 200-220 are all in circulation, and each one is somebody measuring a real screen. In our own sample of 12,988 posts captured at the moment of truncation, the median visible text was 206 characters.

How many characters show before “see more” on LinkedIn?

The working answer is two numbers. On a desktop browser, in the main feed, at a default window size and font size, the preview holds around 210 characters. In the LinkedIn mobile app, on a phone held in portrait, it holds around 140. If you want one number to write against, use 140, because that is the one most of your readers are subject to.

The reason those are approximations rather than limits is structural. LinkedIn is not counting your characters and cutting at a threshold. It is rendering your text into a fixed-height block, showing what fits, and putting a “see more” link at the end of the last visible line. Everything that changes how much text fits into three lines therefore changes the character count, and there are more of those things than most articles admit.

The 3,000-character cap on the whole post is a genuine, documented limit, and it is the only number in this area that LinkedIn confirms in writing. The Posts API returns a FIELD_LENGTH_TOO_LONG error asking you to reduce the length of the commentary field, which is the body of the post (LinkedIn Posts API documentation). The cap and the caps for every other LinkedIn field are covered in the guide to how long a LinkedIn post should be. This page is about the other number, the one nobody publishes.

Why do published see more character counts disagree?

Because they are measurements taken on different screens, and none of them is wrong. Three current sources, all of which have measured it themselves:

Read those three rows together and the disagreement dissolves. A source quoting 140 is describing a phone. A source quoting 210 is describing a laptop. A source quoting one number for both has measured one device and generalised. A source quoting 215 has measured a slightly wider browser window than the one that produced 210. There is no contradiction to resolve, only a missing variable, and the missing variable is the screen.

What none of them can do, and what we cannot do either, is quote LinkedIn. The company has never published the truncation point, does not treat it as a stable contract, and changes feed layout without announcement. Any page that states the number as though it came from LinkedIn is telling you something it cannot know.

Why is there no single LinkedIn see more character count?

Six variables move the cut, and most of them are outside your control.

• Viewport width. The desktop feed column is much wider than a phone column, so a line holds more characters. This is the single biggest factor and the reason the desktop and mobile figures differ by roughly 70 characters.
• Font size and zoom. A reader who has bumped their system font up two steps for accessibility sees fewer characters per line, and therefore a shorter preview, on the same post. Browser zoom does the same thing.
• Hard line breaks. The largest factor you do control, covered in its own section below.
• Attached media. An image, a video player, or a link card takes vertical space in the same feed unit, and the text block above it gets less room. Treat a post with media as having a shorter preview than a text-only post.
• Where the post is being viewed. The main feed truncates. The permalink page for a single post shows considerably more, sometimes all of it. A notification preview and a search result show far less. The same post has several different folds depending on the surface.
• Which build of the feed you are served. LinkedIn runs experiments continuously. Two people scrolling the same post on identical phones can see different amounts of it.

Wide characters deserve a mention as well. Styled Unicode letters, the ones that look like bold or italic in a post, are not letters with formatting applied. They are separate characters, and several of them are wider on screen than the plain letters they imitate, so a hook written in fake bold fills a line sooner. Emoji are wider still. If your first line is a row of emoji bullets, you are spending line width at three or four times the rate of plain text.

What do 12,988 posts say about where the fold falls?

Our dataset turns out to be an unusually direct measurement of the desktop cut, by accident. The source captured each post's text only up to the point where LinkedIn truncated it, which means every row in the file is one observation of where the fold landed for that post. There are 12,988 of them, from 65 accounts.

Split those observations by subject matter and the distribution barely moves. Twenty topics, and the interquartile range sits inside 202 to 208 characters in every single one.

Be careful about what this is. It is not a finding about how creators choose to write. Practically every author in the set wrote past the cut, so the numbers describe the cut rather than the writing. It is also desktop-shaped, because that is how the source was collected. What it does give you is 12,988 independent observations of the desktop truncation point clustering in a five-character band, which is a much stronger basis for “about 206” than one person counting characters in one browser window.

The corollary is worth stating because it saves people time: since almost nobody writes a hook shorter than the cut, hook length cannot be a differentiator, and in our data it is not. The median visible hook in the top decile was 206 characters and in the bottom half 205. One character. The patterns that do separate them are set out in the LinkedIn hooks data.

Here is what a full preview at that length actually contains. Two real posts, captured at the fold, at 206 characters each.

How do line breaks change the see more fold?

This is the part that turns the character count from trivia into something actionable. Because the feed shows a fixed number of rendered lines, a hard line break does not just insert a newline. It ends the current line and forfeits whatever space was left on it.

Work the arithmetic. Suppose the desktop feed shows three lines of about 70 characters each. Written as a single paragraph, your preview holds roughly 210 characters. Written as three short lines of twelve characters each, the same three lines hold 36 characters and the reader hits “see more” almost immediately. On a phone, where a line holds roughly 45 characters, the same one-idea-per-line hook can trigger the cut after two or three short sentences.

None of that makes line breaks bad. White space is close to the only formatting tool LinkedIn gives you, and the one-idea-per-line pattern is genuinely effective below the fold. The rule is about placement: no line break before the point that makes someone tap. Get the tension into the first unbroken run of text, then break as much as you like. The mechanics of inserting breaks on each device, and why they sometimes disappear, are in how to add line breaks in LinkedIn posts.

What is a safe character budget on each surface?

Working numbers, to be treated as budgets rather than as limits. These are what we write to, and they are deliberately conservative.

The 120-character row is the one people miss. Two real posts at opposite ends of the observed band show why the number is worth respecting.

Does getting cut off by the fold hurt your reach?

No. Everything longer than about three lines gets cut off, which is nearly every post published on the platform. Being truncated is the default state, not a penalty. What matters is whether the visible part earns the tap, because the tap is a signal of interest and interest is what the ranking system is looking for. There is more on how that works in the LinkedIn algorithm guide.

The related myth is that a very short post which never truncates does better, because it needs no click. In our data, hook length did not separate the top decile from the bottom half at all, and short posts are not overrepresented among winners. A post that fits entirely above the fold has simply chosen to spend all its budget at once. Whether that works depends on whether the line is good, not on the absence of a “see more” link.

Why does the mobile fold matter more than the desktop one?

Because the smaller number is the binding constraint, and almost every article about LinkedIn hooks quotes the larger one. If your preview works at 140 characters it works everywhere. If it only works at 210, it works for the minority of your readers sitting at a laptop and fails for the rest.

There is a second reason, less obvious and more important. The desktop figure encourages a particular writing mistake: three lines of setup that resolve on line three. That structure survives on a wide screen and collapses on a phone, where line three is behind the cut. The mobile budget forces a different structure, one sentence that carries the tension and a second that supports it, and that structure works on both devices. Writing to the smaller number costs you nothing and protects you from the failure mode.

A practical consequence for anyone writing in the popular broken-up style: the style is a below-the-fold technique. Above the fold it is expensive, because each break forfeits line space you cannot get back. Use continuous prose for the opening, then break freely once the reader has committed. The same logic drives most of how to format a LinkedIn post, and the opening-line drills are in how to start a LinkedIn post.

What should the visible preview actually contain?

A budget is only useful if you know what to spend it on. Three things belong in the preview, in this order, and everything else is a candidate for deletion.

1. The tension. A claim, a moment, a number, or a contradiction. Something that creates a question the next line answers. This has to arrive inside the first sentence, and preferably inside the first eight words, because the first eight words are what survives every surface including notifications.
2. The stake. Why the tension matters, or who it happened to. One clause, rarely more.
3. The unresolved edge. The sentence should still be moving when the cut arrives. A preview that completes its own thought has told the reader they can stop.

Four things do not belong there, and all four are common. A greeting. A hashtag block, which spends characters on tokens the reader skips and is separately associated with weaker posts in our data, as set out in the hashtag analysis. A URL, which is expensive in characters and pulls attention off the page. And a summary of what the post is about, which is the most common waste of all: readers do not need to be told a post is coming, they can see it.

The Berkeley Haas example earlier is the textbook case of a full budget spent on nothing. Two hundred and six characters, an institution, a conference, a job title and a thank-you, and 7 comments from a 12,000-follower account. The truck-driver example spends its first 30 characters on a fact that stops a reader dead and collects more comments than reactions from a 3,000-follower account. Same budget, different purchase.

Does the fold work the same for polls, documents, and reposts?

Not quite, and the differences are worth knowing if you publish anything other than plain text.

• Document carousels. The document viewer occupies a large block under the text, so the text above it gets a short preview. Treat the caption on a LinkedIn carousel as a single sentence. The first slide is doing the hook work anyway.
• Polls. The question and the options render as their own block below the text, which pushes the cut up. A poll post with three lines of framing above the question is mostly hidden.
• Reposts with a comment. Your added commentary gets a very short preview because the reposted unit sits underneath it. One line, and make it the reason you are resharing rather than a summary of what you are resharing. There is more on what reposts cost in the reposting guide.
• Link posts. The preview card takes vertical space and the URL itself, if left in the body, takes characters. Both squeeze the text.
• Native video. The player is large, so the caption preview is short. This is one reason video captions in our data are shorter in feel even though the captured character counts are the same: the writers are working to a tighter visible budget.

How do you test your own see more cutoff in five minutes?

Every number on this page is a population estimate. Yours is measurable, and the measurement is worth more than any published figure because it accounts for your own device, your own font size, and the way you actually write.

1. Take a post you already published that runs past three lines. Open your own profile activity in a desktop browser at your normal window size.
2. Find where “see more” appears and copy the text up to that point into a character counter. Write the number down. That is your desktop budget.
3. Open the same post in the mobile app, on your own phone, at your own font size. Repeat. That is your mobile budget, and it is the one that matters.
4. Now repeat both with a post that has an image attached, and with a post written one idea per line. You will get two more, smaller numbers.
5. Take the smallest of the four and use it as your working hook budget from now on. For most people it lands somewhere between 100 and 140 characters.
6. Check drafts against it before publishing rather than after. The hook analyzer counts characters to your first line break, which is usually the number that binds.

Do this once a quarter. The feed layout changes, and a budget measured eighteen months ago is a guess.

What else on LinkedIn truncates?

The feed post is the famous one, but the same rendering logic applies across the product, and each surface has its own cut.

• Commentscollapse after a few lines with their own “see more”, which is why a long comment often reads as a post published in the wrong place.
• The profile headline holds 220 characters, but the version that appears next to your name in feeds and comment threads is a short truncation of the front. Load the front. There is more in the profile optimization guide.
• The About section collapses after roughly two or three lines.
• Link preview cards truncate the page title and description to fit the card, independent of your post text.
• Notification and email digest previews show far less than the feed does, often under 100 characters.

The pattern across all of them is the same: the front of the text is the only part guaranteed to be read anywhere. That is the entire argument for front-loading, and it is a stronger argument than any specific character count.

The short version of the LinkedIn see more fold

The LinkedIn see more fold character count is about 210 on desktop and about 140 on mobile, and the honest framing is that it is a three-line cut wearing a character count as a costume. Published figures disagree because they measure different screens, LinkedIn does not publish a number, and the only reliable version is the one you measure on your own device. Our 12,988 captured previews put the desktop cut at 206 characters with an interquartile range of 203 to 208. Write the sentence that has to land inside 140, keep line breaks out of the preview, and treat everything past that as a bonus.