kebl3541195 downloadsOne-click buttons that export the current note to Word, PDF, HTML, EPUB, LaTeX, and any other format Pandoc supports.
An Obsidian plugin with one-click buttons that export the current note to Word, PDF, HTML, EPUB, LaTeX, and any other format Pandoc supports.
If this plugin adds value for you and you would like to help support continued development, please use the buttons below:
☕ Buy me a coffee · 💙 Donate via PayPal
If you like this plugin or find it useful, please consider giving it a star on GitHub!
![[Another note]], ![[Note#Heading]], and ![[Note#^block]] embeds are replaced by the embedded content (recursively, cycle-safe), so the export reads like the note does in preview.%%comments%% are removed (they're hidden in Obsidian), while anything inside code blocks or inline code stays exactly as written.![[image.png]] embeds, including ones inside embedded notes, are resolved to real paths before conversion.[@key] syntax automatically get --citeproc; point the settings at your .bib file and CSL style once (or declare them in note frontmatter).--toc, --number-sections, custom templates…) can be set once and apply to every export.Word (docx), PDF, HTML, EPUB, LaTeX, ODT, RTF, PowerPoint (pptx), plain text, GitHub-flavored Markdown, reStructuredText, Org, MediaWiki, DocBook, Jupyter notebook, Typst. Toggle which buttons appear in settings.
brew install pandoc on macOS). The plugin auto-detects it in the usual homebrew/system locations; a custom path can be set in settings.brew install tectonic), xelatex, typst, or wkhtmltopdf, all auto-detected. Without one, PDF export falls back to the built-in renderer automatically.Desktop only (the plugin runs the pandoc executable).
This plugin needs two capabilities that Obsidian's review process rightly flags, so here is exactly how they are used:
child_process.execFile): the plugin's sole purpose is to run Pandoc. It executes only the Pandoc binary (auto-detected in standard locations, or the path you set) and, for PDF, the PDF engine. Arguments are passed as an array; no shell is invoked, so note names and settings cannot inject commands. Nothing runs except when you click an export button or run an export command.fs): note content is read through Obsidian's vault API, never fs. Direct filesystem access is limited to: writing the exported file where you chose, writing/deleting one temporary HTML file when the built-in PDF renderer is used, creating the output folder if missing, and checking whether the Pandoc/engine binaries exist during auto-detection.MIT © kebl3541