Markdown Paragraphs

A Markdown paragraph is a block of text separated from the next block by a blank line.

Unlike word processors, Markdown doesn't create a new paragraph every time you press Enter. A single line break is usually treated as part of the same paragraph, while an empty line starts a new one.

This simple rule is followed by most Markdown applications, including GitHub, GitLab, VS Code, and Obsidian.

Example

This is the first paragraph.

This is the second paragraph.

Output

If you're learning Markdown for the first time, start with Markdown Basics for an introduction to the core syntax. This guide focuses only on paragraphs and spacing, while topics such as headings, lists, and links are covered in their own dedicated guides.

Creating a new paragraph is simple: finish your current paragraph, leave one empty line, and start writing again.

Markdown treats each block of text separated by a blank line as a separate paragraph. This keeps documents easier to read and helps create a clear structure in README files, documentation, articles, and notes.

Example

Markdown is easy to learn.

It is widely used for documentation.

It also works well for README files.

Output

A common beginner mistake is assuming that pressing Enter once creates a new paragraph. In standard Markdown, it doesn't.

When two lines are separated by a single newline, most Markdown renderers treat them as one continuous paragraph. To start a new paragraph, leave one empty line between the two blocks of text.

Example

This is line one.
This is line two.

Most Markdown applications render it like this:

To create a new paragraph, add an empty line.

Correct

This is line one.

This is line two.

A line break and a new paragraph are not the same thing.

Use a line break when the text should continue within the same paragraph but appear on the next line. Common examples include postal addresses, poetry, song lyrics, or formatted contact information.

For everything else, a normal paragraph is usually the better choice.

Method 1 — Two trailing spaces#

The standard Markdown way to force a line break is to add two spaces at the end of a line before pressing Enter.

Some editors make these trailing spaces difficult to see, so they're represented below with dots.

First line··
Second line

(The dots represent two trailing spaces.)

Output

Method 2 — HTML <br>#

Many Markdown applications allow inline HTML, including the <br> tag.

Use this approach only when you specifically need HTML support or when trailing spaces are difficult to maintain. For portable Markdown documents, the two-space method is usually preferred.

First line<br>
Second line

Output

For a complete comparison of every line-break method—including renderer differences and CommonMark behavior—see the dedicated Markdown Line Breaks guide.

Paragraph behavior is consistent in most Markdown editors because blank lines are part of the core Markdown syntax.

However, line breaks can behave differently depending on the renderer. For example, some applications automatically convert a single newline into a line break, while others follow the CommonMark specification and keep both lines within the same paragraph.

If the formatting looks different after publishing, check how your Markdown application handles line breaks before changing your content.

List items can contain more than a single line of text. By indenting a paragraph under a list item, you can add explanations, notes, or additional instructions without breaking the list structure.

This is especially useful in installation guides, tutorials, and project documentation where each step needs extra details.

Example

- First item

  This paragraph belongs to the first item.

- Second item

Output

Indented paragraphs make long lists easier to follow without turning each step into a separate section.

For more examples, see the dedicated Markdown Lists guide.

Blockquotes can contain multiple paragraphs, making them useful for notes, warnings, documentation callouts, or quoted content.

Leave a blank quoted line (>) between paragraphs to keep them separate.

Example

> First paragraph.
>
> Second paragraph.

Output

You'll often see this pattern in documentation for notes, warnings, tips, and important information.

Learn more in the Markdown Blockquotes guide.

When writing tutorials or technical documentation, keep normal text and code blocks separated with a blank line.

Introduce the command or example first, place the code inside a fenced code block, then continue with the explanation in a new paragraph. This structure is easier to read and works consistently across most Markdown renderers.

Example

Install the package.

```bash
npm install
```

Run the application after the installation completes.

Output

npm install

Separating paragraphs from code blocks also prevents formatting issues and makes step-by-step instructions easier to scan.

See Markdown Code Blocks for language identifiers, syntax highlighting, and fenced block examples.

Good Markdown documents are usually easier to read because they use short, focused paragraphs.

Follow these guidelines:

• Keep each paragraph focused on a single idea.
• Leave one blank line between paragraphs.
• Break long explanations into smaller sections.
• Combine paragraphs with headings and lists to improve scanning.
• Place explanatory text before or after code blocks instead of mixing prose with commands.
• Review your document in preview mode before publishing.

These small habits improve readability on GitHub, documentation sites, knowledge bases, and note-taking applications without changing your Markdown syntax.

Most paragraph formatting problems come from using the wrong amount of spacing. These issues are easy to fix once you understand how Markdown separates blocks of text.

Paragraph syntax is part of the core Markdown specification, so it works consistently across almost every Markdown application.

Good paragraph structure makes documentation easier to read than long blocks of uninterrupted text.

When writing Markdown:

• Keep paragraphs focused on a single topic.
• Split long explanations into smaller sections.
• Use headings to introduce new ideas instead of writing one large block.
• Combine paragraphs with lists or code examples where they improve clarity.
• Preview your document before publishing to check spacing and formatting.

These habits improve readability without adding unnecessary formatting.

Looking for paragraph spacing inside lists, tables, or blockquotes? Explore the Markdown Lists, Markdown Tables, and Markdown Blockquotes guides for element-specific examples.