Markdown Blockquote Syntax: A Complete Guide from Basics to Advanced

When writing documentation, you often need to quote someone else's words, highlight an important note, or make a section stand out. Markdown gives you a simple way to do this — the blockquote.

Whether you're writing technical docs, taking notes, or putting together a README on GitHub, blockquotes are one of those things you'll reach for all the time.

Basic Markdown Blockquote Syntax

Creating a blockquote is straightforward: add a > (greater-than sign) at the start of a line, followed by a space, then your quoted content.

> This is a quoted line of text.

Rendered output:

This is a quoted line of text.

The > symbol corresponds to the <blockquote> HTML tag. So the Markdown above actually generates this HTML:

<blockquote>
<p>This is a quoted line of text.</p>
</blockquote>

Once you understand this, the rest of the blockquote behavior makes a lot more sense.

Multi-paragraph Blockquotes

When your quote is long enough to need multiple paragraphs, add > on the blank lines between paragraphs too.

> This is the first paragraph of the quote.

>
> This is the second paragraph. The blank line above also needs a > symbol.

Rendered output:

This is the first paragraph of the quote.

This is the second paragraph. The blank line above also needs a > symbol.

Here's the key point: blank lines must also have >, otherwise the quote breaks into two separate blocks. A lot of tutorials gloss over this, but it's one of the most common things people get wrong.

I once wrote a long blockquote and forgot the > on a blank line in the middle — it rendered as two separate quote boxes, which looked pretty odd. So if you want everything to stay in one blockquote, every line (including blank ones) needs >.

Nested Blockquotes (Quotes Within Quotes)

Markdown supports nesting blockquotes — putting a quote inside another quote. Add more > symbols: >> for a second level, >>> for a third level, and so on.

> This is the outer quote
>
> > This is a nested quote (inside the outer quote)
>
> Back to the outer quote

Rendered output:

This is the outer quote

This is a nested quote (inside the outer quote)

Back to the outer quote

Nested quotes are especially handy for reply chains and threaded conversations. In practice, two or three levels of nesting is usually enough — going deeper just hurts readability.

Using Other Markdown Syntax Inside Blockquotes

A blockquote isn't limited to plain text — you can use almost any Markdown formatting inside one, including bold, italic, links, lists, and code.

Bold and Italic Inside Quotes

> This quote has **bold text** and *italic text*.

Rendered output:

This quote has bold text and *italic text**.

Lists Inside Quotes

> A list inside a quote:
>
> - First item
> - Second item
> - Third item

Rendered output:

A list inside a quote:

• First item
• Second item
• Third item

Code Blocks Inside Quotes

> Code example inside a quote:
>
> ```javascript
> console.log("Hello, World!");
> ```

Links Inside Quotes

> For more syntax, see the [Markdown link syntax guide](/markdown/link/).

One thing to keep in mind when nesting syntax inside quotes: not all Markdown renderers support every combination. According to the CommonMark spec, blockquotes can contain any block-level element, but some platforms (especially those with custom parsers) may behave differently. If something renders oddly, check whether it's a platform compatibility issue first.

Blockquotes Inside Lists

When a blockquote appears inside a list item, it needs to be indented to align with the list content.

1. First item
2. Second item
   > A blockquote inside a list item
   > Needs to be indented to align
3. Third item

I tested this on GitHub and VS Code — blockquotes inside lists need to be indented 3 spaces (aligned with the list text) to render as part of the list item. With less indentation, the quote can break out and become a separate block. Honestly, this is easy to overlook, but it comes up a lot when writing technical docs.

The "Lazy Continuation" Mechanism

By the way, the CommonMark spec has something called "lazy continuation," which is worth knowing about.

In short, if the first line of a paragraph starts with >, subsequent lines can omit the > and still be treated as part of the same quote.

> This line has the > symbol
This line doesn't have >, but it's still part of the quote

In some renderers, this will render as a single complete blockquote.

However, this behavior isn't supported everywhere. In GitHub Flavored Markdown (GFM), lazy continuation only works within the same paragraph — across paragraphs (with a blank line in between), you must add > to every line. My advice: just get in the habit of adding > to every line. That way it works everywhere and you don't have to think about compatibility.

Platform Differences for Blockquote Syntax

Different platforms have some variations in how they handle Markdown blockquotes. Here's a comparison table I put together:

Discord's >>> syntax deserves special mention: on Discord, everything after >>> becomes a quote until the end of the message. This is different from standard Markdown, where >>> means a third-level nested quote.

According to the Discord documentation:

• > creates a single-line quote
• >>> creates a multi-line quote (everything after it is quoted)

This is a Discord-specific extension, not standard Markdown syntax.

Practical Use Cases for Blockquotes

Now that you know the syntax, let's look at how blockquotes are actually used in practice.

Quoting Famous Sayings or References

> Any sufficiently advanced technology is indistinguishable from magic.
>
> — Arthur C. Clarke

Callout Boxes in Documentation

Many documentation systems style blockquotes as callout or alert boxes. This isn't the standard purpose, but it's very common in practice. For example:

> **Note**: Make sure you've backed up your database before running this command.

Replies and Conversations

In GitHub Issues or mailing lists, blockquotes are commonly used to quote someone's words when replying — which is actually where the name "blockquote" comes from:

> Original report: The login page isn't rendering correctly.

Thanks for the report. This has been fixed in the latest release.

Using HTML for Blockquotes

If adding > to every line feels tedious, there's another option — use the HTML <blockquote> tag directly. Most Markdown renderers support HTML tags.

<blockquote>
  First paragraph of quoted content.

  Second paragraph of quoted content. No > symbols needed on each line.
</blockquote>

This approach is especially handy for quoting long passages. Just keep in mind that once you use HTML tags, Markdown syntax won't work inside them (so **bold** won't render as bold — you'd need to use <strong> instead).

Frequently Asked Questions

What's the difference between a blockquote and a code block?

A blockquote (lines starting with >) highlights text content, typically displaying as an indented block with a vertical line on the left. A code block (wrapped in backticks `) displays code and preserves original character spacing and line breaks. They serve different purposes: blockquotes emphasize importance or attribution, while code blocks display program code.

Can I put images inside a blockquote?

Yes. Blockquotes support Markdown image syntax:

> ![Image description](image-url.png)

Why isn't my blockquote rendering?

Common causes include:

1. No space after > (some renderers require it)
2. No blank lines before or after the blockquote (add blank lines on both sides to be safe)
3. Mixing indentation styles (spaces are more reliable than tabs)

How many levels of nesting are allowed?

The Markdown spec doesn't impose a limit, but in practice, more than three levels of nesting hurts readability. Most style guides recommend staying at two levels or fewer.

How do you pronounce "blockquote"?

It's simply "block quote" — two words. It means a block-level quotation. It's an HTML tag name that corresponds to the quote element created with > in Markdown.

Wrapping Up

Honestly, the syntax itself is just a handful of lines, but the tricky parts are all in the details. A single > gets you a quote — the hard part is remembering to add > on blank lines for multi-paragraph quotes, not going too deep with nesting, and knowing the little differences between platforms. My advice: make it a habit to add > on every line, and you won't run into issues regardless of where you're writing.

By the way, if you're writing technical docs, nesting bold, italic, code blocks, lists, and links inside blockquotes is something you'll do all the time — worth practicing.

References:

• CommonMark Specification — The official Markdown standard
• Markdown Guide - Basic Syntax — Markdown syntax reference
• Discord Markdown Text 101 — Discord Markdown formatting guide
• GitHub Flavored Markdown Spec — GitHub Markdown specification