Markdown to PDF: Obsidian, Notion & VS Code (2026)

TL;DR

To turn a Markdown file into a properly typeset PDF without installing a toolchain, drop the .md file into the Convert: Anything to PDF extension and click convert. It renders your headings, lists, code blocks, and emphasis into a clean PDF entirely inside your Chromium browser (Chrome, Edge, Brave, Arc, Opera, Vivaldi). No pandoc. No terminal. No online paste box. And because conversion is 100% local, your notes never get uploaded — zero network requests fire during conversion.

This is for the people who live in Markdown — engineers exporting design docs from Obsidian, teams sharing Notion exports, students writing in VS Code, anyone with a folder of README files — and keep hitting the same wall: the person receiving the doc wants a PDF, not a .md.

Why Markdown-to-PDF is a recurring headache

Markdown is the best format to write in. It's plain text, it's version-controllable, it's portable, and it stays out of your way. But it's rarely the format anyone wants to receive.

An architecture review board wants a PDF. A professor wants a PDF. A client wants a PDF. A compliance archive wants a PDF. So every Markdown writer eventually faces the conversion step — and the existing options are all a little painful:

• pandoc / CLI tools are powerful but require installing software and typing terminal commands (with a LaTeX dependency if you want nice output). Great for engineers who already have it set up; a non-starter for everyone else, and annoying even for engineers on a fresh machine.
• Online MD-to-PDF sites are one paste away — but you're pasting your document, which might be an unpublished design or private notes, into a stranger's web form. That's a privacy problem for anything confidential.
• Copy into Word loses your code formatting and reflows your careful structure into a mess.

The extension is the fourth option: local, no-install-beyond-the-extension, no terminal, no upload.

Who actually needs this

Engineers submitting design docs

Scenario: You wrote an RFC or a design doc in Obsidian. The review board runs on PDFs attached to a ticket. You need design-doc.md → design-doc.pdf without booting up pandoc on a machine that doesn't have it.

Drop the .md in, convert, attach. The headings become a readable hierarchy, your code blocks stay monospaced and intact, and the review board gets a clean document. Then attach the JSON payloads or logs alongside it — see JSON and XML to PDF for bug reports and audits.

Writers and note-takers

Scenario: You draft everything in Markdown — blog posts, chapters, meeting notes — and need to hand a clean copy to an editor or collaborator who doesn't use Markdown.

The typeset PDF reads like a finished document, not source code. No reformatting, no screenshots.

Students

Scenario: You take lecture notes in Obsidian or write assignments in VS Code, and submissions have to be PDF.

One click and your notes are a submittable PDF — with real, selectable text, so a grader can search it.

Teams exporting from Notion

Scenario: Someone exports a Notion page as Markdown to get it out of Notion, and now needs a shareable PDF of it.

Notion's own PDF export is fine, but if you've already got the Markdown export in hand (or you're assembling several into one document), converting the .md locally keeps it simple and keeps the content off any third-party converter.

Step by step

1. Open the extension and choose Upload Files. Markdown conversion is a file job, not a web-page capture.
2. Drop in your .md file. One file, or several if you want them combined.
3. Pick paper size and orientation. A4 for most of the world, US Letter for US contexts; Legal and Tabloid are there if you need them. Portrait is the usual choice for a doc.
4. Convert. The extension renders the Markdown to a PDF locally with jsPDF. Done in seconds, no upload.

Want to combine several notes — say a Markdown cover page plus a few section files — into one PDF? Drop them all in, order them, and merge. Full walkthrough in Merge images, CSV, and Markdown into one PDF.

Formatting: what carries over

Markdown's common elements render as you'd expect:

• Headings (#, ##, ###) become a visual hierarchy.
• Lists — ordered and unordered — keep their structure.
• Code blocks and inline code stay monospaced and readable.
• Emphasis — bold and italic — is preserved.

The output is real, selectable text, not an image of your document. That means the grader, reviewer, or archive can search and copy from the PDF — a meaningful difference from tools that flatten Markdown into a screenshot.

A practical tip: Markdown is a family of dialects, and some tools pack in extras (Obsidian's callouts, Notion's toggles, wiki-links, embedded queries). Plain-Markdown structure — headings, lists, code, emphasis, tables written in standard Markdown — is the reliable core. Keep confidential design docs in that standard subset and they'll typeset predictably.

Markdown to PDF: the options compared

pandoc wins on power and typographic control if you've already got it installed and don't mind the terminal — it's the right tool for a book with a bibliography. But for the everyday "I just need this note as a PDF right now," a browser extension with no terminal and no upload is the faster path. And unlike online MD-to-PDF sites, your private notes never leave the machine — the case laid out in why a PDF converter should not upload your files.

The no-code angle

You don't write a single command. There's no pandoc -o output.pdf input.md, no wrestling with a LaTeX install error, no npm install for some MD-to-PDF package. It's drag, click, done — which is the whole point for the writers, students, and PMs who are fluent in Markdown but have zero interest in a build toolchain.

Why local matters for your notes

Your Markdown files are often your rawest thinking — unpublished designs, private research, personal notes, draft strategy. Pasting those into an online converter means handing a copy to a third party.

Here, zero network requests fire during conversion. The rendering happens on your device with jsPDF. Your notes stay yours, and it works offline — convert a design doc on a plane, in a locked-down corporate environment, wherever. For the fuller privacy argument, see the privacy-first file conversion guide for 2026, and if you're building a paperless remote setup, remote-work paperless PDF tools.

Good to know

• Markdown, not .docx or .xlsx. This converts .md files. For spreadsheets, export to CSV first — see CSV to PDF.
• Standard Markdown is the reliable subset. Tool-specific extras (callouts, toggles, embeds) aren't standard Markdown; keep to headings, lists, code, emphasis, and standard tables for predictable output.
• No OCR — but Markdown is already text, so there's nothing to OCR; your output is fully selectable.
• Output isn't password-protected. Add encryption separately if a doc requires it.
• Chromium only — Chrome, Edge, Brave, Arc, Opera, Vivaldi. Not Firefox or Safari.

Frequently asked questions

How do I convert a Markdown file to PDF without pandoc?

Install the Convert: Anything to PDF extension, choose Upload Files, drop in your .md, pick a paper size, and click convert. It renders the Markdown to a typeset PDF locally — no pandoc, no terminal, no LaTeX.

Does it work with Obsidian and Notion Markdown?

Yes. Any .md file works, including notes exported from Obsidian or a Notion Markdown export. Standard Markdown structure — headings, lists, code blocks, emphasis, standard tables — renders reliably. Tool-specific syntax (Obsidian callouts, Notion toggles) isn't part of standard Markdown, so keep confidential docs in the standard subset for predictable results.

Are my notes uploaded anywhere?

No. Conversion is 100% local using jsPDF, and zero network requests fire during conversion. Your Markdown — including unpublished designs and private notes — never leaves your device, and it works offline.

Is the PDF text selectable, or just an image?

Selectable, real text. A reviewer, grader, or archive can search and copy from the resulting PDF — it's not a flattened screenshot of your document.

Can I combine several Markdown files into one PDF?

Yes. Drop multiple .md files into the Upload Files area, order them, and merge into a single PDF. You can even mix in images or a CSV in the same merge.

Do code blocks survive the conversion?

Yes. Code blocks and inline code stay monospaced and intact — a key advantage over pasting Markdown into Word, which tends to mangle code formatting.

Which browsers does it work in?

Any Chromium browser: Chrome, Edge, Brave, Arc, Opera, and Vivaldi. Firefox and Safari are not supported.

Bottom line

If you write in Markdown, the conversion to PDF shouldn't require a toolchain or a trip through someone's web form. Convert: Anything to PDF turns your Obsidian notes, Notion exports, README files, and VS Code Markdown into typeset, selectable PDFs — locally, no pandoc, no terminal, no uploads.

Install it and make the "can you send that as a PDF?" request a one-click answer. And when the design doc's shipped, CineMan AI is a free companion that overlays IMDb and Rotten Tomatoes scores plus an AI Taste Match on Netflix, Prime, and Disney+.