Initializing... drag & drop files here
Supports: PPTX
If the slides are going onto a web page, an app, a help centre or an email template, WebP is almost always the better raster: it carries alpha like PNG, has a lossy mode that handles photographic slides like JPEG, and is read by roughly 96% of tracked browser traffic. If the slides are going to a print shop, a Word document or a colleague who will open them in whatever their OS ships with, PNG is the safer file. This page renders each slide at 300 DPI and writes one WebP per slide.
| Property | WebP (this page) | PNG |
|---|---|---|
| Compression modes | Lossy and lossless, selectable | Lossless only on "Highest"; palette-quantised otherwise |
| Colour ceiling | Full colour in both modes | 256 colours unless you pick "Highest" |
| Alpha | 8-bit alpha in both lossy and lossless mode | 8-bit alpha always |
| Animation | Supported by the format, not produced here | Not supported |
| Browser support | Chrome 32+, Firefox 65+, Edge 18+, Safari 16+ (14-15.6 partial) | Universal |
| Desktop app support | Patchy in older imaging and Office tools | Universal |
| Best for | Web and app delivery of slide artwork | Handoff, print prep, anything offline |
| Where it fails | An old viewer shows a broken image | Gradients band on the default preset |
The "Lossless?" control on this page has "No (Recommended)" preselected. Both modes keep alpha, so this is purely a fidelity-versus-bytes decision.
| Setting | What the encoder does | Pick it when |
|---|---|---|
| No (Recommended) | Transform-based lossy coding; the Quality Preset sets the quantiser | Photographic slides, screenshots with gradients, anything web-facing |
| Yes | Exact pixel reproduction using predictors and a colour cache | Flat diagrams, logos, charts, or a master you will re-edit |
With "Lossless?" set to Yes the Quality Preset stops discarding detail — the pixels come back exactly as rendered. Lossless WebP is not capped at a 256-colour palette the way a quantised PNG is, so gradients stay smooth; whether it lands smaller than the equivalent PNG depends entirely on how flat the slide is, so if bytes matter, export both and compare.
One per slide. A 20-slide deck returns 20 WebP files plus a "Download All (Zip)" option. WebP can hold an animation, but this page writes stills — if you want the whole deck as one moving file, PPTX to GIF assembles every slide into a single animated GIF instead.
300 DPI, fixed. The DPI selector is only exposed for document sources, so presentations always rasterise at 300. That means a 13.333 x 7.5 inch widescreen slide arrives as 4000 x 2250 pixels and a 10 x 7.5 inch standard slide as 3000 x 2250. For web use that is usually far more than you need — set "Image resolution" to a preset height such as 1080p or 768p, or a percentage, and the width follows the slide's aspect ratio.
Around 96% of tracked browser traffic supports WebP, per caniuse: Chrome from 32, Firefox from 65, Edge from 18 and Safari from 16, with Safari 14-15.6 partial. The gap is old Safari, Internet Explorer and pre-2013 mobile browsers. If you need to cover that tail, serve WebP inside a <picture> element with a PNG or JPG fallback rather than choosing one format for everyone.
Yes, in both lossy and lossless mode — WebP carries an 8-bit alpha channel either way. Our slide renderer produces an ARGB image and applies no background fill, so a slide whose background is set to "No fill" arrives genuinely transparent. Decks that inherit an opaque theme background come back solid, which is the deck's doing rather than the converter's.
At a high preset, yes — much better than JPEG at a comparable size, because WebP's prediction and filtering handle hard edges far more gracefully than a plain DCT codec. If you can see softening around small type, either raise the Quality Preset or set "Lossless?" to Yes; text-and-line-art slides are exactly the content lossless WebP handles well.
Current versions of the major editors and of Windows and macOS decode WebP; older releases often do not, and support in niche or in-house tooling is genuinely unpredictable. That is the main practical cost of choosing WebP. If the file is going to a person rather than a web server, PPTX to PNG removes the question entirely; if it is going to a browser, WebP is the better choice.
Not for presentation sources. The size-targeting search runs on the still-image path; a slide deck goes through the presentation renderer, which does not consume it. The controls that genuinely move the output here are "Lossless?", the Quality Preset and "Image resolution" — and resolution is by far the biggest lever, since halving the height quarters the pixel count.
Drop the resolution first: web pages almost never need a 4000-pixel-wide slide. After that, keep "Lossless?" on No and step the Quality Preset down one notch at a time, checking the smallest text on the slide as you go. Files that are already exported can be squeezed again with compress WebP.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.