Markdown Blockquotes: Syntax and Creative Uses

Blockquotes indent text with a vertical bar to visually set it apart from the surrounding content. The syntax is a > prefix at the start of each line. Beyond quoting someone, blockquotes are used for callouts, warnings, notes, and highlighted information.

Basic Syntax

> This is a blockquote.

You can span multiple lines by adding > to each:

> This is the first line of a longer quote.
> This is the second line.
> And the third.

For lazy wrapping, only the first line of a paragraph needs the >:

> This is a long paragraph that continues on the next line
without a `>` prefix, and most parsers still include it in the blockquote.

However, adding > to every line is clearer and avoids parser inconsistencies.

Multi-Paragraph Blockquotes

Separate paragraphs with a blank line that has a > prefix:

> First paragraph of the quote.
>
> Second paragraph of the quote.

Without the > on the blank line, some parsers end the blockquote at the first paragraph.

Nested Blockquotes

Stack > characters to nest quotes:

> Outer quote
>
>> Inner quote
>>
>>> Third level

This is useful for threaded conversations or email reply chains, but nesting beyond two levels gets hard to read.

Blockquotes with Other Elements

Blockquotes can contain most markdown elements.

Bold and italic inside a blockquote:

> This is **important** and *worth remembering*.

Lists inside a blockquote:

> Requirements:
>
> - Node.js 18+
> - pnpm
> - A terminal

Code blocks inside a blockquote:

> Example:
>
> ```bash
> mdtolink publish notes.md
> ```

Links inside a blockquote:

> Read the [documentation](https://mdtolink.com/docs/getting-started) for setup instructions.

Headings inside a blockquote:

> ## Section Title
>
> Content under this heading.

Not all renderers support headings inside blockquotes. GitHub handles it fine; some simpler parsers may not.

GitHub-Style Admonitions (Alerts)

GitHub introduced alert syntax in 2023 as an extension to blockquotes:

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

> [!TIP]
> Helpful advice for the reader.

> [!IMPORTANT]
> Key information the reader should know.

> [!WARNING]
> Something that needs attention or could cause issues.

> [!CAUTION]
> Risk of data loss or other negative outcomes.

These render as colored callout boxes on GitHub with distinct icons. Outside GitHub, they render as regular blockquotes with the [!TYPE] text visible.

Alert Support by Platform

Obsidian has its own callout syntax that predates GitHub’s alerts and supports additional types like [!INFO], [!QUESTION], [!BUG], and custom callouts. The syntax is compatible with GitHub’s alerts for the five types above.

Common Uses for Blockquotes

Beyond literal quotes, blockquotes serve several practical purposes:

Attribution quotes:

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

Notes and tips in documentation:

> **Note:** This feature requires Pro plan or higher.

Disclaimers and warnings:

> **Warning:** Running this command deletes all data. Make a backup first.

Highlighting key information:

> **TL;DR:** Use `mdtolink publish file.md` to get a shareable URL in seconds.

Showing example output:

> Expected output:
>
> ```
> Published to: https://mdtolink.com/abc123
> ```

Platform Differences

Common Mistakes

Forgetting the space after >. A > without a following space still works on most parsers, but adding the space is standard:

<!-- Works but not standard -->
>No space

<!-- Standard -->
> With space

Breaking a multi-paragraph blockquote. A blank line without > ends the blockquote:

<!-- Breaks into blockquote + paragraph -->
> First paragraph.

Second paragraph is outside the blockquote.

<!-- Stays in the blockquote -->
> First paragraph.
>
> Second paragraph stays inside.

Overusing blockquotes for emphasis. If you use blockquotes for every other paragraph, the visual distinction disappears. Reserve them for content that genuinely needs to stand apart: quotes, notes, warnings, key takeaways.

Copy-Paste Templates

Simple quote:

> This is a blockquote.

Multi-paragraph quote:

> First paragraph.
>
> Second paragraph.

Nested quote:

> Original message.
>
>> Reply to the message.

Note callout:

> **Note:** Additional context the reader should know.

Warning callout:

> **Warning:** This action cannot be undone.

GitHub alert:

> [!TIP]
> Helpful advice for the reader.

Quote with attribution:

> The only way to do great work is to love what you do.
>
> Steve Jobs

FAQ

How do I create a blockquote in markdown?

Start the line with > followed by a space: > Quoted text. Every line of the blockquote needs a > prefix. For multiple paragraphs, use > on the blank line between them.

Can I nest blockquotes?

Yes. Use >> for a second-level quote, >>> for a third level, and so on. Most renderers support multiple nesting levels, but readability drops beyond two.

What are GitHub alert boxes?

GitHub supports five alert types inside blockquotes: [!NOTE], [!TIP], [!IMPORTANT], [!WARNING], and [!CAUTION]. These render as colored boxes with icons on GitHub. On other platforms, they appear as regular blockquotes.

How do I add a code block inside a blockquote?

Prefix every line of the code fence with >:

> ```bash
> echo "Hello"
> ```

This places the code block inside the blockquote.

Try It Out

Test blockquote formatting in the MDtoLink editor with real-time preview. When your document is ready, publish it to a shareable URL.

See the full syntax in the markdown cheat sheet. For list nesting (which follows similar indentation rules), see the markdown lists guide.