Markdown Blockquotes
TL;DR
- Start a blockquote line with
>. - Consecutive quoted lines become part of the same quote.
- Use a blank quoted line to create multiple paragraphs inside one blockquote.
- Blockquotes can contain other block elements, but the quote marker has to stay in the places where it is required.
What it is
A blockquote is a container block for quoted or callout-style content. In source, it is marked with a leading >.
Why it matters
Blockquotes are common in documentation, notes, and discussions. They are also the basis for several platform-specific patterns, including GitHub alerts, so it helps to understand the core form first.
Syntax
> One paragraph quote
> First paragraph
>
> Second paragraph
Minimal example
Source
> This line is quoted.
What it does
This renders one quoted paragraph.
More examples
Example 1: One quote, multiple lines
> Markdown keeps these lines
> inside the same blockquote.
What it does
Both lines belong to the same quoted paragraph.
Example 2: Two paragraphs inside one quote
> First paragraph.
>
> Second paragraph.
What it does
The blank quoted line separates the quote into two paragraphs.
Example 3: Quote containing a list
> Steps:
> - open the file
> - make the change
> - save the file
What it does
The list stays inside the blockquote because each list line is still part of the quoted block.
Common pitfalls
- Forgetting the
>on a line that still belongs to the quote- Why it happens: a blockquote can feel visually obvious in the editor even after the marker disappears
- Fix: if the line must remain inside the quote, keep the marker where the block structure requires it
- Expecting two paragraphs without a blank quoted line
- Why it happens: two consecutive quoted lines still form one paragraph
- Fix: insert a line that contains only
>to separate quoted paragraphs
- Accidentally ending the quote before a list or code block
- Why it happens: list items, fenced code blocks, and indented code inside quotes are sensitive to markers and indentation
- Fix: build the quote one line at a time and preview the result before adding more nesting
- Using blockquotes as a styling trick instead of for meaning
- Why it happens: quoted blocks are visually distinct
- Fix: use them for quoted content, callouts, or intentionally offset material, not just indentation
Portability and platform notes
- Blockquotes are core CommonMark.
- CommonMark does not require blank lines before or after a blockquote, though adding them can make source easier to read.
- GitHub supports normal blockquotes in comment fields and
.mdfiles. - GitHub alerts build on blockquote-like syntax, but alerts are platform-specific and should be treated as a separate topic.
FAQ
Do I need > on every line?
Use it everywhere the quote structure requires it. A quoted paragraph can use lazy continuation in some cases, but lists, fenced code blocks, and other nested structures are much easier to manage when you keep the markers explicit.
How do I make two paragraphs in one quote?
Add a blank quoted line:
> First paragraph.
>
> Second paragraph.
How do I quote a reply on GitHub?
In GitHub conversations, you can highlight text and press R, or use the "Quote reply" action on a comment. That is a GitHub workflow feature, not a core Markdown rule.
Practice
- Create one blockquote with a single paragraph and one with two paragraphs.
- Add a short bulleted list inside a quote and confirm the list stays inside it.
Related topics
- Alerts / callouts
- Lists
- Code blocks
- Paragraphs and blank lines