Obsidian is a private, local-first note-taking tool. That design philosophy is exactly what makes it great for personal knowledge management, and exactly what makes sharing notes with other people so difficult.
If you've ever needed to send an Obsidian note to a colleague, a client, or anyone who doesn't use Obsidian, you've probably discovered this the hard way. There's no "Share" button. There's no export menu that outputs a properly formatted Google Doc or email. Your options are limited, and most of them require trade-offs.
This guide covers every current method for sharing Obsidian notes with non-users, including the strengths and limitations of each.
Why sharing from Obsidian is hard
Obsidian stores your notes as plain .md files on your local filesystem. When you see beautifully formatted headings, tables, and code blocks in the app, you're looking at Obsidian's live rendering of raw markdown text. The files themselves are just symbols and syntax.
When you try to share those files, the recipient needs some way to render the markdown. If they don't have a markdown viewer (and most people don't), they'll see raw text littered with ## marks, pipe characters, backticks, and asterisks.
Obsidian was never designed as a collaboration or publishing tool. It was designed as a private thinking environment. Sharing was an afterthought, and the available options reflect that.
Option 1: Obsidian Publish ($8 to $10/month)
Obsidian's official publishing solution turns selected notes from your vault into a website hosted on publish.obsidian.md.
What it does well:
- Notes retain their formatting on the web, including headings, tables, code blocks, and callouts.
- Graph view can be included on the published site.
- You can choose which notes to publish and which to keep private.
- Custom domains are supported.
Limitations:
- Costs $8/month for a single site or $16/month for multiple sites.
- Publishes to the web only. There's no way to get your note into Google Docs, Word, Slack, or Email through Publish.
- Recipients get a web link, not a document they can edit or incorporate into their own workflow.
- The published site has Obsidian's design, not a custom professional template.
Obsidian Publish is a reasonable option if you want a wiki-style website for your notes. It's less useful if you need to deliver a formatted document into someone else's app.
Option 2: Share Note plugin (encrypted temporary link)
The community-built Share Note plugin lets you create a temporary, encrypted link to a single note. The note is uploaded to an external server and can be viewed by anyone with the link.
What it does well:
- Quick and simple. Right-click a note, share it, get a link.
- Encryption means the server host can't read your content.
- No monthly fee.
Limitations:
- Links are temporary. They expire, and there's no guarantee of long-term availability.
- Single notes only. You can't share a collection or a set of related notes.
- Limited formatting support. Complex Obsidian features like dataview queries, callouts, and embedded notes may not render correctly.
- No control over styling or templates.
- The recipient gets a read-only web page, not a document they can work with.
Option 3: PDF export
Obsidian has built-in PDF export on desktop (File > Export to PDF). Some community plugins like Better Export PDF offer more control over the output.
What it does well:
- Produces a self-contained file that anyone can open.
- Formatting is generally preserved for basic content.
- No internet connection needed for the export.
Limitations:
- Not available on Obsidian mobile (iOS/Android).
- PDFs are not editable. If the recipient needs to modify the content, they're stuck.
- Tables and code blocks sometimes render poorly.
- No template system. Every export looks the same.
- Uploading a PDF to Google Docs produces an approximation with broken formatting.
Option 4: Sharing the raw .md file
You can send the .md file directly via email, cloud storage, or any file sharing service.
What it does well:
- Zero effort. Just attach the file.
- Preserves the exact source content.
Limitations:
- The recipient needs a markdown viewer or editor to read the file properly. Most people don't have one.
- Opening an
.mdfile in Notepad, TextEdit, or a web browser shows raw markdown syntax. - Obsidian-specific syntax (callouts, wikilinks, dataview, embeds) won't render in any other markdown viewer.
- This approach essentially asks the recipient to do the work of figuring out how to read your file.
Option 5: Copy-paste from Obsidian
Select all in your note, copy, paste into the destination app.
What it does well:
- No tools, no plugins, no cost.
- Works for very simple notes (just prose with some bold and italic text).
Limitations:
- Copying from Edit Mode gives raw markdown text. Your recipient sees
## Headinginstead of a heading,| col | col |instead of a table, and**text**instead of bold. - Copying from Reading Mode is inconsistent. Some formatting transfers (bold, italic), but headings lose their levels, tables may break, and code blocks rarely survive.
- Google Docs has a "Detect Markdown" preference, but it only handles basic bold and italic. Not headings, tables, or code.
- You'll spend 5 to 15 minutes manually reformatting every time.
Option 6: Static site generators (Quartz, Hugo, Jekyll)
You can use tools like Quartz, Hugo, or Jekyll to generate a static website from your Obsidian vault.
What it does well:
- Full control over the design and hosting.
- Can publish your entire vault or selected sections.
- Free hosting on GitHub Pages, Netlify, or Vercel.
- Quartz is specifically designed for Obsidian vaults and supports wikilinks, backlinks, and graph view.
Limitations:
- Requires Git knowledge and command-line familiarity.
- Setup takes hours, not minutes.
- Like Obsidian Publish, this creates a website, not a formatted document for Google Docs, Word, or Slack.
- Ongoing maintenance when Obsidian or the static site generator updates.
- Significant technical barrier for non-developers.
The Unmarkdown approach: share to any destination
Unmarkdown™ takes a different approach to the sharing problem. Instead of creating a website from your notes, it converts your markdown into properly formatted content for whatever app your recipient uses.
The workflow is straightforward:
- Open your note in Obsidian and copy the markdown content (Cmd+A, Cmd+C from Source mode).
- Go to unmarkdown.com and paste it into the editor.
- Choose your destination.
That third step is where the value is. Instead of a single output format, you get six destination-specific conversions:
- Google Docs: Real heading styles (all 6 levels), native tables with borders, styled code blocks, working hyperlinks. Paste into Google Docs and everything just works.
- Word: Proper Word heading styles, formatted tables, monospace code blocks. Compatible with Microsoft's clipboard format.
- Slack: Converts standard markdown to Slack's mrkdwn syntax. Single asterisks for bold, angle bracket links, headings converted to bold text (since Slack has no heading support).
- Email: Inline CSS that renders correctly across Gmail, Outlook, Apple Mail, and other email clients. Tables, headings, code blocks all formatted.
- OneNote: Heading levels, tables, and formatting optimized for OneNote's clipboard handling.
- Plain Text: Strips all markdown syntax, leaving clean readable text.
You can also publish your note as a web page with a shareable URL, choose from 62 professional templates, and use AI editing to polish the content before sharing.
Handling Obsidian-specific syntax
Standard markdown elements (headings, tables, bold, italic, code blocks, links, lists) convert cleanly. Obsidian-specific extensions need some awareness:
- Callouts (
> [!note],> [!warning]): Convert as styled blockquotes with the callout type preserved. - Wikilinks (
[[page name]]): Brackets are stripped, leaving the page name as readable text. - Embedded notes (
![[other note]]): Won't transfer. Copy the embedded content separately, or use the Easy Bake plugin to flatten embeds into the note before copying. - Tags (
#tag): Become plain text with the hash removed. - Dataview queries: Won't render. Copy the rendered results from Reading Mode instead.
- Mermaid diagrams: Unmarkdown™ renders these as SVG images that transfer to most destinations.
Which method should you use?
The right choice depends on what your recipient needs.
If they need a web link: Obsidian Publish, Share Note plugin, or Unmarkdown™ publishing.
If they need an editable document: Unmarkdown™ (copy for Google Docs or Word) is the only option that produces an editable, properly formatted document in the recipient's app.
If they need a Slack message: Unmarkdown™ is the only option that handles the markdown-to-mrkdwn conversion.
If they need an email: Unmarkdown™ handles inline CSS formatting. Copy-paste from Obsidian puts raw markdown in the email body.
If you're technical and want a full website: Quartz or Hugo for maximum control. Obsidian Publish for convenience.
The core converter at unmarkdown.com is free with no account required, so the easiest way to evaluate it is to paste one of your notes and see the difference.
Try the Unmarkdown plugin for Obsidian
Unmarkdown is now available as an Obsidian community plugin. Right-click any note and copy it formatted for Google Docs, Word, Slack, OneNote, Email, or Plain Text, directly from your vault. You can also publish notes to the web with 62 templates.
How to install (Community Plugins directory approval pending):
- Download
main.js,manifest.json, andstyles.cssfrom the latest release - In your vault, create the folder
.obsidian/plugins/unmarkdown/ - Move the three downloaded files into that folder
- Open Obsidian Settings > Community Plugins > Enable "Unmarkdown"
- Go to Settings > Unmarkdown > Click "Connect account" to link your free Unmarkdown account
Once approved for the Community Plugins directory, you can install by searching "Unmarkdown" in Obsidian's plugin browser.
