If slides disappear when you turn an R Markdown HTML presentation into a PDF, first check whether the content is missing from the generated HTML deck or only from the printed PDF. If it is absent from HTML, inspect the slide boundaries and headings in the source. If it appears in HTML but not in the PDF, investigate the browser’s print preview and print styling—or render a PDF slide deck directly with Beamer instead.
There is no single confirmed cause for an unspecified file. The right fix depends on the R Markdown output format, the conversion route, and where the content first vanishes.
First identify which HTML-to-PDF route you are using
R Markdown presentation formats do not all reach PDF the same way. ioslides_presentation and slidy_presentation produce HTML presentations. For ioslides, the R Markdown reference recommends printing to PDF from Google Chrome. By contrast, beamer_presentation produces a PDF presentation through LaTeX. These are different rendering paths, not interchangeable settings applied to the same finished deck.
| Route | Use it when | Check first |
|---|---|---|
| Print an ioslides HTML deck from a browser | You want to preserve the HTML presentation’s visual styling. | Whether the HTML deck contains every slide; browser print preview; print CSS or template changes. |
| Render with Beamer | You want a PDF slide presentation produced from the R Markdown source. | The Beamer YAML output setting, slide level, and installed LaTeX engine. |
| Inspect slide structure | Slides or their content already appear to be missing in HTML. | Heading levels, horizontal rules, and manual slide breaks. |
The ioslides reference says: “To create a PDF version of a presentation you can use Print to PDF from Google Chrome.” It also notes that print-CSS support affects results and names Chrome as having the best support at the time that documentation was written. That is guidance, not a guarantee for every browser version, custom stylesheet, or presentation.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
Determine where the missing material disappears
- Read the YAML output setting. At the top of the
.Rmdfile, identify whether the output isioslides_presentation,slidy_presentation, orbeamer_presentation. This tells you whether the path is HTML followed by browser printing or direct PDF output through Beamer. - Open the generated HTML deck. Navigate through the entire presentation and look for the first missing slide or item. Check the HTML deck itself, not only the PDF.
- Compare the two results. If the content is absent in HTML, focus on the source document and slide structure. If it is visible in HTML but not in the saved PDF, focus on printing, pagination, and print styling. This comparison narrows down the stage where content is lost; it does not by itself identify the cause.
- Record the first failure. Note the slide title or content that vanishes, its position in the deck, and whether later slides are also affected. A precise first example is more useful than a report that the page count “looks wrong.”
If the content is already missing from the HTML deck, inspect slide boundaries
Pandoc uses a selected slide level to determine which headings start slides. It also treats horizontal rules as slide starts. If the slide level is not explicitly set, Pandoc infers it from the document structure. A heading at an unexpected level, or a separator in the wrong place, can therefore change how content is grouped into slides rather than create the slide you expected.
Review nearby headings and separators
- Check the heading immediately before the missing content and the next heading after it. Confirm that the heading levels match the presentation’s intended slide structure.
- Look for horizontal rules around that section. Pandoc treats them as slide starts, so a misplaced rule can alter where a slide begins.
- Check whether an intended manual break is present. The R Markdown lesson documents
***as a manual slide break. - Compare the generated deck’s slide sequence with the source in order. This can reveal whether the content was omitted or simply grouped into a different slide than expected.
Make one structural change at a time, regenerate the HTML, and check the same location again. If the item is still missing before printing, adjusting browser print settings will not restore content that the HTML deck never contains.
If the HTML is complete, inspect browser print preview
When all slides and content appear in the HTML deck, use the browser’s Print to PDF route for ioslides and examine the preview before saving. Check whether the missing slide is absent in the preview or whether content is being clipped, split, or moved across printed pages. This distinguishes a print-output problem from a later problem with the saved file.
Rank #2
- Open the complete HTML presentation in the browser.
- Choose the browser’s print function and select its PDF destination.
- Inspect the preview from the first page onward, watching for the first point where the printed sequence differs from the HTML deck.
- If a slide is absent in the preview, temporarily remove custom print CSS or template changes and compare the preview again.
The R Markdown documentation describes configurable CSS and templates, making them relevant things to inspect; removing custom changes is a diagnostic test, not a guaranteed fix. If the preview changes after that test, review the custom print rules in small pieces to find which change affects the output. If it does not, restore the styling and continue investigating the browser’s print behavior and the presentation structure.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe ioslides reference recommends browsers with good print-CSS support and names Chrome as having the best support “as of this writing.” Because the documentation’s wording is time-relative and does not promise identical results across current browser versions or custom CSS, compare the actual preview rather than assuming that another browser will behave identically.
When a PDF slide deck is the goal, consider Beamer
If the intended deliverable is a slide-shaped PDF generated from the R Markdown source, beamer_presentation is the documented direct PDF presentation route. It uses a LaTeX engine rather than printing a finished HTML deck. This may suit the target format better, but it is a different rendering path and does not guarantee that a particular source document will render without adjustment.
A minimal output setting looks like this:
output: beamer_presentationBeamer’s documented settings include slide_level, keep_tex, and latex_engine. The reference lists pdflatex as the default engine and names pdflatex, xelatex, and lualatex as engine choices. Verify the available settings against the R Markdown version installed on your system before relying on a particular option.
Keep the intermediate TeX when you need to diagnose rendering
Set keep_tex: true in the Beamer output settings if you need to inspect the intermediate .tex file. This helps locate whether the material made it from the R Markdown source into the generated TeX. It does not by itself repair the output; it gives you another point in the rendering path to inspect.
Free tools Windows power users keep installed
One-click scans. No signup required.
If the issue concerns which source headings become slides, review slide_level alongside the document’s heading structure. If the PDF fails during generation, check that the configured LaTeX engine is installed and available. Do not treat a Beamer issue as a browser-pagination issue: Beamer bypasses the HTML browser-print stage.
Common symptoms and next checks
| Symptom | Likely stage to inspect | Next check |
|---|---|---|
| The slide is not present when navigating the HTML deck. | Source structure or HTML generation. | Check heading levels, the selected slide level, horizontal rules, and *** breaks. |
| The HTML slide is visible, but absent in print preview. | Browser printing or print styling. | Inspect print preview, then compare after temporarily removing custom print CSS or template changes. |
| The preview contains the slide, but the saved PDF does not match it. | The step after preview, or the saved output itself. | Save a new PDF and compare it with the preview at the first point of difference; record the browser and print route. |
| A Beamer PDF is missing a slide or content. | Beamer rendering and source-to-slide structure. | Check slide_level, the LaTeX engine, and the retained .tex file if keep_tex is enabled. |
What to collect if the problem remains
A specific diagnosis requires more than the statement that pages are missing. Keep these details together when asking for help or comparing a corrected output:
- The complete YAML output setting and relevant presentation options.
- The R Markdown and Pandoc versions.
- The source
.Rmd, generated HTML, and resulting PDF. - The browser and version, if printing HTML, and the exact print-to-PDF method.
- Any custom CSS or template changes.
- The first slide or page that differs, with a description of what is missing.
These details identify whether the failure occurs during source structuring, HTML generation, browser printing, or Beamer rendering. Without them, the documented workflows support a diagnostic process, but not a case-specific root-cause finding.
Or skip the browser setup
If you only need a screenshot of a publicly reachable HTML page—not conversion of an entire multi-slide R Markdown deck—ScreenshotNeo can return a webpage screenshot through one GET request. It is not a substitute for diagnosing missing slides or for generating a complete slide-deck PDF.
Best Value
Example cURL request for a hosted HTML page; replace the example URL with your publicly reachable page. See the ScreenshotNeo API documentation for setup and options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://your-site.example/slides.html -o shot.webp- Before a capture, ScreenshotNeo accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of these steps can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Each response includes
X-Page-VerdictandX-Billedheaders. - An MCP server provides
take_screenshot,get_page_info, andcapture_pdftools for Claude, Cursor, and other MCP clients. - The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. All features are available on every plan.
Sign up for ScreenshotNeo’s free plan to try 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
