A report has a divider between sections, but the next section remains on the same Word page. A visual divider and a required page start are different instructions. Decide which boundary the recipient needs before changing the Markdown source.
Write a visual divider clearly
Pandoc defines a horizontal rule using a line of at least three asterisks, hyphens or underscores. It recommends blank lines around that line to avoid other interpretations.
This short source example separates two paragraphs:
First section ends here.
***
Next section starts here.
Use this structure in the source file, not inside a code block, if you want a divider. The block above only makes the syntax visible for this guide.
Check the downloaded Word document
- Keep the Markdown source and make a small delivery sample.
- Open Markdown to Word and convert the file.
- Open the downloaded DOCX in the destination application.
- Check the divider, the text on both sides and the page on which the next section starts.
- Apply required page breaks in the destination editor and inspect the final document again.
FileMyLove uses Pandoc to convert document structure. This workflow has no page-break placement control. Do not assume a divider guarantees a new page, or repeatedly add dividers to try to move the next heading.
Pick the boundary for the job
| Needed result | Suggested approach |
|---|---|
| Visible separation within the text | A horizontal rule with blank lines around it |
| A named section in the outline | A proper Markdown heading |
| A chapter starting on a new page | Review page-break controls in the destination editor |
| The characters *** printed literally | Put the example in a code block |
Our recommendation is to avoid stacks of blank paragraphs for layout. After final edits, inspect the next heading and the last lines of the preceding page together.
Keep the final check focused
A divider is not a substitute for a meaningful heading. See Markdown headings for Word for document structure. If you wanted the separator characters themselves to remain visible, use literal-symbol examples instead.
Keep both the editable source and the final delivery copy so later revisions do not depend on recreating the layout from memory.



