Callout Studio
approvedby niv20
Callout Studio is the only callout plugin you'll ever need to download. It offers regular callouts, inline callouts, and callout headings. Plus, you can easily design your own custom styles! - This plugin has not been manually reviewed by Obsidian staff.
Callout Studio
Callout Studio is a powerful callout management plugin for Obsidian.
It lets you create, edit, and style your own callout types, override the built-in ones, pick icons from large libraries, and use every callout as a Block Callout, a Heading Callout, or an Inline Callout - all from a single settings tab!
The syntax
The same callout type can be written three ways:
| Type | Default content | Custom content |
|---|---|---|
| Heading | ## [!note] | ## [!note] A custom heading title |
| Inline | [!note] | [!note]{A custom inline title} |
| Block | > [!note] | > [!note] A custom block title |
Unlock the full potential of Callout Studio! Explore the User Guide to discover advanced features like custom color palettes, icon management, global styling, context menus, vault discovery, themes, and more.
💖 Special Thanks
A huge thank you to everyone who took the time to report bugs, identify issues, and help make Callout Studio more stable and reliable. Your reports, testing, and detailed feedback have been incredibly helpful:
brianjwalton · astreloff · rubcap · Xto-tT0 · Jarsgon · Ravencaller213 · frudolph77 · DesertSnak3 · alythobani · dragonish · Ana-Mendes123 · EddyCurrrent · Indra-Reaper · hisbo
And a huge thank you to everyone who shared ideas, suggested enhancements, and helped shape the direction of Callout Studio. Many of the features and improvements in the plugin have been inspired by your feedback and suggestions:
ericxob77 · TechnoMaverick · epilo9er · Xto-tT0 · TyceHerrman · eth-p · kwhsiung · archangelglass · quantumstargazer · BloatedBlowfish · Camouflagee
Thank you all for helping make Callout Studio better!
Privacy, in short
A device-local recovery copy protects plugin settings when a synced data.json is replaced while the plugin is closed. Concurrent edits and recognized conflict copies are merged automatically when valid; damaged or unsupported data is kept for recovery. Install the same updated build on every device. See multi-device editing and recovery.
Callout Studio never sends vault content anywhere, and collects no telemetry or analytics. The only things it ever downloads are icon artwork you actually pick and, when needed, the plugin's own UI translation — both explained in full, with exactly what's stored where, in Privacy & permissions.
Install
Community plugins (recommended)
- Open Settings → Community plugins in Obsidian.
- Search for Callout Studio and select Install, then Enable.
Manual install
- Download
manifest.json,main.js, andstyles.cssfrom the latest GitHub release. - Copy them into
<Vault>/.obsidian/plugins/callout-studio/. - Restart Obsidian and enable Callout Studio in Settings → Community plugins.
Development
npm install
npm run dev # watch build
npm run build # production build (typecheck + minified bundle)
npm run lint # ESLint with the official obsidianmd plugin rules
Source lives under src/ and is bundled by esbuild into main.js. The release artifacts are main.js, manifest.json, and styles.css.
Digging into how it's built, or preparing a pull request? See docs/internals-docs/ for the architecture, and CONTRIBUTING.md for the process.
Plugin API
Callout Studio exposes a small read-only API so other plugins can list the user's callout types and react when that list changes. See API.md.
License & Third-Party Assets
Callout Studio's code is available under a permissive license — use it however you like, no attribution required. There is one informal ask, and it is not a license term: please don't repackage this code and publish it as a new plugin in Obsidian's Community Plugins directory. Reuse it, learn from it, build on it — just not that.
The icon libraries offered within the plugin are separate works and retain their own licenses. You can view the full text for each in THIRD-PARTY-NOTICES.md or directly through the plugin via Settings → Icon licences and credits.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.