Obsidian to Markdown Converter (Wikilinks)
Convert Obsidian wikilinks and callouts to standard markdown, then export Obsidian notes to PDF or Word. Free wikilink converter, no signup.
--- title: Weekly review tags: [productivity, review] --- # Weekly review Linked notes: [Project Atlas](Project%20Atlas.md), [open risks](Project%20Atlas.md#risks) and [Meeting notes 2026-09-12](Meeting%20notes%202026-09-12.md). <img src="architecture.png" alt="" width="400"> > [!WARNING] > **Deadline moved** > The launch is now on **October 3**. Update the [Roadmap](Roadmap.md). > [!TIP] > Use <mark>highlights</mark> for anything the team must read. ## Next actions - [ ] Draft the release notes #writing - [x] Book the retro room #admin - Review `[[not a link]]` inside code stays as it is ```dataview LIST FROM #writing WHERE !completed ```
Export the converted note
- Wikilinks
- 4
- Embeds
- 1
- Callouts
- 2
- Highlights
- 1
- Tags
- 2
- Comments
- 1
Dataview blocks and inline code are left unchanged. Everything runs in your browser; only the PDF and Word exports send the text to the server.
What Are Wikilinks and Why Convert Them?
Wikilinks are Obsidian's double-bracket links, such as [[Project Atlas]] or [[Project Atlas#Risks|open risks]], that connect notes inside a vault by name rather than by file path. They are convenient inside the app, but every other markdown consumer expects [text](path.md) links, so an obsidian to markdown step is needed before publishing a note to GitHub, a static site, a wiki or a colleague's editor.
This converter rewrites obsidian links, embeds, callouts, highlights, comments and tags into standard markdown in your browser, and can run in reverse to bring standard notes into a vault.
How to Convert Obsidian to Markdown
- Open the note in Obsidian, switch to source mode and copy everything, or open the .md file from your vault folder.
- Paste it into the left pane. The converted note appears on the right immediately.
- Pick the link target style: Note.md for GitHub, no extension for wikis and Hugo, slug for sites that lowercase file names, or plain text to drop the links.
- Choose a callout style and whether highlights become <mark> or bold.
- Decide whether to keep #tags and the YAML front matter.
- Copy the result, download the .md, or use the obsidian export buttons for PDF and Word.
Obsidian Syntax to Standard Markdown Reference
| Obsidian | Standard markdown | Notes |
|---|---|---|
| [[Note]] | [Note](Note.md) | Spaces are URL-encoded |
| [[Note|Alias]] | [Alias](Note.md) | Alias becomes the link text |
| [[Note#Heading]] | [Note > Heading](Note.md#heading) | GitHub-style anchor slug |
| ![[image.png|300]] | <img src="image.png" width="300"> | Or  without width |
| > [!tip] Title | > [!TIP] / !!! tip "Title" | Selectable style |
| ==text== | <mark>text</mark> | Or **text** |
| %% comment %% | removed | Inline and multi-line |
| #tag | #tag or removed | Headings are never touched |
Obsidian to PDF and Word Export
Obsidian's built-in obsidian to pdf export prints the note as it looks in the app, which keeps unresolved wikilinks and app-only callout styling. Converting to standard markdown first gives you a clean document: links point at real files, callouts render as quoted blocks, and the same markdown feeds both the PDF and the Word download. PDF and Word generation happens on the server and shares the free daily pool; the conversion itself never leaves your browser.
Going the Other Way: Standard Links to Wikilinks
Switch the direction to bring notes into a vault. Local [text](Note.md) links become [[Note|text]], local images become ![[image.png]] embeds, GitHub alerts and MkDocs admonitions become callouts and <mark> becomes ==highlight==. External http links are left alone, since wikilinks only work for notes inside the vault. Together with the forward direction this makes your notes portable in both directions without a plugin.
Frequently Asked Questions
What are wikilinks in Obsidian?
Wikilinks are the double-bracket links Obsidian uses to connect notes: [[Note name]] links to a note, [[Note#Heading]] to a section and [[Note|Alias]] shows different text. They are not part of standard markdown, so GitHub, Jekyll, Hugo and most editors render them as literal brackets.
How do I convert Obsidian to markdown that works on GitHub?
Paste the note, keep the direction set to Obsidian to standard markdown and choose the [Note](Note.md) link style. Callouts become GitHub alerts, highlights become <mark> tags and comments are removed. Copy the output or download it as a .md file.
Can I export Obsidian notes to PDF or Word?
Yes. After converting, the Download PDF and Download Word buttons send the standard markdown to the converter and return a file. This is the fastest obsidian export when you need a document for someone who does not use the app.
What happens to Obsidian callouts?
You choose. GitHub alerts (> [!NOTE]) work on GitHub and GitLab; the blockquote style works everywhere; MkDocs admonitions (!!! note) suit Material for MkDocs sites. Callout types without a GitHub equivalent map to the closest one, for example danger becomes CAUTION.
Does it change my Dataview queries or code blocks?
No. Fenced code blocks, including dataview and dataviewjs blocks, and inline code are copied through unchanged. Only prose outside code is converted.