Before sharing a PDF made from Markdown, open the downloaded file and check that its images are present, diagrams are readable and page breaks preserve the reading order. Search for a sentence and copy a code sample to check whether the text remains usable. A successful export alone does not answer those questions.
This chapter is a review checklist for an output you have already generated. The conversion methods guide covers choosing a tool and exporting the source. Here the task is to decide whether the resulting PDF is ready for its reader. The recommendations draw on format and platform documentation; they are not results from a comparative converter test.
It is part of The Markdown Layer, published by MD2FILE. The editor and extension described below are our products. Their inclusion illustrates workflow choices, not an independent ranking or a promise of identical output across converters.
Rendering adds decisions that Markdown leaves open
The conversion path determines how source becomes pages. Pandoc, for example, documents a default LaTeX route to PDF and alternative intermediate formats, including HTML. Its styling options depend on the selected path. This is one reason the same Markdown source can produce different documents in different tools. Pandoc's PDF documentation.
Paged media introduces its own controls: page dimensions, margins, breaks and running material. Screen layout does not settle those choices. A wide code block may be comfortable in a horizontally scrolling preview and unsuitable for a narrow printed page. CSS paged media documentation.
The workflow is a proposed review process, not a measured funnel. Inspection follows pagination because a heading, table or caption can move when the document gains page boundaries.
Start with assets and explicit requirements
Write down what must survive before choosing an export mode. For a technical report, that might mean selectable code, readable equations, an intact table and diagrams whose labels remain legible at the intended page size. A visual match to a webpage and editable text may require different compromises.
| Element | Inspect before export | Inspect in the downloaded file |
|---|---|---|
| Images | File location, loading and alternative text | Presence, resolution and relationship to captions |
| Mermaid diagrams | Successful rendering and readable labels | Clipping, scaling and page placement |
| Equations | Correct notation and supported rendering | Missing symbols, baseline and line breaks |
| Tables | Clear headers and manageable width | Split rows, repeated context and legible text |
| Code | Correct characters and language labeling | Wrapping, truncation and copied text |
| Links | Correct destination and access | Clickable destination where supported |
Remote images deserve a separate check. Access rules or browser cross-origin restrictions can prevent an image from being fetched during conversion. A preview that displayed an image earlier is insufficient proof that an exporter can retrieve it. Prefer an asset package or deliberately accessible images when the workflow supports them, and inspect the resulting file.
The README-to-PDF guide has a small source-and-PDF example. For diagram notation and formula checks, use the existing Mermaid and LaTeX guide. Documents with Chinese, Japanese or Korean text also need a font coverage review.
Review page breaks with an actual reading task
An illustrative failure is a “Workflow” heading at the bottom of a page with its diagram on the next page. Both elements exist, but their separation makes the document harder to follow. A reader should not need to guess whether the following figure belongs to that heading or the next section.
Possible repairs include reducing an oversized figure, shortening its surrounding text or adjusting the content order. Select the smallest change that preserves meaning. Avoid shrinking an entire report until the labels become unreadable just to achieve a preferred page count.
For a long report, inspect the first page, every section transition and pages containing wide or tall material. Also search for a sentence near the end and copy a representative code sample from the PDF. These checks answer different questions: an attractive screenshot does not prove that the text can be retrieved correctly.
A visually readable PDF is not automatically an accessible or archival-standard PDF. W3C guidance for complex images calls for both a short identification and a fuller text equivalent. Keep the chart's meaning and essential data available as text alongside the visual. W3C complex-image guidance.
Editing and existing-file conversion are different jobs
When the source needs changes, the MD2FILE web editor provides an editing and preview step before PDF or HTML export. Save current work before importing another document. The Markdown-to-PDF methods guide explains the existing controls and shows a downloadable example.
When a .md file is already ready, the MD2FILE Markdown extension provides a separate file-to-PDF workflow. Its public listing describes browser processing with Mermaid, KaTeX and optional CJK support. These capabilities still require review on the actual document; “supports diagrams” does not guarantee that every diagram fits every page size. Chrome Web Store listing.
Browser-side generation also has a narrower meaning than “no network activity.” MD2FILE's standard web PDF path builds the file locally, while usage metadata and optional account, AI or cloud features have separate handling. Remote assets can require requests. The web privacy policy explains the document-content boundary. Extension privacy and permissions should be assessed for the installed version rather than inferred from the website's policy.
If automation, repeated builds or citation processing is the main requirement, a command-line publishing workflow may be more suitable. The existing Pandoc comparison discusses that decision. Saved HTML introduces further layout and resource questions, covered in the HTML-to-PDF guide.
Keep a reproducible handoff
Retain the source, required assets and the version of the released output together. Record the conversion path and any settings that materially affect the document. When an output contains an attached copy of its source, inspect that attachment too; removing visible text from a later presentation is not a reliable way to remove information from the original source.
For a research report, keep a small release note identifying its date, version and corrections. Give readers a canonical web page for updates and a dated download for the fixed edition they used. That arrangement lets a citation refer to a particular document without concealing later corrections.
Part of The Markdown Layer: State of Markdown 2026. Previous: knowledge portability · Research overview · Next: AI conversations as documents · Methodology and limitations.