Initializing... drag & drop files here
Supports: PPT
.ppt is the legacy binary PowerPoint format that PowerPoint 97–2003 saved before the XML-based .pptx took over in 2007. Converting one here renders every slide to its own full-resolution image and writes each as a .apng file. Read that carefully, because it is the thing people get wrong about this conversion: you get one still per slide, not one animation of the whole deck. APNG's animation chunks are only assembled on the GIF path, so a presentation converted to APNG produces a set of ordinary, static PNG streams that happen to carry the .apng extension. If a looping animation of your deck is what you came for, PPT to GIF is the conversion that actually does it.
.ppt onto the page or click "Add Files". The deck is read slide by slide; a 15-slide presentation will produce 15 output images.The conversion is a three-stage pipeline. Your .ppt is first laid out and exported to PDF, preserving one PDF page per slide. That PDF is then rendered page by page to lossless PNG images. Finally each PNG is written out in your chosen target format. Only one target — GIF — has a fourth stage that collects those PNGs and assembles them into frames of a single animated file. APNG does not go through that stage; each PNG is converted individually, so each output is a single-frame image.
A single-frame APNG is, by definition, just a PNG. The animation is carried by three chunks defined in the W3C PNG Third Edition Recommendation of 24 June 2025 — acTL for animation control, fcTL per frame and fdAT for frame data — and a one-frame file contains none of them. That is why the result opens fine everywhere and simply sits there. It is not corrupt; there is nothing to play.
| Stage | Behaviour on this page |
|---|---|
| Layout engine | The deck is laid out and exported to PDF first, one PDF page per slide |
| Render resolution | 300 DPI. The render-quality control is not shown on presentation sources, so this value is fixed here |
| Resulting pixel size | A 4:3 slide (10 x 7.5 in) renders near 3000 x 2250 px; a 16:9 slide (13.333 x 7.5 in) renders near 4000 x 2250 px |
| Intermediate format | Lossless PNG — there is no JPEG step in this pipeline, so nothing is degraded between render and output |
| Alpha | The render keeps an alpha channel and is not flattened onto a solid colour here, so a slide with no background fill comes through transparent |
| Output count | One file per slide; more than one slide switches the job to a multi-file result with a ZIP download |
| Animation | None. Frame assembly exists only on the GIF target |
| Property | APNG (this page) | GIF (PPT to GIF) |
|---|---|---|
| Animates a deck? | No — one static file per slide | Yes — all slides assembled into one loop |
| Colour depth | Full 24-bit | 256 colours per frame |
| Transparency | 8-bit alpha, soft edges | 1-bit on/off, hard edges |
| Compression | Lossless, PNG-based | Lossless within a 256-colour palette |
| Standardised in | W3C PNG Third Edition, 24 June 2025 | GIF89a, 1989 |
| Browser support | ~96% of tracked usage; Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 46+ (caniuse) | Universal |
| Where it wins | Photo-heavy or gradient slides you want pixel-perfect | Anything that must loop, or must work in old email clients |
.ppt, the layout engine substitutes the nearest available font, which can shift spacing and line breaks. Re-save from PowerPoint with File > Options > Save > "Embed fonts in the file" before uploading.If the file is actually a modern .pptx rather than a true legacy .ppt, use PPTX to APNG, which reads the OOXML structure directly and reproduces recent decks more faithfully. If the deck is password-protected or damaged, no server-side renderer can open it — repair or unlock it in PowerPoint first. And if what you really need is a moving asset for a README, a docs page or a chat message, stop here: convert to GIF for the loop, or export the slideshow to video from PowerPoint and convert that, because a single still per slide is not going to do the job however you package it.
No. Every slide is rendered to its own image and written as its own .apng file, so a 12-slide deck produces 12 files. The stage that collects rendered slides and assembles them into animation frames only exists on the GIF target, so nothing on the APNG path ever builds the acTL and fcTL chunks an animated PNG needs. Each output is a valid single-frame PNG stream under an .apng name. For an animated result from a deck, use PPT to GIF.
At 300 DPI, applied to the physical slide size in your deck. A classic 4:3 PowerPoint slide is 10 x 7.5 inches, so it lands near 3000 x 2250 px; the modern 16:9 default of 13.333 x 7.5 inches lands near 4000 x 2250 px. Decks with a custom page size scale accordingly. The render-quality control that would let you pick a different DPI is not displayed on presentation sources, so if you want smaller images, use the Image resolution control to scale the rendered result down instead.
No. The deck goes to PDF, the PDF is rendered to lossless PNG, and the PNG is written out as APNG — every stage is lossless, and there is no JPEG intermediate anywhere on this route. What you lose is not fidelity but behaviour: animations, transitions, timings, speaker notes, embedded audio and video, and the ability to edit the text.
Because the renderer keeps an alpha channel and, on this route, does not flatten the page onto a solid colour. A slide whose background is explicitly filled — a theme colour, a gradient, a picture — renders with that fill exactly as you see it. A slide with the background set to none has nothing drawn behind its content, so those areas stay transparent, and APNG preserves that alpha faithfully. If you need a guaranteed opaque result, set an explicit background fill on the slide master before exporting.
For a single still there is no difference in the pixels; the choice is about what opens the file without friction. A one-frame APNG is byte-compatible with PNG, so browsers and modern viewers handle it, but plenty of desktop applications, CMS uploaders and image libraries filter on the extension and will simply refuse .apng. PPT to PNG sidesteps all of that with the same output quality. Pick APNG only if something downstream specifically expects that extension.
They are dropped, and they have to be. A still image records the rendered visual state of a slide — the final position of every object after all builds have run. Entrance and exit animations, slide transitions, motion paths, timed builds, embedded video and any audio have no representation in a static picture. If preserving motion within a slide matters, export the presentation to video from PowerPoint and convert that video instead; if only the slide order matters, GIF will at least advance through them.
Yes — queue multiple .ppt files and they are processed with the same settings. Be aware of how the output multiplies: three decks of ten slides each is thirty images, all delivered as a multi-file result with a "Download All (Zip)" button. If you are batching, it is worth setting a Resolution Percentage first, because thirty full-size 300 DPI renders is a lot of megabytes to download for no benefit.
Your .ppt is uploaded over an encrypted connection and rendered entirely on our servers — decks need a real layout engine and font substitution to render correctly, which is why this is not something a web page can do on its own. Both the uploaded deck and the generated images are deleted automatically after a few hours. No account is required, nothing is watermarked, and your files are never shared or made public.