PDF to PowerPoint
Turn every page of a PDF into a slide — rendered as an image, sized to fit, packaged as a real .pptx.
Drag & drop a PDF here
or click to select a file — PDF only
About PDF to PowerPoint
Drop in a PDF and get back a .pptx in which every page has become a slide. Pages are rendered with pdf.js at the resolution you choose, placed on slides sized to match the document, and packaged into an Office Open XML archive — all inside this browser tab, with no upload and no server.
The slides are pictures
Say it once more, because it decides whether this tool is right for you: each slide contains a single image of a page, and nothing else. There are no text boxes to click into, no bullet levels, no shapes and no editable objects. You can reposition or crop the picture, layer your own annotations over it, and use the deck to present — but you cannot retype a heading.
That is not a shortcut; it is the honest ceiling of the format. A PDF page records glyphs at coordinates, vector paths and images. It does not record that a run of text was a title, that three lines belonged to one list, or that a rectangle and a caption were grouped. Any converter promising editable slides is inventing that structure, and what it invents is usually dozens of overlapping text boxes in substituted fonts. Rasterising instead guarantees pixel-for-pixel fidelity to the original page.
Deck size and letterboxing
A PowerPoint deck has one size for all its slides, while a PDF can change page size from page to page. On Auto, the first page is measured and the deck is set to whichever of 16:9 (10 × 5.625 in) or 4:3 (10 × 7.5 in) is closer to its shape. Every page is then scaled to fit inside that slide and centred, so nothing is ever cropped and any difference in shape appears as white space. A portrait A4 page is much taller than either deck, so the bands are wide: on 4:3 the page fills about 5.3 of the 10 inches and leaves roughly 2.3 inches white at each side, and on a widescreen deck it fills about 4 inches and leaves 3 at each side. Choosing Match the PDF page exactly defines a custom deck the same size as the first page — 8.27 × 11.69 inches for A4 portrait — and the first page then fills it edge to edge. That mode obeys one hard rule of the file format: a slide edge must be between 1 and 56 inches. A page outside that range is scaled to the nearest size that fits with its shape intact, and the note under the dropdown says so. The single shape that cannot be matched is one longer than 56:1 — a till receipt or a banner — because shrinking the long edge to 56 inches would take the short edge under an inch and produce a file PowerPoint offers to repair; there the deck is set to the closest legal size and the page is fitted inside it.
There are ceilings on the raster too, and they are worth separating. The first belongs to the slide. A page image is displayed at the size of the slide, not the size of the page, so a page that has to shrink to fit gets denser as it goes: a 200-inch drawing asked for at “2× the page” would be a 2,185 DPI picture on a 7½-inch slide, which needs a 268-megapixel canvas — over a gigabyte of memory — to produce a 4.8 MB deck holding one slide. Nothing in PowerPoint, on a projector or on paper can resolve that, so the render stops at 1,000 DPI of finished slide. The same slide then comes out of a 20-megapixel canvas at about a megabyte and is indistinguishable to look at. The ceiling only engages once a page is roughly five times larger than the slide it must fit inside — a portrait A4 at 3× on a widescreen deck is 449 DPI and an A2 is 900 — so ordinary documents are rendered at exactly the multiplier you asked for.
The second ceiling belongs to the browser. A canvas holds about 268 million pixels and no more than 32,767 on a side; over that, encoding quietly returns an empty image instead of failing, which is exactly how other converters end up shipping a blank slide inside a deck that reported success. Each page is measured against that limit as well and rendered at the highest multiplier that fits, stepping down repeatedly — as far as a twentieth of full size — if your browser’s real limit is tighter than the numbers above. When the deck is saved, pages that stopped at the slide ceiling are listed as having lost nothing you can see, and only pages the browser pushed below 300 DPI of slide are flagged as softer. A page that cannot be rendered at all is left out and named rather than added blank, so the slide count you are shown is always the number of slides that carry a picture.
Resolution, format and file size
- The multiplier is the page’s DPI. A PDF point is 1/72 inch, so 1× renders at 72 DPI, 1.5× at 108, 2× at 144 and 3× at 216. An A4 page at 2× is about 1190 × 1684 pixels.
- What lands on the slide can differ. A page shrunk to fit gets denser and is capped at 1,000 DPI of slide; a page enlarged to fill the slide gets thinner, so a small-format PDF is worth converting at 3× or with Match the PDF page exactly.
- 2× is the sweet spot for anything shown on a screen or a projector. 3× is for printed handouts or very fine print; beyond that you only pay in memory and megabytes.
- PNG keeps type crisp. Lossless compression is very efficient on the flat white of a document page, so PNG is both the default and usually the best-looking choice.
- JPEG is for photographs. It is far smaller on image-heavy pages, at the cost of a faint halo around small text. 80–85% is a sensible band.
- Range conversion lets you take five pages out of a two-hundred-page report without loading the rest into a deck.
When to reach for something else
If you want the words rather than the picture, PDF to Text gives you the raw text layer and PDF to Word rebuilds paragraphs you can edit; paste either into your own slide template and you will get a better deck than any automatic conversion. If you only need images to drop into an existing presentation, PDF to JPG and PDF to PNG hand you the pages as separate files or a ZIP. To trim the document before converting, use Split PDF or Organize PDF. An encrypted document has to pass through Unlock PDF first, because a renderer cannot draw a page it cannot decrypt.
One slide per page, sized to match
Each page is rendered to a bitmap and placed on its own slide, scaled to fit and centred so nothing is cropped. The deck is set to 16:9 or 4:3 by measuring the first page, or to the exact page size if you would rather have no letterboxing at all — within the 1 to 56 inch range PowerPoint allows on a slide edge.
Resolution and format you control
Render at 1×, 1.5×, 2× or 3× the page size — 72 to 216 DPI — as lossless PNG or as JPEG with a quality slider. A text-heavy report at 2× PNG looks perfect on a projector; JPEG at 80% cuts the file to a fraction of the size. A page several times bigger than the slide stops at 1,000 DPI of slide, because nothing past that is visible in a deck.
A real .pptx, built in your browser
The output is genuine Office Open XML that opens in PowerPoint, Keynote, LibreOffice Impress and Google Slides with no import step. Rendering and packaging both happen in this tab — the PDF is never uploaded.
Frequently Asked Questions
Will I be able to edit the text on the slides?
No, and this is the most important thing to know before you start. Every slide holds one picture of a page and nothing else — there are no text boxes, no bullet placeholders, no shapes and no editable objects. You can move, crop, resize or delete the picture, and you can add your own text boxes on top of it, but you cannot click into a sentence and retype it. That is a deliberate trade: rasterising is the only conversion that is guaranteed to look exactly like the original PDF, because it copies what the page draws rather than guessing at what it means.
Why can no tool turn a PDF into editable slides properly?
Because a PDF page has no slide structure to recover. It stores glyphs at coordinates, vector paths and images — it does not record "this is a title", "this is a three-item bullet list", "this box is a group". Converters that claim editable output reconstruct those objects by guesswork, and the result is usually a mess of overlapping text boxes in the wrong fonts that takes longer to repair than to rebuild. If you need to edit the words, take them out with PDF to Text or PDF to Word and paste them into a real slide template.
How is the slide size chosen?
On Auto, the first page is measured and its width-to-height ratio compared against 16:9 and 4:3; whichever is closer wins for the whole deck. A landscape presentation PDF therefore lands on a widescreen deck, while an A4 report — which is taller than 4:3 is — lands on 4:3 with white bands down the sides. Choosing "Match the PDF page exactly" instead defines a custom deck the same size as the first page, so a portrait A4 gives you an 8.27 by 11.69 inch portrait deck with the image filling it edge to edge. PowerPoint only permits 1 to 56 inches on a slide edge, so a page outside that range is scaled — shape intact — to the nearest size that fits, and the note under the dropdown tells you when that has happened. One shape cannot be matched at all: a page longer than 56:1, such as a metre of till receipt, since shrinking it to 56 inches would push the other edge below one inch. There the deck becomes the closest legal size and the page is fitted inside it with bands, which is the only alternative to a file PowerPoint offers to repair.
Why are there white bands around some slides?
Because the page shape and the slide shape are not identical. Each image is scaled to fit inside the slide and centred, which preserves the aspect ratio and never crops content, so any leftover space shows as background. A portrait A4 page loses roughly a quarter of the slide width to white at each side on a 4:3 deck, and closer to a third on a widescreen one; that is the geometry, not a bug. Use "Match the PDF page exactly", or accept the bands and crop the picture inside PowerPoint if you would rather it bleed. A document whose pages are not all the same size will letterbox differently from slide to slide, since the deck can only have one size.
Which resolution should I pick?
A PDF point is one seventy-second of an inch, so the multiplier maps directly to the DPI of the page: 1× is 72, 1.5× is 108, 2× is 144 and 3× is 216. Two times is the right default — an A4 page becomes about 1190 by 1684 pixels, which is sharper than any projector and still reasonable in file size. Go to 3× only if the deck will be printed as handouts or if the pages carry very fine print. Two things are worth knowing about how that multiplier lands on a slide. A page much bigger than the slide is shrunk to fit, which multiplies its density: a five-foot-wide site plan squeezed onto a 7½-inch slide carries well past a thousand dots per inch at 3×, so the render stops at 1,000 DPI of slide instead and the summary names the pages that hit the ceiling — the picture looks identical and the file is a fraction of the size. A page much smaller than the slide has the opposite problem: it is enlarged to fill the slide, so its density drops. A business card at 2× is only about 50 DPI once it is blown up across a widescreen deck, and the only cure is to pick 3× or to choose "Match the PDF page exactly" so it is never enlarged at all.
PNG or JPEG?
PNG is lossless and handles the large flat white areas and crisp black type of a document page extremely well, so it is the default and usually looks best. JPEG throws away detail to save space and puts a faint grey halo around small text, but on photographic or heavily coloured pages it can be five to ten times smaller. The practical rule: text and diagrams stay on PNG, scanned photographs and image-heavy brochures go to JPEG at 80 to 85 percent. Try one page each way if the deck has to be emailed.
My deck came out enormous.
That is the arithmetic of bitmaps. Thirty A4 pages at 2× PNG is thirty images of roughly two megapixels each, and the PPTX container barely compresses data that is already compressed. Drop to 1.5×, switch to JPEG, or convert a page range instead of the whole document. Converting more than about sixty pages in one pass also risks exhausting the tab, since every rendered page is held in memory until the file is written.
Are links, comments and form fields carried over?
Their appearance is, their behaviour is not. The renderer paints annotations that carry an appearance stream, so highlights, sticky-note icons, stamps and the values typed into form fields all show up in the picture exactly as a PDF reader displays them. But a hyperlink becomes blue underlined pixels with nothing behind it, a form field becomes a picture of a filled box, and bookmarks and the document outline are dropped entirely.
Nothing happened, or a slide came out blank.
An encrypted PDF cannot be parsed at all — run Unlock PDF first — and a damaged or partly downloaded file fails the same way, so re-download it or re-export it from a reader. Genuinely enormous pages are the third cause, and the tool handles them itself, under two separate ceilings. The first is the slide: a picture is never rendered past 1,000 dots per inch of finished slide, because a deck cannot show more than that and the pixels are pure file size — that is what stops a two-metre page at 2× from demanding a 268-megapixel canvas and a five-megabyte deck for one slide. The second is the browser: a canvas tops out at roughly 268 million pixels of area and 32,767 pixels on a side, and some browsers stop far earlier (iOS Safari near 17 megapixels). Every page is measured against both, rendered at the highest multiplier that fits, and retried at progressively lower ones — all the way down to a twentieth of full size — if the browser turns out to be tighter than advertised. A page that still cannot be encoded is left out of the deck and named in the summary rather than shipped as a blank slide, so the count you are shown is always the count of slides that actually carry a picture. The panel under the button distinguishes the two cases: pages that hit the slide ceiling are listed as costing nothing visible, and only pages that the browser forced below 300 DPI of slide are flagged as softer.
Is my document uploaded anywhere?
The document is not. It is read from disk with the File API, rendered by pdf.js inside this tab, packaged into an Office Open XML archive here as well, and handed to your downloads folder; no network request carries the file or anything derived from it, and between pressing Convert and the download appearing the page makes no requests at all. To be straight about the rest of the page: like every page on this site it loads Google advertising and analytics scripts, so simply opening it does contact those third parties with the ordinary page-view information any website sees. That is separate from your PDF, which never leaves the machine — which is the reason to use a browser-based converter for a board pack or an unreleased deck in the first place.