Four Ways to Quote Text in Confluence (and When to Use Each)

[#1]

Quoting text well is a small thing that makes documentation read like documentation instead of a wall of paragraphs. A quote separates someone else's words from your own — a customer request inside a spec, a policy sentence inside a runbook, a line of an email inside a postmortem.

Confluence doesn't have a single dedicated "quote block," but there are four practical ways to get there. I'm Simon from NGPILOT (we build Confluence apps on the Atlassian Marketplace), and I'll walk through all four — including two that need nothing but the native editor.

---

1. The native way: Indent (Tab)

The closest built-in option is the Indent toolbar button:

1. Type or paste the quoted text as its own paragraph.
2. Select it and click Indent in the toolbar (or press Tab).

You get an indented block with a left border — the classic "quoted" look, and it works in every Confluence Cloud space with zero setup.

Where it falls short:

• It's visual only. There's no semantic "this is a quote" marker, so exports and other tools just see an indented paragraph.
• One indent level per keypress. Deep nesting means lots of Tab pressing, and the border doesn't change per level.
• No attribution field. If you want "— Jane, from the March retro" under the quote, that's a manually-styled second line.

This is the right choice for quick, one-level quotes in meeting notes and everyday pages — which, honestly, is most quotes.

2. The native way: Info / Note / Warning panels

The built-in panel macros also work as quotation containers when you want the quote to stand out with a colored background instead of a border:

1. Type /info (or /note, /warning) and insert the panel.
2. Paste the quoted sentence inside.
3. Add the attribution on the last line, usually in italics.

This is the better native choice when the quote carries context — "read this before following the steps below" — because the panel color signals importance. It's still not semantically a quote, and every panel gets the same icon treatment, so a page with several quotes can start to look like a wall of warnings.

3. The markup way: Markdown blockquote syntax

If you write in Markdown — or paste Markdown into Confluence often — the blockquote syntax you already know from GitHub works too:

• > quoted text for a quote block
• >> nested quote for a second level
• Combine with *italic* inside the quote for emphasis and attribution

Worth knowing: the new editor doesn't render Markdown blockquote syntax as a styled quote everywhere — behavior depends on where you're typing it (comments, the Markdown import path, or a marketplace editor extension). If your team lives in Markdown, test the path you actually use before standardizing on it.

4. The styled way: panel macros with custom colors

When the page is customer-facing — release notes, a knowledge base, a public spec — a bare indent can look plain. The native Info panel gets you a colored background; if you want to control the exact border, background, and text colors, several Marketplace apps offer customizable panel/callout macros. My team builds Content Formatting Macros & Page Builder for Confluence (Marketplace link), whose Panel macro supports custom colors, border position, and icon choice — one example among the options a Marketplace search for "panel macro" will show you. Pick by the page style you need, not by vendor.

---

Which one should you use?

Your situation	Reach for
Quick quote in meeting notes	Native Indent (Tab)
"Read this first" quote in a runbook	Native Info/Note panel
You write in Markdown anyway	Markdown > syntax
Customer-facing docs where style matters	A styled panel macro

All four solve the same problem at different levels of polish, and the two native ones cover most everyday needs. Questions about a specific quoting setup you have? Ask in the comments.

[Mia Tamm _Simpleasyty_]

Really useful breakdown. I especially like the distinction between something that looks like a quote and something that is actually treated as one structurally. For quick notes, indentation is probably enough most of the time, but the semantic side becomes much more interesting once content starts being exported, reused, searched or consumed by other tools.

It makes me wonder whether Confluence could eventually benefit from a native quote block with attribution built in — something as simple to use as a panel, but with the meaning preserved behind the scenes.

Thanks for putting the four approaches side by side. The “which one should you use?” table at the end makes this particularly useful. 👏