August 6, 2026PDF Layout & Page Breaks

Written and tested by the MD Converter editorial team

Recommended Markdown PDF Settings by Document Type

Compare practical Markdown PDF settings for specifications, proposals, meeting minutes, reports, technical documents, and minimal handouts.

There is no universal best PDF setting

Narrow margins fit more information but reduce breathing room and space for handwritten review. A cover and table of contents are valuable in a long specification but excessive in one-page minutes. Page numbers help control printed sets, while a simple flyer may not need them. Choose settings from the document's purpose, audience, length, and printing requirements rather than personal preference alone.

Recommended settings at a glance

Document	Margin	Body size	Cover	TOC	Numbering	Background
Japanese specification	10mm	13–14px	Yes	Yes	1/n	White
Proposal	15mm	14–15px	Yes	If 3+ pages	1/n	White or pale color
Meeting minutes	15mm	13–14px	Optional	Usually no	For multiple pages	White
Report	20mm	14px	Yes	Yes	1/n	White or ivory
Technical document	10mm	13px	Yes	Yes	1/n	White
Minimal handout	20mm	14px	No	No	Optional	White

Treat these values as starting points. If wide tables, code, or images do not fit, restructure them before making all text smaller.

Japanese specifications and design documents

Requirements, basic designs, and detailed specifications contain dense information that readers revisit by chapter. Start with a 10mm margin and 13–14px body text, then enable a cover, TOC, and 1/n page numbering. The total count helps a reader detect missing printed sheets.

A practical cover contains the document title, system, organization, author, date, and version. A restrained centered title and metadata block usually fits Japanese internal documentation better than decorative artwork. Use H2 for chapters and H3 for supporting topics so the TOC remains useful. See the Japanese-style Markdown system design template.

Do not solve every wide table by approaching zero margin. Reduce the number of columns first. Printers that do not support borderless output can still clip content close to the physical edge.

Proposals

A proposal needs visual rhythm as well as information density. Begin with a 15mm margin and 14–15px body text. Put proposal name, recipient, sender, and date on the cover. Add a TOC when Problem, Proposal, Benefits, and Schedule create three or more substantial pages; omit it for a short pitch so the conclusion appears sooner.

A page background can reinforce a brand, but a saturated background consumes ink and reduces readability. Prefer white or a very pale tint, with stronger colors reserved for the cover and heading accents. Browser print settings may suppress background graphics, so inspect the print preview before saving.

Meeting minutes

Minutes prioritize decisions and actions. A 15mm margin, 13–14px text, and white background are dependable. Skip the cover and TOC for a one- or two-page weekly meeting; put the meeting name, date, and attendees at the top. Add formal front matter only for longer governance or steering records.

A single page does not need numbering. For a printed multi-page record, enable 1/n and keep the decision list and action table away from awkward page boundaries. Start with the Markdown meeting-minutes template.

Reports and research documents

Monthly reports, investigation results, and incident reviews benefit from a 20mm margin, 14px text, and slightly generous line spacing. Add a cover, TOC, and 1/n numbers. Organize Summary, Method, Results, Analysis, and Conclusion as H2 sections. Wider margins give reviewers somewhere to write comments.

A pale ivory background can feel comfortable on screen, but white remains safest for formal submission and high-volume printing. Check chart contrast and transparent images against any non-white background.

Technical and API documentation

API specifications and operational procedures need width for code and tables. Start at 10mm and 13px with a white background, cover, TOC, and numbering. Do not reduce code until it is unreadable: split long lines, remove irrelevant logs, and replace raw URLs with descriptive links.

Use H2 for features or endpoint groups and H3 for requests, responses, and errors. Split a five-column table into a summary and detailed prose when possible. The ChatGPT prompt collection for design documents can help create a structured first draft.

Minimal handouts

A one- or two-page notice, checklist, or internal memo often works best with a 20mm margin, 14px body text, no cover, and no TOC. Add numbering only when the printed result spans several sheets. Rely on one H1, a few H2 sections, and short lists.

Minimal does not mean undesigned. Consistent spacing, type size, and heading hierarchy—plus fewer borders and colors—let the information itself become the design.

How to choose margins

Ten millimeters is useful for dense technical content, 15mm for general business documents, and 20mm for reports that emphasize reading comfort or handwritten review. Applying one value to all sides keeps the setup understandable and prevents unexpected visual shifts.

The browser print dialog may apply its own margin in addition to the document's @page rule. Browser and printer behavior cannot be made identical in every environment. Check that the outer white area has not doubled. Hardware without borderless printing may retain a physical margin even when software requests zero.

Prefer 1/n page numbering

When numbering is enabled, 1/7 communicates more than a standalone 1. It helps detect an incomplete printout, a failed PDF merge, or a partial attachment. Decide whether the cover belongs in the count according to your organization's rule, then use that rule consistently.

Pagination changes when page breaks move, so verify the numbers in the final saved file rather than trusting an earlier preview.

Use page background colors carefully

Apply one background consistently across the document instead of changing every page. Pale gray, ivory, or a highly diluted brand color are reasonable choices. Maintain sufficient contrast and ensure the hierarchy survives grayscale printing.

Photographs, transparent PNGs, white logos, and fine black lines may look different on a tint. Inspect a cover page, a normal body page, and an image-heavy page. Also verify the browser option for printing background graphics.

Save a baseline for each document type

For specifications, proposals, meeting notes, reports, and technical documents, save a coordinated baseline covering the cover, TOC, margins, numbering, and typography. Start each new document from the closest baseline and change only what the actual content requires.

This workflow is faster and produces more consistent documents than deciding every control from zero for each file.

Pre-save checklist

The selected baseline matches the document's purpose
Body text is comfortable at 100 percent
Tables and code remain inside the page width
Cover title, organization, date, and version are correct
H2 page references in the TOC match the body
The denominator in 1/n equals the final page count
No heading is stranded at the bottom of a page
Text and images contrast sufficiently with the background
Browser print margins have not created excessive whitespace
The saved PDF has been reopened and inspected

FAQ

Do smaller margins always improve the document?

They fit more content, but reduce reading comfort and print safety. Simplify tables and prose first, then narrow margins only when necessary.

Should every PDF have a cover and TOC?

No. They help long specifications and reports but slow down readers of a one-page handout or short meeting record.

Why is my background missing from the PDF?

Check whether background graphics are disabled in the browser print dialog. Color can also vary by printer and PDF viewer, so inspect the actual saved file.

Can settings vary on individual pages?

Keeping margins, page numbering, and background global makes the document easier to understand and export reliably. For a genuinely exceptional page format, consider exporting it separately and combining the final documents.

Summary

More controls do not automatically produce a better PDF. Specifications prioritize reference, proposals prioritize flow, minutes prioritize actions, reports prioritize comfortable reading, and technical documents prioritize usable information density. Start from a document preset and adjust margins, body size, cover, TOC, 1/n numbering, and background only where the content demands it.

Create a Markdown PDF with recommended settings