Markdown Line Breaks Not Working? Use the Right Break

If your Markdown line breaks are not working, first decide whether you need a new paragraph or a new line inside the same paragraph. Use a blank line for a new paragraph. In CommonMark-compatible Markdown, use a backslash immediately before the newline, or two trailing spaces, for a hard line break. Pressing Enter once normally creates a soft break that may display as a space.

You can compare those cases in the Markdown to HTML converter. Inspect both the rendered preview and the HTML source: separate paragraphs produce separate <p> elements, while a hard break inside a paragraph produces <br>. That distinction is more informative than judging only the vertical gap on screen.

A source newline does not always request a visible break

Markdown files are often wrapped into short lines so they remain comfortable to edit in a text editor. Those physical source lines can still belong to one paragraph. A renderer may join them visually, allowing the browser or document viewer to wrap the paragraph at its own available width.

For example:

The release notes begin here.
The next sentence belongs to the same paragraph.

Seeing those sentences on one rendered line is not necessarily a conversion error. You supplied a soft line break, and the renderer is allowed to display it like ordinary whitespace. The CommonMark specification describes this behavior explicitly.

Do not try to fix normal paragraph wrapping by inserting repeated spaces between words. Those spaces can collapse in HTML, create odd gaps elsewhere, and make the source harder to maintain without establishing a real paragraph boundary.

Use a blank line to start a paragraph

A paragraph break is usually the right choice when the next sentence develops a different thought:

The first paragraph explains the result.

The second paragraph explains the next action.

Each paragraph becomes its own block. The destination stylesheet or Word paragraph style decides the spacing between those blocks. If the gap looks too large, the issue may be paragraph styling rather than missing or excessive Markdown syntax.

This distinction matters when exporting a document. A new paragraph can carry its own style, spacing, and document semantics. A forced line inside an existing paragraph is still part of that paragraph. Choose based on the structure of the text, not only on the appearance of one preview window.

Use a hard break for short lines that belong together

Addresses, verse, and a short label followed by a related detail can reasonably need a new line without a new paragraph. A visible backslash at the end of the source line makes that intention easy to inspect:

Documentation team\
Building 4, second floor

The backslash must directly precede the newline. Adding another character after it changes the source. The rendered text should show the two address lines without displaying the backslash.

Two spaces at the end of a line provide another standard hard-break form. However, trailing spaces are difficult to see, and some editors or save hooks remove them automatically. If an apparently correct break disappears after saving, inspect the file with whitespace markers enabled. A backslash can be easier for teammates to recognize and preserve.

These forms are documented under hard line breaks in CommonMark. Not every system calling its format “Markdown” implements exactly the same rules, so test the destination that will actually display the content.

Understand when an HTML break is appropriate

An inline <br> can work in a Markdown renderer that permits raw HTML. It can be useful in a GitHub-style table cell, where a physical newline can interfere with the row structure. It is less portable when the same source must pass through several document exporters or a system that strips HTML.

Do not assume that a tag visible in a browser preview will have an identical effect in a DOCX or PDF. A converter may sanitize the HTML, reduce it to text, or implement only a subset of HTML semantics. Use paragraph structure wherever that accurately expresses the content, and keep format-specific exceptions small.

Also avoid <br> for creating large areas of vertical whitespace. Several break tags may look acceptable at one font size but produce awkward pagination or empty space after export. Page layout belongs to the destination document’s layout controls.

Check the surrounding Markdown context

The same punctuation can behave differently inside another construct. Inside a fenced code block, newlines are normally literal code layout. In an ordinary paragraph, they can be soft breaks. Inside a table, a newline can end the row. A heading has its own block syntax and should not be used as a container for a multiline paragraph.

Lists also need enough indentation to associate continuation text with the intended item. If a line unexpectedly leaves a list or creates a new paragraph outside it, inspect the indentation before adding more break characters. Reduce the example to one list item and two short lines, then rebuild the structure gradually.

Verify the final output, not only the editor

Start with a tiny test containing one soft break, one hard break, and two paragraphs. Confirm how the target renders each case. Then apply the correct structure to the full document.

For a Word handoff, the guide to converting Markdown to Word without losing document structure explains why the preview and exported file need separate checks. For a fixed-page deliverable, use the Markdown to PDF converter and inspect the actual downloaded pages, including headings near the bottom of a page.

A successful fix should preserve the intended reading order at different widths. If the text only looks correct at one window size, you may be using manual breaks to imitate a layout that should instead be handled by paragraphs, styles, or the document’s page settings.