Does Markdown support page breaks?

Standard Markdown does not define a page-break feature. The converter, raw HTML, or print CSS must provide that behavior.

You can use it in a pipeline that preserves raw HTML and applies matching print CSS. Sanitizers or other renderers may remove or ignore it.

Why does my page break create a blank page?

A preceding break, a forced break on the next element, or an element that already starts a new page can create an empty page. Inspect the generated HTML and CSS.

Should every Markdown heading start on a new page?

Usually no. Reserve forced breaks for major sections where pagination supports navigation. Let normal content flow for shorter sections.

Add Page Breaks to Markdown PDF

Markdown has no standard page-break syntax. Add page breaks through the PDF conversion tool, a supported raw HTML element, or print CSS such as `break-before: page`. The correct method depends on whether your pipeline renders Markdown to HTML first or converts it through a document format. Test the generated PDF because headings, tables, code blocks, and images can change pagination. Keep page-break instructions separate from ordinary prose when possible, so the source remains portable to web and text outputs.

Why Markdown needs a converter rule

Markdown describes content structure rather than physical pages. A heading, paragraph, or list does not specify where a printer should end one page and begin another. Page size, margins, font metrics, line spacing, headers, footers, and table layout all affect pagination. A converter can add physical page controls during rendering. HTML-based pipelines commonly use print CSS. A document converter may support a raw block, a special command, or a reference template. These approaches are tool-specific. Do not assume that a page-break marker supported by one application will work in another. Record the converter, version, and configuration with the build.

CSS method for HTML-based pipelines

If Markdown becomes HTML before PDF generation, create a class that requests a page break before the next content block. A simple source marker can use raw HTML, such as `<div class="page-break"></div>`. The print stylesheet can define `.page-break { break-before: page; }`. Older engines may require `page-break-before: always`, although modern CSS uses the `break-*` properties. This method keeps the break explicit and easy to locate, but raw HTML may reduce portability. Some Markdown renderers sanitize or remove it. Place the marker between complete blocks, not inside a paragraph or list. If the engine supports it, also control orphaned headings, table splitting, and code-block overflow with print CSS.

Tool-specific and layout checks

Some converters accept a page-break command or a raw document block. Follow the selected tool's manual rather than copying syntax from a different pipeline. For example, a Markdown-to-Word-to-PDF workflow may interpret page breaks through a reference document, while a browser-based workflow uses CSS. After conversion, inspect every intended break. Confirm that the following heading remains with its introductory paragraph, tables do not lose headers, code remains readable, and images fit within the printable area. Generate a PDF from a clean build and compare page counts when content changes. Fixed breaks can create large blank areas, so use them only at meaningful boundaries such as chapters, appendices, or title pages.

How do you do it step by step?

1Identify whether the pipeline uses HTML and CSS, a document format, or a direct PDF renderer.
2Check the converter documentation for raw blocks, page-break commands, and print options.
3Add a break between complete Markdown blocks at a meaningful document boundary.
4Configure page size, margins, headers, footers, and break behavior before fine tuning.
5Open the PDF and inspect pagination, headings, tables, code, images, and blank areas.

Working example

An HTML-based pipeline can use a source marker and print CSS.

Input

## Installation

Complete the installation steps.

<div class="page-break"></div>

## Configuration

Set the required environment variables.

Result

The PDF places the Configuration heading on a new page when the renderer preserves the div and applies the print stylesheet.

The example depends on raw HTML support and a CSS-aware PDF renderer. If either condition fails, use the converter's documented page-break feature.

Frequently asked questions

Does Markdown support page breaks?: Standard Markdown does not define a page-break feature. The converter, raw HTML, or print CSS must provide that behavior.
Can I use `<div class="page-break"></div>`?: You can use it in a pipeline that preserves raw HTML and applies matching print CSS. Sanitizers or other renderers may remove or ignore it.
Why does my page break create a blank page?: A preceding break, a forced break on the next element, or an element that already starts a new page can create an empty page. Inspect the generated HTML and CSS.
Should every Markdown heading start on a new page?: Usually no. Reserve forced breaks for major sections where pagination supports navigation. Let normal content flow for shorter sections.