obsidian-export VS pandoc

Found: https://github.com/zoni/obsidian-export but hope this can be part of a single solution.

I use this obsidian-export CLI program to convert prior to pushing to my repo and it's been working pretty well. This gives me a read-only version of my notes that is accessible from devices I don't have obsidian on (work laptop, for example).

If you limit your use of third party plugins, you can always use https://github.com/zoni/obsidian-export for this as well. I originally built it for exactly this use case (but now also use it as a crucial step in my pipeline to publish content to my own website)

It came from here! https://github.com/zoni/obsidian-export

Worth noting I maintain a project which does exactly this: https://github.com/zoni/obsidian-export

I have similar folders to [Oudwin](https://www.reddit.com/user/Oudwin/)... - dm - _inbox - assets - checklist - communications - research-reference - elements - sessions Additionally, I have had reasonable success using [obsidian-export](https://github.com/zoni/obsidian-export) to export my Obsidian vault to CommonMark. From there you have more options. I then build html pages using [mdbook](https://rust-lang.github.io/mdBook/) to control the information that is revealed to players. I am playing with using [MkDocs](https://www.mkdocs.org/) to see if it offers more control/flexibility. Regardless, the /elements folder contains all the lore chunks of the world including information I keep on the PCs. The /communications and /sessions folders can contain info with links to /elements that are revealed as needed. I make heavy use of transclusion ![[CoolThingFormAnotherFolder]] to keep it a bit more elegant and some custom styles are needed to make it how it look how I wish.

I have had reasonable success using obsidian-export to export a vault to CommonMark. From there you have more options. I am using it for world-building in D&D and I then build html pages using mdbook to control the information that is revealed to players.

Shameless plug: obsidian-export. It will convert [[WikiLinks]] and ![[Embeds]] to plain Markdown (among a few other things) so you'll always have a way to go back if Obsidian doesn't work out the way you hoped.

So really you can't get what you want at all. You could try an external tool like this to export your notes to commonmark which is more widely supported. Ultimately if you are changing the path to files outside of obsidian (meaning they won't be automatically updated) you will break links. So maybe your best bet is to use wikilinks + an export tool.

`Textile` is a similar language to Markdown, used to weave text across multiple IDEs, programming languages, and CMSs:

https://textile-lang.com/

Textile is one of the core markups supported by GitHub and Pandoc:

https://github.com/github/markup / https://pandoc.org/

And many CMS, most famously TextPattern and MoveableType, but also things like Jekyll:

https://textile-lang.com/article/textile-markup-language-sup...

==> pandoc : stable 3.9.0.2 (bottled), HEAD

Swiss-army knife of markup format conversion

https://pandoc.org/

Installed (on request)

From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/...

License: GPL-2.0-or-later

==> Installed Kegs and Versions

pandoc 3.9.0.2 (11 files, 274.7MB) [Linked]

==> Dependencies

Required (1): gmp

Recursive Runtime (1): all installed

==> Analytics

install: 31,898 (30 days), 119,598 (90 days), 369,388 (365 days)

As every developer using AI knows, using markdown (md) files is the best way to communicate with AI in May 2026. On the other hand, as far as I know, AI cannot read and write Word files directly. A Word .docx file is a zip file and contains document.xml, styles.xml, and others, so it is not suitable for AI to read directly. So it is better to convert Word files to md for AI. This time, I tried the popular document conversion tool Pandoc. https://pandoc.org/ Using Pandoc, we can easily convert Word files into md, but detailed styles will be lost.

The Swiss army knife for document conversion, Pandoc, supports compiling to WASM since 3.9 [1]. It supports Markdown, in a wide variety of flavours, and Typst. Their official demo page provides a PDF output via Typst, all done client-side [2]. Furthermore, you get .docx and other output formats as well

[1]: https://github.com/jgm/pandoc/releases/tag/3.9

[2]: https://pandoc.org/app/

There's an Obsidian extension for Pandoc so you can convert your Obsidian notes to any other format.

https://github.com/jgm/pandoc/pull/11135

There are a number of basic errors in this report, but since it's LLM-written I suppose I shall put as much effort correcting them as the author put into generating them. Sigh.

From the pandoc release announcement: https://github.com/jgm/pandoc/releases/3.9 :

> Starting with this release, pandoc can be compiled to WASM, making it

I’d highly recommend pandoc[0] if you need markdown conversion. Basically converts from everything and any markdown style to everything else. And then for clipboard just use `| pbcopy` on a Mac or `| xsel -ib`. Full command on a Mac would just be `pandoc README.md —to html | pbcopy`.

0: https://pandoc.org/

I looked into this and nothing worked well for me. I ended up just using Pandoc: https://pandoc.org/

That's when I found pandoc. Pandoc is a document converter that can turn markdown into PDF. It does this by converting markdown to LaTeX first, then using LaTeX to generate the PDF.