Obsidian Callouts: All 13 Types, Folding and Custom CSS

November 11, 2026 · 10 min read

Obsidian Callouts: All 13 Types, Folding, Nesting and Custom CSS

Obsidian callouts are blockquotes whose first line starts with a type in brackets, such as > [!tip]. Obsidian turns that quote into a coloured box with an icon and a title. This reference lists all 13 built-in types and their aliases, then covers folding, nesting, custom CSS types and what happens outside Obsidian.

How Obsidian Callout Syntax Turns a Blockquote Into a Box

An Obsidian callout is an ordinary Markdown blockquote with one extra token. Put [!type] at the very start of the first quoted line, and every following > line becomes the body. Any text after the bracket on that first line replaces the default title.

> [!info] Server migration window
> The API is read-only from 02:00 to 03:00 UTC.
> Details live in [[Ops runbook]].

Obsidian renders a box titled "Server migration window" with the info icon, and the body below it. Without the custom title, the box would just say "Info", because the default title is the type name in title case. Drop the body lines and you get a title-only callout, which works well as a one-line banner.

Two parsing details save you debugging time:

  • The type identifier is case-insensitive, so [!TIP], [!Tip] and [!tip] look identical.
  • The body takes regular Markdown, wikilinks and embeds, so everything in our Obsidian Markdown cheat sheet works inside it.

You rarely need to type Obsidian callouts by hand, though. The app has two helpers:

  • The Insert callout command (open the command palette and search for it) adds a default [!note] and puts your cursor in the type name. Select some text first and the command wraps it, lists and code blocks included. You can bind it to a key under Settings, Hotkeys.
  • In Live Preview, right-click a callout's name to switch its type from a menu.

What Are All the Obsidian Callout Types?

Obsidian ships 13 callout types. Eight of them have aliases, alternate names that look like the parent type by default. Your theme decides the exact colours, so the table sticks to names and sensible uses.

TypeAliasesA good fit for
notenoneNeutral context or a side remark
abstractsummary, tldrA summary at the top of a long note
infononeBackground facts and definitions
todononeOpen items you still need to act on
tiphint, importantShortcuts and better ways to do something
successcheck, doneConfirmed results, finished steps
questionhelp, faqOpen questions or self-quiz prompts
warningcaution, attentionGotchas that cost time if ignored
failurefail, missingThings that broke or don't exist
dangererrorData loss or anything irreversible
bugnoneKnown defects and workarounds
examplenoneWorked examples and sample output
quoteciteQuotations and source excerpts

The list of Obsidian callout types isn't closed. Any identifier Obsidian doesn't know, such as [!recipe], still renders as a callout in the note style until you give it its own CSS. When you invent a type, keep it to one lowercase word or a hyphenated name like recipe-card, because that's the exact string your CSS selector has to match.

How Do You Make a Collapsible Callout in Obsidian?

Any of the Obsidian callouts can fold. Add a + or - directly after the closing bracket. A plus makes the callout foldable and open by default. A minus makes it foldable and closed by default. With neither sign, the callout can't be folded at all.

> [!question]- What does HTTP 409 mean?
> Conflict. The request clashes with the current state of the resource,
> for example a duplicate slug.

> [!example]+ Sample response
> The body includes an error code and a suggested fix.

The first box shows only its title row until you click it, which turns any note into a quiz deck. The second starts open but collapses on click. Always give a folded callout a title, because the title is all a reader sees while it's closed.

Nesting Callouts and Putting Embeds, Code and Tasks Inside

Add another > to start a callout inside a callout. You can go several levels deep and mix types freely.

> [!todo] Release checklist
> - [ ] Tag the build
> - [ ] Update the changelog
>
> > [!warning] Before you tag
> > Run the migration script first:
> >
> > ```bash
> > npm run migrate
> > ```
>
> ![[Release notes#Known issues]]

Obsidian draws a todo box with two working checkboxes. Inside it sits a warning box holding a highlighted code block, and the "Known issues" section of the Release notes note is embedded at the bottom. Two details trip people up. Every line of the fenced code block keeps its > > prefix, fences included. And a blank line inside a callout still needs its >, or the callout ends there.

Embeds work the same way as anywhere else in your vault: a whole note, one heading, a block reference or an image.

What about a callout inside a bullet list? Obsidian's help page doesn't cover callouts indented under a list item. If you try it, check the result in both Reading view and Live Preview before you build a template around it. Our review of Obsidian's editor explains how those two modes differ.

How Do You Create a Custom Callout Type With a CSS Snippet?

A custom type is a few lines of CSS. Obsidian callouts all carry a data-callout attribute holding their type, so a CSS snippet can give any identifier its own colour and icon.

  1. Open Settings, then Appearance, and under CSS snippets select Open snippets folder. By default, the folder is .obsidian/snippets inside your vault.
  2. Create a file such as callouts.css and paste the snippet below.
  3. Back in Appearance, select Reload snippets and switch the new snippet on.

On a phone or tablet, the help docs have you use a file manager instead. Open your vault's .obsidian folder, create snippets if it's missing, add the file, then reload and enable it in Appearance. Edits to an enabled snippet apply as soon as you save, with no restart.

.callout[data-callout="recipe"] {
  --callout-color: #c2410c;
  --callout-icon: lucide-chef-hat;
}

Now > [!recipe] Weeknight dal renders as an orange box with a chef's hat icon. The icon value is any icon name from Lucide with a lucide- prefix. Obsidian bundles a specific Lucide release, so a very new icon may not show up yet. You can also pass an SVG string instead, written as --callout-icon: '<svg>...</svg>';.

One version detail matters here. Since Obsidian 1.13, --callout-color takes any valid CSS colour. Older versions expect a bare RGB triplet such as 194, 65, 12, and that's what most snippets on forums still use. If your colour is ignored, check which format your version wants.

To restyle a built-in type, target its identifier the same way. The attribute holds the identifier you typed, so [data-callout="warning"] doesn't touch [!caution]. Add a selector for each alias you use. To restyle callouts in one note only, give that note a class through cssclasses, which our Obsidian front matter guide covers.

Hiding the icon or the title

Callouts expose child elements you can hide per type. This removes the icon from aside callouts and hides the whole title row on plain callouts:

.callout[data-callout="aside"] .callout-icon {
  display: none;
}
.callout[data-callout="plain"] .callout-title {
  display: none;
}

Borders, padding, radius and title size all have their own variables, such as --callout-border-width and --callout-title-color. The full set is in Obsidian's callout CSS variable reference.

Callout Metadata: Text After a Pipe in the Type

Anything you write after a | inside the brackets becomes metadata. Since version 0.14.3, Obsidian copies it into the HTML as a data-callout-metadata attribute. On its own it changes nothing visible. It only matters when a snippet or theme reads it.

> [!info|wide] Quarterly numbers
> This box can be widened by a snippet that targets the wide flag.
.callout[data-callout-metadata*="wide"] {
  margin-inline: -4rem;
}

The type stays info, with its normal colour and icon, and the snippet widens only the boxes flagged wide. Some community themes ship their own metadata flags, so check your theme's documentation before you invent names that might clash.

Do Obsidian Callouts Work on GitHub and Other Markdown Apps?

Partly. GitHub renders five alert types (NOTE, TIP, IMPORTANT, WARNING and CAUTION) using the same bracket syntax, and the GitHub Docs alerts section lists them. Our Markdown callout guide compares that syntax with MkDocs and others.

We ran the variants through GitHub's Markdown API. A bare > [!note] became a proper Note alert, in lowercase too. But > [!info], > [!tip]+ and > [!NOTE] Custom title all fell back to a plain blockquote showing the bracket text literally. Custom titles, fold signs and Obsidian-only types don't survive the trip. Note the alias mismatch as well: Obsidian lists important as an alias of tip and caution as an alias of warning, while GitHub gives each its own alert.

So if one note has to look right in both Obsidian and a GitHub README, stick to the five GitHub names, with no custom title and no fold sign.

Obsidian Publish renders callouts natively. Most other Markdown apps show a plain quote, and that includes our editor. Its preview doesn't render callouts, so > [!note] appears as an ordinary blockquote with the bracket line as text. When you want the syntax typed out for you, the Markdown callout generator builds the Obsidian version plus five other formats in your browser, ready to paste.

Picking a Callout Type for Notes You Reread

We prefer a small set of Obsidian callouts used consistently over all 13 types. Colour only carries meaning when it's rare, and a note with six different boxes reads like a warning label.

A set that covers most vaults: note for context, tip for shortcuts and warning for gotchas. Add a folded question for self-quizzing, quote for sources and todo for open items. Add a custom type only when you notice yourself writing the same kind of box every week.

Obsidian callouts give you 13 types, folding with a single character, nesting, and a CSS hook for anything else you need. Keep the full syntax inside Obsidian or Publish, and expect plain quotes almost everywhere else. Need the syntax for Obsidian, GitHub or MkDocs without memorising it? The callout generator writes it for you, and the Obsidian help page on callouts stays the canonical reference.