April 5, 2026

Why Markdown Line Breaks Don't Show — Causes and Fixes

Markdown ignores single Enter by design (CommonMark). Explains paragraph breaks vs hard breaks—blank lines, two trailing spaces, backslash, and ` `—with team writing tips.

In Markdown, "I pressed Enter but the preview shows one line" is common. That is usually not a bug—specs like CommonMark treat a single newline inside a paragraph as soft wrapping, not a hard HTML line break. Think separately about paragraphs vs line wrapping.

Why one newline becomes "one line"

Under CommonMark, one Enter inside running text often becomes a single space (or disappears) in HTML so you can reflow prose in the editor without changing paragraph boundaries—the same spirit as "paragraph breaks are blank lines." It is not Word's "what you see on screen is always a physical line." Your editor may soft-wrap visually while the file still has one long logical line.

Common misconception

People assume "HTML wraps paragraphs in , so my source newlines map 1:1 to the DOM." In practice the parser first builds logical blocks (paragraphs, lists), then emits  /  . Source newlines are not guaranteed to map to DOM line breaks. If only one paste target misbehaves, it may be treating input as plain text.

Separate paragraphs (most common)

Insert a blank line between blocks for a new paragraph. Blank lines also separate many block types—get in the habit of meaningful blank lines instead of chat-style dense text.

Hard breaks inside one paragraph

For poetry, addresses, or short stacked lines where you keep one paragraph but change lines:

Two trailing spaces then newline
Backslash at end of line then newline (CommonMark hard break)
  if raw HTML is allowed

Trailing spaces are easy to lose—if your editor strips them on save, prefer backslash or confirm   policy.

Lists, tables, dialects

GFM and other flavors differ in how blank lines between list items interact with nested content. For cells, see Line breaks in Markdown tables—often   or row splits.

Preview and PDF

Rules in your head only help after you see output. Markdown to HTML shows rendered HTML. Standardize CommonMark vs GFM across the team. For PDF, layout still goes through HTML—if preview and print diverge, suspect paragraph vs break rules first.

Summary

Markdown intentionally avoids treating a single newline as a paragraph break. Use blank lines for paragraphs; use hard-break syntax or   when you need in-paragraph line breaks. For shared READMEs, a one-page authoring guide cuts review debate.

FAQ

How do I get a single Enter to create a new line, like Word?

Add two trailing spaces before pressing Enter. That produces a   within the same paragraph. A backslash \ at the end of the line also works and is safer if your editor strips trailing spaces.

Blank lines make paragraph spacing too large

That is a CSS margin-bottom on  elements—not a Markdown spec issue. Adjust the stylesheet (or use layout settings in this app) to control paragraph spacing.

GitHub rendered my line breaks but another tool doesn't

GitHub Flavored Markdown (GFM) applies different rules than CommonMark. Identify which flavor each tool uses and standardize your team.

I wrote ` ` but it doesn't show

The platform or tool may sanitize raw HTML tags for XSS prevention. Confirm whether raw HTML is allowed. See Using   in Markdown for details.

Add a short section to your README: "Separate paragraphs with a blank line; use backslash or   for in-paragraph breaks." Link a shared preview environment so everyone can verify output quickly.