Free tool · works now

Callout Portability Converter

Translate Obsidian and GitHub callouts into standard blockquotes, HTML disclosures, or portable headings.

Runs 100% in your browser. Paste Markdown containing Obsidian or GitHub callouts to convert them into universally portable blockquotes, collapsible HTML disclosures, or normalized alerts.

5Callouts detected
5Unique types
1Collapsible callouts
1Nested callouts
Detected 1 collapsible callout(s). In standard blockquotes, foldability (+/-) is represented as static emphasized text.
Input Markdown with calloutsEditable
Portable converted outputConverted

Callout detection audit ledger

Overview of callout types, titles, and structural nesting found
TypeFold stateNesting levelCustom titleClassification
[!NOTE]StaticTop-levelCore Architectural PrincipleStandard
[!WARNING]Collapsed (-)Top-levelDeprecated Cloud FallbacksStandard
[!IMPORTANT]StaticTop-levelRecovery StrategiesStandard
[!CAUTION]StaticNested (2x)Critical Recovery ActionStandard
[!TIP]StaticTop-levelPerformance RecommendationStandard

The challenge of callout portability in modern Markdown

Callouts have become an essential typographic element in modern knowledge bases and technical documentation. Originally popularized in documentation engines and Obsidian, callout blocks allow authors to highlight critical warnings, helpful tips, and parenthetical clarifications inside notes.

However, callout syntax remains an extension rather than a core CommonMark standard. While Obsidian and GitHub recognize > [!NOTE], many traditional Markdown processors—including static site generators, email authoring tools, and document conversion pipelines—display the raw syntax literally as > [!NOTE], breaking the intended visual hierarchy.

The Callout Portability Converter solves this fragmentation. It translates proprietary callout syntax into universally supported standard formats: emphasized blockquotes for maximum compatibility, HTML details elements for interactive disclosure, or standardized GFM alert blocks for repository documentation.

Comparing export targets for different publishing workflows

Depending on your destination platform, different export formats offer specific advantages:

  • Standard Blockquote (Recommended for universal notes): Converts callouts into > **Note: Title** followed by the indented body. This format renders cleanly across 100% of Markdown editors, mobile apps, terminal viewers, and documentation sites without requiring custom plugins or themes.
  • HTML Details Disclosures: Converts callouts into semantic <details><summary> elements. This is ideal for static site generators (such as Astro, Hugo, Jekyll, or MkDocs) where you want readers to be able to collapse or expand callouts interactively in the web browser.
  • Section Headings: Transforms callout boxes into standard Markdown headings (e.g., ### Note: Title) followed by plain body text. This is beneficial when compiling long documents into PDF or Word format, where nested blockquotes create unwanted indentation.
  • GitHub Alerts Normalization: Normalizes non-standard aliases (such as [!INFO] or [!BUG]) into GitHub's five officially supported alert types (NOTE, TIP, IMPORTANT, WARNING, CAUTION) and removes Obsidian-specific fold markers.

Code block protection and syntax preservation

Technical documentation frequently contains instructions explaining how to write callouts. Naive search-and-replace scripts inadvertently mangle these code examples, corrupting tutorials and code snippets.

Our parsing engine isolates code fences and inline backticks before performing transformations. Any callout examples contained within triple backtick blocks (```) or inline backtick spans (`...`) remain completely untouched and are restored with byte-for-byte fidelity upon export.

Private browser-local processing

Proprietary documentation and personal knowledge vaults often contain confidential information. This converter operates entirely within your local browser session using standard string processing algorithms. No document text, headings, or callout contents are ever uploaded to any server or external API.

For additional note-formatting utilities, explore our related tools: create Obsidian-style callouts with the Obsidian callout builder, convert note link syntax with the Wikilink to Markdown converter, renumber footnote citations with the Footnote renumbering assistant, or inspect note health with the vault health inspector. Browse the complete suite in our browser tools catalog.

Questions

What are Markdown callouts and how do different apps render them?

Callouts (also known as alerts or admonitions) are visually distinct breakout boxes designed to emphasize tips, warnings, or notes. Obsidian and GitHub recognize lines beginning with > [!TYPE] as styled banners. However, standard CommonMark, older Markdown parsers, email clients, and static site generators treat them as raw blockquote text with literal bracket syntax.

Why should I convert Obsidian callouts to standard blockquotes or HTML?

When sharing Markdown files with colleagues who use plain text editors, exporting to static document sites, or sending notes to publishing pipelines, proprietary callout syntax renders as broken raw markers (> [!NOTE]). Converting to standard bold blockquotes or HTML details disclosures ensures complete visual fidelity across all Markdown viewers.

How does the converter handle collapsible callouts (+ and -)?

Obsidian supports collapsible callouts using plus (> [!NOTE]+) for open and minus (> [!NOTE]-) for folded states. When exporting to HTML details, the converter maps these to <details open> and <details> respectively. When converting to standard blockquotes, fold markers are cleanly omitted while preserving the text.

Are code blocks and inline backticks protected during conversion?

Yes. Before evaluating callout markers, the parser shields all fenced code blocks (``` and ~~~) and inline code spans (`...`) using cryptographic placeholder tokens. Any example callout syntax inside programming tutorials or configuration files is restored byte-for-byte upon output.

Does this tool upload my notes or document data over the network?

No. The entire callout transformation engine executes locally in your browser session. No text, outlines, or metadata are ever transmitted to any remote server or third-party service.

Want notes that remain portable everywhere?

Full Obsidian vault compatibility, clean Markdown on disk, and private on-device meeting recording in Oyma.

tools callout portability converter downloadDownload for Mac

No account needed. Intel Mac build