Skip to content
100% local

Markdown callout converter

Convert callout and admonition blocks between GitHub, Obsidian, Docusaurus and MkDocs syntax.

Input
Output

Markdown callout converter

Callout blocks—the boxed "Note", "Tip" or "Warning" asides in READMEs and documentation sites—are written differently by every platform. GitHub uses blockquote alerts like `> [!NOTE]`, Obsidian extends that syntax with custom titles and foldable arrows, Docusaurus wraps content in `:::tip` fences, and MkDocs (and Material for MkDocs) uses indented `!!! note` blocks with `???` for collapsible ones. Moving documentation between tools usually means rewriting every callout by hand—this tool converts them automatically.

Pick a source and target notation from the option panel, then paste content written in the source format. Every recognized callout is parsed and rewritten in the target syntax; anything else in the input—paragraphs, headings, other Markdown—passes through unchanged. "Keep custom block title" preserves a heading like Obsidian's `> [!info] Heads up` when the target supports one (GitHub has no title syntax, so a kept title becomes a bold first line instead). "Keep foldable/collapsible state" preserves Obsidian's `+`/`-` fold markers and MkDocs's `???`/`???+` syntax where the target has an equivalent; GitHub and Docusaurus have no collapsible callouts, so the toggle has no effect there. "Normalize block type" maps less common names (important, caution, success, question…) onto the five types every format shares: note, tip, warning, danger and info.

The body of each callout is preserved exactly as written, including nested lists, inline formatting, links and fenced code blocks—those are just ordinary lines inside the block. Multiple callouts in one document convert in a single pass, and Windows and Unix line endings are handled the same way.

Everything runs locally in your browser; your documentation is never uploaded anywhere. Copy the result, download it as a .txt file, or send the output back into the input to chain another conversion.

FAQ

Which callout types does it recognize?
Any type name in the source syntax—note, tip, warning, danger, info and platform-specific ones like important or faq. Turn on "Normalize block type" to map the less common ones onto the five types every format shares.
What happens to a custom title when the target format has none?
GitHub alerts have no title syntax, so a kept title is added as a bold first line inside the block instead of being dropped.
Are collapsible callouts supported?
Yes, between Obsidian ("+"/"-" after the type) and MkDocs ("???"/"???+"). GitHub and Docusaurus have no collapsible syntax, so the state is dropped when converting to either.
Will lists and code blocks inside a callout survive the conversion?
Yes. Everything inside a callout body is carried over as-is—nested lists, inline formatting and fenced code blocks included.
Is my document uploaded anywhere?
No. The conversion runs entirely in your browser—your text never leaves your device.