Files stay on your device

Markdown to PDF

Convert MD to PDF — headings, code, tables, in your browser

Turn a Markdown file into a polished, shareable PDF. Headings, lists, tables, code blocks and links are all rendered properly — in your browser, with nothing uploaded.

🔒 Never uploaded ⚡ Instant 🔎 Selectable text ✓ Free

From plain Markdown to a finished document

filesmith.io/convert/md-to-pdf
The Filesmith converter turning a 5.6 KB Markdown file into a 49.7 KB three-page PDF, with the size increase shown in red as plus 786 percent
The file gets bigger, and that is the expected result. Markdown is a few kilobytes of plain text; a PDF carries page geometry, embedded fonts and layout instructions for every page. Here 5.6 KB became 49.7 KB across three pages.
Markdown is perfect for writing but awkward to share — not everyone has a viewer, and raw .md looks like code. Converting to PDF gives you a clean, self-contained document anyone can open, while you keep writing in the format you like.

What’s rendered

Headings become real headings, and inline bold, italic, inline code and links all render. Bullet and numbered lists, blockquotes, fenced code blocks, horizontal rules, and pipe tables are all supported, so a README or a set of notes comes out looking like a proper document.

Great for READMEs and notes

A GitHub README, a project spec, meeting notes or documentation written in Markdown converts into something you can email, print or attach — no formatting lost, no viewer required.

Markdown has no pages

This is the one thing worth understanding before you convert. Markdown describes structure — this is a heading, this is a list, this is code — and says nothing about pages, margins, or where one sheet ends and the next begins. A PDF is made of pages by definition.

So the converter decides. Content flows onto the page and breaks wherever it runs out of room, with headings and code blocks kept with their content where possible. What you don't get is fine control: you can't force a section to start on a new page, because Markdown has no way to say so. If you need that level of control over layout, Markdown isn't the right source format — but for a README, a set of notes, a spec, or documentation, the automatic result is usually exactly what you wanted.

Images and links from a README

The most common surprise when converting a GitHub README: images referenced by relative path, like ./docs/screenshot.png, have nothing to resolve against once the file leaves the repository. They'll be missing from the PDF. Images referenced by full URL are fine, as are inline data URIs.

Links convert to clickable links in the PDF and keep working. Anchor links that jump to another heading in the same document keep working too, which makes a converted README genuinely navigable rather than just readable.

Long code lines

Code blocks don't reflow the way prose does — a line longer than the page width has to either wrap awkwardly or run past the margin. If your document contains long commands or minified snippets, break them across lines before converting and the PDF will look considerably better.

Frequently asked
Is my file uploaded?
No. The Markdown is rendered to PDF entirely in your browser.
Which Markdown features are supported?
Headings, bold, italic, inline code, links, bullet and numbered lists, blockquotes, fenced code blocks, horizontal rules and pipe tables.
Will the PDF text be selectable?
Yes. The PDF is built from real text, so it stays selectable and searchable rather than being an image.
Can I convert a GitHub README?
Yes. Save the README.md and drop it here — headings, code blocks and tables all render.
Is it free?
Yes, with no limits.