New in Obsidian: Obsidian Callouts (available now!)
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.
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?
How does Callouts syntax differ from the older Admonition approach?
What callout types are available, and how are they used in practice?
What does collapsing a callout change, and how is it controlled?
Why is native Callouts support on Obsidian Publish a big deal?
What compatibility and parsing benefits come from using blockquotes?
Review Questions
- What specific syntax change distinguishes Obsidian Callouts from Admonition, and why does that matter for rendering?
- Give two examples of callout types and describe what kind of information each is best for.
- How do collapsing-by-default callouts improve skimming, and what mechanism controls that behavior?
Key Points
- 1
Obsidian Callouts move admonition-style boxes into core, so they work without installing or enabling a plugin.
- 2
Callouts use blockquote-based syntax (not fenced code blocks), with a type, title, and content structure.
- 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
Native Callouts render correctly on Obsidian Publish without CSS hacks, keeping public notes consistent.
- 5
Blockquote rendering improves compatibility in unsupported Markdown environments and allows Markdown inside callouts (links, embeds, Dataview queries) to be parsed and spellchecked.
- 6
Admonition remains usable and can convert existing admonition blocks to callouts, but Callouts are the recommended default for new writing.