How to convert Obsidian Markdown to standard Markdown
Translate Obsidian-flavored notes — wikilinks, embeds, and callouts — into standard Markdown so they render correctly on GitHub, blogs, and other tools.
Obsidian is a wonderful place to write, but its Markdown has dialect: [[wikilinks]], ![[embeds]], and > [!note] callouts that other tools don't understand. The Obsidian Markdown Converter translates those into standard Markdown so your notes travel.
What's Obsidian-specific
A few constructs are Obsidian (and wiki) flavor, not standard Markdown:
- Wikilinks —
[[Page Name]]instead of[Page Name](page-name.md). - Embeds —
![[image.png]]or![[Other Note]]to transclude content. - Callouts —
> [!note],> [!warning]blocks with a special header.
Paste these into GitHub or a static-site generator and they render as literal text. The converter rewrites them into the standard equivalents.
What it does
[[wikilinks]]→[text](link)standard links, so they work outside your vault.- Callouts → blockquotes (or GitHub-style alerts where supported), keeping the emphasis.
- Embeds → standard image/link syntax, so images display and references become real links.
Why convert
- Publishing. Move a note from your vault to a blog, a docs site, or a README and have it render correctly.
- Sharing. Send a note to someone who doesn't use Obsidian.
- Portability. Keep your knowledge in a format that isn't tied to one app.
The other direction
Bringing standard Markdown into Obsidian usually just works, since Obsidian reads plain Markdown fine — the friction is almost always on the way out, which is what this tool smooths.
Privacy
Conversion runs in your browser — your notes, which are often personal, never leave your machine.
Write in Obsidian, convert on the way out, and publish notes that render anywhere.