Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
First find out whether the slides are missing from the generated HTML deck or only from the PDF. If they are absent in HTML, check the R Markdown source and slide boundaries. If they appear in HTML but not in the PDF, investigate the browser’s print preview, print CSS, and conversion route. For a PDF slide deck generated directly from the source, consider Beamer instead of printing an HTML presentation.
Identify which conversion route you are using
R Markdown has different presentation formats, and they do not all produce PDF by the same route. ioslides_presentation and slidy_presentation produce HTML presentations. Printing one of those decks to PDF adds a browser’s print and pagination behavior to the process. beamer_presentation, by contrast, is an R Markdown format for producing a PDF presentation through LaTeX.
Start with the output value in the document’s YAML header. For example:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows 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 reinstall---
title: "Quarterly review"
output: ioslides_presentation
---If that is your format, render the HTML deck first and print it from a browser. The ioslides documentation describes this route directly: “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 deck.
#1 Best Overall
If the desired result is a slide-shaped PDF built from the R Markdown source rather than a printout of the HTML, try Beamer. These routes can differ in layout and styling; switching formats is a workflow choice, not a setting that makes browser printing and LaTeX rendering interchangeable.
Check whether the missing content is in the HTML deck
- Render the R Markdown document to HTML. Use the same source file and output format that you use for the failing conversion.
- Open the resulting HTML and navigate through the full presentation. Check the slide before and after each suspected omission, not just the opening screen.
- Compare the deck with the PDF. If the slide or content is already absent in HTML, focus on the source structure, slide boundaries, and rendering. If it is visible in HTML but absent in the PDF, focus on browser printing or pagination.
- Record the first discrepancy. Note the slide title or content, the corresponding PDF page if any, and whether the print preview already omits it. This narrows the point in the workflow where the loss occurs.
This comparison is a diagnostic method, not a determination of the cause in any particular file. Without the source, generated HTML and PDF, browser details, and an example of the missing content, the specific failure cannot be identified.
Inspect slide boundaries and heading levels
When material is missing in the HTML presentation itself, check whether the source actually defines the slide you expect. Pandoc uses a selected slide level to decide which headings start slides; it also treats horizontal rules as slide starts. If the slide level is not explicitly set, it is inferred from the document structure. A heading at an unexpected level or a separator in the wrong place can therefore change where slides begin.
- Inspect the headings immediately around the missing material. Confirm that an intended slide heading is at the expected level.
- Look for horizontal rules near the affected passage. Pandoc may interpret one as a slide boundary.
- Check whether content was placed between boundaries in a way that makes it part of a preceding slide, rather than a new slide.
- For a manual break in the documented R Markdown lesson’s example, use
***as the slide separator where appropriate.
After editing the structure, render HTML again and navigate the deck before testing PDF output. This separates a source-structure correction from a print-settings change.
Rank #2
When the slides exist in HTML but disappear in PDF
Use print preview to locate the loss
For an ioslides deck, open the generated presentation in a browser and choose its Print to PDF workflow. Inspect print preview before saving. Check the page count and identify the first point at which the expected slide or content disappears. If the preview already lacks it, saving the PDF again is unlikely to restore it; the issue is upstream in the browser’s print rendering or the page layout it receives.
Print behavior can depend on the browser’s support for print CSS, the presentation’s styles, and any custom CSS or template changes. If the document uses custom print styling, temporarily remove those modifications and compare a fresh preview with the original. This is a troubleshooting test, not proof that custom CSS caused the problem. Restore the styles after the test and make any correction narrowly, so that an intended on-screen layout is not accidentally changed.
Try a Chrome-based print route
The ioslides reference recommends printing to PDF from Google Chrome and says browser print-CSS support matters. A separate route mentioned in R Markdown: The Definitive Guide is pagedown::chrome_print(), which uses Chrome to print an R Markdown document or HTML file to PDF. Treat it as an alternative to test, not as a guarantee that every missing-page problem will be fixed. Compare its preview or output against the browser’s ordinary Print to PDF result.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChange one variable at a time
For a useful comparison, keep the same rendered HTML and change only one factor per attempt: browser or printing method, then custom print CSS or template. Record whether the first missing page moves, appears, or remains absent. Changing the source, browser, and styling together makes it harder to tell which change affected the output.
Render a PDF presentation with Beamer instead
If you need a PDF slide deck and do not need to preserve the HTML deck’s exact visual styling, try beamer_presentation. A minimal YAML change looks like this:
---
title: "Quarterly review"
output: beamer_presentation
---Beamer renders through a LaTeX engine, so this changes the production route rather than adjusting browser pagination. The documented options include slide_level, keep_tex, and latex_engine. The reference lists pdflatex as the default engine and supports selecting pdflatex, xelatex, or lualatex. Check the documentation for the R Markdown version installed in your environment before relying on a particular option or default.
To retain the intermediate TeX file for inspection, add keep_tex: true under the output format:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
---
title: "Quarterly review"
output:
beamer_presentation:
keep_tex: true
---If the PDF build fails or omits a slide, inspect the retained .tex output alongside the source and rendered PDF. Confirm that the intended slide content reached the TeX stage before treating the issue as a PDF viewer or pagination problem. If it is missing from the TeX output, revisit the source and slide structure; if present, investigate the LaTeX build and its output.
Choose the route that matches the result you need
| Route | Best fit | First checks |
|---|---|---|
| Print ioslides HTML from a browser | You want to retain the HTML presentation’s visual styles in a PDF. | Confirm the deck is complete in HTML; inspect browser print preview, print CSS, and browser behavior. |
| Render with Beamer | You want a PDF slide presentation generated directly from the R Markdown source. | Check Beamer output settings, slide level, LaTeX engine, and retained .tex if needed. |
| Inspect Pandoc/R Markdown slide structure | Slides or content are already missing in the HTML deck. | Review heading level, horizontal rules, and any manual *** breaks. |
Troubleshooting by symptom
A slide is absent from both HTML and PDF
Do not start by changing browser settings. Check that the source contains the content, then inspect nearby headings, separators, and the selected slide level. Render HTML again after each structural change and verify the slide there.
The slide is visible in HTML but absent in print preview
Test the browser’s print-to-PDF route and check the print styling. If you use custom CSS or a template, compare with those modifications temporarily removed. A Chrome-based print route is also worth testing for an ioslides deck, but outcomes can vary with the browser version and presentation styling.
The slide is in print preview but not in the saved PDF
Compare the preview with the saved file and confirm that you are viewing the newly saved PDF. If the discrepancy persists, note the browser and version, the selected PDF destination, and the first affected page; those details are needed to distinguish a print-output issue from a stale or different file.
Beamer cannot build the PDF
Check that a LaTeX engine is installed and that the configured engine is available to the R Markdown installation. The documented engine choices include pdflatex, xelatex, and lualatex; the default is documented as pdflatex, but verify the installed version’s behavior. Retain the intermediate TeX with keep_tex: true to see whether the missing material reached the LaTeX stage.
Best Value
The cause remains unclear
For a focused diagnosis, gather the output YAML, R Markdown and Pandoc versions, resulting HTML and PDF, browser and version, exact print-to-PDF method, any custom CSS or template, and one example of the omitted slide or page. Without those details, the evidence supports a workflow for isolating the problem but not a case-specific root cause.
Or skip the browser setup
If your goal is to capture a particular rendered HTML page for inspection, ScreenshotNeo can return a website screenshot or PDF from one GET request. It is not a replacement for rendering an R Markdown slide deck as a paginated PDF: use the browser or Beamer workflow above for that. ScreenshotNeo’s cookie handling and page checks can help when capturing a web page, and its API can be used without configuring a local browser-print workflow.
ScreenshotNeo API documentation
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://your-hosted-deck.example/presentation.html -o shot.webpBefore a capture, ScreenshotNeo accepts cookie or consent banners 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, and responses identify the page verdict and billing status in headers. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Free tools Windows power users keep installed
One-click scans. No signup required.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently Asked Questions
What information should I provide when asking someone to diagnose the problem?
Share the relevant output YAML, the first missing slide or page, and whether that content appears in the generated HTML and print preview. Include the R Markdown and Pandoc versions, browser and version, print method, and any custom CSS or template.
Does Beamer preserve the appearance of my HTML slides?
Not necessarily. Beamer and browser printing are different rendering routes; choose based on whether you need a PDF slide deck or a PDF that retains the HTML presentation’s styling.
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.
Recommended Free Tools
