Initializing... drag & drop files here
Supports: PPTX
.pptx decks. Batch is supported — every slide of every file becomes a separate AVIF image.PPTX is the Office Open XML presentation format Microsoft introduced with PowerPoint 2007 and standardized as ECMA-376 / ISO/IEC 29500. AVIF (AV1 Image File Format) was released by the Alliance for Open Media in 2019 and uses AV1 intra-frame coding inside an HEIF container. Converting slide-by-slide flattens each page to a single still image, so the output is no longer editable — but it is dramatically smaller, web-embeddable, and renders identically on every modern browser without a PowerPoint viewer.
<img> tag and ships in roughly half the bytes of JPEG at matched quality, which speeds up Largest Contentful Paint on slide-heavy blog posts and documentation pages..pptx cleanly; sending a folder of AVIF images sidesteps the viewer problem and stays well under most email caps (Gmail's 25 MB limit, Outlook.com's 20 MB limit per message as of 2026).| Property | PPTX | AVIF |
|---|---|---|
| Standardized | ECMA-376 / ISO/IEC 29500 (2008) | AOMedia AVIF spec (2019) |
| Type | Editable multi-slide presentation (XML + media in a ZIP) | Still raster image (one per slide after rasterization) |
| Codec | N/A (vector + embedded media) | AV1 intra-frame in HEIF container |
| Editable text and shapes | Yes (in PowerPoint, Keynote, Google Slides) | No — flattened pixels |
| Animations / transitions / video | Preserved in source | Not preserved (static frame only) |
| Typical size | 1–50 MB per deck | 15–200 KB per slide |
| Browser native rendering | No (needs a viewer) | Yes — Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ |
| HDR / wide gamut | Limited to embedded media | Native (10/12-bit, BT.2020, PQ/HLG) |
| Speaker notes / metadata | Preserved | Stripped |
| DPI preset | Best for | Typical size per slide (Very High quality) |
|---|---|---|
| 72 (Web) | Inline blog images, social previews | 15–40 KB |
| 96 (Screen) | Documentation thumbnails, intranets | 25–70 KB |
| 150 (Balanced) | Default web hero imagery, pitch decks online | 50–150 KB |
| 200 (Office) | Internal share, retina-friendly displays | 80–250 KB |
| 300 (Print) | Print-quality archival, handouts | 150–500 KB |
| 600 (Archival) | High-fidelity preservation of design-heavy slides | 400 KB–1.5 MB |
| 1200 (Fine Art) | Maximum-detail artwork capture | 1–3 MB |
Sizes are rough — actual output depends on slide complexity (gradients, photos, and detailed charts compress less efficiently than flat-color text slides).
Yes. A 20-slide PPTX produces 20 AVIF files named in slide order. The rasterizer renders one frame per slide, so animations are flattened to their final visual state — exactly what you'd see if you stopped on each slide in presentation mode without playing animations.
No. AVIF is a still-image format, so animations, builds, slide transitions, embedded videos, and audio narration are dropped. If you need motion preserved, export the deck to MP4 from PowerPoint first, or use PPTX to PDF to keep a vector-faithful page-per-slide document with hyperlinks intact.
For inline web images, 96 DPI matches PowerPoint's default screen resolution and produces the smallest acceptable file. For retina/HiDPI displays, render at 150–200 DPI and let the browser downscale via CSS — visually crisper at roughly 2× the bytes. Use 300 DPI only when print or print-ready archival is the goal; web browsers don't benefit from anything higher.
AVIF uses AV1's modern intra-frame coding — 64×64 superblocks, directional prediction, and chroma-from-luma — which compress flat slide regions and gradients more efficiently than JPEG's 8×8 DCT or PNG's DEFLATE. For typical slide content (text on solid backgrounds, charts, photographs), AVIF is commonly 30–50% smaller than JPEG and 20–40% smaller than WebP at matched perceptual quality.
Chrome 85+ (released August 2020), Firefox 93+ (October 2021), Safari 16.4+ (March 2023), Edge 121+ (January 2024), and current iOS Safari and Chrome for Android. Per caniuse, global support is around 94% as of 2026. For audiences on older browsers or in environments where you can't guarantee version, fall back to PPTX to PNG or PPTX to JPG.
Yes — text is rendered to pixels using the system fonts available during conversion, then encoded into the AVIF. There is no font substitution at view time because the output is just an image. The trade-off is that you can't re-edit text, copy it, or have it indexed by search engines unless you also publish a transcript or alt text alongside the image.
Yes. Drop several .pptx files into the upload area and a single Convert click renders every slide of every deck to AVIF using the same DPI, resolution, and quality settings. Output is delivered as a ZIP grouping each deck's slides together so a 5-deck × 20-slide batch arrives as one downloadable archive of 100 AVIF files.
WebP (Google, 2010) is older and more universally supported, but AVIF generally produces 10–25% smaller files at the same visual quality and has better high-frequency detail retention — useful for slides with small text or fine chart lines. WebP wins on encode speed and IE/legacy-browser compatibility (which AVIF does not target). If you need the smallest file with broad-modern-browser support, AVIF; if you need broad-everywhere support, PPTX to JPG.
The conversion is processed via xconvert's standard pipeline; nothing is attached to a user account, no sign-up is required, and there is no watermark on the output. For sensitive decks (legal, M&A, internal financials), consider exporting slides to PNG locally in PowerPoint first and then using PNG to AVIF so the source PPTX never leaves your machine.