Markdown to PDF

It supports CommonMark with GitHub Flavored Markdown extensions: ATX headings (# through ######), unordered and ordered lists, nested lists, fenced code blocks with optional language tag, inline code, links, images, blockquotes, horizontal rules, bold and italic, strikethrough, and tables with pipe syntax. GFM-specific features like task lists (- [ ]) and auto-linking of URLs work too. What is not supported: footnotes, definition lists, MathJax/LaTeX equations, mermaid diagrams (the source code shows as plain text in code blocks), and custom HTML inside Markdown beyond basic tags. For documents heavy on math or diagrams, render the Markdown to HTML separately with a tool that supports those features, then use HTML to PDF here.

Yes, if you tag the fenced code block with a language identifier (like ```javascript or ```python). The tool uses the chosen theme's syntax-highlighting palette to color keywords, strings, comments, and other token types. Supported languages cover the major ones: JavaScript, TypeScript, Python, Ruby, Go, Rust, C/C++, Java, C#, HTML, CSS, SQL, JSON, YAML, Bash, and many more. If the language is unrecognized, the code renders as plain monospaced text with no highlighting, which still looks clean. Inline code (single backticks) is rendered in monospaced font without highlighting. For exporting source code documentation, this produces polished output rivaling tools like Pandoc — without installing anything.

Mostly no, because Markdown to PDF currently uses the in-browser HTML renderer to render the parsed HTML, which produces a raster image embedded in the PDF — text is part of the image, not selectable. This is a known limitation. For a fully searchable text PDF from Markdown, use Pandoc (a desktop tool) or convert the Markdown to HTML first and use a browser's native print-to-PDF, which preserves text. A future version of Markdown to PDF may switch to a native PDF text layout engine, but for now the trade-off is styled output (with images, custom fonts, colors, and code highlighting) versus searchable plain text. For text-only Markdown without styling, Text to PDF preserves searchability at the cost of fidelity.

Not in the current version. The themes (GitHub, Academic, Minimal) are designed to cover the common cases without configuration — pick one and the typography, colors, and spacing are set. For full customization, use HTML to PDF: convert your Markdown to HTML with any tool (or use the marked library directly in your own code), apply custom CSS, then drop the HTML into HTML to PDF for conversion. This is more steps but gives total control over fonts, brand colors, header styles, and page layout. A custom-theme upload feature is on the roadmap and would let you supply a CSS file to apply during conversion. For now, the three built-in themes cover most practical needs.

Yes. The standard Markdown image syntax () embeds images during rendering. URLs must be accessible from your browser with appropriate CORS headers; data URIs (base64-encoded inline images) work without CORS issues. For local images, drop the image files into the upload area alongside the .md file and the tool will resolve relative paths automatically. The image is rendered into the page at its natural size by default; control sizing with HTML img tags inside Markdown if needed (most parsers including marked support raw HTML in Markdown). Large images can slow rendering — pre-compress them if needed before referencing.

By default, content flows naturally and breaks at page boundaries based on content height. To force a page break, insert an HTML comment like <!-- pagebreak --> in your Markdown — the tool detects this convention and starts a new page. Alternatively, use raw HTML with a CSS page-break style attribute. For chapter-based documents, prefix each chapter with a top-level heading (# Chapter Name) and the page-break-before: always style applied to h1 by the theme will start each chapter on a new page automatically. Headings are kept with their following paragraph (no orphaned headings at page bottoms). For complex pagination, preview carefully — Markdown's flexibility means there is no single right pagination scheme.