Markdown Alert Converter

How to use

1. 1Pick Single block to convert one alert, or Whole document to rewrite every alert in a Markdown file at once.
2. 2Choose the target flavor (GitHub, Obsidian, MkDocs, Docusaurus, or Hugo) from the dropdown in the top right.
3. 3Paste the source alert or document into the input. The source flavor is detected automatically and shown above the outputs.
4. 4In single mode, copy the converted output for any of the five flavors from the side-by-side panels. The card matching your target is highlighted.
5. 5Optionally edit the parsed type, title, or foldable state in the builder under the input to fine-tune every output at once.
6. 6In document mode, review the detection summary to see how many alerts of each flavor were found, then copy the converted file from the output panel.

About this tool

Markdown Alert Converter rewrites note, tip, info, warning, important, caution, and danger blocks between the five major Markdown alert dialects so the same idea reads correctly on every platform you publish to. GitHub Flavored Markdown introduced its `> [!NOTE]` alert blocks in 2023 with five fixed types (Note, Tip, Important, Warning, Caution). Obsidian callouts use the same quote syntax but expand the vocabulary to dozens of types (info, success, question, abstract, example, quote, bug, failure, and more) and add an optional title plus a `+` or `-` foldable indicator. MkDocs and Material for MkDocs use `!!! note "Title"` admonitions with four-space indented bodies, plus collapsible `???` and `???+` variants. Docusaurus and Astro Starlight wrap admonitions between `:::note[Title]` and `:::`. Hugo and the Doks / Hextra / Geekdoc themes use a `{{< callout type="note" title="Heads up" >}}` shortcode. This tool parses every flavor into a single normalized model (type, title, foldable, body) and re-emits the block in any target dialect side by side. The single-block mode is great for converting one example you pasted from a tutorial. The whole-document mode scans an entire Markdown file, leaves fenced code blocks untouched, and rewrites every alert in place, including a per-flavor detection count so you can verify the source was parsed correctly. When the target flavor lacks an exact equivalent for a type, the closest semantic neighbor is used: GitHub falls back to Note for Info and Question, mkdocs-material collapses Important into Warning, and Docusaurus collapses Bug into Danger. Useful for moving a README between GitHub and a Docusaurus site, porting Obsidian vault notes to MkDocs, copying examples from Hugo themes into a Discord-flavored chat, and any documentation refactor where the alert syntax differs between the source and the destination. Everything runs locally in your browser. The blocks and documents you paste are never uploaded.

Free to use. Works in your browser. No signup, no login.