The Obsidian Callout Ecosystem

graph TD
    A[Obsidian Callouts] --> B[Informational]
    A --> C[Action & Success]
    A --> D[Warning & Danger]
    A --> E[Queries & References]
    B --> F(note, info, abstract)
    C --> G(success, check, todo)
    D --> H(warning, danger, bug)
    E --> I(question, quote, example)

Callouts are the primary mechanism for breaking up monolithic walls of text in Obsidian. They leverage the standard Markdown blockquote syntax (>) but inject CSS-driven background colors, distinct margins, and SVG icons based on a specific keyword bracketed at the very top. This creates an immediate visual hierarchy within the note.

By categorizing information into distinct visual buckets—like making critical errors red and foundational theories blue—the cognitive load of scanning a dense document is drastically reduced. You are no longer just formatting text; you are designing a user interface for your future self. The parser reads the [!keyword], maps it to a predefined CSS class, and renders the stylized box dynamically.

Native Callout Keywords

Obsidian supports a robust library of native callouts. Any of the keywords below can be placed inside the brackets (e.g., > [!warning]) to trigger the corresponding style.

Advanced Callout Engineering

Folding Mechanics (Collapsibility)
You can turn any callout into an accordion menu by appending a - or + directly after the closing bracket.

• Use > [!info]- to make the callout closed by default. This is highly effective for burying dense reference data, raw code blocks, or answer keys that you only want to see on demand.
• Use > [!info]+ to make it open by default but still collapsible.

Title Overrides
By default, the callout's title matches the capitalized keyword (e.g., > [!bug] outputs a box titled "Bug"). You can overwrite this by typing directly after the brackets.
Example: > [!bug] The Rendering Issue replaces the default title with your exact text, while keeping the red color and bug icon.

Deep Nesting
Because callouts are built on blockquotes, they can be nested infinitely by stacking the > prefix.

> [!note] Parent Container
> This is the main theory.
>> [!example]- Nested Example
>> Here is the hidden practical application.

Self-Test: Checking Your Grip

1. Syntax: What is the exact string of characters required to create a red "danger" callout that is folded/closed by default and titled "Critical System Failure"?
2. Logic: Why would you use a [!quote] callout instead of a standard Markdown blockquote (> Text)?
3. Application: If you are drafting a long technical tutorial, which callout type is best suited for the "TL;DR" at the very beginning of the document?

Answers: 1. > [!danger]- Critical System Failure; 2. The callout provides a distinct icon, an explicit title bar, and a dedicated background color, whereas a standard blockquote is usually just an indented line with a left border; 3. [!abstract] or [!summary].

Showcase