A browser preview is not automatically a print proof
Screen content flows through an effectively endless canvas. Print introduces finite pages, margins, repeated furniture, page breaks, widows and orphans, and content that can overflow a fixed width.
MDLoom's Print Proof is an immutable artifact from the canonical PDF renderer. It is refreshed intentionally after edits, which keeps page numbers stable while you inspect them.
Resolve the common layout risks
Wide tables, long unbroken URLs, large diagrams, code with long lines, and missing font glyphs cause many avoidable print failures. MDLoom's current worker measures width overflow, failed inline images, long links, font-loading completion, and Mermaid failures; glyph coverage and page-by-page editorial review remain manual checks.
- Choose paper size and margins before polishing manual page breaks.
- Wrap or refactor code that exceeds the printable measure.
- Use static, high-resolution fallbacks for interactive diagrams.
- Confirm fonts cover every script, emoji, and symbol in the document.
- Keep headings with the first paragraph when practical.
Use precise language about fidelity
MDLoom displays the downloaded canonical PDF blob itself as Print Proof, rather than rendering a second approximation. It does not claim that an office printer, a third-party PDF viewer, and every operating system will rasterize each pixel identically.
Run a preflight before sharing
Review the first page, last page, table of contents, every forced break, headers and footers, and wide content. Check glyph coverage manually for every script you use. Keep the source and artifact hashes plus the server report when reproducibility matters.