Your Markdown has three headings, but the exported presentation puts all three sections on one slide. Keep the headings and add a slide separator between the sections. In the Marp workflow used here, a horizontal rule creates the slide boundary; another heading alone does not do that job.
Treat the Markdown file as the editable original and the generated HTML as the presentation output. The example starts with the same short text in two files: one without slide separators and one with two separators. Convert both, then compare the actual slide count before adding images or polishing the theme.
Open the complete example · Download the full HTML source
Start with a small source you can inspect
Use this original fictional briefing about preparing a reading table. It describes an invented arrangement, not an actual event or purchase. Save the following as reading-table.md:
# Reading table
Fictional preparation example.
---
# Materials
- Six booklets
- Two trays
---
# Arrangement
Place three booklets in each tray.
There are three intended slides: Reading table, Materials and Arrangement. The two horizontal rules divide them. For the comparison file, remove only the two --- lines and save it as reading-table-unbroken.md. Keep the headings and all other words unchanged. This isolates the boundary problem from changes in content.
Marp's official introduction shows horizontal rules separating slides. An ordinary Markdown reader may display those rules as lines; the slide converter gives them a different role. The Markdown HTML report workflow is useful when your reader needs a continuous document instead of a deck.
Convert the original, then inspect the output
With the Marp command available in your own environment, run:
marp reading-table.md --template bare -o reading-table.html
marp reading-table-unbroken.md --template bare -o reading-table-unbroken.html
These commands request HTML output using the bare template. The Marp command-line documentation describes HTML conversion and the available templates. The prepared downloads were converted with the official standalone Marp CLI 4.5.1, using Marp Core 4.4.0. You do not need to upload your source to reproduce this local conversion.
Open both generated files. Count rendered slides rather than counting Markdown headings. The broken version should expose the grouping mistake: all three headings belong to one rendered slide. The corrected version should contain three slides, each with its own heading. If your result differs, compare the downloaded source with the file you actually converted and check the converter version and options.
The example's arithmetic is deliberately small: six booklets divided equally between two trays gives three per tray. That number checks the wording on the last slide; it does not establish tray capacity, dimensions or suitability. Replace the illustrative text with your real material before presenting.
Keep the reading view and the native output distinct
The on-page comparison makes the headings and source readable at a narrow width. Its comparison control switches between the unbroken source and the corrected source, and the displayed counts come from the actual converted files. It is a reading aid, not a browser implementation of Marp's presentation controls.
Download the generated HTML to inspect the converter's own output. A fixed slide canvas can scale down substantially on a phone. Check the actual file at the intended display size; making the surrounding article responsive does not make small slide text large. This example does not establish PDF or PowerPoint output, presenter navigation, an offline guarantee or successful delivery through your organization's presentation system.
Hand over both files
Send the generated presentation together with reading-table.md when a colleague will revise the content. Ask them to identify a slide by heading and describe the requested edit. Update the Markdown, convert it again and reopen the new HTML. Editing only the rendered copy leaves the source out of step with the next export.
For a browser presentation that needs navigation and rehearsal, continue with the HTML presentation guide. For this conversion task, finish by checking the three boundaries and the wording in the actual generated file. A clear source-to-output pair is the handoff: your colleague can read the deck and still has the original needed to produce the next version.
Download the corrected Markdown source · Download a blank three-slide source
Download the unbroken Markdown · Download the actual three-slide native HTML · Download the actual one-slide native HTML