Markdown Quotes and Blockquotes

Basic Quote Syntax

A blockquote starts with a > character followed by a space. Renderers show it indented with a vertical bar down the side. Use it for citations, quoted replies, and callouts.

> This is a blockquote.

> Every consecutive > line joins the same quote.
> This all renders as one continuous blockquote.

> First paragraph of the quote.
>
> Second paragraph — the blank line still needs its >.

Line Breaks Inside a Quote

This is the part that surprises people. Putting > on two lines does not give you two lines — a blockquote holds ordinary Markdown paragraphs, so the lines wrap together. You break them the same way you break any paragraph.

> First line of the quote.
> Second line of the quote.

> First line of the quote.  
> Second line of the quote.

> First line of the quote.\
> Second line of the quote.

Nested Blockquotes

Each additional > nests one level deeper, which is how quoted replies are shown in email-style threads. There is no practical depth limit, though the indentation gets unreadable after three or four levels.

> Outer quote.
>> Inner nested quote.

> Outer quote here.
>> Second level nested.
>>> Third level — use >>> for deep nesting.

> Original message here.
>
>> Reply to the message above.

Attribution and Sources

Markdown has no citation syntax — no author field, no source URL. The convention is an attribution line inside the quote, introduced with an em dash. Because it is just another line of the same paragraph, it needs a hard break or a paragraph break in front of it, or it runs on from the quote text.

> The best way to predict the future is to invent it.  
> — Alan Kay

> Simplicity is a great virtue.
>
> *— Edsger W. Dijkstra, 1984*

<blockquote cite="https://example.com/source">
  <p>Markdown has no syntax for a citation URL.</p>
  <footer>— <cite>Example Source</cite></footer>
</blockquote>

Quotes with Other Formatting

A blockquote is a container, not a text style, so it holds everything Markdown can express: inline formatting, lists, headings, tables, and fenced code. Prefix every line of the block with >.

> **Bold text** inside a blockquote.
> *Italic* and [links](https://example.com) work too.

> Use `inline code` inside a quote.

> Here is a list inside a blockquote:
>
> - Item one
> - Item two
> - Item three

> ### Heading inside a quote
>
> You can use headings and other block elements.

> ```javascript
> const msg = "Code block inside a quote";
> console.log(msg);
> ```

GitHub Alert Callouts

GitHub turns a blockquote into a colored alert box when the first line is [!TYPE]. There are five types, and the keyword must be uppercase and on a line of its own. Everywhere else this renders as a normal quote with the literal [!NOTE] text at the top — which is exactly what the previews below show.

> [!NOTE]
> Useful information users should know, even when skimming.

> [!TIP]
> Helpful advice for doing things better.

> [!IMPORTANT]
> Key information users need to know to achieve their goal.

> [!WARNING]
> Urgent info that needs immediate user attention.

> [!CAUTION]
> Advises about risks or negative outcomes of an action.

Common Mistakes

Nearly every blockquote problem is a blank-line problem: one missing >, or one blank line too few.

> Line one of the quote.
> Line two of the quote.

> Line one of the quote.\
> Line two of the quote.

> First paragraph.

> Second paragraph.

> First paragraph.
>
> Second paragraph.

> A quoted sentence.
This line was meant to be normal text.

> A quoted sentence.

This line is normal text.

>>> Third-level nested quote.

> Level one
>> Level two
>>> Level three

Quick Reference

Platform Support

The > character quotes text almost everywhere. What varies is nesting, and what the extra > characters mean.

Frequently Asked Questions