Get AI summaries of any video or article — Sign up free
New in Obsidian: Obsidian Callouts (available now!) thumbnail

New in Obsidian: Obsidian Callouts (available now!)

Nicole van der Hoeven·
5 min read

Based on Nicole van der Hoeven's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Obsidian Callouts move admonition-style boxes into core, so they work without installing or enabling a plugin.

Briefing

Obsidian is rolling out “Callouts” as built-in functionality, bringing the familiar “admonition-style” note boxes into core so they work out of the box—without installing or enabling a plugin—and render correctly on Obsidian Publish. The practical payoff is better skimmability: callout boxes visually flag what matters (or what applies only in certain situations), while still letting the rest of a note read normally.

Before Callouts landed, many users relied on the Admonition plugin, which used a code-block-like syntax (three backticks) to create labeled boxes such as reminders, tips, and warnings. With live preview, those blocks become visually distinct, and—crucially—can be collapsed by default so readers can scan quickly and expand only when needed. In Nicole van der Hoeven’s examples, callouts act like “meta notes” for technical documentation: troubleshooting steps hidden until an error occurs (e.g., “g not found” after installing the Go package manager “g”), platform-specific instructions for tutorials (Mac vs. Windows), and even conditional story elements in D&D sessions that need to appear only when players choose certain paths.

Callouts change the syntax and move the feature into core Obsidian. Instead of fenced code blocks, the new format uses blockquotes: a blockquote marker followed by brackets and an exclamation point, then a callout type (most commonly “note”), a title, and the content below it. Visually, the result includes an icon and styling that differentiates the callout from surrounding text. The feature also supports many callout types—abstract/summary/TLDR, info, todo, tips and hints, important, success, questions/FAQ, warnings/caution/attention, fail/missing, danger/error, bug, and even more specialized forms like quote and cite.

Beyond types, Callouts add folding behavior. A minus sign placed in the callout header collapses the box by default, while other settings can keep it expanded. Styling can vary by theme and can be customized via CSS, with the “Primary” theme highlighted as an example. A major workflow win is that Callouts now render natively on Obsidian Publish, so public notes keep the same callout appearance without extra CSS hacks that previously helped plugin-based admonitions.

The shift from Admonition to Callouts isn’t just cosmetic. Using blockquotes improves compatibility with Markdown renderers that don’t support the older syntax: unsupported environments will still show a blockquote rather than a misleading code block. It also means Markdown inside callouts—links, embeds, and even Dataview queries—gets parsed, and spellcheck can operate normally (code blocks often suppress spellchecking).

Admonition remains available and continues to support its original syntax, but it also adds conversion tools to migrate existing admonition blocks into callouts. It further offers quality-of-life controls like drop shadows, collapsibility defaults, copy buttons, and icon customization using Font Awesome (plus additional icon sets like Octicons and RPG-Awesome). Even so, Callouts are positioned as the forward path for new work, while Admonition can still be worth installing for deeper customization needs and for users who want the plugin’s extra features. At the time of recording, Callouts are available in Insider Build version 0.14, with public rollout expected later.

Cornell Notes

Obsidian’s built-in “Callouts” bring admonition-style note boxes into core, improving how technical notes and tutorials get skimmed. The new syntax uses blockquotes (not fenced code blocks), supports many callout types (note, TLDR, todo, warning, bug, and more), and can be collapsed by default. Because Callouts are native, they render correctly on Obsidian Publish without extra CSS workarounds. Blockquote-based rendering also degrades gracefully in Markdown environments that don’t fully support the older syntax, while still parsing Markdown inside the callout (links, embeds, Dataview queries) and enabling spellcheck. Admonition still works and can convert older admonition blocks to callouts, but Callouts are the recommended default going forward.

Why do callouts matter for technical writing and learning notes in Obsidian?

Callouts make notes more skimmable by visually separating “important or conditional” information from the surrounding text. They function like “meta notes” (notes about notes): troubleshooting steps can stay hidden until relevant, platform-specific instructions can stand out, and conditional tutorial or game information can appear only when needed. Collapsing by default supports fast scanning—readers can expand only the sections that match their situation.

How does Callouts syntax differ from the older Admonition approach?

Admonition used fenced code-block-style syntax (three backticks) with an admonition keyword, title, and content. Callouts instead use blockquotes: a blockquote marker followed by brackets and an exclamation point, then a callout type (like “note”), a title outside the brackets, and the content below. The visual styling (icon + highlighted box) comes from the callout type and theme.

What callout types are available, and how are they used in practice?

Callout types include note (standard), abstract/summary/TLDR, info, todo, tips/hint/tip, important, success/check/done, questions/help/FAQ, warning/caution/attention, fail/failure/missing, danger/error, bug, and quote/cite. In practice, “warning” or “attention” fits gotchas and programming errors, “todo” fits action items, “info” can represent “box text” read word-for-word in D&D, and “bug” helps document issues.

What does collapsing a callout change, and how is it controlled?

Collapsing determines whether a callout starts minimized or expanded. In Callouts, adding a minus sign in the callout header (right outside the type’s parentheses) makes it minimized by default; readers can click to expand and view the hidden content. Admonition also offers settings to control default collapsibility, but Callouts provide a simple per-callout mechanism.

Why is native Callouts support on Obsidian Publish a big deal?

Previously, admonition-style blocks often didn’t render correctly on Obsidian Publish because they were plugin-based. With Callouts in core, notes using the callout syntax display the same way on public publish pages “out of the box,” eliminating the need for CSS workarounds. This makes public documentation consistent with private vault notes.

What compatibility and parsing benefits come from using blockquotes?

Blockquote-based callouts fall back to standard blockquote rendering in Markdown renderers that don’t support the newer syntax, avoiding confusing code-block appearance. Because callouts are blockquotes, Markdown inside them is parsed—links and embeds work, and Dataview queries can run. Spellcheck also treats the content as normal text rather than code-block text, improving editing quality.

Review Questions

  1. What specific syntax change distinguishes Obsidian Callouts from Admonition, and why does that matter for rendering?
  2. Give two examples of callout types and describe what kind of information each is best for.
  3. How do collapsing-by-default callouts improve skimming, and what mechanism controls that behavior?

Key Points

  1. 1

    Obsidian Callouts move admonition-style boxes into core, so they work without installing or enabling a plugin.

  2. 2

    Callouts use blockquote-based syntax (not fenced code blocks), with a type, title, and content structure.

  3. 3

    Callouts support many types (note, TLDR, todo, warning, bug, and more) and can be collapsed by default using a minus sign in the header.

  4. 4

    Native Callouts render correctly on Obsidian Publish without CSS hacks, keeping public notes consistent.

  5. 5

    Blockquote rendering improves compatibility in unsupported Markdown environments and allows Markdown inside callouts (links, embeds, Dataview queries) to be parsed and spellchecked.

  6. 6

    Admonition remains usable and can convert existing admonition blocks to callouts, but Callouts are the recommended default for new writing.

Highlights

Callouts are built into core Obsidian, eliminating the plugin dependency that previously limited how admonition-style notes appeared on Obsidian Publish.
Using blockquotes makes callouts degrade gracefully: unsupported renderers show a normal blockquote instead of a misleading code block.
Callouts parse Markdown inside the box (including links, embeds, and Dataview queries) and allow spellcheck to work normally.
Admonition still offers deeper customization—icons, copy buttons, shadows, and conversions—but Callouts are positioned as the forward standard.

Topics

  • Obsidian Callouts
  • Admonition Migration
  • Markdown Rendering
  • Obsidian Publish
  • Skimmable Documentation