Markdown Blockquotes: How to Quote and Nest Content

Blockquotes in Markdown use the > character to create indented, styled content blocks. They appear in almost every README, documentation page, and technical blog post you encounter — and if you have ever pasted a snippet from someone else's writing into a GitHub issue, you have probably used one already without thinking twice about the underlying syntax. A markdown blockquote serves multiple purposes: quoting text, adding callouts, highlighting important information, and creating visual hierarchy in documentation. This guide covers the full syntax — from basic quotes to nested blocks, combined elements, and renderer-specific styling — based on the CommonMark specification. MacMD Viewer, a native macOS Markdown viewer ($9.99, SwiftUI, 2 MB), renders blockquotes with styled left borders and proper nesting — it does not require custom CSS or theme configuration.

TL;DR: Prefix lines with > for blockquotes. Nest with >>. Combine with other Markdown elements inside. Most renderers add a left border and indentation.

How Do You Create a Blockquote in Markdown?

A single > character at the start of a line creates a markdown blockquote. The parser wraps everything that follows into an HTML <blockquote> element:

> This is a blockquote.
> It can span multiple lines.

Place a blank line before and after the blockquote for consistent rendering across parsers. Every line inside the block starts with > followed by a space. Some writers skip the > on continuation lines — a technique called lazy continuation — where subsequent lines without the prefix are still included in the block. It works in most renderers but makes the raw source harder to scan, so explicit > on every line is the clearer practice and the one recommended by the Markdown Guide.

For multi-paragraph blockquotes, separate paragraphs with a line containing only > between them:

> First paragraph inside the blockquote.
>
> Second paragraph, still inside the same blockquote.

The blank > line acts as a paragraph separator while keeping both paragraphs inside the same quoted block. Without it, parsers treat the second paragraph as regular body text outside the markdown blockquote — a subtle difference that trips up even experienced writers when they move between different renderers that handle edge cases differently.

How Do You Nest Blockquotes in Markdown?

Each additional > character adds a nesting level. Two levels deep uses >>, three levels uses >>>, and so on:

> First level quote
>
>> Second level — a quote within a quote
>>
>>> Third level — deeply nested

Nested blockquotes mirror email-style threaded quoting. Each reply indents the previous message one level deeper. The result? A clear visual hierarchy. Most renderers add a distinct left border at each level, making the conversation thread immediately scannable even in sprawling exchanges with dozens of back-and-forth messages that would otherwise blur together into an unreadable wall of text. GitHub, VS Code, and MacMD Viewer all support three or more nesting levels without issues.

To return to a higher level, simply use fewer > characters on the next line. The transition is immediate — no blank line required between nesting levels, though adding one improves readability in the raw source file:

> Back to the first level after nesting.

What Can You Put Inside a Markdown Blockquote?

Almost any Markdown element works inside blockquotes. The > prefix acts as a container — everything after it is parsed as regular Markdown, which means you get the full formatting toolkit inside a quoted block.

Headings inside blockquotes use the standard # syntax after the prefix:

> ## This Is a Heading Inside a Blockquote
> Regular paragraph text follows.

Lists work with the usual - or 1. markers:

> Key points:
> - First item
> - Second item
> - Third item

Inline code uses backticks directly inside the blockquote line. For fenced code blocks, prefix every line — including the opening and closing fences — with >:

> Here is a code example:
>
> ```javascript
> const greeting = "Hello, world";
> console.log(greeting);
> ```
>
> The code above logs a message.

Bold, italic, links, and images all work inside blockquotes without any special handling. Even tables render correctly inside blockquotes in renderers that support GitHub Flavored Markdown.

What does not work well: deeply nested combinations of blockquotes, lists, and code blocks can break in some parsers. If your markdown blockquote contains more than two levels of mixed nesting, test it in your target renderer before publishing. The .md file format is intentionally simple, and complex nesting pushes against its design boundaries.

How Are Blockquotes Used Beyond Quoting?

Modern documentation has repurposed the markdown blockquote syntax for callouts and admonitions — styled alert boxes that draw attention to warnings, tips, and important notes. The blockquote container is reused because it already provides the visual indentation and left-border styling that callout boxes need.

GitHub introduced alert syntax using special markers inside blockquotes:

> [!NOTE]
> This is a note with additional context.

> [!WARNING]
> This action is irreversible.

> [!TIP]
> Use keyboard shortcuts for faster navigation.

> [!IMPORTANT]
> Read the migration guide before upgrading.

> [!CAUTION]
> This will delete all data permanently.

Five types. Five colors. Each alert renders with a distinct icon on GitHub. Obsidian uses a similar callout syntax with > [!info] and supports custom callout types. Docusaurus uses its own admonition blocks with ::: markers. The underlying concept is the same everywhere: repurposing blockquote semantics for structured alerts.

MacMD Viewer renders standard blockquotes with a styled left border and subtle background. For GitHub-style alerts, view the file on GitHub directly or in a renderer that supports the alert extension. For a broader look at Mac rendering tools, see our best Markdown viewer for Mac comparison.

How Do Markdown Renderers Style Blockquotes?

The CommonMark specification defines the semantics of blockquotes — what constitutes a valid markdown blockquote and how it maps to HTML — but says nothing about visual styling. Every renderer applies its own CSS, which is why the same > syntax looks different everywhere:

• GitHub — Gray left border, slight indentation, no background color change. Clean and minimal.
• VS Code — Left border that matches the current editor theme. Dark themes get a lighter border, light themes get a darker one.
• MacMD Viewer — Themed blockquote styling with an accent-colored left border and subtle background tint. Renders consistently across light and dark modes. See all features.
• Typora — Theme-dependent. The default theme uses a subtle gray background with a left border. Custom themes can override every aspect of blockquote appearance.
• Obsidian — Left border with callout support. Standard blockquotes are minimal, but callout-style blockquotes get colored backgrounds, icons, and collapsible behavior.

If you need consistent styling, define your own CSS for the blockquote element. In static site generators like Hugo and Jekyll, add a blockquote rule to your stylesheet. In dedicated viewers, the styling is built into the theme. For a detailed look at how different Mac viewers render Markdown elements including blockquotes, see our Markdown viewer for macOS guide.

Conclusion

One character. That is all it takes. The humble > gives you quoted text, nested conversations, callout boxes, and styled containers for literally any Markdown element you can think of — from headings and lists to fenced code blocks and even tables in renderers that support GitHub Flavored Markdown extensions. Master the basic syntax, learn the nesting rules, and you have a versatile tool for structuring content in any .md file.

To see how blockquotes render with proper styling, syntax highlighting, and Mermaid diagram support on Mac, try MacMD Viewer — a native SwiftUI viewer built for clean, distraction-free reading. Check pricing to get started.

Frequently Asked Questions