AnyFormat

00 Markdown → PDF

Markdown to PDF

Structure survives. No Node, no headless browser, no upload.

01MD in
02PDF out
03Options 6

72 points is an inch. 56 is about 2 cm, which is a normal book margin.

1.45 is comfortable for continuous reading. 1.15 is tighter; 2 is double-spaced.

  • No upload The conversion runs in this tab. Your file never travels — not to us, and not to the advertising.
  • No sign-up, no email, no daily cap There is no account system to sign up to.
  • No size limit we invented Only your device's memory — about ~2 GB on a desktop browser, ~400 MB on a phone.
  • Turn your Wi-Fi off and convert anyway The conversion needs nothing but this page. Ads will not load without a connection; your file will still convert. That is the whole claim, and it takes five seconds to check.

Typesets Markdown into a PDF with its structure intact. The usual alternative is installing a toolchain — Pandoc, or a Node package that drives a headless browser — for a job that takes one drag here.

What is understood

Headings — # through ######, mapped onto three visual levels since more than three is rarely useful on a page.

Lists — bulleted and numbered, both rendered with a bullet and an indent.

Block quotes — > lines, set in italic and indented.

Fenced code — triple-backtick blocks, set monospaced with their line breaks preserved exactly.

Paragraphs — separated by blank lines and re-wrapped to the page.

What is flattened

Inline emphasis, links and inline code become plain text: **bold** loses its bold, and [text](url) becomes "text (url)" so the destination is not lost.

The reason is that this lays out text directly rather than rendering HTML, and mixing typefaces within a line needs a richer model than that. Tables and images are not rendered either.

If you need faithful rendering with styling, the honest answer is Pandoc or a headless-browser pipeline. If you need a readable, well-structured document from a README or a set of notes, this is one drag and no install.

Latin script only, and why

PDF has fourteen built-in fonts that every reader already has, and they cover WinAnsi — Latin letters, accented European characters, curly quotes, the euro and pound signs. Nothing else.

Writing Chinese, Japanese, Korean, Arabic, Hebrew, Thai, Devanagari or Cyrillic means embedding a font that contains those glyphs, and a font with usable CJK coverage is several megabytes. Downloading that on the chance a visitor needs it is not a reasonable trade for a page that mostly converts English.

So instead of producing a document full of blank boxes, unencodable characters become a question mark and the conversion tells you exactly how many were affected and which script they belonged to. If your text is in one of those scripts, this is the wrong tool and you should use a desktop converter — that is a more useful answer than a broken file.

Other names for this

Also searched as “markdown to pdf”, “md to pdf converter”, “readme to pdf”.

Questions

Will my bold and italic survive?
No — inline emphasis is flattened to plain text. Headings, lists, quotes and code blocks all keep their structure.
What about tables and images?
Neither is rendered. Use Pandoc or a headless-browser pipeline if you need them.
Do links still work?
They become plain text with the URL in brackets, so the destination is visible but not clickable.
Is my file uploaded?
No. The PDF is built in this tab and handed to you as a download. That matters here more than most places: the documents people convert to PDF are contracts, CVs, medical letters and manuscripts.
Can I convert several files at once?
Yes. Drop as many as you like, or a whole folder. Each becomes its own PDF keeping its original name.