Markdown to PDF Converter
Convert a Markdown file to PDF in your browser. Useful for sharing READMEs, technical documentation, blog drafts, or any markdown-formatted content as a polished PDF. Real selectable text in the output, not an image. The file stays on your device — important when the content is unpublished or sensitive.
-
Sensitive documents stay private
Resumes, contracts, NDAs, notes you'd never paste into a chatbot — these are the documents most worth keeping off cloud converters. Everything here happens in your browser. The converted file goes straight to your downloads, then it's gone from memory.
-
MD → PDF done right
Headings, paragraphs, bullet and numbered lists (including nesting), bold and italic text, inline code, code blocks, blockquotes, tables, and horizontal rules all transfer. Hyperlinks are styled in blue but not clickable in v1. The PDF uses Helvetica with monospace Courier for code. US Letter, 1-inch margins.
-
No signup, no watermark, no email
You don't make an account, you don't enter an email, you don't see ads, and the output isn't watermarked. Free in the actual sense of the word — not "free for now, while we figure out a paywall."
Frequently asked questions
Does my file ever leave my device?
No. The conversion runs entirely in your browser. The file is read into memory, processed by a JavaScript library running in the same tab, and the result is delivered straight to your downloads. Open DevTools while you convert — you'll see zero network traffic carrying your file. This matters for anything sensitive: contracts, drafts, financial documents, personal notes.
Is there a file size limit?
No fixed limit. The real ceiling is your device's memory. Most text and PDF files are small enough that this is never a concern — multi-megabyte documents convert fine on phones. Very large files (hundreds of MB) may struggle on older or memory-constrained devices.
What about the original file?
Untouched. The converted file is a separate copy that lands in your downloads. Your original stays exactly where it was on disk.
Does this work on mobile?
Yes. Tap the drop zone to open your phone's file picker, choose a file from Files / Downloads / Drive / iCloud, hit Convert. The result downloads to your device's standard download location.
How is this different from online converter sites that ask for an email?
Those sites upload your file to their servers, run conversion server-side, and email you a download link. They get to read your document, log your IP, and store the file (for some period). This tool does none of that — everything runs in your browser tab. We don't even have an account system, so there's nothing to sign up for and nothing to log out of.
Which Markdown flavor does this support?
GitHub-Flavored Markdown (GFM) — the de facto standard. That covers standard CommonMark plus tables (with the | col1 | col2 | syntax), task lists (- [ ] item), strikethrough (~~text~~), autolinks, and fenced code blocks. If your markdown renders correctly on GitHub or in VS Code's preview, it should render correctly here.
Are code blocks syntax-highlighted?
Not in v1. Code blocks render in monospace (Courier) with preserved newlines, but no token highlighting. Syntax highlighting requires a separate library (Prism / highlight.js) that we'd embed at runtime. On the roadmap, but adds 50-200KB depending on language coverage.
What about images embedded in the Markdown?
Not preserved in v1 — image references in your markdown are parsed but the images themselves aren't embedded in the PDF. The image's alt-text appears as plain text where the image would have been. Image support requires a fetch + embed pipeline that handles both URL references and local data URLs; it's on the roadmap.
Are hyperlinks clickable in the output PDF?
Visually present (rendered in blue) but not clickable in v1 — pdf-lib supports link annotations and we'll add that in a future update. For now, link URLs are visible in the text where you wrote them, so readers can still copy them manually.
Does it handle large Markdown files?
Yes. Marked parses very fast (megabyte-scale files in well under a second), and the PDF rendering is linear in content length. Multi-thousand-line README files convert smoothly on phones and desktops alike. The output PDF size scales with content — typical 100-line README becomes a 4-6 page PDF.
Can I customize the styling (fonts, colors, page size)?
Not in v1. The output uses Helvetica throughout for consistency and so it renders identically on every PDF viewer. Custom fonts would need font embedding (multi-MB), custom colors / theming, and page-size options are on the roadmap. If you need typography control, use Markdown → HTML and apply your own CSS, then print to PDF from the browser.