A blockquote wraps content in a visually indented container, conventionally used for quoted or cited material. Each line of the blockquote is prefixed with a > character and an optional space.
> This is a blockquote. It can span multiple lines.
> Each line begins with a `>` character.
Blockquotes can contain other block elements.
> Including multiple paragraphs, separated by a `>` on a blank line.
>
> Second paragraph
>> Even nested blockquotes
>>> Even more nested blockquotes
This is a blockquote. It can span multiple lines.
Second paragraph Each line begins with a
>character.
Blockquotes can contain other block elements.
Including multiple paragraphs, separated by a
>on a blank line.Even nested blockquotes
Even more nested blockquotes
Best Practice
- Prefix every line with
>for clarity, even though lazy continuation allows some lines to omit it. - Use a
>on blank lines within the blockquote to keep multi-paragraph quotes visually clear in source. - Blockquotes are semantically for quotations; for callouts and alerts, use the admonition or callout syntax supported by your flavour instead.
Notes
Nesting
Blockquotes can be nested by adding additional > characters:
> Outer blockquote.
>
> > Inner blockquote, nested one level.
> >
> > > Nested two levels.
Lazy Continuation
A continuation line does not need to repeat the > prefix, as long as it is not a blank line:
> This line starts the blockquote.
This continuation line is still part of the blockquote.
This line is outside because of the blank line above.
While valid in CommonMark, repeating > on every line is clearer and more portable.
Blockquotes Containing Other Elements
Headings, lists, code blocks, and thematic breaks can all appear inside a blockquote:
> ## Heading inside a blockquote
>
> - List item one
> - List item two
>
> ```markdown
> Code block inside a blockquote
> ```
Markdown Flavour Support
Supported by all major flavours.
Flavour Support Detail
| Flavour | Support | Notes |
|---|---|---|
| Original Markdown | Yes | Defined in the original spec, modelled on email quoting conventions. |
| CommonMark | Yes | Precisely specifies lazy continuation and nesting rules. |
| GitHub Flavored Markdown | Yes | Inherits CommonMark rules; also extends blockquotes with the > [!NOTE] alert syntax. |
| Pandoc Markdown | Yes | Supported; blockquotes in output formats such as LaTeX map to the quote environment. |
Practical Examples
- Highlighting a memorable passage in book notes: Set apart a line that stayed with you so it stands out clearly from your own commentary.
I finished chapter four last night. This line stayed with me:
> We accept the love we think we deserve.
— *The Perks of Being a Wallflower*, Stephen Chbosky
I finished chapter four last night. This line stayed with me:
We accept the love we think we deserve.
— The Perks of Being a Wallflower, Stephen Chbosky
- Pulling a key quote in a blog post: Draw the reader's attention to the most important thing a person said before you discuss it.
When asked about her process, the author was clear:
> I write the ending first. Everything else is just finding my way back to it.
When asked about her process, the author was clear:
I write the ending first. Everything else is just finding my way back to it.
- Responding to a message or comment: Quote the original text, then write your reply below — the same convention used in email threads.
> Are you still planning to come on Saturday? It would be lovely to see you.
Yes! I will bring the dessert. See you around seven.
Are you still planning to come on Saturday? It would be lovely to see you.
Yes! I will bring the dessert. See you around seven.