For most posts, 900 to 1,800 characters (about 150 to 300 words) tends to perform well. The hard platform limit is 3,000 characters. Your hook has to land inside the first 140 characters on mobile (around 210 on desktop) before the 'see more' cutoff, because that is all readers see without taking any action.
Below: an ideal-length-by-format reference table, a length-by-use-case comparison matrix, a short vs. long post breakdown, seven pitfall callouts that trip up even experienced creators, and real engagement data from a large-scale post analysis.
TL;DR
Aim for 900 to 1,800 characters (roughly 150 to 300 words) for most posts. LinkedIn's hard limit is 3,000 characters, and only the first 140 characters on mobile (about 210 on desktop) show before "see more" truncates the rest, so the hook has to carry the post regardless of total length.
Most posts perform best between 900 and 1,800 characters, or roughly 150 to 300 words. That is long enough to develop one idea past the "see more" cutoff without turning the post into a mini-article, and it stays well inside LinkedIn's hard 3,000-character limit.
There is no single correct length because LinkedIn does not score posts on character count. According to LinkedIn's own help documentation, the platform's only hard rule is a 3,000-character ceiling per post. Everything between "very short" and that ceiling is a judgment call, and the right call depends on the format, illustrated in the post format you are writing.
What the length decision really comes down to is the trade-off between completion rate and depth. Shorter posts get read in full more often. Longer posts, when the hook earns the click, let you build a real argument or story. An analysis of 1,194,021 LinkedIn posts by MagicPost found that median likes climbed from 19 on posts under 25 words to 47 on posts of 400 words or more, with median impressions rising from 508 to 999 across that same range. Their practical recommendation, though, was not to max out length: the study lands on 200 to 400 words (roughly 1,200 to 2,400 characters) as the sweet spot that balances that extra reach against the reader's patience.
In practice, that means writing to the length the content needs rather than a fixed target. A question that can be answered in one sentence does not need padding to reach 900 characters. A case study with real numbers should not be trimmed to fit an arbitrary "keep it short" rule. Write your hook to work independently of length, then let the body run as long as it needs to deliver on that hook and no longer.
MagicPost walks through the same short-versus-long trade-off with worked examples, which is a useful second pass once you have read the data above.
Match your length to your format. Each post type has a natural length that fits the reader's expectation and maximizes engagement for that content style.
| Format | Ideal characters | Ideal words | Notes |
|---|---|---|---|
| Opinion / hot take | 300 to 700 | 50 to 115 | Short punchy takes perform well because they are easy to read and react to instantly. Keep them under 700 characters or the brevity effect is lost. |
| Story post | 900 to 1,800 | 150 to 300 | Story posts need enough space to build tension and deliver the payoff. Under 600 characters, the story feels rushed. Over 2,000, most readers drop off before the lesson. |
| How-to / educational post | 1,000 to 2,000 | 165 to 330 | Educational posts earn dwell time when they deliver specific, actionable steps. 5 to 7 concrete steps with a line break between each is the sweet spot. |
| Personal milestone / announcement | 500 to 1,200 | 85 to 200 | Share the news, give context, and express one genuine reflection. Over 1,500 characters, milestone posts start to read as self-promotional essays. |
| Question / conversation starter | 200 to 500 | 35 to 85 | The shortest posts. The question should be clear in 1 to 3 sentences. Too much setup before the question reduces the comment rate because readers sense it is performative. |
| Case study / analysis | 1,500 to 2,500 | 250 to 415 | The one format where longer consistently outperforms shorter. Readers who click 'see more' on a case study expect depth. Delivering full detail rewards their attention with dwell time. |
| Numbered list (tips / mistakes) | 700 to 1,500 | 115 to 250 | Each item should be 1 to 2 lines. 5 to 8 items is the ideal count. Under 5 feels thin; over 10 causes readers to skim and drop off before the end. |
| Contrarian / debate post | 600 to 1,200 | 100 to 200 | State your position clearly, give 2 to 3 supporting reasons, and end with a direct question. Over 1,500, contrarian posts become lectures, which lose the debate dynamic that drives comments. |
Source: MagicPost post-length study
47 vs. 19
Median likes on LinkedIn posts of 400+ words versus posts under 25 words, from an analysis of 1,194,021 LinkedIn posts published over a 12-month window. Median impressions followed the same pattern, rising from 508 to 999 as posts got longer.
View the study →Source: LinkedIn Help
3,000 characters
LinkedIn's own help documentation confirms 3,000 characters as the hard ceiling for a standard feed post. There is no official minimum, and LinkedIn Articles have no character limit at all.
View LinkedIn's help page →Lifast writes each post already inside the right range for its format, from a 300-character question to an 1,800-character story, with the hook built to survive the 'see more' cutoff.
Try Lifast Free90 days of consistent posting. No ads.
Short Posts
Under 600 characters (under 100 words)
Strengths
Fast to read: the entire post is visible without clicking 'see more'.
Lower time investment for the reader means higher completion rate.
Works extremely well for opinions, observations, and questions.
Lower production friction: easier to post consistently.
Weaknesses
Provides less dwell time signal to the algorithm.
Harder to communicate nuanced ideas or tell a full story.
May feel thin or low-effort on complex topics.
Best for
Hot takes, questions, announcements, quick lessons, reactions.
Long Posts
1,000 to 2,500 characters (165 to 415 words)
Strengths
Higher dwell time signals when readers expand and stay to read the full post.
Allows for full story arc: setup, tension, resolution, lesson.
Positions the author as thorough and credible on complex topics.
Case studies and how-to posts convert better with full detail.
Weaknesses
Higher production investment per post.
Readers who are not hooked by the first line will not expand 'see more'.
Can look like a wall of text without careful formatting (line breaks are essential).
Best for
Stories, case studies, how-to guides, analysis, frameworks.
The by-format table above starts from the content type. This matrix flips the question around and starts from length, so you can work backward from how much space you have to what you should actually write in it.
| Length band | Range | Fits these formats | Typical use case |
|---|---|---|---|
| Micro | Under 300 chars~50 words | Poll captions, one-line reactions, rapid questions | Fast comment-bait, daily posting cadence, near-zero production time |
| Short | 300 to 900 chars~50 to 150 words | Opinion / hot take, announcement, quick tip | Sharing a reaction or a single lesson, keeping a consistent posting rhythm |
| Standard | 900 to 1,800 chars~150 to 300 words | Story post, how-to / educational post, numbered list | The most common 'good' length for B2B growth content and audience building |
| Long | 1,800 to 2,500 chars~300 to 415 words | Case study / analysis, contrarian post, framework breakdown | Thought leadership and lead-gen content aimed at a high-intent reader |
| Near-limit | 2,500 to 3,000 chars~415 to 500 words | Comprehensive teardown, multi-part framework | Rare, only when the topic genuinely needs the space; consider a LinkedIn Article instead |
Not directly. LinkedIn's ranking signals reward dwell time, early engagement velocity, and click-through on 'see more,' not character count itself. Length only matters insofar as it changes those behaviors: a longer post that earns the 'see more' click and holds attention generates the dwell time signal the algorithm rewards.
Generally yes. Posts with an obvious sales angle lose readers faster than personal or educational posts, so keeping sales-adjacent posts closer to 400 to 800 characters, with the offer clear before the 'see more' cutoff, tends to outperform a long pitch that asks for extended attention before delivering any value.
The character ceiling is the same 3,000-character limit on both, but company page posts generally perform better shorter because they lack the personal voice that earns 'see more' clicks on a founder or employee profile. See the full breakdown of LinkedIn's character limits across post types, profile fields, and messages for the complete picture.
These are the most common length-related mistakes that reduce engagement, reduce distribution, or damage credibility, even on posts with strong ideas.
Writing more than 140 characters before the 'see more' cutoff
The first approximately 140 characters of your post on mobile (around 210 on desktop) is what appears in the feed before the reader clicks 'see more'. If your first sentence runs past that, readers see a truncated, unfinished thought. Every word before 'see more' must work to earn the click. Write to the tighter mobile threshold so the hook lands complete on both devices.
Writing a long post with no line breaks
A 2,000-character post formatted as a single paragraph looks like a wall of text on mobile. Even a reader who wants to engage will scroll past because the visual density signals effort. Break every 1 to 3 sentences into its own line, with a blank line between groups. This increases visual dwell time and makes the post skimmable from top to bottom.
Padding length with filler to hit a 'longer is better' target
There is no SEO-style word count floor on LinkedIn. Length does not signal quality to the algorithm. Dwell time does. A padded 1,800-character post that loses readers at line 5 generates worse dwell time than a tight 900-character post read fully. Every sentence should earn its place. When in doubt, cut.
Ending abruptly because you hit the character limit mid-thought
LinkedIn's 3,000-character limit is hard. If your post consistently runs over 2,500 characters, you are writing articles, not posts. Either cut to the core message or publish as a LinkedIn Article (which lives on your profile and is indexed by search but gets less feed distribution). Never truncate a post mid-argument because you ran out of characters: it reads as unfinished and damages credibility.
Writing a 3-line post for a complex topic that needs depth
Under-delivery on depth is as common as over-padding. A case study compressed into 3 bullet points is not a case study: it is a teaser. If your topic genuinely needs 1,500 characters to do it justice, write 1,500 characters. Readers who came for depth will reward that depth with the dwell time the algorithm values most.
Treating every post type the same length
A question post should be 200 to 400 characters. A how-to post should be 1,000 to 1,800 characters. Writing every post at the same length regardless of format ignores the natural expectations each format sets. Use the Ideal Length by Format table above as a quick reference and match length to type.
Writing a hook that is only half a sentence before the 'see more' cutoff
This is perhaps the most invisible pitfall. If your first sentence is 200 characters long, the feed truncates it around character 140 on mobile (roughly 210 on desktop) mid-clause. Readers see a sentence that ends abruptly with no payoff: '...which is why I think the conventional approach to LinkedIn outreach is...'. The truncation leaves a cliff-hanger with no context, and most readers scroll past rather than click to resolve the incomplete thought. Every hook should be a complete, self-contained statement under 140 characters so it survives the tighter mobile cutoff.
'See more' cutoff
140 to 210 chars
140 characters on mobile, roughly 210 on desktop. Everything before this line is guaranteed visible without any action from the reader.
Optimal post length
900 to 1,800 chars
The range where dwell time and engagement rate both perform well for most post types, per a 1.19M-post analysis by MagicPost.
Hard platform limit
3,000 chars
LinkedIn's help documentation confirms this as the maximum for standard posts. Articles have no limit.
Sweet spot word count
150 to 300 words
Translates to roughly 900 to 1,800 characters. Fast to read, rich enough to deliver value.
Minimum for stories
600 chars
Below this, story posts feel rushed and fail to build the tension that earns the payoff.
Maximum before drop-off
2,500 chars
Above 2,500 characters, average completion rate drops sharply. Cut aggressively at this threshold.
Manually calibrating post length for every format while also thinking about the hook, the format, the question, and the link placement is genuinely tedious. Creators who post 3 to 5 times a week quickly learn to hate the process. Lifast generates posts at the right length for the format by default, with the hook placed before 'see more' and the structure calibrated for dwell time, so you can focus on the idea instead of the ruler.
Most advice about LinkedIn post length focuses on total character count. The more important threshold is the 'see more' cutoff, which lands around 140 characters on mobile and roughly 210 characters on desktop. That first line is the only text LinkedIn guarantees every person in your feed distribution will see without taking any action.
Think of the first 140 characters as your headline and the rest of the post as the article body. The headline must be complete enough to stand alone as a compelling statement AND create enough curiosity that readers want to click 'see more'. A hook that is cut mid-sentence by the truncation gives readers no reason to continue.
Test your hook independently: write the first 140 characters of your post on a blank page. Does it make a complete, compelling point on its own? Does it open a question you want answered? If yes, the hook is strong. If it reads as half a thought, rewrite it to deliver a complete micro-statement before the cutoff, then continue the full story after.
The honest answer is that neither is universally better. Short posts (under 600 characters) get higher completion rates and work well for opinions, questions, and quick observations. Long posts (1,000 to 2,500 characters) generate more dwell time when the hook earns the 'see more' click and the content delivers on its promise.
The variable that matters more than absolute length is format-length fit. A question post at 1,800 characters reads as a lecture. A case study at 200 characters reads as a teaser. Match the length to the format and the format to the intended reader action. Question posts should be short enough to answer in a comment. How-to posts should be long enough to be genuinely useful.
One practical heuristic: write until you have said everything that genuinely needs saying, then cut 15 to 20 percent. Most first drafts are 15 to 20 percent longer than they need to be due to throat-clearing sentences, redundant qualifications, and transitional phrases that slow the reading pace without adding information.
LinkedIn Articles (the long-form blog format on LinkedIn, separate from standard posts) have no character limit and support headers, images, and formatted body text. They are indexed by Google and Bing, which means they can rank in search. They get significantly less feed distribution than posts but can accumulate views over months from search traffic.
Use a LinkedIn Article when you want to publish a 600 to 2,000 word deep-dive that would be too long for a post, when search visibility for a topic is more important than immediate feed reach, or when you want to create a permanent reference piece you can link to from future posts (in the first comment).
For most B2B creators building an audience through the feed, standard posts drive faster growth. Articles are a complement, not a substitute. The best strategy is to use standard posts for feed distribution and link to detailed Articles in the first comment when you have created something worth a deep read.
The first 140 to 210 characters (mobile to desktop) should be a complete, compelling statement. These examples show the difference between hooks that earn the click and hooks that lose the reader.
"I have been thinking a lot about this lately and wanted to share some thoughts on something that has been on my mind in the world of B2B sales..."
Tells the reader nothing. No tension. No reason to click 'see more'. By character 140, the only information conveyed is that the author has thoughts.
"Cold email response rates have dropped 70 percent in 3 years. Cold calling has not. Here is why one is dying and the other is not."
States a specific claim, gives a data point, and opens a clear question the reader wants answered. Complete thought under 140 characters.
"Today I want to share a personal story about something that happened to me a few years ago that really changed my perspective on how I approach client relationships and sales."
Truncated by 'see more' before it gets specific. The first 140 characters reveal nothing specific about what happened or why it matters.
"I lost a $180k deal in 4 minutes because of one sentence in a demo."
Under 70 characters. States the stakes (dollar amount), the timeline (4 minutes), and the mystery (one sentence). Every element is a reason to keep reading.
"In this post I am going to walk you through my process for writing LinkedIn posts that actually get engagement. I have been doing this for 2 years and learned a lot..."
The reader sees a truncated preamble. No specific number, no curiosity gap. The 'I will tell you stuff' opener is the weakest possible hook structure.
"Here are the 7 words I remove from every LinkedIn post before publishing. Each one was costing me 30 percent of my reach."
Specific number (7 words), specific stakes (30 percent reach loss), and an implied before/after. Fully under 140 characters and earns the click.
Length is only half the equation. The same 1,200-character post formatted as one paragraph generates far worse dwell time than the same content formatted with deliberate line breaks. These rules apply regardless of post length.
One sentence or one idea per line in the body
Readers scan vertically before committing to read. Short lines create a visual rhythm that pulls the eye down the post.
Blank line between every 1 to 3 lines of body text
White space makes posts feel readable on mobile. Dense blocks of text signal effort and cause scroll-past behavior.
Hook on its own line, separated from the body
Separating the hook from the first body paragraph creates a visual pause that encourages the reader to re-read the hook before continuing.
The key insight or payoff near the end, not buried in the middle
Readers who skim to the end to decide whether to read the full post should land on your strongest line. This reverses the scroll-past decision.
The closing question on its own line, after a blank line
Isolating the question makes it visually obvious that you are inviting a response. Questions buried in a paragraph get fewer replies than questions given their own space.
No more than 3 consecutive lines without a break for posts over 600 characters
At 600 characters and beyond, text density becomes the primary reading barrier. A wall of text that extends past the initial screen view loses most readers before they finish.
Avoid center-aligned text for long posts
Center alignment is hard to read in paragraph form. It works for single-sentence posts or standalone emphasis lines, but not for multi-paragraph content.
Use bold text sparingly (1 to 2 words per section maximum)
LinkedIn supports basic bold via asterisks. Used sparingly, bold draws the eye to a key stat or phrase. Used frequently, it loses its contrast value and makes posts look like sales copy.
End with exactly one question, not a list of options
Giving readers three questions to answer ('What do you think? Have you experienced this? Let me know in the comments!') creates decision paralysis. One specific question gets dramatically more replies than three vague ones.
Precise answers to the most common questions about LinkedIn character limits, word counts, and length strategy.
LinkedIn's own help documentation confirms a hard limit of 3,000 characters for standard posts, including spaces and punctuation. The 'see more' truncation in the feed appears at approximately 140 characters on mobile and around 210 characters on desktop. LinkedIn Articles (the long-form format) have no character limit. If you regularly hit 3,000 characters, consider whether the content is better suited to a LinkedIn Article.
Yes. Each emoji counts as 1 to 2 characters toward the 3,000-character limit, depending on the specific emoji. Multi-code-point emojis (flags, certain combined emoji sequences) can count as 2 to 4 characters. If you are writing near the character limit, emoji use can push you over. The CLAUDE.md guidelines for this project also specify using icons rather than emojis, keeping this a non-issue for Lifast-generated content.
Not universally. A 150-character opinion post that is sharp and specific can outperform a 1,500-character essay that meanders. However, extremely short posts (under 100 characters) often feel like placeholder content and generate lower engagement rates in the B2B space where audiences expect professional depth. The practical floor for most B2B post types is around 200 to 300 characters.
Only when the hook earns the 'see more' click. A long post whose hook fails to earn the click generates near-zero dwell time because readers scroll past without opening it. The dwell time signal that the algorithm values comes from reading time after the full post is revealed. So a long post with a weak hook gets worse dwell time than a short post that is read fully. Length only improves impressions when hook quality is strong enough to earn the expansion.
No. Format variety is valuable on its own because it resets audience scroll behavior and prevents recognition-induced skipping. Rotating between a 300-character question post, a 1,200-character story post, and a 900-character list post keeps your feed presence feeling fresh. The only length-related consistency worth maintaining is always keeping your hook under 140 characters, regardless of total post length.
No. LinkedIn does not penalize posts based on length alone. A 50-word post can get strong distribution if it generates high engagement velocity. What the algorithm rewards is engagement rate, dwell time, and early comment velocity, not word count. The only way post length negatively affects distribution is indirectly: a post that is too short to deliver on its hook promise will have poor engagement, or a post too long with dense formatting will have low dwell time.