Markdown blockquote
Start a line with a greater-than sign and a space to quote it. Everything that follows on that line, and on the lines after it that also start with the sign, becomes one quote.
Nothing here is uploaded. Check your network tab.
First paragraph.
Second paragraph.
The lone `>` on the middle line is what keeps the two paragraphs inside the same quote.
a quote
a quote inside it
[!NOTE] Useful information a reader should know.
[!WARNING] Something that could go wrong.
GitHub, and now several other renderers, style these as coloured admonitions. Elsewhere they are ordinary quotes with a bracketed word.
What usually goes wrong
- A quote ends at the first line that does not start with
>. Forgetting the sign on a continuation line splits one quote into two. - Other markdown works inside a quote: lists, code blocks and headings all render, as long as every line keeps its
>. - The space after the sign is not strictly required, but leaving it out makes the source harder to read and some renderers stricter.
Where it behaves differently
It renders as written on GitHub, GitLab, Obsidian, VS Code preview and Slack. Everywhere else in this table it does something else, and that is worth reading before you paste.
| Platform | Behaviour |
|---|---|
| Notion | > makes a toggle list. A quote is a double quote and a space. |
| Discord | > for one line, >>> for everything after it. |
For the .md file that arrives in Mail
A markdown file on a phone is the worst case: no editor, no preview, and a share sheet full of apps that want to import it into a library. The iPhone and iPad app opens it where it landed, renders it, and lets you edit and save it back.
For iPhone and iPad.