PDFJadoo › Blog › Markdown to PDF, Typeset

Markdown to PDF: draft in plain text, deliver a real document

Markdown is where writing happens now — notes, READMEs, drafts, documentation — because it is fast, portable and version-friendly. But the deliverable the world asks for is a PDF: the report, the handout, the submission. Markdown to PDF is the typesetting step: paste your Markdown and the renderer produces a properly typeset document — headings in a real hierarchy, justified text, real margins, page numbers — honouring headings, paragraphs, bold and italic, inline and fenced code, lists, blockquotes and horizontal rules. It also states its limits in plain sight: tables and images are not supported yet, and emoji or non-Latin scripts are limited by the built-in fonts. This article covers the supported syntax, the workflow it enables, and working within the stated limits.

Free, in your browserFiles never uploadedHeadings · code · lists · quotes — typeset
PDFJadoo logoBy the PDFJadoo Team5 min read
Diagram: Markdown text with hashes and asterisks transforming into a typeset PDF page
The draft's plain text, dressed for delivery: hierarchy, margins, page numbers.

The supported syntax — the document writer's kit

The renderer's set is chosen for documents: # headings through the hierarchy, **bold** and *italic*, `inline code` and ``` fenced code blocks (set in monospace, unbroken by justification), lists bulleted and numbered, > blockquotes set apart, and --- horizontal rules for section breaks. Justified body text with real margins and automatic page numbers gives the output the finish of a word-processed document — the reader sees a report, not a printout of a text file. For the enormous class of text-first documents — reports, essays, documentation, letters, chapters — this kit is the whole requirement, and its constraint is a kind of focus: the writing carries the document, not its decoration.

The stated limits deserve the same clarity. Tables: not yet — a Markdown table in the source will not render as a grid; the workarounds are a list-structured presentation of the data, or typesetting that one document by another route. Images: not yet — the document is text-only by current design. Scripts and emoji: the built-in fonts cover Latin text; characters beyond them (emoji, many non-Latin scripts) may not render — for Urdu, Arabic or CJK documents, another route serves better today. Limits stated on the tool's own page, repeated here without softening, because a typesetter you can plan around beats a typesetter that surprises you at page nine.

The workflow: Markdown as master

The deeper value is the workflow the converter completes: draft and keep the master in Markdown — in your notes, your repo, anywhere text lives — and export the PDF when a document is needed. Edits happen in the master (diffable, searchable, future-proof); PDFs become regenerable outputs rather than precious originals. The reverse converter (PDF to Markdown) exists for documents that began life as PDFs; this one exists so the next document doesn't have to.

Typeset Markdown as a PDF, step by step

Step 1 — write or paste the Markdown. Compose directly, or paste from your notes/repo into Markdown to PDF. A live character count keeps the document's size in view.

Step 2 — check the plan against the limits. Tables or images in the source? Restructure tables as lists; images belong to another route for now.

Step 3 — press Make my PDF and read the result. Headings hierarchical, code intact, quotes set apart, pages numbered.

Step 4 — proof the typesetting. Long code lines, deep heading nesting and list continuations are the places to eyeball — the same places every typesetter earns a proof.

Step 5 — keep the Markdown. The .md is the master; the PDF is its export. Regenerate, don't re-edit the PDF.

Small documents, serious finish

The converter's centre of gravity is the everyday formal document: the two-page report, the project handout, the meeting brief, the chapter draft. For these, the route from a text file to a presentable PDF — without opening a word processor, without an upload — is a small daily mercy that compounds.

Write in text. Deliver in PDF.

Headings, emphasis, code, lists and quotes, typeset with margins and page numbers — from a paste.

Open Markdown to PDF

A worked example: the field report

An engineer's site-visit notes live in Markdown on her phone — headings per system, bullet findings, a fenced block of the controller's log output, a quoted line from the client's brief. The office needs “the report as a PDF” by evening. Pasted into the typesetter, the notes emerge as a paginated document: systems as headings, findings as lists, the log verbatim in monospace, the client's words set as a quotation — justified, margined, numbered. She sends the PDF and keeps the Markdown; next visit's report starts from the same master, and the format never has to be thought about again.

Edge cases

Nested lists and deep hierarchies. Supported syntax renders best at sane depths — four heading levels, two list levels. Beyond that, restructure for the reader's sake as much as the renderer's.

Raw HTML in the Markdown. Markdown often allows inline HTML; this careful renderer is a Markdown renderer — do not rely on embedded HTML surviving.

Very long documents. Books are possible in principle; the paste-and-typeset flow suits documents, and chapter-wise generation with a later merge is the practical route to a long work.

Before you finish: the 60-second check

Fair questions

How do I convert Markdown to PDF for free?

Paste your Markdown into Markdown to PDF and press Make my PDF. Headings, bold and italic, inline and fenced code, lists, blockquotes and rules are typeset into a justified, paginated PDF — in your browser.

What Markdown syntax is supported?

Headings, paragraphs, bold, italic, inline code and fenced code blocks, bulleted and numbered lists, blockquotes and horizontal rules. Tables and images are not supported yet, and emoji or non-Latin scripts are limited by the built-in fonts.

What do I do about a table in my Markdown?

It will not render as a grid yet. Restructure the data as a list, or typeset that particular document by another route (a word processor export). The limit is stated on the tool's page so you can plan around it.

Why keep the Markdown after making the PDF?

Because the Markdown is the master: editable, diffable, future-proof. The PDF is an export — regenerate it after edits rather than editing the PDF itself.

Can I write non-Latin text (Urdu, Arabic, Chinese)?

The built-in fonts are limited for non-Latin scripts and emoji, so those documents are better served by another route today. Latin-script documents are the converter's home ground.

Is my text uploaded?

No — typesetting runs in your browser; your draft never leaves your device.

Tool behaviour — the supported syntax list, justified typesetting with margins and page numbers, and the plainly stated limits (no tables or images yet; font limits for emoji and non-Latin scripts) — is from PDFJadoo's own Markdown to PDF page. Checked 18 November 2026.

Keep reading