Obsidian ↔ Markdown Converter

Obsidian stores plain .md files, but four pieces of its syntax break everywhere else: [[wikilinks]], ![[embeds]], > [!note] callouts, and ==highlights==. This browser-only converter rewrites them into portable GFM — inline links ending in .md, GitHub alert syntax for the five alert types GitHub renders, and <mark> for highlights — then removes %%comments%% and ^block-ids. YAML frontmatter and inline #tags each have a keep-or-strip option. The reverse direction turns local .md links back into wikilinks and <mark> back into ==highlights==. Code fences and inline code are never rewritten.

Direction:Obsidian → standard MarkdownStandard Markdown → Obsidian

YAML frontmatter:Inline #tags:

Obsidian note

Standard / GFM Markdown

What the converter changes

[[Note]] and [[Note|alias]] become [alias](Note.md). Spaces in the target are percent-encoded.
![[image.png]] becomes ![](image.png). An Obsidian size hint such as |300 is dropped, because Markdown has no equivalent.
Callouts become GitHub alert syntax — > [!note] → > [!NOTE] — for the five types GitHub renders (note, tip, important, warning, caution). Every other callout type becomes a plain blockquote with a bold label, which renders anywhere.
==highlight== becomes <mark>highlight</mark>. Renderers that block raw HTML will show the text without the highlight.
%%comments%% and ^block-ids are removed. Frontmatter and inline #tags follow the options above.
Text inside fenced or inline code is never rewritten. Dataview queries and other plugin blocks pass through unchanged — they have no Markdown equivalent.

The reverse direction rewrites links only when the target looks like a local note (a relative path ending in .md). URLs, mailto links, and same-page anchors stay as standard Markdown.

Obsidian export guides

Exact answers for taking notes out of a vault: wikilinks, callouts, frontmatter, tags, and publishing a vault to GitHub.

Wikilinks to MarkdownObsidian writes links as [[Note]] and [[Note|alias]]. Only Obsidian reads that syntax. Convert each one to [alias](Note.md) so the link works on GitHub and any other renderer.Callouts to GitHub AlertsObsidian callouts use > [!note] Title. GitHub supports five alert types with uppercase names and no inline title. Here is the mapping the converter applies.Obsidian to GitHubA vault file copied straight into a repository shows literal wikilinks, unrendered callouts, and ==highlight== markers. Convert the Obsidian syntax first, then commit.Frontmatter and TagsYAML frontmatter drives properties in Obsidian and drives nothing on GitHub. Inline #tags are vault navigation. Decide per destination, then keep or strip both with one option each.Vault to Portable MarkdownPortable Markdown is text that renders the same in every reader. This is the list of Obsidian-only syntax that stops a note being portable, and what each piece becomes.

Was this rewrite usable?

Get new tools by email

We add tools most weeks. Give an email address and we send you the new ones, plus short notes on how to use them. No more than one email a week. Unsubscribe with one click.

Related Tools

Markdown Editor

Free online Markdown editor with live preview. Write and preview Markdown in real-time with GitHub Flavored Markdown support.

WYSIWYG Markdown Editor

Rich text WYSIWYG editor that outputs clean Markdown. Free online visual Markdown editor.

Markdown to HTML

Convert Markdown to clean HTML code instantly. Free online Markdown to HTML converter with copy and download options.

HTML to Markdown

Convert HTML to clean Markdown instantly. Free online HTML to Markdown converter. Paste HTML and get Markdown output.

About Obsidian ↔ Markdown Converter

Convert Obsidian notes to standard GFM Markdown — wikilinks, embeds, callouts, highlights, tags, and frontmatter — or convert standard Markdown back to Obsidian syntax. This tool runs entirely in your browser, so your content is not sent to a server. MarkdownMe provides free, fast, and reliable Markdown tools for developers, writers, and anyone who works with Markdown.