Markdown Blockquote Syntax: Complete Guide with Examples
Learn markdown blockquote syntax with clear examples, nested quotes, and formatting tips to write cleaner docs—start quoting like a pro.
Introduction
Markdown blockquote syntax uses the greater-than symbol (>) to mark text as quoted or highlighted. In Markdown, a blockquote is a block-level element that separates quoted text, notes, and examples from surrounding content in README files, documentation, and other plain text workflows.
You’ll use blockquotes when you want to quote a source, highlight a warning or tip, or separate supporting text from the main body. The syntax is compact, but the result can change how readable a page feels, especially in technical documentation. If you need a refresher on the basics of Markdown itself, see Markdown basics and plain text formatting.
This guide covers the core patterns you’ll actually use: basic blockquotes, nested blockquotes, multi-paragraph quotes, formatting inside quotes, and common mistakes that break rendering.
What Is a Blockquote in Markdown?
A blockquote is a block-level section used to present quoted or highlighted text. In Markdown, > turns that text into the HTML blockquote element, which visually separates it from surrounding content and gives it semantic meaning for browsers and assistive tools. For the basics, see Markdown basics.
Use inline quotation marks for a short quote inside a sentence, such as The docs said "use > for quotes", but use a blockquote for a full quoted passage or a highlighted note:
> Markdown blockquote syntax separates quoted text from the main paragraph.
Use a blockquote instead of simple emphasis when the content needs its own block. In documentation, blockquotes often become the base for callouts and admonitions, but those styled components are not the same thing; they add labels, icons, or colors on top of the quote structure. See developer docs and the Markdown Guide for more context.
Basic Blockquote Syntax
The simplest way to write a blockquote in Markdown is > quoted text. Most Markdown parsers also accept >Text, but > Text is the clearer, more portable style used in most Markdown basics and Markdown formatting guide references.
To quote multiple lines in Markdown, start each line with >:
> First line
> Second line
> Third line
Continuation lines stay in the same quote as long as they keep the > marker. End a blockquote by starting a new non-quoted paragraph. Rendered HTML becomes an HTML blockquote element:
<blockquote>
<p>First line<br>
Second line</p>
</blockquote>
Use the Markdown formatting checklist to keep quote styling consistent across Markdown files.
Nested Blockquotes and Multi-Paragraph Quotes
Nested blockquotes use repeated greater-than symbols (>>, >>>) to show quote levels in Markdown. A Markdown parser like CommonMark treats each added > as a deeper layer, which is useful in transcripts, threaded discussions, and documentation examples.
> Parent quote
>> Reply inside the quote
>>> Third-level note
For a single quote that spans multiple paragraphs, repeat the quote marker on each paragraph and keep the blank line inside the quote:
> First paragraph of the quote.
>
> Second paragraph of the same quote.
Most Markdown styles, including CommonMark, expect each paragraph to stay marked as quoted. Inconsistent indentation or missing markers can break the visual structure, so check your output in a Markdown cheat sheet or follow a Markdown style guide.
Formatting Inside Blockquotes
Markdown blockquote syntax supports most common Markdown formatting inside the quote. You can combine bold text, italic text, and links without breaking the blockquote:
> This note uses **bold text**, *italic text*, and a [link](https://markdownmastery.com/blog/content-formatting-guide-for-markdown).
inline code works well for commands, filenames, and short identifiers in technical writing, especially in developer docs:
> Run `npm install` before starting the app.
Lists also fit inside quotes, but indentation matters for each - or 1. line to stay inside the blockquote:
> Steps:
> - Install dependencies
> - Run tests
Code blocks can appear inside quotes too. In CommonMark and GFM, fenced code blocks inside blockquotes are supported when each fence line is quoted:
> ```bash
> npm run build
> ```
This formatting is common in README files and documentation, and a good Markdown formatting guide helps keep it consistent.
Common Blockquote Mistakes and Troubleshooting
A missing > on a continuation line breaks the quote into separate paragraphs or plain text. For example, > First line followed by Second line renders only the first line as a quote in many Markdown parser implementations.
Blank lines can split one quote into multiple blocks, especially in CommonMark and GitHub Flavored Markdown (GFM). If you want one continuous quote, keep every quoted paragraph marked and avoid stray empty lines.
Indentation causes another common failure: four spaces can start code blocks instead of quotes, and mixed indentation can confuse the parser. Keep blockquotes clean and consistent, and follow the Markdown formatting guide.
Parser rules also differ slightly between CommonMark and GFM, so test edge cases against the CommonMark specification and use a Markdown formatting checklist. Troubleshooting checklist: verify every quoted line starts with >, remove accidental blank lines, check indentation, and preview in your target Markdown parser.
Blockquotes in GitHub Flavored Markdown and HTML
Markdown blockquote syntax is broadly consistent in CommonMark and GitHub Flavored Markdown (GFM): > starts a quote, and the CommonMark specification defines the core behavior most parsers follow. In HTML, that markup becomes the blockquote element, which preserves the semantic quote structure even when styling differs.
On GitHub, you’ll see blockquotes in README files for notes, in issues for quoted replies, and in comments for references or warnings. The same syntax also underpins many developer docs patterns and quick-reference pages like a Markdown cheat sheet.
Plain blockquotes are not the same as callouts or admonitions. Callouts may be built on blockquote styling, but they usually rely on extra labels, icons, classes, or platform-specific extensions. Parser-specific behavior can still differ for lists, raw HTML, and extended Markdown features, so a Markdown parser may render edge cases differently even when the core quote syntax matches.
Quick Reference: Markdown Blockquote Cheat Sheet
Use this as a compact Markdown cheat sheet for the core blockquote patterns.
> Basic blockquote text
> Parent quote
>> Nested blockquote
>>> Third level
> First paragraph of a quote.
>
> Second paragraph stays inside the same blockquote.
> This quote includes **bold text**, *italic text*, a [link](https://markdownmastery.com/blog/markdown-basics-for-beginners), and `inline code`.
Key rules to keep in mind:
- Use the greater-than symbol (
>) at the start of each quoted line. - Repeat
>for nested blockquotes when you need deeper levels. - Leave a blank line with
>on its own to preserve multi-paragraph quotes. - Keep spacing consistent, especially
>before text. - Test the result in your target Markdown parser, since rendering can vary slightly across platforms.
If you want a reliable takeaway, remember this: blockquote syntax is simple, but consistent spacing and parser testing are what make it render cleanly across tools.
FAQ
What is markdown blockquote syntax?
It is the Markdown formatting rule that uses > at the start of a line to create a quoted block. In rendered HTML, it usually becomes the HTML blockquote element.
How do you make a blockquote in Markdown?
Start the line with > followed by a space and your text:
> This is a blockquote.
Do you need a space after the > symbol in Markdown?
Most Markdown parsers accept both >Text and > Text, but > Text is the safer choice for readability and compatibility.
How do you nest blockquotes in Markdown?
Add another > for each level:
> Level 1
>> Level 2
>>> Level 3
How do you write a multi-paragraph blockquote?
Keep the > marker on every paragraph, including the blank line between them:
> First paragraph.
>
> Second paragraph.
Can you use lists inside a blockquote?
Yes. Keep the list items quoted so the Markdown parser keeps them inside the blockquote.
Can you use bold, italics, and links inside a blockquote?
Yes. Bold text, italic text, inline code, and links all work inside blockquotes in standard Markdown.
Why is my blockquote not rendering correctly?
Common causes include missing > markers, extra blank lines, incorrect indentation, or parser differences between CommonMark and GFM.
What is the difference between a blockquote and a callout?
A blockquote is standard Markdown quote syntax. A callout is usually a styled UI pattern built on top of a quote, often with labels, icons, or platform-specific formatting.
Does Markdown blockquote syntax work the same in GitHub Flavored Markdown and CommonMark?
The core syntax is the same, but some edge cases can differ. Test in your target renderer, especially for lists, code blocks, and other nested content.
Can blockquotes contain code blocks?
Yes. Fenced code blocks can be nested inside blockquotes when each fence line is also quoted.
How do you quote multiple lines in Markdown?
Start each line with >.
How do you end a blockquote in Markdown?
Start a new paragraph without >.
What are common blockquote mistakes in Markdown?
Missing markers, inconsistent indentation, and blank lines that split the quote are the most common issues.
How do blockquotes render in HTML?
They render as the HTML blockquote element, usually with paragraph tags inside it.