Quillpost
← All guides

How long should a LinkedIn post be?

Practical length guidance for founder posts: the same idea written short, medium, and long, and how to tell which version earned its lines.

There isn't one right length

LinkedIn lets a post run to 3,000 characters. That is a ceiling, not a target. On most screens the feed shows about two lines — roughly 200 characters — before “…see more”. Those lines have to earn the tap. What follows has to earn the time. A founder post that does both can be a few sentences or a short story. The number is what is left after you cut, not a goal you write toward.

Ranges by post type — a short announcement, a lesson, a how-to — are in the post length guide. This page is the part a range can't decide: given one real week, which draft is long enough.

Give each sentence a job

A short founder post has four jobs: what happened, what you expected, one detail that makes the turn believable, and one closing line. That shape is in post structure for busy founders. If a sentence doesn't do one of those jobs, it is length you didn't earn.

The reverse mistake is cutting the only specific detail so the post looks short. Then it is shorter and worse. Length problems are usually job problems: a sentence is repeating, stalling, or pitching, or a sentence you needed is missing.

The same idea, three lengths

Below is one made-up week, written three ways, so you can see what each length is doing. These are not results, and they are not a post to copy. They are the same scene with lines added or removed.

Too short. A stranger can't tell what happened, so the last line has nothing to stand on:

We shortened onboarding. It worked. Ship less.

Enough. One situation, the wrong guess, the change, and what you're still watching:

A customer forwarded our onboarding email with one line: “too many steps.” I assumed they wanted more explanation. They wanted fewer screens. We removed the company-size question and the invite-your-team step. I'm watching whether people who finish setup come back the next day.

Too long. The extra lines restate the point, then ask for something:

I've been thinking a lot about onboarding. A customer forwarded our onboarding email: “too many steps.” My first instinct was tooltips, a Loom, and a checklist. I watched one session. They weren't stuck. They paused on company size, then left when we asked them to invite a teammate before they had imported anything. We deleted both steps. Two fields, not a redesign. The lesson is that respect for someone's time is a product decision, and founders forget that when they add steps just in case. Audit your onboarding. If you want the checklist, it's on my profile.

The middle version is the post. The short one is a caption. The long one says the same thing twice and ends like an ad. The middle version also doesn't invent a before-and-after number. If you measured one, that sentence belongs — one line, which is what a proof line is for. If you didn't measure it, leave it out.

Stay short when the fact is the post

A decision, a correction, a single observation. If the sentence is already specific, a paragraph of warmup makes it less specific. “We stopped the free trial on Monday. The people who complained had never connected a mailbox.” doesn't need a moral under it.

Short also wins when a thin idea is about to become slides. If it fits in a few lines, a carousel is padding. Carousel vs text is that check. The opening still has to work above the fold: hooks that get reads.

Go longer only when the next line answers a new question

A longer post earns the extra lines when each paragraph answers something the previous one raised. Setup the reader actually needs. A step they couldn't guess. The downside in a hiring note. The thing you left out of a launch.

It doesn't earn length when paragraph four repeats paragraph two in cleaner words, or when you add a second lesson because the first one felt small. Save the second lesson. One post, one turn.

A how-to can run longer than a story because the steps are the content. A step that says “be consistent” is still not a step. Cut it. If you're choosing between a tight text post and a document, write the text first and keep only the lines you'd read out loud.

A five-minute length check

1. Read the first two lines on your phone. If you wouldn't tap “…see more”, the length below them doesn't matter yet.

2. Delete the first sentence. If the post gets clearer, you started one sentence too early.

3. Mark any sentence that explains what the previous sentence already showed. Delete those.

4. If two takeaways are fighting for the last line, move one to next week.

The same pass shows up in how to edit an AI draft. AI drafts get long in the wrong places: a preamble, three vague bullets, and a question you wouldn't ask a colleague.

Match your length, not a template's

Posts you've already published and still like are a better target than a generic range. If those run short, with one-line breaks, a long draft will sound like someone else even when the facts are yours.

Quillpost can aim a first draft at that length from posts you've pasted. It only drafts. It never posts for you: there's no LinkedIn login, and nothing goes live until you copy it and publish it yourself. Free is 3 drafts a day, enough to write the long version, cut it, and throw one out. Pro is coming soon and isn't live, so there is nothing to upgrade to yet.

Read the version you kept next to the one you cut. Post the one where every remaining line still has a job.

Want a draft in your own voice?

Try the free generator →