Markdown vs HTML blockquote — which should I use?

Use Markdown when your destination supports it (GitHub, Reddit, Discord, Substack, most static-site generators). Markdown is more portable and easier to edit. Use HTML when you need precise styling control (custom CSS classes, embedded citation tags) or your destination is HTML-only (WordPress block editor accepts both, classic editor needs HTML). Both render identically in most contexts.

How do I cite the source?

Three conventions: (1) inline attribution within the blockquote ( — Author Name, Title), (2) below the blockquote in italics or smaller text, (3) HTML <cite> tag inside the blockquote (semantic but not always styled). Pick one and stay consistent within a single document. For academic writing follow the citation style (APA, MLA, Chicago); for blog posts the inline em-dash convention is most common.

Should I use ellipses or [brackets] for edits?

Use ellipses (...) when omitting words from the middle of a quote. Use [brackets] for editorial insertions like clarifications, pronoun changes, or capitalization adjustments at the start of a sentence. The reader needs to know what you changed vs what was original. Editorial integrity matters; attributing words the source didn't actually say is plagiarism territory.

How long can a quoted passage be?

Fair-use law in the US permits short quotations (typically a few sentences from an article, a stanza from a poem) without permission, when used for commentary, criticism, or scholarship. Longer quotes (300+ words from an article, full paragraphs from a book) increasingly need permission or fall outside fair use. Always provide attribution regardless. For commercial use, consult an IP attorney.

What about nested blockquotes (quotes within quotes)?

Markdown supports nesting with multiple greater-than signs: >> for double-nested. HTML can nest blockquote elements. Visually, most renderers indent each nesting level further. Useful for email threads (quote your reply, quote the previous reply, quote the original message). Avoid more than 2-3 levels of nesting — readability collapses.

Can I add a CSS class for custom styling?

In HTML, yes: <blockquote class="pullquote">...</blockquote> lets you target it with custom CSS for typography, color, border styles. In Markdown, you can't add classes directly; you'd need MDX/Markdoc with custom components, or pre-process Markdown into HTML and add classes there. For typical styling needs, the platform's default blockquote rendering is usually sufficient.

Text & Writing Utilities · Free tool

Blockquote Formatter

Wrap your selection in clean blockquote syntax for blog posts and threads instantly. Generate styled pull-quotes with proper citation free online.

Updated June 2026

QuoteAttribution

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

Found this useful?Email Buy Me a Coffee

What it does

Blockquotes are the typographic device for presenting quoted content distinctly from surrounding prose — pulled to the side or indented, often with different styling (italics, smaller font, accent color left-border). They're central to blog posts citing other writers, technical articles quoting documentation, threaded discussions where you need to reference a previous message, academic writing where pull-quotes highlight key arguments, and email replies where you're responding to specific parts of an earlier message. Different publishing platforms have different blockquote syntaxes that don't quite agree.

The formatter accepts your raw quote text and an optional attribution (author, source, URL), then outputs in three common formats: Markdown (greater-than-prefix on each line: `> The quoted text`), HTML (`<blockquote>...</blockquote>` with optional `<cite>` for attribution), and Slack-flavored markdown (similar to standard markdown with subtle differences in how multi-line is rendered). Pick based on your destination platform. GitHub, Reddit, Discord, most static-site generators (Hugo, 11ty, Next.js with MDX), and Substack all accept standard Markdown blockquotes. WordPress and most CMSes use HTML blockquotes. Slack threads use Slack-flavored markdown.

Conventions worth respecting: attribution should follow the quote, not precede it (the quote leads, the source supports). Use ellipses (...) when omitting words from the middle of a quote; use [brackets] for any editorial insertions. Long quotes (over 4 lines or 40 words) typically deserve their own blockquote block with attribution; short quotes (single sentence) often fit better inline with quote marks. Pull-quotes (excerpted quotes set apart visually for emphasis) are typically a smaller subset of the article's overall blockquote inventory — used for the most striking insight, not every quote.

Embed this tool on your siteShow snippet

Paste this snippet into any page. Loads on-demand (lazy), no tracking scripts, and sized to most dashboards. Replace the height to fit your layout.

<iframe src="https://freetoolarena.com/embed/blockquote-formatter" width="100%" height="720" frameborder="0" loading="lazy" title="Blockquote Formatter" style="border:1px solid #e2e8f0;border-radius:12px;max-width:720px;"></iframe>

Embed docs →

How to use it

Paste your quote text into the input.
Add attribution (author, optional source title, optional URL).
Pick the output format: Markdown, HTML, or Slack-flavored Markdown.
Copy the formatted blockquote.
Paste into your blog post, email, or message — preview to confirm rendering.

When to use this tool

Citing other writers or sources in blog posts and articles.
Pull-quotes to highlight key insights visually in long-form content.
Email replies that quote specific parts of the previous message.
Threaded discussions referencing earlier messages.
Academic writing where quotes need consistent attribution formatting.

When not to use it

Inline short quotes (single sentence) — use quote marks (" ") inline instead.
Speech / dialogue — use proper dialogue formatting, not blockquotes.
Long quotes that should be paraphrased — fair-use limits and reader engagement both favor brief quoting.
Code snippets — use code blocks (```) rather than blockquotes.

Common use cases

Educational use — demonstrating the underlying concept
Onboarding a colleague who needs the same calculation/conversion
Verifying a number or output before passing it on
Quick use during a typical workday

Frequently asked questions

Markdown vs HTML blockquote — which should I use?: Use Markdown when your destination supports it (GitHub, Reddit, Discord, Substack, most static-site generators). Markdown is more portable and easier to edit. Use HTML when you need precise styling control (custom CSS classes, embedded citation tags) or your destination is HTML-only (WordPress block editor accepts both, classic editor needs HTML). Both render identically in most contexts.
How do I cite the source?: Three conventions: (1) inline attribution within the blockquote ( — Author Name, Title), (2) below the blockquote in italics or smaller text, (3) HTML <cite> tag inside the blockquote (semantic but not always styled). Pick one and stay consistent within a single document. For academic writing follow the citation style (APA, MLA, Chicago); for blog posts the inline em-dash convention is most common.
Should I use ellipses or [brackets] for edits?: Use ellipses (...) when omitting words from the middle of a quote. Use [brackets] for editorial insertions like clarifications, pronoun changes, or capitalization adjustments at the start of a sentence. The reader needs to know what you changed vs what was original. Editorial integrity matters; attributing words the source didn't actually say is plagiarism territory.
How long can a quoted passage be?: Fair-use law in the US permits short quotations (typically a few sentences from an article, a stanza from a poem) without permission, when used for commentary, criticism, or scholarship. Longer quotes (300+ words from an article, full paragraphs from a book) increasingly need permission or fall outside fair use. Always provide attribution regardless. For commercial use, consult an IP attorney.
What about nested blockquotes (quotes within quotes)?: Markdown supports nesting with multiple greater-than signs: >> for double-nested. HTML can nest blockquote elements. Visually, most renderers indent each nesting level further. Useful for email threads (quote your reply, quote the previous reply, quote the original message). Avoid more than 2-3 levels of nesting — readability collapses.
Can I add a CSS class for custom styling?: In HTML, yes: <blockquote class="pullquote">...</blockquote> lets you target it with custom CSS for typography, color, border styles. In Markdown, you can't add classes directly; you'd need MDX/Markdoc with custom components, or pre-process Markdown into HTML and add classes there. For typical styling needs, the platform's default blockquote rendering is usually sufficient.

Learn more

Explore more text & writing utilities tools

100% in-browserNo downloadsNo sign-upMalware-freeHow we keep this safe →