LinkedIn post preview

Paste your draft and see where the "…see more" fold amputates it — on desktop and on mobile — before your audience does. Everything below the fold is invisible until a reader clicks; this shows you what's left.

free · no login · runs in your browser

Your Name · 1st
Now · 🌐
Your post appears here as you type…
0
characters
0
visible before the fold
0
hidden behind “see more”

The fold is modelled two ways at once — a character budget (~210 desktop / ~140 mobile) and a three-line budget — and lands on whichever runs out first, which is why a hook broken across short lines gets cut earlier than the same words in one paragraph. All of these are unofficial approximations: LinkedIn documents none of them and they shift with UI, font size and device width. Treat the numbers as a target zone, not a hard line.

Done editing?

How to use it

  1. Paste your draft (or write directly in the editor). Nothing you type leaves your browser.
  2. Switch between the Desktop and Mobile tabs. Everything after …see more is invisible until a reader clicks — click it yourself to expand, like in the feed.
  3. Edit until the strongest sentence sits fully above the mobile fold, then copy the post out.

The fold decides reach

Every LinkedIn post gets judged twice. Once by the readers who see only the pre-fold fragment and decide, in about a second, whether to click …see more. And once by the feed, which amplifies posts people stopped for. A brilliant post with a weak first 140 characters performs like a weak post, because for most of the audience the fragment was the post.

That's the whole reason this preview exists: writers judge their drafts in full, but readers meet them amputated. The single most useful pre-publish habit is reading your post the way the feed serves it — cut mid-sentence, with everything you were building toward hidden behind a click.

Read your hook amputated

Look at the preview above and ignore everything you know about the rest of your post. Does the visible fragment contain one complete reason to click — a tension, a specific number, a claim that cuts against common advice? Or does it spend its ~210 characters on warm-up ("I've been thinking a lot lately about…")? The fold is the most expensive real estate you have; throat-clearing there costs more than anywhere else. If the fragment doesn't earn the click, fix the opening before touching anything else — our hook generator exists for exactly that edit, and the character counter tracks the fold as a live stat while you rewrite.

Line breaks count toward the fold

The fold is really two limits at once, and it lands on whichever runs out first: a character budget and a line budget. Every line break spends a whole line — so a hook written as three short punchy lines gets truncated earlier than the same words as one flowing paragraph, even though the character count is identical.

This preview models both. It word-wraps your draft at a typical LinkedIn feed column for the device you picked — roughly 92 characters per line on desktop, 46 on mobile — counts the rendered lines, and cuts at the character limit or the third line, whichever comes sooner. Those column widths are fixed assumptions about LinkedIn's layout rather than a measurement of your own screen, so an unusually large or small display will read a little differently. That is why pasting a break-heavy hook can shorten the visible fragment dramatically the moment you switch to the mobile tab: at mobile width the same words wrap onto more lines, and the line budget runs out long before 140 characters do. Most preview tools count only characters and quietly tell break-heavy hooks they are safe.

The usual caveat still applies, and it is not a small one: LinkedIn documents none of this. Character limits, line counts and wrap widths all shift with device, font size, zoom and whatever the UI team shipped this quarter. The model here is a good approximation, not a guarantee — if your draft leans on line breaks for rhythm, check the mobile tab and leave yourself margin. The line break fixer helps when the breaks themselves are the problem.

For AI agents

Drafting LinkedIn posts with Claude Code or another agent? Install the skill version — it applies the same fold rules (~210 desktop, ~140 mobile, line breaks counted) so your agent can show you the pre-fold fragment of any draft without leaving the terminal:

npx skills add liftli-ai/skills --skill linkedin-post-preview

Part of the liftli-ai/skills collection — browse all 28 skills, one per tool on this site. For the full pipeline (voice extraction, strategy memory, publishing), connect the Liftli MCP.

Frequently asked questions

How many characters show before "see more" on LinkedIn?

Roughly 210 characters on desktop and around 140 on mobile. LinkedIn doesn't publish the exact numbers and they shift with UI changes, so treat them as a target zone rather than a hard rule: a hook that lands fully inside the first 140 characters is safe on every device.

Do line breaks count toward the see-more fold?

Yes, and they often decide the fold before the character count does. LinkedIn clamps a feed post by both a character budget and a line budget, whichever runs out first, so a hook written as three short lines is cut earlier than the same words in one flowing paragraph. This preview models both: it word-wraps at a typical LinkedIn feed column for the device you selected (about 92 characters per line on desktop, 46 on mobile), counts rendered lines, and folds at the character limit or the third line. Exact behavior still varies by device, font size and zoom.

Why does this preview look different from the real LinkedIn feed?

It's deliberately not a pixel-clone. The fold isn't a fixed pixel line — it depends on device, font settings and LinkedIn's current UI — so a fake-perfect replica would be a false promise. This preview uses the approximate character cutoffs (~210 desktop, ~140 mobile) to answer the question that matters: what does my hook read like, amputated?

Should I optimize for the desktop or mobile fold?

Mobile. If your hook works inside ~140 characters, it works everywhere; the reverse isn't true. Unless you know your audience reads LinkedIn at a desk, assume a large share of your impressions happen on a phone, where the fold cuts hardest.

Is my post uploaded anywhere when I use this preview?

No. The preview runs entirely in your browser with plain JavaScript — nothing you type or paste leaves your machine.

What should go above the fold in a LinkedIn post?

One complete, self-contained reason to click: a tension between two facts, a specific number with an unexpected outcome, a confession, or a claim that cuts against common advice. What shouldn't go there: greetings, context-setting, or throat-clearing like "I've been thinking a lot lately" — the fold is the most expensive real estate in the post.

Related free tools

Previewing the fold is the last step. Liftli handles the rest.

Voice notes, calls and commits in — posts in your extracted voice out, hook above the fold, waiting for your one-tap yes.

Start free — no card