Print-accurate preview
Editor and page preview share one renderer, so standard PDF exports place headings, tables, code and math exactly where you previewed them. Compliance exports may reflow.
Preflight reads the Markdown source before you export, and compliance exports also get a report that measures the finished PDF. Here is what each step looks at.
Editor and page preview share one renderer, so standard PDF exports place headings, tables, code and math exactly where you previewed them. Compliance exports may reflow.
A3, A4, A5, Letter, Legal, Tabloid or Ledger, margins, headers, footers, a cover page and a table of contents with real page numbers.
Convert a folder of .md files at once, with per-file status, retries and a diagnostics report.
Combine chapters into one PDF with a single table of contents and page breaks between chapters.
Archive- and accessibility-grade exports with embedded fonts, tagged structure and native compliance identifiers.
Catch missing images, alt text, heading jumps and broken links before the document leaves your desk.
Import Markdown, images and includes from public GitHub or GitLab repositories, subdirectories included.
When Word is the deliverable, export a .docx from the same source.
Watch your document typeset itself as you type. Switch between source, split, and full-preview modes without ever losing your place.
Choose paper size, orientation, margins, headers, and footers so the PDF matches your printer.
Mermaid flowcharts and KaTeX formulas render consistently in the preview and in the exported PDF.
Start from a blank page, paste an existing file, or choose a structured template.
Clean report with header and page footer.
Numbered paper with a print-friendly theme.
Numbered long-form book with compact margins.
Numbered manual with chapter starts and document navigation.
Start from a plain .md file — the front matter already sets the title, table of contents, section numbers and theme. Replace the sample text and export.
Pick a theme and the headings, tables and code blocks follow it. A theme only changes typography — PDF/UA tags, language, title and reading order come from the export path, and the same checks run on every theme.
Technical documentation in GitHub's own look: tight headings, neutral greys, monospace code.
Serif body text on a warm page for articles and reports meant to be read on paper.
A dark page with light type for handouts and reading on screen.
Minimal and airy, with generous margins for essays and short reports.
Maximum contrast with no background tint — built for photocopying and plain printing.
Themes change typography only. They never add or remove accessibility metadata: PDF/UA and PDF/A are produced by the export path, not by the theme.
Headings, tables, lists and images all become PDF structure. If the source loses that structure, no exporter can put it back after the fact.
Aligned columns, clean dividers, and content-aware sizing.
Syntax-aware styling and print-friendly wrapping for technical docs.
Checklists render as crisp, scannable documents.
Clickable references with readable URLs in printed output.
Place, align, and caption images without breaking the page.
Emphasize ideas with elegant blockquotes and callouts.
Open the checker, paste a document, and read the same list of issues an accessibility reviewer would flag.
Open the studio