How Do I Add a Line Break on LinkedIn?

A LinkedIn line break works with a plain Enter key in a post, a comment, the About section and an experience description, and with Shift+Enter inside a direct message. The one place a real line break never works is the single-line headline field, where a separator character is the honest workaround, not a formatting trick.

I ghost-write and format LinkedIn posts, About sections and outreach messages every week, and the line-break question comes up more than almost anything else I get asked, because LinkedIn's editor behaves differently in every field. This guide goes field by field: posts, comments, the About section, experience descriptions, messages and the headline, with the one tool I use to check spacing before I publish anything.

What counts as a line break on LinkedIn, and why it breaks unpredictably

A line break on LinkedIn means one of two things: a soft return that starts a new line inside the same paragraph, or a hard return that adds a genuine blank line between two blocks of text. Most fields on LinkedIn accept both if you type them directly, which is the part people trust.

The part that breaks is pasting. A line break copied from Word, Google Docs, Notion or an email client often does not survive the trip. The reason is not a LinkedIn bug: LinkedIn's composer is a rich text field, not a plain text box, and rich text fields interpret pasted formatting rather than accepting it literally.

Word and Google Docs wrap every paragraph in hidden formatting codes, and when LinkedIn's paste handler meets those codes, it sometimes keeps the break, sometimes collapses it, and sometimes merges two paragraphs into one dense block. This single quirk is behind most of the "why did my spacing disappear" messages I get from clients, and it is completely avoidable once you know the fix, covered next.

Why line breaks vanish when you paste into LinkedIn

If you have pasted a carefully spaced post from Google Docs into LinkedIn and watched every blank line collapse, this is why: your source document carries invisible formatting, and LinkedIn's paste handler does not reliably preserve it. The fix is to strip that formatting before it reaches LinkedIn, not to fight LinkedIn's editor afterwards.

On a laptop, paste as plain text instead of a normal paste: Ctrl+Shift+V on Windows, Cmd+Shift+V on a Mac, inside most browsers. That single habit change fixes the majority of vanishing-line-break complaints I hear from clients who draft in Docs.

The more reliable long-term fix is to stop drafting in a rich text app altogether. Write in Notes, a plain text file, or directly inside LinkedIn's own composer, where every Enter key press is already plain text with nothing hidden behind it. I draft almost everything this way now, specifically to avoid this problem.

One more source of the same symptom: copying text that already contains styled Unicode characters, the kind a LinkedIn text formatter produces for bold or italic. Those characters are plain Unicode, not rich text formatting, so they paste reliably on their own. The trouble starts if you built your draft by copying bold text out of a Word document instead of a formatter, since then you are carrying Word's formatting along with it.

Line breaks in a LinkedIn post, on desktop and mobile

Inside the post composer itself, a plain Enter key works exactly as expected: press it once for a new line, twice for a blank line between paragraphs, on both the desktop site and the mobile app. This is the one surface where LinkedIn behaves the way every other text box does.

The mistake is not the key, it is the amount of white space. A blank line between every one-sentence paragraph is what makes a post readable on a phone screen, and my guide to formatting LinkedIn posts covers the full hook-and-spacing structure, along with what goes on that opening line before the first break; this guide is only about getting the break itself to register and survive.

On mobile specifically, the return key on your phone's keyboard behaves the same as Enter on a laptop inside the post composer, so there is no separate trick needed there. What does trip people up on mobile is autocorrect inserting a stray space right before a line break, which can leave an odd gap. Type the post, then re-read it once before posting.

Line breaks in comments

A comment on LinkedIn accepts a line break the same way a post does: press Enter for a new line. The difference is what a line break is worth to you there, since a comment truncates far sooner than a post.

Keep a comment's line breaks purposeful rather than decorative. One blank line to separate a direct answer from a follow-up question works well; five short lines to make a ten-word comment look substantial reads as noise in a feed built for scanning, not for reading a manifesto in the replies.

Line breaks in the About section and experience descriptions

Both the About section and each experience description are plain multi-line text fields, and Enter works there exactly as it does in a post: type your line, press Enter, and the break holds when you save. This is the one part of formatting a profile that never surprises people.

Where people do go wrong is pasting a resume bullet list straight out of Word into an experience description, which brings back the same hidden-formatting problem covered above. Paste as plain text first, then add your own line breaks by hand inside LinkedIn's own field.

For the fuller picture on writing and structuring the About section itself, not just the line breaks inside it, my LinkedIn About section guide covers the opening hook, keyword placement and the closing call to action.

Line breaks in LinkedIn messages: Shift+Enter and the send setting

Messages behave differently from every other field on this list, because Enter is bound to Send by default rather than to a new line. Press Shift+Enter instead, and the cursor drops to a new line without sending anything, which is the one shortcut worth remembering above every other rule in this guide.

If you send a lot of multi-paragraph outreach messages, LinkedIn's own messaging settings also let you turn off press Enter to send. With that setting off, Enter itself adds a line break and a separate Send button submits the message, which suits anyone drafting longer messages who does not want to hold Shift for every line.

A short message with one idea per line reads better in a phone notification than a dense paragraph, the same rule that governs a post. For outreach specifically, I keep a first message to three or four short lines with one blank line before the actual ask, so the notification preview does not bury the point. That habit fits inside the wider system I cover in my LinkedIn marketing guide for 2026.

The headline problem: why a real line break is impossible there

The headline field is a single-line input, not a multi-line text box, and no key combination, paste trick or Unicode character inserts a genuine line break inside it. Anyone claiming an invisible character forces a real second line is describing something LinkedIn's own layout does not honour consistently across search, connection requests and your profile, so I would not build a headline strategy around it.

The honest workaround is a separator, not a break: a vertical bar, a middle dot, or a comma placed near the 30 to 40 character mark gives a narrow mobile display a natural point to wrap the text onto a second visual line, even though it is still technically one line of text underneath. It is a formatting choice, not a genuine line break, and worth knowing the difference before you promise a client something LinkedIn cannot do.

My LinkedIn headline examples guide covers the character limit and exactly where the field gets cut off in different placements, which matters more for a headline than the line-break question does.

Previewing your spacing with a LinkedIn text formatter

Because line breaks behave differently across posts, comments, messages and the headline, I check spacing before publishing rather than guess. The LinkedIn text formatter on this site, one of the 11 free tools I maintain here, includes a live feed preview next to the editor, so you can see exactly where LinkedIn's own see more cutoff lands before you post anything.

Paste your draft into the tool in plain text, and the preview shows your line breaks the way the LinkedIn feed will actually render them, not the way your word processor rendered them. If a break you expected has collapsed in the preview, it will collapse on LinkedIn too, so fix it there rather than after the post is live.

The same tool adds bold or italic Unicode to a hook line or a key phrase without touching your line breaks, since the two are independent: styling a word does not remove the break before or after it. That makes it a reasonable single stop for both problems, and my LinkedIn bold text guide covers the styling side in full. If you already pay for a scheduler such as Taplio or Typegrow, my LinkedIn post editor comparison covers how each one handles spacing and line breaks specifically.

Step 1: Draft in plain text first

Open Notes, a plain text file, or LinkedIn's own composer directly, rather than starting in Word or Google Docs. Plain text carries no hidden formatting for LinkedIn's paste handler to mishandle later.

The common pitfall is drafting a long post in Docs out of habit, then discovering the spacing broke on paste. Verify by checking your draft file's format before you write a single word: if it is a .docx file or a Docs link, switch it now rather than after you have finished writing.

Step 2: Write one idea per line

Press Enter after each sentence rather than letting sentences run together in one paragraph. On LinkedIn specifically, one short line per idea is what actually gets read before the see more cutoff.

The pitfall is over-breaking single words onto their own line, which starts to look like a poem rather than a post. Verify by reading your draft back at a normal pace; if you pause awkwardly mid-thought, merge that break back in.

Step 3: Add a blank line between paragraphs

Press Enter twice between each one-line paragraph rather than once, which is what creates the actual white space readers notice on a phone screen. A single Enter alone still reads as a dense block once LinkedIn wraps it.

The pitfall is assuming Shift+Enter does this inside a post the way it does in a message; it does not, and produces a tighter line instead. Verify in the composer's own preview before publishing, where the gap should be clearly visible between every line.

Step 4: Paste as plain text if you started in a rich text app

If you drafted somewhere other than plain text after all, paste with Ctrl+Shift+V on Windows or Cmd+Shift+V on a Mac instead of a normal paste, which strips the hidden formatting before it reaches LinkedIn.

The pitfall is using a normal paste out of habit and only noticing the collapsed spacing once the post is already live. Verify immediately after pasting, while it is still a draft, by counting that every blank line you wrote is still a blank line.

Step 5: Preview before you publish

Check the post in LinkedIn's own composer, or paste it into a formatter such as the free LinkedIn text formatter on this site, and confirm the spacing survived exactly as you wrote it.

The pitfall is trusting how the draft looks in your notes app rather than how LinkedIn will actually render it, since the two are not always the same. Verify by reading the preview on your phone specifically, not only on a wider desktop editor.

Where each field stands: a quick reference

This table summarises everything above in one place, for the next time you forget which key does what in which field.

Accessibility: when a decorative line break or character backfires

A plain Enter key line break is invisible to this problem, but the decorative characters people add alongside line breaks are not. Bold or italic Unicode text, along with symbols used purely to force a visual gap, are read aloud letter by letter or symbol by symbol by many screen readers, rather than skipped or read naturally.

A UK accessibility resource for businesses, Scope's guide to screen readers and Unicode symbols, puts it plainly: before adding a stylised character, ask whether standard text would do the job just as well. A plain line break costs nothing here, since it is genuine paragraph structure, not a styled symbol, so screen readers handle it the way they handle any other paragraph break.

Screen readers also read punctuation inconsistently depending on a listener's own verbosity settings, according to WebAIM's own guidance on designing for screen reader compatibility, which is one more reason a plain sentence on its own line is safer than a line built entirely from symbols or dashes.

The practical rule I follow: use line breaks freely, since they are structural and accessible, and use decorative Unicode or symbol-only lines sparingly, reserved for a hook or a single emphasised word rather than every line of a post. My LinkedIn caption formatter guide goes further into where bold and italic help a caption and where they start to work against it.

Common mistakes with LinkedIn line breaks

A handful of line-break mistakes account for most of the "my formatting broke" messages I get, and every one of them is avoidable once you know which field you are in.

• Drafting a full post in Google Docs, then pasting it directly into LinkedIn without stripping the formatting first.
• Expecting Shift+Enter to add a blank line inside a post the way it does in a message; inside a post it just adds a tighter single break.
• Trying to force a two-line headline with an invisible Unicode character, then finding it renders differently in search results than on your own profile.
• Using one line per word to make a short comment look substantial, which reads as noise rather than structure.
• Never previewing on mobile, where a break that looks fine on a wide desktop editor can land in a completely different place.

None of this is complicated once you have the field-by-field picture. A line break is one of the smallest formatting decisions you make on LinkedIn, and also one of the most visible, since a wall of text is the fastest way to lose a reader before your point even lands. Pair this with my LinkedIn post size guide for the pixel side of formatting, and my LinkedIn hook formulas guide for what to put on that first line once the spacing is right.

Frequently asked questions

Why do my LinkedIn line breaks disappear after I paste them in?

Your line breaks disappear because the source document, usually Word or Google Docs, wraps every paragraph in hidden formatting that LinkedIn's paste handler does not reliably preserve. The fix is to paste as plain text using Ctrl+Shift+V on Windows or Cmd+Shift+V on a Mac, which strips that hidden formatting before it reaches LinkedIn. An even more reliable habit is drafting inside a plain text app or LinkedIn's own composer from the start, so there is nothing hidden to strip later.

How do I add a line break in a LinkedIn message?

Press Shift+Enter to add a line break inside a LinkedIn message, since a plain Enter key sends the message immediately by default. If you would rather use Enter itself for a new line, LinkedIn's messaging settings let you turn off press Enter to send, after which a separate Send button submits the message instead. Either way, one short line per idea reads better in the narrow message panel than one long, unbroken paragraph.

Can I add a line break in my LinkedIn headline?

No, the headline field is a single line of text and no key combination or hidden character reliably forces a genuine second line inside it. What creators use instead is a separator, a vertical bar, a middle dot or a comma, placed near the 30 to 40 character mark, which gives a narrow mobile screen a natural point to wrap the text visually. It still counts as one line of text underneath, and renders differently across search results, connection requests and your own profile.

How do I add a line break in a LinkedIn comment?

Press Enter inside a LinkedIn comment box exactly as you would in a post, and the line break holds once you submit it. Because a comment truncates sooner than a post and sits in a feed built for scanning, keep breaks purposeful: one blank line to separate a direct answer from a follow-up question works well, while several one-word lines in a short comment tend to read as noise rather than structure.

Is it safe to use a line break generator or Unicode symbol tool on LinkedIn?

Yes for the formatting itself, since LinkedIn renders standard Unicode characters natively and does not penalise reach for using them. The caution is accessibility rather than safety: screen readers can announce stylised Unicode letters one at a time by their technical name instead of reading the word naturally, so heavy use makes a post harder to follow for anyone using assistive technology. Use bold or decorative characters sparingly, and rely on plain Enter key breaks for the actual paragraph structure.

Related guides

• LinkedIn Post Size 2026: Image, Carousel and Video Specs
• How to Format LinkedIn Posts in 2026
• LinkedIn Post Editor Guide
• LinkedIn Caption Formatter Guide
• LinkedIn Bold Text Guide
• LinkedIn About Section Guide
• LinkedIn Headline Examples
• Free LinkedIn Text Formatter

Your next step

Open a draft post in plain text, apply the field-by-field rules above, then run it through the free LinkedIn text formatter to confirm the spacing before you publish. If you want your whole LinkedIn presence built around this kind of detail, get in touch and I will look at it with you.