Pandoc can convert almost anything, but most people only need markdown to PDF, Word, or HTML. Here's how to do those without installing Pandoc and LaTeX, and when Pandoc is still worth it.
Pandocis the most capable document converter there is. For a one-off "turn this README into a PDF", though, it asks a lot:
# The typical Pandoc route to PDF pandoc README.md -o README.pdf --pdf-engine=xelatex -V geometry:margin=2cm
| Pandoc | Browser converter | Desktop editor | md-to-pdf (CLI) | |
|---|---|---|---|---|
| Install needed | Pandoc, plus LaTeX for PDF | None | The editor app | Node.js and a headless Chrome |
| Markdown → PDF | Yes, via LaTeX by default | Yes | Yes | Yes |
| Markdown → Word | Yes | Yes (Markdown Utils) | Some, often via Pandoc | Rarely |
| Other formats | Dozens (EPUB, LaTeX, reST…) | HTML | A few | HTML |
| Citations | Yes (citeproc) | No | Limited | No |
| Batch / CI | Yes | No | No | Yes |
| Learning curve | Flags, templates, filters | Paste and click | Low | Moderate |
For the three conversions most people use Pandoc for, a browser tool is the shortest path. Markdown Utils runs each one locally in the page, so the file never leaves your machine:
Trade-off: one file at a time, and only these output formats. For a side-by-side of Word converters, see the best markdown to Word converters; for PDF, the best markdown to PDF converters.
If you already write in a dedicated editor, its export menu may be enough. Typora exports PDF and HTML on its own, but hands Word and most other formats to Pandoc, so you still need Pandoc installed for those. Marked 2 on macOS previews and exports markdown to PDF and Word-compatible formats.
Trade-off: you are buying or installing an editor to get an export button.
If you want a command but not LaTeX, md-to-pdf (npm) and the Markdown PDF extension for VS Code both render markdown to HTML and print it to PDF with headless Chrome. Styling is plain CSS, which most developers find easier than LaTeX templates.
npx md-to-pdf README.md
Trade-off: PDF and HTML only, and installing it pulls in a Chromium build.
None of the alternatives above replace Pandoc for:
--citeproc.--reference-doc.A common split: Pandoc in the build pipeline, and a browser tool for the quick one-off conversions everyone else on the team needs.
Pandoc itself is a command-line program. Browser-based converters cover its most common jobs, which are markdown to PDF, Word (.docx), and HTML. Markdown Utils runs those conversions entirely in your browser, so your file is never uploaded.
Yes. Pandoc's default PDF route goes through a LaTeX engine, which is a large install. Browser-based converters and tools such as md-to-pdf or the VS Code Markdown PDF extension render HTML and print it to PDF instead, so no LaTeX is needed.
Yes. A browser converter can write a native .docx file with real Word heading styles, tables, code blocks, and equations. Markdown Utils' Markdown to Word tool does this without any install or upload.
Use Pandoc when you need formats beyond PDF, Word, and HTML (EPUB, LaTeX, reStructuredText, and dozens more), citations and bibliographies with citeproc, custom Lua filters, a corporate Word template via --reference-doc, or batch conversion in a script or CI pipeline.
📄
Markdown to PDF, Word, or HTML in your browser. No upload, no account.