2026-04-29T00:00:00.000Z

What Are Obsidian Callouts (And Why They Are a Game-Changer)

Q: Q: Do callouts break if I export my notes to plain Markdown?

The `> [!TYPE]` syntax is just a blockquote with a specific bracket notation. In plain Markdown editors that don't support callouts, it renders as a standard blockquote — readable, just not styled.

Q: Q: My custom callout icon isn't showing. What's wrong?

Obsidian uses [Lucide icons](https://lucide.dev). The icon name in CSS must match exactly — `lucide-check-square`, not `lucide-checksquare`. Check the Lucide site for the precise name string.

Provide a 'copy-paste' CSS snippet library for 5-7 non-standard, workflow-oriented callouts (e.g., 'Action Item', 'Key Insight', 'Project Goal') that users can immediately implement.

How to Use Callouts in Obsidian for Better Notes (A Practical PKM Guide)

TL;DR

Obsidian callouts use a simple > [!TYPE] syntax to create visually distinct blocks that make notes scannable in seconds.
The 12 built-in types cover most needs, but five copy-paste CSS snippets in this guide give you workflow-specific callouts like [!action] and [!key] immediately.
Connecting callouts to PARA, Zettelkasten, and Evergreen Note workflows turns a formatting trick into a genuine thinking tool.

What Are Obsidian Callouts (And Why They Matter)
The Fundamentals: Callout Syntax Explained
A Practical Guide to the 12 Default Types
How to Create Custom Callouts with CSS Snippets
Your Custom Callout Starter Pack (Copy & Paste)
The Callout Cookbook: Real-World Note Templates
Callouts and Your PKM System
Advanced Techniques: Nesting, Aliases, and Mobile
Comparison Table: Default vs. Custom Callouts
FAQ
Conclusion

What Are Obsidian Callouts?

A callout is a visually distinct block inside your note. It has a colored left border, an icon, and an optional title. It renders from a modified blockquote syntax, so it works in plain Markdown and shows up formatted in Reading View or Live Preview.

Compare two versions of the same note section:

Without callouts:

Warning: Do not delete the raw source files before archiving. Action: Schedule backup by Friday. Key insight: This bottleneck affects every downstream process.

That text is a wall. Your eye has nowhere to land.

With callouts: Three separate, color-coded blocks — a red warning, a green action item, a yellow insight — each with its own icon. Scanning that same information takes under three seconds.

The difference is not cosmetic. When you return to a note two weeks later, visual hierarchy is the difference between finding what you need and re-reading everything.

The Fundamentals: Callout Syntax Explained

Every callout follows the same structure:

> [!TYPE] Optional Title
> Content line one
> Content line two

Breaking it down:

> — standard Markdown blockquote character
[!TYPE] — the callout identifier; controls color and icon
Optional Title — if omitted, the type name becomes the title
Subsequent > lines — the body content

Example:

> [!warning] Back Up First
> Never run the migration script on a live database without a verified backup.

That renders as a yellow/orange block with a triangle-warning icon and the title “Back Up First.”

Foldable callouts: Add + (open by default) or - (collapsed by default) after the type:

> [!summary]- Full Meeting Notes
> Content is hidden until the reader clicks the arrow.

Foldable callouts are essential for long notes. They preserve detail without forcing you to scroll past content that’s only relevant sometimes.

A Practical Guide to the 12 Default Types

Type	Icon	Best Use Case
`note`	Pencil	General annotations, side comments
`info`	Info circle	Background context, definitions
`tip` / `hint`	Flame	Shortcuts, workflow improvements
`success` / `check`	Checkmark	Completed milestones, confirmed facts
`question` / `faq`	Question mark	Journaling prompts, open research questions
`warning` / `caution`	Triangle	Risks, caveats, things not to skip
`failure` / `missing`	X mark	Blocked tasks, failed experiments
`danger` / `error`	Lightning bolt	Critical risks, irreversible actions
`bug`	Bug icon	Software issues, errors to investigate
`example`	List icon	Code samples, illustrative scenarios
`quote` / `cite`	Quotation mark	Verbatim citations from sources
`todo`	Checkbox	Inline task lists within a note

Practical pairings:

[!question] inside a Zettelkasten literature note flags gaps to investigate later
[!quote] preserves exact source text, separated from your paraphrase
[!todo] inside a meeting note creates inline tasks without a separate task file
[!success] on a project page marks completed deliverables at a glance

How to Create Custom Callouts with CSS Snippets

CSS snippets are plain text files with a .css extension. Obsidian loads them from a specific folder and applies the styles across your vault. You do not need to know CSS deeply — the templates below require only color and icon changes.

Step-by-step setup:

Open Obsidian Settings → Appearance
Scroll to CSS Snippets and click the folder icon — this opens YourVault/.obsidian/snippets/
Create a new file, e.g., custom-callouts.css
Paste your CSS, save the file
Return to Settings → Appearance → CSS Snippets and toggle your file on

If you want dozens of beautiful pre-configured callouts without writing a single line of code, a premium Obsidian theme from Gumroad or Ko-fi typically includes an entire custom callout library out of the box — worth considering if design consistency matters to your workflow.

Your Custom Callout Starter Pack

Five callouts designed for real PKM workflows. Copy each block into your custom-callouts.css file.

1. `[!action]` — Action Item (Green)

.callout[data-callout="action"] {
  --callout-color: 34, 197, 94;
  --callout-icon: lucide-check-square;
}

Usage: > [!action] By Friday — one callout per deliverable inside meeting or project notes.

2. `[!key]` — Key Insight (Amber)

.callout[data-callout="key"] {
  --callout-color: 245, 158, 11;
  --callout-icon: lucide-key;
}

Usage: Wrap the single most important takeaway from a book chapter or lecture. Forces you to identify it explicitly.

3. `[!summary]` — TL;DR Block (Blue-Grey)

.callout[data-callout="summary"] {
  --callout-color: 100, 116, 139;
  --callout-icon: lucide-align-left;
}

Usage: Drop a [!summary] at the top of long evergreen notes. When you link to that note from elsewhere, the summary callout is the first thing you read.

4. `[!person]` — Contact / Attendee (Purple)

.callout[data-callout="person"] {
  --callout-color: 168, 85, 247;
  --callout-icon: lucide-user;
}

Usage: List meeting attendees or the person a note is about. Makes people immediately scannable — critical in PARA-style Area notes.

5. `[!goal]` — Project Goal (Teal)

.callout[data-callout="goal"] {
  --callout-color: 20, 184, 166;
  --callout-icon: lucide-target;
}

Usage: Pin the stated objective at the top of every project note. When scope creeps, you re-read it.

The Callout Cookbook

Meeting Note Template

> [!person] Attendees
> - Sarah (PM), Dev (Engineering Lead), You

> [!info] Agenda
> 1. Q3 roadmap review
> 2. Blocker on API integration

> [!warning] Decision Made
> We are pushing the mobile release to October. Non-negotiable.

> [!action] Next Steps
> - [ ] Dev: fix auth token issue by Wed
> - [ ] You: update stakeholder doc by Thu

Book Summary Template

> [!summary]- One-Sentence Summary
> The book argues that deliberate practice, not talent, explains elite performance.

> [!key] Core Insight
> Feedback loops must be immediate and specific — vague effort produces vague results.

> [!quote] Best Quote
> "The most effective practice is a form of problem-solving." — Anders Ericsson

> [!question] Open Questions
> - How does this apply to creative work, where output quality is subjective?

Project Dashboard Template

> [!goal] Project Goal
> Launch beta to 500 users by November 1.

> [!info] Status
> 🟡 In progress — blocked on design review

> [!success]- Completed Milestones
> - ✅ Architecture finalized
> - ✅ Auth flow built

> [!action] This Week
> - [ ] Finish onboarding copy
> - [ ] QA pass on Android

Callouts and Your PKM System

PARA (Projects / Areas / Resources / Archive):

Project notes → [!goal], [!action], [!status] at the top
Area notes → [!person] for key contacts, [!warning] for recurring risks
Resource notes → [!summary], [!quote], [!key] for captured knowledge

Zettelkasten:

Literature notes → [!quote] for source text, [!key] for your synthesis
Permanent notes → [!summary] forces the atomic idea to be stated clearly
[!question] flags connections you haven’t made yet

Evergreen Notes:

Every evergreen note benefits from a [!summary]- callout (foldable) at the top stating the claim the note makes — readable when you link to it, collapsible so it doesn’t dominate the note body

Advanced Techniques

Nesting callouts: Place >> to nest one callout inside another:

> [!info] Project Context
> Background on the client.
>> [!warning] Known Risk
>> Their IT team has not approved the integration yet.

Aliases: Obsidian recognizes multiple names for the same type (tip, hint, important all trigger the same style). You can use whichever reads naturally in context.

Changing the display title only: The title after [!TYPE] is purely display text. > [!action] Schedule by EOD Friday shows the green action icon with the custom title — the type still controls the style.

Mobile: Callouts render identically in the Obsidian mobile app. If you use custom CSS snippets, sync them through Obsidian Sync — the most reliable method to keep your .obsidian/snippets/ folder consistent across every device without manual file transfers.

Comparison Table

Feature	Default Callouts	Custom CSS Callouts
Setup time	Zero	5 minutes
Available immediately	Yes	After snippet install
Custom color	No	Yes
Custom icon	No	Yes (Lucide icons)
Works on mobile	Yes	Yes (with sync)
Requires code knowledge	No	Minimal
Tied to theme	Partially	Independent
Best for	General use	Workflow-specific use

Conclusion

Callouts are one of the highest-leverage formatting decisions you can make in Obsidian. The syntax takes two minutes to learn. The five custom callouts in this guide take five minutes to install. The return — notes you can scan in seconds, templates that enforce consistent structure, and visual signals that survive the gap between writing and reviewing — lasts as long as you keep the vault.

Start with the meeting note cookbook template this week. Add [!key] to your next book chapter note. Once those are habits, layer in the project dashboard structure.

If you want to go further and build a complete, linked PKM system around these ideas — not just formatting but linking, retrieval, and synthesis — Linking Your Thinking by Nick Milo is the most thorough practical course available for Obsidian users at this level.

Some links in this article are affiliate links. They cost you nothing extra and help fund future guides like this one.

Frequently Asked Questions

Q: Do callouts break if I export my notes to plain Markdown?

The > [!TYPE] syntax is just a blockquote with a specific bracket notation. In plain Markdown editors that don’t support callouts, it renders as a standard blockquote — readable, just not styled.

Q: Can I use callouts inside tables or other complex structures?

No. Callouts are block-level elements. They cannot be placed inside a Markdown table cell. Use them before or after tables to annotate table content.

Q: My custom callout icon isn’t showing. What’s wrong?

Obsidian uses Lucide icons. The icon name in CSS must match exactly — lucide-check-square, not lucide-checksquare. Check the Lucide site for the precise name string.

Q: Are callouts the same as admonitions?

Functionally yes. “Admonitions” was the term used with the community plugin of that name. Obsidian’s native callouts replaced that plugin in version 0.14 and are built into core — no plugin needed.

Q: Will callouts slow down Obsidian in a large vault?

No meaningful impact has been documented for normal vault sizes (under 10,000 notes). CSS snippets are loaded once at startup and do not affect note-opening or search speed.