Blockquotes in Markdown: Syntax, Nesting, and Use Cases

Blockquotes in markdown are created with a single character: the greater-than symbol (>). They are one of the oldest typographic conventions in digital writing, borrowed from email quoting conventions, and they serve a wide range of purposes in modern documentation, blog posts, and technical notes.

This guide covers every pattern you need: basic syntax, nested blockquotes, combining blockquotes with other formatting, and the GitHub callout block extension.

Quick Answer: Markdown blockquotes use > at the start of a line. Nest them with >> or >>>. They fully support bold, italic, inline code, lists, and code blocks inside. GitHub extends blockquotes with 5 typed alert callouts ([!NOTE], [!TIP], [!IMPORTANT], [!WARNING], [!CAUTION]) that render with colored icons.

What Is the Basic Blockquote Syntax?

The > character at the start of a line creates a blockquote:

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

Renders as:

The best way to predict the future is to invent it.

For multi-line blockquotes, add > to each line, or use a single > followed by a blank > line to keep paragraphs grouped:

> This is the first paragraph of the blockquote.
>
> This is a second paragraph, still inside the same blockquote.

Renders as:

This is the first paragraph of the blockquote.

This is a second paragraph, still inside the same blockquote.

Both approaches are valid. Prefixing every line is more explicit; the single-> per paragraph approach is more common in prose writing.

How Do You Nest Blockquotes?

You can nest blockquotes by stacking > characters:

> This is the outer quote.
>
>> This is a nested quote inside the first.
>>
>>> And this is nested one level deeper.

Renders as:

This is the outer quote.

This is a nested quote inside the first.

And this is nested one level deeper.

Nested blockquotes are most commonly used for email-style threads, where you quote a previous message and reply to it:

>> Original message from Alice:
>> "Can you send me the updated report?"
>
> Hi Alice, the report is attached. Let me know if you have questions.

Do not over-nest. Two levels is readable. Three or more is usually a sign that the content should be restructured.

What Formatting Can You Use Inside Blockquotes?

Blockquotes fully support other markdown formatting. You can use bold, italic, inline code, links, and even headings and lists inside them.

Bold and Italic

> **Important:** This behavior changed in version 3.0.
> The old `config.json` format is _no longer supported_.

Important: This behavior changed in version 3.0.
The old config.json format is no longer supported.

Lists Inside Blockquotes

> Key points from the meeting:
>
> - Budget approved for Q2
> - Launch date moved to March 15
> - Design review scheduled for next Thursday

Key points from the meeting:

• Budget approved for Q2
• Launch date moved to March 15
• Design review scheduled for next Thursday

Code Blocks Inside Blockquotes

> Use the following command to initialize the project:
>
> ```bash
> npm create next-app@latest my-project
> ```

Use the following command to initialize the project:

npm create next-app@latest my-project

Headings Inside Blockquotes

> ## Section Title
>
> Content of the blockquoted section follows here.

Headings inside blockquotes are technically valid but rarely used well. Reserve them for cases where you are genuinely quoting a structured document section.

What Are the Most Common Use Cases for Blockquotes?

Pull Quotes

Pull quotes draw attention to an important statement. They are common in long-form articles:

> "The problem is not writing the code. The problem is maintaining it six months later."

This observation drives the entire architecture of the system described below.

Callout Boxes

Blockquotes are frequently repurposed as callout boxes by pairing them with a bold label:

> **Note:** This feature requires Node.js 20 or higher.

> **Warning:** Running this command will overwrite existing data.

> **Tip:** You can press Ctrl+Z to undo the last action.

This pattern is widely used in documentation and works in any markdown renderer.

Email Citations

The blockquote convention originated in email clients that indented quoted messages. Markdown inherits this use case naturally:

> From: Alex Chen
> Date: February 20, 2026
>
> "Could you review the pull request before end of day?"

I reviewed it this morning. Left two comments on the auth module.

Disclaimers and Attributions

> The views expressed here are those of the author and do not represent the official position of any organization.

How Do GitHub Alert Callout Blocks Work?

GitHub extended the standard blockquote syntax with typed alert blocks. These render with colored icons and distinct visual styling on GitHub:

> [!NOTE]
> This is a note. Use it for supplementary information the reader should be aware of.

> [!TIP]
> This is a tip. Use it for helpful suggestions that improve the experience.

> [!IMPORTANT]
> This is important. Use it for critical information required for success.

> [!WARNING]
> This is a warning. Use it for content that could cause problems if ignored.

> [!CAUTION]
> This is a caution. Use it for potential negative outcomes or risks.

On GitHub, each of these renders with a colored left border, an icon, and a bold label. Outside of GitHub (in standard markdown renderers), they render as regular blockquotes with the label text visible.

These are especially useful in:

• README files
• Contributing guides
• GitHub Wiki pages
• Pull request descriptions

For more context on GitHub-specific markdown features, see the markdown for GitHub guide.

How Do You Style Blockquotes with CSS?

In standard HTML rendering, a blockquote becomes a <blockquote> element. Most markdown-aware tools apply default styles (left border, indentation, lighter text). In custom documentation sites or blogs, you can style them further:

blockquote {
  border-left: 4px solid #0070f3;
  padding: 0.5rem 1rem;
  margin: 1.5rem 0;
  background-color: #f0f7ff;
  font-style: italic;
  color: #444;
}

Different visual treatments serve different content types. A blue left-border suits informational callouts. A yellow background suits warnings. A subtle gray suits attributions and pull quotes.

What Should You Avoid with Blockquotes?

Avoid using blockquotes purely for visual indentation. If you want to indent content, use a list or a heading with nested content. Blockquotes carry semantic meaning (“this content is quoted or set apart”) and misusing them confuses screen readers and parsing tools.

Avoid very long blockquotes without attribution. If you are quoting a source, attribute it. If you are not quoting a source but just want to visually separate a section, use a horizontal rule or a heading instead.

Avoid mixing deeply nested blockquotes with complex formatting. It becomes hard to read and the rendering behavior varies across tools.

Blockquotes in Context

Blockquotes are one piece of a larger markdown toolkit. For a full reference of syntax patterns, the markdown cheat sheet covers everything in one place. If you write for GitHub specifically, the markdown for GitHub guide covers how alert callouts, task lists, and other GitHub-flavored extensions interact with standard blockquote syntax.

Try Blockquotes in Your Markdown

Open edtr.md and experiment with blockquote patterns in real time. The live preview lets you immediately see how nesting, inline formatting, and code blocks render inside quotes. It is the fastest way to find the pattern that works for your content.