Markdown to PDF
Paste in the writing and download a PDF with a readable line length, and headings that look like headings.
Nothing is uploaded. Parsing and rendering happen here, and the PDF is produced by your own print engine.
Preview — A4
Design Review — Q3
A short brief showing how the document sets. Replace this with your own Markdown.
Summary
The interface is largely sound. What is failing is governance: four teams each maintain a private fork of the same component library, and there is no contribution path, so forking is faster than contributing.
Findings
- 214 colour values in production, against a defined palette of 31.
- Eleven button variants, of which four are visually identical.
- No named owner for the shared library.
A redesign would reset the clock without touching the mechanism winding it down.
Recommendation
| Action | Owner | Weeks |
|---|---|---|
| Name a library owner | Design lead | 1 |
| Build the contribution path | Design systems | 3 |
| Reconcile the four forks | Engineering | 6 |
| Re-adopt, team by team | All | 12 |
Space is the loudest element in the layout — see --measure in the exported CSS.
What the chat window cannot finish.
Most Markdown-to-PDF output is technically correct and typographically illiterate: 100-character lines, no hierarchy, Times New Roman. This one applies the studio's own type system — a capped measure, an optical scale, hanging punctuation — so the document you export looks like something a person designed.
An assistant will happily write your document. It cannot hand you the PDF. Chat returns text; a printable, shareable, typeset file is a rendering job, and rendering is exactly what a browser is for.
Nothing you paste leaves your browser. The PDF comes from your own print engine.
Typesetting applied
The defaults this tool prints with, and why.
- Measure
- 68 characters — the working range for continuous prose is 60–75
- Body size
- 11pt at 1.65 leading
- Page
- A4 with 22mm margins, or US Letter
- Hierarchy
- Weight, case and space — not size alone
- Widows / orphans
- Suppressed via CSS `orphans: 3; widows: 3`
- Headings
- `break-after: avoid` so a heading never ends a page
These constants are published under CC BY 4.0. Quote them, cite them, put them in your own documentation. Attribution to Original Design Studio is the only condition.
The principles behind what this tool tells you.
Does my document get uploaded anywhere?
No. Parsing and rendering happen entirely in your browser, and the PDF is produced by your own print engine. Nothing is transmitted, which is the point if you are working under an NDA.
How do I actually save the PDF?
Press Export, then choose 'Save as PDF' as the destination in the print dialog. Leave headers and footers off and margins set to Default for the intended result.
Which Markdown is supported?
GitHub-flavoured Markdown: headings, lists, tables, code blocks, blockquotes, links, images, and task lists.
Can I change the typeface?
The document sets in the studio's stack — Instrument Serif for display, Hanken Grotesk for text. You can switch between a serif and a sans body setting above the preview.
Next tool
Colour accessibility checker
Want this run across your whole product?
A written plan against the ten disciplines.