Skip to content
Back to Journal
GuideMay 4, 2026·4 min read

How to Add a Blockquote in Markdown

Markdown blockquote syntax, nested quotes, and alerts. When to use blockquotes and platform support.

The quick answer: Start a line with a greater-than sign (>) followed by a space. Every line of the quote must start with >.

Basic Syntax

> This is a blockquote. > This blockquote spans two lines. > Both lines are part of the same quote.

The > tells markdown this line is quoted content. Rendered output typically shows the text indented with a left vertical border.

Multi-Paragraph Blockquotes

To include multiple paragraphs in one blockquote, add a > on the blank line between paragraphs: > First paragraph of the quote. > > Second paragraph, still inside the same blockquote.

Without the > on the blank line, the second paragraph starts a new blockquote element.

Nested Blockquotes

Stack > symbols to create nested quotes: > Outer level quote. > > > Inner nested quote — two > symbols. > > Back to the outer level.

Nesting is useful for conversation threads (quoting a reply to a quote) and for emphasizing the source of a quoted source.

Markdown Elements Inside Blockquotes

All inline and block markdown elements work inside blockquotes — prefix every line with >: > ## Heading inside a blockquote > > - Bullet list inside a quote > - Second bullet > > inline code` inside a quote > > Bold and italic inside a quote

GitHub Alerts (Typed Callout Boxes)

GitHub Flavored Markdown extends blockquote syntax with five special alert types. These render with distinct colored icons and backgrounds on GitHub: > [!NOTE] > Highlights information the reader should know, even when skimming. > [!TIP] > Optional tips for doing things better or more easily. > [!IMPORTANT] > Crucial information necessary for the user to succeed. > [!WARNING] > Critical content that needs immediate attention to avoid problems. > [!CAUTION] > Advises about risks or negative outcomes of certain actions.

These alerts are GitHub-specific. On other renderers (Obsidian, standard markdown processors) they display as plain blockquotes.

Platform-by-Platform Breakdown

GitHub and GitLab

Full blockquote support. GitHub also supports the five alert types ([!NOTE], etc.) which render with colored styling. GitLab supports blockquotes but not the GitHub alert syntax.

Obsidian

Full blockquote support. Obsidian also has its own callout syntax using blockquote-style markers: > [!info] > Obsidian callout content

Obsidian supports many callout types: info, warning, tip, important, todo, question, example, quote, and more.

Notion

Notion supports blockquotes in markdown import. They render as Notion "quote" blocks with a left border. Notion does not support GitHub alerts or Obsidian callouts.

Discord

Discord renders blockquotes with a grey left border. The > syntax works correctly. Nesting with >> also works in Discord.

Slack

Slack does not natively support markdown blockquotes. > text renders as a grey left-border quote block in some Slack contexts but behavior varies.

Common Mistakes

Missing Space After >

>Text without space — many parsers will not render this as a blockquote. Always use > Text with a space.

Not Continuing > on Subsequent Lines

> First line of a long quote Second line without > marker — this breaks out of the blockquote > First line > Second line — correct: every line needs >

Forgetting > on Blank Lines Between Paragraphs

To stay inside a blockquote across a paragraph break, the blank line between paragraphs must also have >: > Para 1 ` ← missing >, breaks out of blockquote > Para 2 > Para 1 > ← correct, stays in blockquote` > Para 2

When to Use Blockquotes

| Use case | Best approach | | --- | --- | | Quoting a person or source | Regular > blockquote | | Important note or callout | GitHub [!NOTE] or Obsidian [!info] | | Warning to the reader | GitHub [!WARNING] | | Visual separation for key text | Blockquote with bold text inside | | Email quote threads | Nested blockquotes |

Real-World Use Cases

Technical Documentation

Blockquotes work well for quoting specifications, standards documents, or RFCs: "According to RFC 2119: > The key words MUST, MUST NOT, REQUIRED..."

AI-Generated Content

When AI tools generate analysis that includes direct quotes from sources, those quotes are often formatted as blockquotes. MarkdownTools renders blockquotes with a styled left border in all three themes.

Knowledge Base Notes

In Obsidian note-taking workflows, blockquotes capture verbatim source material before paraphrasing. Callout blocks ([!note]) mark your own analysis vs the original source.


Full reference: Markdown Blockquotes.

Ready to put this into practice? Paste your markdown into the free MarkdownTools PDF exporter or HTML converter — no signup required.

Frequently Asked Questions

How do you add a blockquote in markdown?

Start a line with a greater-than sign (>) followed by a space: > This is a blockquote. Each line of the quote must start with >.

How do you nest a blockquote inside another blockquote?

Use two > symbols for the inner quote: >> inner quote. Use a single > on an empty line between the inner and outer quote to maintain the outer context.

What are GitHub markdown alerts?

GitHub extends blockquotes with typed alert callouts: > [!NOTE] for notes, > [!WARNING] for warnings, > [!TIP] for tips, > [!IMPORTANT] for important info, and > [!CAUTION] for cautions. These render with colored icons on GitHub.

Can you put other markdown inside a blockquote?

Yes. Blockquotes support all inline and block markdown elements: bold, italic, code, headings, lists, and even other blockquotes. Prefix every line with > to keep content inside the quote.

MT

MarkdownTools Team

May 4, 2026

Try it free

Make your AI output beautiful

Paste markdown from ChatGPT or Claude. Pick a theme. Export as PDF or HTML in seconds.

Open App — It's Free