Preview-first approval
The preview is the working surface, so the PDF export starts from a layout someone already approved.
Draft2Doc is built for the moment a markdown document has to become a presentable PDF. Open the file, approve the preview, choose the export settings, and download the version you can actually send.
The preview is the working surface, so the PDF export starts from a layout someone already approved.
Margins, spacing presets, headers, footers, and page numbers affect the exported PDF, not just the UI chrome.
Wide tables, long code blocks, quotes, and nested lists are part of the ugly-doc regression pack.
The point is not to create another complex markdown app. The point is to get from raw markdown to a trustworthy document with as little friction as possible.
Open a `.md` file quickly or start with one of the built-in trust samples.
Tune spacing, margins, and style until the preview feels ready for delivery.
Download a cleaner PDF path that is optimized for readability, printing, and final share-out.
Long rows and dense columns are part of the core regression pack so PDF, Word, Pages, and Google Docs stay part of the test story.
Dark code surfaces, grouped spacing, and export-aware wrapping are treated as first-class output, not as a decorative preview trick.
Flowcharts, sequence diagrams, and Gantt charts render to clean SVG inside the preview and carry through into PDF export automatically.
Inline $...$ and block $$...$$ equations render with KaTeX so research notes, engineering specs, and data science docs display correctly.
No. The PDF path uses export settings, paper size controls, preview-aware styling, and a dedicated render pass so the result feels closer to the approved document.
Briefs, specs, reviews, summaries, and handoff documents where typography, headings, code blocks, and tables need to stay readable.
Yes. A4, Letter, Legal, A5, and Executive are supported, along with margin presets, spacing presets, optional headers, footers, and page numbers.