Obsidian Callout Syntax: Complete Guide to Notes, Warnings, and Foldable Blocks

Obsidian callout syntax uses a blockquote marker followed by [!type] to create highlighted content blocks, supporting optional titles, foldable states with + or - markers, and unlimited nesting.

The Obsidian callout syntax extends standard Markdown to create visually distinct content blocks for notes, warnings, and structured information. According to the kepano/obsidian-skills repository, this feature is implemented through a specific blockquote pattern defined in skills/obsidian-markdown/references/CALLOUTS.md and overviewed in skills/obsidian-markdown/SKILL.md, supporting multiple types, custom titles, and interactive folding.

Basic Callout Syntax Structure

Every Obsidian callout begins with a standard Markdown blockquote character (>) followed immediately by a callout marker in the format [!type].

The general pattern implemented in the source code is:

> [!type] optional‑title
> Callout content line 1
> Callout content line 2

• type — A supported callout identifier such as note, tip, warning, info, or faq as defined in skills/obsidian-markdown/references/CALLOUTS.md
• optional‑title — Custom text that replaces the default type label; omit to display the type name as the title
• Blockquote continuation — Every content line must start with >

For example, a basic note callout without a custom title:

> [!note]
> Remember to back up your vault daily.

A callout with a custom title:

> [!warning] ⚠️ Security Risk
> Do not share your vault password.

Foldable and Collapsible Callouts

You can make callouts foldable by appending a - or + to the callout marker, as documented in the reference files.

- collapses the callout by default (content hidden until expanded):

> [!faq]- Frequently Asked Question
> This content is hidden until the user expands it.

+ expands the callout by default (visible but can be collapsed):

> [!tip]+ Pro Tip
> This content is visible but can be collapsed.

Nested Callouts

The Obsidian callout syntax supports nesting by placing a child callout inside the blockquote of a parent callout.

> [!question] How do I embed images?
> > [!tip] Use the wiki-link syntax
> > Type `![[image.png]]` to embed.
> > > [!example] Resize inline
> > > Use `![[image.png|200]]` for 200px width.
> Continue outer callout content here.

Supported Callout Types

The file skills/obsidian-markdown/references/CALLOUTS.md defines the following supported types and their aliases:

• Abstract — aliases: summary, tldr (teal clipboard icon)
• Info — no aliases (blue info icon)
• Todo — no aliases (blue checkbox icon)
• Tip — aliases: hint, important (cyan flame icon)
• Success — aliases: check, done (green checkmark)
• Question — aliases: help, faq (yellow question mark)
• Warning — aliases: caution, attention (orange warning)
• Failure — aliases: fail, missing (red X)
• Danger — alias: error (red zap icon)
• Bug — no aliases (red bug icon)
• Example — no aliases (purple list icon)
• Quote — alias: cite (gray quote icon)

Example usage with aliases:

> [!tldr] Quick Summary
> This is an abstract callout using the TLDR alias.

> [!attention] Security Notice
> This renders as a warning callout.

Custom Callout CSS

For callout types not included in the default set, the repository documents CSS-based custom callouts in skills/obsidian-markdown/references/CALLOUTS.md.

Add this to your vault's CSS snippet:

.callout[data-callout="alert"] {
  --callout-color: 255, 0, 0;
  --callout-icon: lucide-alert-circle;
}

Then use the custom type in your Markdown:

> [!alert] Critical Update Required
> This is a custom-styled callout with red coloring.

Summary

• Obsidian callout syntax requires a blockquote (>) followed by [!type] where type is a supported identifier like note, warning, or tip
• Optional titles replace the default type label when placed after the closing bracket
• Foldable states are controlled by appending - (collapsed) or + (expanded) to the marker
• Nesting is achieved by placing additional > [!type] lines within parent callouts
• File references: Complete type definitions are in skills/obsidian-markdown/references/CALLOUTS.md and overview documentation is in skills/obsidian-markdown/SKILL.md within the kepano/obsidian-skills repository

Frequently Asked Questions

What is the exact Obsidian callout syntax for a basic note?

The exact syntax requires starting a line with > [!note] followed by your content on subsequent lines prefixed with >. For example: > [!note] on its own creates a callout with the default "Note" title, while > [!note] Custom Title creates one with your specified title displayed in the header.

How do I make a callout collapsible in Obsidian?

Append a minus sign (-) to collapse by default or a plus sign (+) to expand by default immediately after the closing bracket of the callout marker. Use > [!warning]- Hidden Content for collapsed state or > [!tip]+ Visible Content for expanded state.

Can I nest multiple callouts inside each other?

Yes, nested callouts are supported by simply adding additional blockquote markers and callout syntax inside the parent callout's content area. Each nested level requires its own > prefix, such as > > [!note] for a second-level callout inside a parent > [!question] block.

Where is the complete list of Obsidian callout types documented?

The complete authoritative list of callout types, aliases, icons, and color codes is documented in the skills/obsidian-markdown/references/CALLOUTS.md file in the kepano/obsidian-skills repository on GitHub, with an overview available in skills/obsidian-markdown/SKILL.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}