Markdown Blockquotes

A Markdown blockquote is used to highlight quoted text, important notes, warnings, tips, or referenced content.

Instead of displaying text as a normal paragraph, a blockquote visually separates it from the rest of the document, making it easier for readers to notice important information.

Blockquotes are commonly used in:

• GitHub README files
• Technical documentation
• API documentation
• Tutorials
• Blog articles
• Knowledge bases
• Developer guides

Markdown creates a blockquote using the greater-than (>) character at the beginning of a line.

To create a blockquote, place a greater-than symbol followed by a space before the text.

> This is a Markdown blockquote.

Output

The > character tells the Markdown renderer that the following text should be displayed as a quotation.

Blockquotes improve readability by separating important content from regular paragraphs.

They are commonly used to display:

• Important notes
• Helpful tips
• Warnings
• Quoted text
• Documentation highlights
• References
• Callout sections

Using blockquotes makes long documentation easier to scan and understand.

A blockquote can span multiple lines by adding the > character before each line.

> Markdown is a lightweight markup language.
>
> It is widely used for documentation,
> README files, technical blogs,
> and note-taking applications.

Output

Adding > to every line keeps the entire paragraph inside the blockquote.

You can also create multiple paragraphs within the same blockquote.

> This is the first paragraph.
>
> This is the second paragraph.
>
> Both paragraphs belong to the same blockquote.

Output

This formatting is commonly used in tutorials and documentation where additional explanation is required.

Use blockquotes whenever you want readers to pay special attention to a piece of information.

Good use cases include:

• Quoting documentation
• Highlighting important notes
• Displaying warnings
• Showing best practices
• Explaining limitations
• Providing recommendations
• Adding helpful tips

Avoid using blockquotes for every paragraph. Overusing them reduces their visual impact and makes documentation harder to read.

Markdown allows you to create nested blockquotes by adding additional greater-than (>) symbols.

Nested blockquotes are useful for showing replies, quoted conversations, or separating multiple levels of information.

Single Nested Blockquote

> This is the main quote.
>
>> This is a nested quote.

Output

Multiple Levels of Nesting

You can continue nesting blockquotes by adding more > characters.

> Level 1
>> Level 2
>>> Level 3
>>>> Level 4

Output

Although Markdown supports deep nesting, keeping it to two or three levels usually provides the best readability.

You can include Markdown headings inside a blockquote.

> ## Important
>
> Always preview your Markdown before publishing.

Output

This approach works well for documentation notes and highlighted sections.

Lists can be placed inside blockquotes by combining the > character with normal list syntax.

Unordered List

> Features:
>
> - Easy to learn
> - Lightweight
> - Portable

Output

Ordered List

> Setup Steps:
>
> 1. Install Node.js
> 2. Install dependencies
> 3. Start the server

Output

Lists inside blockquotes are commonly used for instructions, recommendations, and documentation highlights. For more on list syntax, see Markdown Lists.

Code examples can be placed inside blockquotes.

> Example command:
>
> ```bash
> npm install
> npm run dev
> ```

Output

This is useful when explaining commands, API requests, or programming examples within an important note. See Markdown Code Blocks for fenced block syntax.

Links work exactly the same inside blockquotes as they do in normal Markdown.

> Read the official
> [Markdown Guide](https://www.markdownguide.org/)
> for more information.

Output

Links inside blockquotes are often used to reference official documentation, external resources, or related guides.

Images can also be included inside blockquotes.

> ![Markdown Logo](logo.png)
>
> Official Markdown logo.

Output

Support for images inside blockquotes depends on the Markdown renderer, but modern platforms such as GitHub, GitLab, and Obsidian handle them correctly. See Markdown Images for image syntax details.

A single blockquote can contain multiple Markdown elements together.

> ## Deployment Checklist
>
> Complete the following steps:
>
> - Install dependencies
> - Configure environment variables
>
> ```bash
> npm install
> npm run build
> ```
>
> Learn more in the Deployment Guide.

Output

This combination is commonly used in technical documentation because it groups related information into one clearly highlighted section while keeping the page easy to scan.

GitHub supports standard Markdown blockquotes as well as GitHub Alerts (also called callouts). These alerts are one of the most useful ways to highlight important information in README files, documentation, Wikis, Issues, and Pull Requests.

GitHub Alerts are supported in GitHub Flavored Markdown (GFM) and help readers quickly identify notes, tips, warnings, and important messages.

Use a NOTE callout to provide additional information without interrupting the main content.

> [!NOTE]
> Markdown is supported by GitHub, GitLab, VS Code, Obsidian, and many other editors.

On GitHub, this renders as a styled NOTE callout with an icon and colored border. In editors that do not support GitHub Alerts, it appears as a plain blockquote.

Output (standard blockquote rendering)

Use a NOTE whenever readers may benefit from additional context or clarification.

Use a TIP callout to share recommendations or productivity tips.

> [!TIP]
> Always specify a language identifier after the opening triple backticks for syntax highlighting.

On GitHub, this renders as a styled TIP callout. Other Markdown editors may display it as a plain blockquote.

Output (standard blockquote rendering)

Tips help readers follow best practices and avoid common mistakes.

Use an IMPORTANT callout for information that should not be overlooked.

> [!IMPORTANT]
> Verify every code example before publishing documentation.

On GitHub, this renders as a styled IMPORTANT callout. Other Markdown editors may display it as a plain blockquote.

Output (standard blockquote rendering)

Reserve IMPORTANT alerts for essential guidance that directly affects the reader.

Warnings highlight actions that could cause problems if ignored.

> [!WARNING]
> Deleting production data cannot be undone.

On GitHub, this renders as a styled WARNING callout. Other Markdown editors may display it as a plain blockquote.

Output (standard blockquote rendering)

Warnings are ideal for security notices, destructive actions, and configuration changes.

Use CAUTION when readers need to be especially careful.

> [!CAUTION]
> Never commit API keys or passwords to a public repository.

On GitHub, this renders as a styled CAUTION callout. Other Markdown editors may display it as a plain blockquote.

Output (standard blockquote rendering)

This alert type is commonly used for security-sensitive documentation.

GitHub callouts are most effective when highlighting:

• Notes
• Tips
• Best practices
• Security recommendations
• Warnings
• Important instructions
• Configuration requirements

Avoid using them for ordinary paragraphs. Too many callouts reduce their impact and make documentation harder to scan.

Platform	Standard Blockquotes	GitHub Alerts
GitHub	✅	✅
GitLab	✅	❌
VS Code Preview	✅	Limited
Obsidian	✅	Theme/Plugin Dependent
Docusaurus	✅	Framework Specific
MkDocs	✅	Theme Specific
Markdown Guide Editors	✅	Usually No

Standard blockquotes are supported almost everywhere, while GitHub Alerts are primarily designed for GitHub Flavored Markdown.

Follow these recommendations when using Markdown blockquotes:

• Use blockquotes only for information that deserves emphasis.
• Keep quoted content concise.
• Use GitHub Alerts instead of plain blockquotes for notes and warnings on GitHub.
• Avoid nesting blockquotes more than two or three levels.
• Place code blocks, lists, and links inside blockquotes only when they improve clarity.
• Maintain consistent spacing after every > character.
• Preview your Markdown in the Markdown Editor before publishing to verify rendering across platforms.

Well-structured blockquotes improve readability and help readers quickly identify important information.

Although blockquotes are simple to create, small syntax mistakes can prevent them from rendering correctly. Here are the most common issues and how to fix them.

Forgetting the Space After >

Incorrect:

>This is a blockquote.

Correct:

> This is a blockquote.

While some Markdown parsers accept both formats, adding a space after > improves readability and follows common Markdown conventions.

Missing the > on Multiple Lines

Incorrect:

> This is the first line.
This line is outside the blockquote.

Correct:

> This is the first line.
> This line is also inside the blockquote.

Every line that belongs to the blockquote should begin with the > character.

Incorrect Nesting

Incorrect:

>> First level
> Second level

Correct:

> First level
>> Second level
>>> Third level

Maintain a logical nesting order to keep the quote structure easy to understand.

Using Too Many Nested Levels

Although Markdown allows multiple levels of nesting, deeply nested blockquotes quickly become difficult to read.

Instead of nesting five or more levels, consider breaking the content into separate sections or using headings instead.

Overusing Blockquotes

Not every paragraph should be inside a blockquote.

Use blockquotes only for:

• Notes
• Tips
• Warnings
• Important information
• Referenced quotations

For normal explanations, use regular paragraphs.

Blockquotes appear in many types of technical documentation.

Documentation Note

> **Note**
>
> Always back up your project before making major configuration changes.

Installation Tip

> **Tip**
>
> Install dependencies using the latest LTS version of Node.js.

Security Warning

> **Warning**
>
> Never commit passwords, API keys, or secret tokens to a public repository.

API Documentation

> **Important**
>
> This endpoint requires authentication using a Bearer token.

README Highlight

> This project supports Windows, macOS, and Linux.

These examples show how blockquotes improve readability without adding unnecessary complexity.

Well-written blockquotes improve the reading experience for everyone.

Follow these recommendations:

• Keep quoted text concise.
• Use clear and descriptive language.
• Avoid placing large sections of content inside a single blockquote.
• Use headings before long blockquotes when appropriate.
• Reserve warning callouts for genuinely important information.
• Maintain consistent formatting throughout your documentation.

Accessible documentation is easier to scan and understand on both desktop and mobile devices.

Markdown blockquotes provide a simple way to highlight important information, quoted text, and documentation notes.

In this guide, you learned:

• Basic blockquote syntax
• Multi-line blockquotes
• Nested blockquotes
• Blockquotes with headings, lists, links, images, and code blocks
• GitHub Notes, Tips, Warnings, and Callouts
• Best practices
• Common mistakes
• Platform compatibility
• Frequently asked questions

Whether you're writing a GitHub README, technical documentation, knowledge base, or tutorial, blockquotes help readers quickly identify key information and improve the overall readability of your content.

Continue learning Markdown with these guides:

Available now

• Markdown Basics — core concepts for beginners
• Markdown Cheat Sheet — quick syntax lookup
• Markdown Syntax — complete reference with examples
• Markdown Headings — document structure with H1–H6
• Markdown Paragraphs — blank lines and spacing
• Markdown Lists — ordered, unordered, nested, and task lists
• Markdown Links — inline, reference, and relative links
• Markdown Images — syntax, URLs, alt text, and GitHub paths
• Markdown Tables — syntax, alignment, and GitHub GFM
• Markdown Code Blocks — fenced blocks and syntax highlighting

Coming soon to MDConvertHub Docs

• Markdown HTML
• Markdown Footnotes
• Markdown Horizontal Rules

The best way to learn blockquotes is by writing them yourself. Open the Markdown Editor to experiment with blockquotes, nested quotes, GitHub callouts, lists, and code examples while previewing the rendered output in real time.