See where LinkedIn cuts your post off
LinkedIn hides most of your post behind "…see more". Whatever survives that cut is doing most of the work of getting the rest read. Paste your draft below and you get the boundary on both desktop and mobile, with LinkedIn's line cap and character cap applied to each.
Oiti writes the part above the line
It learns the way you actually talk from the posts you have already published, then drafts openings that say something before LinkedIn hides the rest.
How to preview a LinkedIn post
Three steps, no account, and nothing leaves your browser.
- 1
Paste your draft
Drop your post into the editor. The preview updates as you type, so you can watch the cutoff move while you rewrite the opening.
- 2
Switch between mobile and desktop
The two viewports cut in different places. Desktop shows around three lines, mobile around two, and the same post can lose a whole sentence between them. Check both.
- 3
Rewrite until the hook survives the cut
Get the interesting part above the line, then copy the post out and paste it into LinkedIn.
Why the cutoff decides whether your post gets read
Everything below the fold is optional reading. A reader has to choose to expand your post, and the only thing they have to go on when deciding is whatever LinkedIn shows before it collapses the rest.
Most drafts spend that space on runway. Context first, then a throat-clearing sentence, then "so I've been thinking about". By the time the actual point shows up it is sitting behind a link nobody clicked.
I have never fixed that with a rule about hooks. What fixes it is watching the boundary move while you write, which is the one thing LinkedIn's own composer will not show you.
How LinkedIn actually truncates a post
Two things cut your post, and whichever happens first wins.
The first is a character count. Past a certain number of characters the rest collapses behind "…see more", and that number is smaller on a phone than on a laptop.
The second is a line count, and this is the one people miss. LinkedIn collapses the post after a small number of visible lines, and a blank line counts as a line. So a short post written with a lot of white space between one-sentence paragraphs can hit the cut having spent barely any words, purely on the double-Enter habit everyone picked up from LinkedIn itself.
That is why a preview built on one character number gets it wrong so often. Line breaks are free to type and expensive to spend.
What makes this preview accurate
Two caps decide the cut, and this preview applies both. There is a character cap and a line cap, and each one is tighter on mobile than on desktop, so the same draft loses a different amount on each. Whichever cap runs out first is the one that ends up hiding the rest of your post.
Blank lines count. An empty line between two paragraphs spends a line of the budget without spending a single character, which is the part most previews get wrong and the reason a short, airy post can hit the cut with barely any words behind it.
It is an approximation rather than a pixel-for-pixel copy of the feed. The card renders at close to LinkedIn's feed width and it models the feed's truncation logic, and we are not claiming identical output across every device, locale, and app version LinkedIn ships. Any tool that does has not checked.
The editor above carries the same bold and italic controls, because both pages run the same editor. The LinkedIn text post formatter is the page built around styling rather than around the cut: nineteen Unicode styles and a grid of variations to pick from. It applies the same caps this page does, so the two tools agree on where a given draft gets cut.
What to put above the line
Things that survive the cut and earn the click:
- A claim someone could disagree with. Nobody stops scrolling to agree with you.
- A number with a story attached, meaning a specific thing that happened rather than a statistic.
- The end of the story first. Start where it got interesting and fill in the setup below the fold.
- A question you actually intend to answer, not one with an obvious answer.
Things that waste it:
- "I've been thinking a lot lately about…"
- Naming the topic before you have said anything about it.
- An opening line that only makes sense once you have read the second paragraph.
- Anything that reads like the first slide of a deck.
Frequently asked questions
- Is there a way to preview a LinkedIn post before publishing?
- Not inside LinkedIn. The composer shows your draft in a box that is a different width from the feed, so it cannot show you where the "…see more" cut will land. That is what this tool does: paste the draft and you see the post rendered at feed width with the cutoff marked, on desktop and on mobile.
- How do I test a post on LinkedIn without publishing it?
- Paste it into the preview above. You get the feed rendering, the truncation point, and the character count without anything touching your account. LinkedIn has no draft-preview mode, and scheduling a post does not show you the collapsed state either, so short of publishing it somewhere and looking, a preview tool is how you check the cut beforehand.
- How many characters does LinkedIn show before "see more"?
- Around 210 on desktop and around 140 on mobile, though the number on its own will mislead you. LinkedIn also collapses the post after a small number of visible lines, and blank lines count toward that. A post can hit the cutoff well under the character limit if it uses a lot of white space, which is why this preview tracks both.
- Does the preview look the same as the real LinkedIn feed?
- It models the feed's column width and its truncation logic. It will not be identical to the pixel across every device and app version LinkedIn ships, and no browser tool can promise that. What it gets right is which of your words land above the cut.
- Is this free? Do I need to sign up?
- It is free and there is no account, no email field, and no usage cap. Your draft is processed in your browser rather than on a server.
- Is my post stored anywhere?
- No. The preview runs in your browser and this tool never sends your draft anywhere. We do not receive it, store it, or use it to train anything, so you can paste an unpublished draft without handing it over.
- Why does my post get cut off earlier on mobile?
- The mobile column is narrower, so the same sentence wraps into more lines, and the mobile caps on both lines and characters are tighter. Drafting happens on a laptop far more often than reading does, so a post that looks fine while you write it can quietly lose its hook for everyone who meets it on a phone.
- Do line breaks count against the limit?
- Yes, and it surprises almost everyone. An empty line between paragraphs takes up a visible line just like a line of text does. Four one-sentence paragraphs with blank lines between them hit the cut faster than one dense paragraph of the same word count.
- Can I preview a post with an image or a video?
- Not yet. This previews the text and the truncation point, which is the part you can still change. Media sits below the text in the feed and does not move the "…see more" boundary.
- Will my formatting carry over when I paste into LinkedIn?
- Yes. Plain text and line breaks paste cleanly, and so does styling: the editor above has bold, italic, underline and strikethrough, and each one is baked into the Unicode characters LinkedIn renders rather than applied as markup, so Copy post hands you text that keeps its styling through the paste. The text post formatter is the bigger version of the same thing, with nineteen styles and a grid of variations, if you want to see a line in all of them at once.
Knowing where the cut lands is one thing.
Writing an opening worth putting above it is the part people actually get stuck on. Oiti learns how you actually talk from what you have already published, then drafts posts that read like you typed them, with an opening built to survive the cut rather than a paragraph of runway before the point.
7 days free · No usage limits