What this does

Drop in a .pptx and each slide is laid out here, on your own machine, then written to PDF by your browser's print engine — one slide per page, at the deck's own proportions. Text stays selectable and searchable, pictures come through, and you can include the speaker notes or leave them out.

Nothing is uploaded. Decks are the sort of thing that carries unreleased numbers, client names and internal strategy, and every online converter that isn't doing the work locally keeps a copy of yours.

Why slides convert better than documents

This is the surprise of the three Office formats. A Word file describes a stream of text whose position is the result of a cascade of styles, so laying it out means reimplementing Word. A PowerPoint slide is the opposite: every shape carries its own coordinates and size, in units of a 914,400th of an inch. There is no layout to compute — only arithmetic — so a slide's shapes land where the author put them.

The one genuinely fiddly part is placeholders. A title usually carries no position of its own; it inherits one from the slide layout, which may inherit from the slide master. A converter that only reads the slide finds a title with no coordinates and drops it in the corner — which is why so many converted decks come out with every heading stacked in the top-left. Each shape here is resolved through slide, layout and master in turn.

What comes across, and what doesn't

Positions and sizes, text with its size, weight, italics, colour and alignment, bullet lists and their indent levels, pictures, tables, solid fills and the slide background. Slide order and the deck's aspect ratio are kept, and each slide starts a new page.

What doesn't:

Charts and SmartArt, which are drawn from data by PowerPoint rather than stored as shapes.
Gradients, shadows, 3-D effects and WordArt — a shape with a gradient fill comes out unfilled rather than approximated wrongly.
Animations and transitions, which have no meaning on paper. Slides are printed in their final state.
Fonts you don't have. Decks reference fonts by name and rarely embed them, so your browser substitutes the nearest match — as PowerPoint itself does on a machine without the font — and long lines may wrap differently.
Autofit text shrinking. PowerPoint quietly reduces type to fit its box; here the stated size is used, so a box that was already overfull may overflow.

For a deck that is mostly titles, bullets, pictures and tables — which is most decks — the result is close. For one built on charts and heavy effects, export from PowerPoint itself. Check the preview before sending; it is the same rendering the PDF will get.

Paper size

By default the paper is made to match the slide, so a 16:9 deck produces a 16:9 PDF with no bands down the sides — which is what you want for something read on a screen. Choose A4 or Letter if it is going to be printed on real paper, and each slide is fitted to the sheet.

Is it private?

Yes. The deck is unzipped and read by JavaScript inside this page, and the PDF is written by your own browser. Nothing is transmitted and nothing is stored — there is no server on the other end. Pictures inside the deck are turned into data held in the page rather than fetched from anywhere, so the preview makes no outside requests at all.

Frequently asked questions

Can it open .ppt?

No — the old binary .ppt is a different format, and the tool says so rather than failing obscurely. Open it in PowerPoint or LibreOffice and save as .pptx.

Can I print several slides to a page, like a handout?

Not here. Your browser's print window can often do it — look for a "pages per sheet" option — or set the paper to A4 and use two-up printing when you print the PDF.

My slide has a chart and it's missing.

Charts are generated by PowerPoint from their underlying data rather than stored as drawable shapes, so they aren't reproduced. A practical workaround is to copy the chart in PowerPoint and paste it back as a picture, which converts perfectly.

Why is my text overflowing its box?

PowerPoint shrinks text to fit a placeholder without changing the size it records. The recorded size is what's used here, so a box that was already tight can overflow. Reducing the font size in the deck itself fixes it for both.