How to Keep Line Breaks When Pasting Into Slack

A tidy list leaves Notepad as five lines and lands in Slack as one paragraph — or as five messages, if Enter sends. Both failures are Slack input policy plus whatever HTML the clipboard offered. Windows did not “strip newlines” as a special feature. This guide uses Slack’s own help pages, then the clipboard side.

How Slack treats Enter

Slack’s formatting article: to start a new line, press Shift+Enter. It also points to a preference that makes Enter insert a newline instead of sending.

Slack’s keyboard-shortcut list: Create a new line = Shift+Enter. Create a new snippet = Ctrl+Shift+Enter on Windows.

That is the whole “I hit Enter and it sent” ticket.

Set Enter to mean newline

1. Open Slack preferences.
2. Find the Enter key / “when writing a message” setting (label varies slightly by desktop vs web).
3. Choose Enter inserts a new line; use Ctrl+Enter (Windows) to send.

This is a per-user preference. It does not travel with a pasted snippet. Teammates will still send mid-paste if they have the default.

Paste paths that preserve breaks

Plain text with real newlines

If the clipboard’s Unicode text contains CR+LF or LF between lines, Slack usually keeps them inside the compose box. Problems start when:

• The copy was HTML with <br> / <p> that Slack’s composer flattens.
• The copy was a single line with wrapping only in the source view (PDF, justified web).
• The composer treats Enter as send while pasting line-by-line with a keyboard macro.

Fix: paste with Ctrl+Shift+V when the Slack client honors it as paste-without-formatting, or scrub through Notepad first: How to Paste Without Formatting on Windows.

Code blocks (monospaced, breaks kept)

Slack’s formatting help includes code and code block. Triple backticks around the paste:

line one line two indented

Slack help: wrap multiple lines; code blocks use a monospace font and do not render other formatting inside the block. This is the right home for logs, JSON, and stack traces.

Keyboard: Slack documents Codeblock selected text as Ctrl+Alt+Shift+C on Windows. Select the pasted lines, then apply the code block.

Slack snippets (the attachment kind)

When the paste is long, Slack’s “Create or paste code snippets” article is the better tool. Ctrl+Shift+Enter opens a snippet window; choose a type, paste, create. The message then links the snippet instead of dumping 200 lines into the channel.

Do not confuse Slack snippets with PhraseExpress snippets. One is a chat attachment. The other is autotext. Reusable replies still belong in an expander: Building a Small Library of Reusable Replies.

Why HTML from the clipboard wrecks lists

Copying from Word, Docs, or a webpage publishes HTML with <p>, <li>, and <br>. Slack’s composer maps that inconsistently:

• Some clients keep list bullets.
• Some join <p> tags into a single block.
• Some insert extra blank lines.

Win+V may store that HTML (history formats include HTML, up to 4 MB, 25 items). Clicking the card is a rich paste. For a list that must stay a list:

1. Paste into Notepad.
2. Confirm each item is its own line.
3. Copy from Notepad.
4. Paste into Slack.
5. If it still joins, wrap in a code block.

Mystery fonts in Slack are the same HTML story: Why Pasted Text Brings Mystery Fonts With It.

Word and Docs as the source

Word often uses soft line breaks (Shift+Enter, ^l) versus paragraphs (^p). Slack may treat them differently. Show paragraph marks in Word before copying. Convert soft breaks to real paragraphs if each line should stand alone.

Google Docs: copy the list, paste into Slack with Ctrl+Shift+V first. If bullets vanish, they were HTML list items; type - prefixes in Notepad.

Expander snippets into Slack

An expander inserts whatever line endings it was given. Test each multi-line canned reply in Slack after creating it. If Espanso or PhraseExpress inserts LF and the result is one line, put explicit newlines in the snippet body (YAML | blocks in Espanso are the usual fix).

Do not store the Slack-ready reply only as a pinned Win+V card. Pins survive restart but have no name, no review, and they occupy the 25-item list. History is still wiped for unpinned items at reboot.

Teams, Discord, and “it works in one chat”

Microsoft Teams often keeps newlines on a plain paste and still uses Enter to send, with Shift+Enter for a break — the same muscle memory as default Slack. Discord is similar in desktop. The failure that differs is markdown: Discord fences with triple backticks; Teams has a toolbar code block that may or may not accept a fenced paste.

When a paste must go to both Slack and Teams, keep a plain text source in Notepad. Paste twice. Do not copy from the Slack message into Teams; that hop is how HTML lists collapse.

Mobile Slack is worse: the on-screen keyboard’s return key may send. Compose long lists on desktop, or use a Slack snippet from the desktop client.

Draft in the compose box, not in Win+V

If the message is long, write it in the Slack box (Enter = newline) or in a notes file, then send. Using history as a staging buffer for a 20-line announcement risks an accidental Enter on a single card paste. Slack drafts exist in the client for a reason. History still holds the URL and the one statistic that was copied from the deck.

Pasting from Excel and Word tables

A 5×3 Excel range copies as tab-separated text plus HTML. Slack will often produce a crooked “table” or a single line of tabs that collapse. For a small grid, convert to a code block so columns stay aligned in a monospaced font. For a real table, attach a CSV or screenshot. Do not fight Slack into becoming Excel.

Word tables become HTML <table> that Slack usually flattens. Same rule: code block or file.

Lists versus paragraphs

A source that used <p> for every line becomes a list of isolated paragraphs in some Slack builds (extra blank lines) and a single block in others. If the Notepad scrub shows real blank lines between items, delete the extras before paste unless a paragraph break is intended. Slack will honor those blank lines as visual space.

Numbered lists typed as 1. 2. 3. in plain text usually survive. Word’s automatic numbering often copies as HTML <ol> that Slack may flatten to 1. 1. 1. or to a paragraph. Another reason to scrub.

Checklist

Optional: keep the raw log and the cleaned list as two cards on a local shelf such as Edge-Drop while composing. Slack still needs the newline rules above.

Related reading

• Pasting Code Into Word, Email, and Chat
• Smart Quotes, Em Dashes, and Other Paste Traps
• How to Paste Without Formatting on Windows
• A Sensible Daily Copy-Paste Workflow

Sources

• Format your messages in Slack (Slack Help) — Shift+Enter for a new line; Enter-key preference link.
• Slack keyboard shortcuts — Shift+Enter new line; Ctrl+Shift+Enter new snippet; code block chord.
• Create or paste code snippets in Slack — snippet window for long pastes.
• Using the clipboard (Microsoft Support) — HTML can be what history replays into Slack.
• Keyboard shortcuts for Google Docs — Ctrl+Shift+V before the Slack paste.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support