LinkedIn line break generator

How to space a post that keeps its paragraphs

LinkedIn keeps ordinary single line breaks, so what is being rescued here is the empty line between paragraphs, which is the gap a reader actually sees as a break.

1. 1Draft somewhere plain: a text editor, or this box. Writing the post in a word processor is the most common reason spacing does not survive the journey.
2. 2Paste the draft above with your usual blank lines. Every non-empty line is treated as its own paragraph.
3. 3Choose single spacing. The feed already puts a little air between paragraphs, so a double gap reads as an omission rather than a break.
4. 4Read the output pane rather than the input one. What you see there is exactly what the composer receives, character for character.
5. 5Glance at the total if the post is close to article length. At 3,000 characters the separators are a rounding error, which is not true on every platform in this family.
6. 6Paste into the composer as plain text and then stop editing. Rewriting inside the composer is where the spacing gets lost the second time.

What gets inserted, and what it costs at this length

Everything the tool produces is plain text, which is the point: there is no formatting in the output for a paste to strip on the way in.

• The separator is U+2800, the braille pattern blank, one per gap on single spacing and two on double.
• U+00A0, a non-breaking space, is the fallback for any client that renders the braille blank as a box.
• A ten paragraph post spends nine characters on single spacing, roughly three tenths of one per cent of the ceiling.
• Running the tool on its own output gives the same result again, because earlier separators are removed before new ones are added.
• The headline and the About section accept the same pasted text, though the About section has its own, much lower ceiling.
• Nothing in the output depends on the client rendering anything unusual, so the post reads the same on the web, in the app and in an embed.

Where LinkedIn spacing goes missing

The spacing usually survives LinkedIn's own composer and dies somewhere on the way to it: inside a scheduling tool, in a copy taken from a rendered page, or during an edit made after the post is live.

• A scheduler that trims whitespace before sending collapses an empty line and keeps a line with a character on it, which is exactly why a character is used.
• Copying a post out of the feed to repost it drops the blank lines, because on a rendered page the paragraphs are layout rather than characters.
• Editing a live post reopens it in the composer, and one stray return during that edit leaves two paragraphs joined.
• A post that publishes as a block is read as a block: the feed collapses it after the first couple of lines and the reader judges the whole thing on what is left showing.

Spacing that helps, and spacing that is noise

At this ceiling the spacing question is about readability rather than cost, and the honest answer is that most LinkedIn posts are spaced too much rather than too little.

• Single spacing between real paragraphs is enough. A gap after every sentence is a habit borrowed from posts trying to look longer than they are.
• One-line paragraphs stacked with gaps read as a list even when the content is an argument, which flattens the argument.
• If the composer is already keeping your spacing, you do not need separators at all: check first, add characters second.
• Gaps make an existing structure visible. They cannot create one where the paragraphs have nothing between them.