Extract presentation slides as images

Exported slide decks often land as PDF. You may need individual slide images for a blog, chat, or another tool. Upload “PDF to image” sites take the whole deck first. LocalPdfImg renders pages locally with pdf.js and packs a ZIP when you need more than one image. Bring a deck you already have the rights to use.

Extract PDF slides as PNG or JPG — no upload

This guide is the slide-export job on the same local engine as the converter. You select a page range, choose PNG for sharp UI/text or JPG when photo slides dominate, and download a ZIP. Soft guidance stays about 40 MiB per PDF and about 50 pages rendered per run. Long decks convert in batches by range.

A worked export

Suppose kickoff-deck.pdf has 24 slides and you need slides 4–7 for a chat update. Drop the PDF on the tool, set range 4-7, prefer PNG for UI/text slides (or JPG for photo-heavy ones), keep 2× scale, and convert. Rename the ZIP entries as needed. Nothing was uploaded.

Another pattern: a 60-slide training PDF where you only need the summary block on pages 55–58. Convert that range alone so the tab never paints all 60 canvases at once. Soft guidance of about 50 pages per run is honesty about memory, not a marketing cap.

Steps

1. Export or save your deck as PDF on this device.
2. Open LocalPdfImg, drop the PDF, leave All pages or set a range for the slides you need.
3. Prefer PNG for sharp UI/text slides; JPG for photo-heavy slides when size matters. Soft guidance: ~40 MiB and ~50 pages per run.
4. Use 2× scale for screen sharing; avoid 3× on low-RAM devices.
5. Download the ZIP. Optional proof: DevTools → Network or the trust check.

PNG vs JPG for presentation pages

PNG keeps crisp edges around diagrams, code screenshots, and small labels. JPG shrinks photo-heavy slides more aggressively but can soften thin text. You can export both in one run when you want to compare. Neither format recovers editable PowerPoint shapes — the pixels are a visual capture of the rendered PDF page.

For chat or blog embeds, start at 2×. For a quick preview on a phone, 1× may be enough. If the tab reloads mid-convert, lower scale, shorten the range, or move to a laptop.

Batching long decks without a cloud queue

A 90-slide PDF is a memory job, not a “pro plan” job. Soft guidance of about 50 pages rendered per run means you convert 1-30, then 31-60, then 61-90, downloading each ZIP before the next range. That keeps canvases from stacking until the tab reloads. Prefer a laptop with spare RAM for dense screenshot slides.

Rename files as you go so blog or chat uploads stay ordered. The ZIP names from the tool are practical, not archival. If a later tool needs a single PDF again, that is a merge job outside this site — LocalPdfImg only exports images so the privacy copy stays accurate.

Honest limits

• This is raster conversion, not editable slide recovery. Text stays pixels — we do not claim OCR or “extract editable PowerPoint.”
• Very large decks may hit the soft page limit. Convert in batches by range.
• Animations, speaker notes, and transitions are not preserved — only the visual page render.
• Merge/split of the PDF itself is a different job; this tool only exports images.
• Encrypted decks may fail locally. Unlock a copy you are allowed to open, then retry. This is not a password or DRM bypass.

Chat and blog embeds from a local ZIP

Once you have PNG or JPG files, most chat apps and static blogs accept a direct image upload. That second upload is your choice and happens outside LocalPdfImg. The privacy win for this site is that the original deck PDF was never posted to a converter to obtain those images. If the chat is itself untrusted for the deck content, do not paste the slides there either — local convert does not make an unsafe channel safe.

What a slide image is good for (and not)

Good for: a chat update of four key slides, a blog figure, a static preview in a ticket, or a quick visual handout. Not good for: recovering speaker notes, re-editing shapes, claiming OCR text, or treating the ZIP as a certified archive of the deck. If you need the deck as a PDF packet again after exporting images, keep the original PDF — do not expect round-trip fidelity from pixels.

Internal links for neighboring jobs: JPG for email when the inbox is the destination, and form screenshots when the PDF is a form rather than a deck.

Related guides and policies

Related: JPG for email, form screenshots, why local matters. Publisher and contact: about · contact. Policy: privacy · terms.