Initializing... drag & drop files here
Supports: PPTX
Both turn every slide in a PowerPoint deck into its own still image, and both are lossy. The difference is a trade you have to make deliberately: HEIC encodes a slide in roughly a third of the bytes JPEG needs at the same quality setting, but it opens natively on Apple platforms and almost nowhere else. Short answer — if the images are going into an iPhone, iPad or Mac photo library, or into Keynote or iCloud, HEIC is the better file. If anyone else has to open them, take the JPG.
| Property | HEIC | JPG |
|---|---|---|
| Defining standard | ISO/IEC 23008-12 (HEIF), HEVC-coded | ISO/IEC 10918 (JPEG) |
| Compression | HEVC intra-frame | DCT baseline |
| One 4000 × 2250 slide at the "Very High" preset | ~108 KB | ~275 KB |
| Bit depth this converter writes | 8-bit, sRGB, no alpha | 8-bit, sRGB, no alpha |
| Native browser support | Safari 17+ on macOS and iOS only, around 15% of users | Every browser ever shipped |
| Windows | Needs Microsoft's HEIF Image Extension for thumbnails and previews | Built in |
| Android | Recent versions read HEIC; older ones do not | Universal |
| Office and Google Slides | Frequently rejected on insert | Always accepted |
| Patent position | HEVC licensing is the reason adoption stalled | Unencumbered in practice |
| Sensible use | Apple-ecosystem storage where size matters | Sharing, embedding, uploading anywhere |
The size gap is real and it is large — the HEIC came in at about 39% of the JPEG's bytes for the same slide at the same preset — but it only pays off if the recipient can open the file. A slide image nobody can view is not a small file, it is a broken one.
.pptx onto the page or click "+ Add Files". Every slide renders separately, so a 15-slide deck returns 15 HEIC files plus a "Download All (Zip)" button.Each preset is a fixed quality value handed to the HEVC encoder. We rendered a standard 16:9 slide at 4000 × 2250 and encoded it at every rung; these are the results.
| Quality Preset | Encoder quality | Size of one slide | Notes |
|---|---|---|---|
| Highest | 100 | ~108 KB | Decodes pixel-for-pixel identical to Very High |
| Very High (preselected) | 95 | ~108 KB | The practical ceiling |
| High | 90 | ~101 KB | First rung that actually changes the pixels |
| Medium | 80 | ~88 KB | Good for screen-sized slide libraries |
| Low | 70 | ~73 KB | Softening visible on small type |
| Very Low | 60 | ~59 KB | Blocking on charts and gradients |
| Lowest | 50 | ~44 KB | Thumbnails only |
The top of the ladder is flat: "Highest" and "Very High" produced files of exactly the same size, and decoding both gave images with zero differing pixels. "High" was the first rung that changed anything, altering about 0.1% of pixels. So there is no reason to move off the preselected setting in search of more fidelity — if you want a smaller file, move down; if you want a bigger one, you will not get one.
Not out of the box in most cases. Windows relies on Microsoft's HEIF Image Extension from the Microsoft Store for thumbnails, Photos previews and Explorer integration; without it a .heic file typically shows as a generic icon. That is the single most common reason a HEIC export ends up needing to be redone as PPTX to JPG.
No. The encoder writes 8-bit sRGB with three colour channels, regardless of what the source deck contains. HEIF as a standard supports 10-bit and wide-gamut images, but this conversion does not produce them — do not expect any HDR benefit over a well-encoded JPEG.
On slide content it is better than half. Encoding the same 4000 × 2250 slide render at the same "Very High" preset gave roughly 108 KB as HEIC against roughly 275 KB as JPEG — about 39% of the size. Ratios vary with content: photographic slides narrow the gap, while flat slides with large single-colour areas widen it, because HEVC's intra-prediction handles them extremely well.
Yes. Slides render at a fixed 300 DPI, and that resolution is written into the file's Exif block, so a 13.333 × 7.5 inch Widescreen slide arrives as a 4000 × 2250 image tagged at 300 DPI. Layout tools that read Exif resolution will place it at its intended physical size rather than guessing.
Yes — HEIC to JPG handles the return trip, and for slide images the quality cost is usually invisible because the HEIC was already encoded at a high setting. It is still a second lossy generation, so if you know some recipients need JPEG, export both from the deck now rather than transcoding later.
Almost nothing in practice. Both are containers defined by ISO/IEC 23008-12; the .heic extension signals HEVC-coded content specifically, while .heif is the generic name. Our encoder writes the same HEVC payload and the same heic brand in both cases, so PPTX to HEIF produces the same bytes under a different filename.
One per slide, in slide order, plus a "Download All (Zip)" button for the set. HEIF's container format can technically hold an image collection, but this converter writes one still image per file. For a single document containing every slide, PPTX to PDF is the right target.
Yes. Switch from Quality Preset to Specific file size, type the number and pick the unit. The encoder searches for a quality level that lands under your target, and enabling Auto Scale lets it also reduce the pixel dimensions when quality alone will not get there. Note that the target applies to each slide image individually, not to the deck as a whole.
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. Nothing from your deck is indexed or reused.