Initializing... drag & drop files here
Supports: PPTX
HEIF — High Efficiency Image File Format — is a container standard, not a codec. It is defined by ISO/IEC 23008-12 and built on the ISO base media file format, the same box structure that underpins MP4. What actually compresses the picture is signalled by a four-character brand in the file's ftyp box: heic for HEVC-coded stills, heix for the 10-bit and range-extension profiles, mif1 as a generic structural brand for single images, msf1 for image sequences. This page renders each slide of a PowerPoint deck into its own HEIF still.
| Property | Value |
|---|---|
| Standard | ISO/IEC 23008-12 (MPEG-H Part 12) |
| Base structure | ISO base media file format (ISOBMFF), the MP4 box model |
| Payload codec | Signalled by brand; HEVC in the heic case |
| Brands in common use | heic, heix, mif1, msf1 |
| Can hold | A single image, an image collection, an image sequence, derived images, thumbnails, Exif |
| Extension convention | .heic implies HEVC content; .heif is the generic name |
| Native browser support | Safari 17+ on macOS and iOS; roughly 15% of users globally |
| Not supported by | Chrome, Firefox, Edge, Opera, Samsung Internet |
| Best for | Apple-ecosystem image libraries where storage matters more than reach |
The reason HEIF never displaced JPEG on the open web is licensing rather than technology: HEVC carries patent obligations that browser vendors declined to take on, which is why AVIF and JPEG XL exist as royalty-free answers to the same problem.
The .heif and .heic targets on this site are the same encoder with a different filename. We converted the same slide render to both and compared them byte for byte: the files were identical, down to the ftyp box, which in both cases carries heic as the major brand and mif1 heic miaf as compatible brands. In other words, choosing .heif here gives you an HEVC-coded HEIF file that any HEIC reader will open — the extension is a naming preference, not a format switch.
A few concrete properties of the output worth knowing before you commit:
heix brand, but this converter does not produce them. There is no bit-depth control on the page and no HDR path..pptx onto the page or click "+ Add Files". Each slide is rendered independently, so a 20-slide deck returns 20 HEIF files.We rendered a standard 16:9 slide at 4000 × 2250 and encoded it at every preset. The top of the ladder is flat, which is the single most useful thing to know about this page.
| Quality Preset | Encoder quality | Size of one slide | Verdict |
|---|---|---|---|
| Highest | 100 | ~108 KB | Same size as Very High, and pixel-identical on decode |
| Very High (preselected) | 95 | ~108 KB | The effective ceiling; leave it here |
| High | 90 | ~101 KB | First rung that changes the image at all |
| Medium | 80 | ~88 KB | Sensible for screen-resolution libraries |
| Low | 70 | ~73 KB | Softening starts to show on body text |
| Very Low | 60 | ~59 KB | Visible blocking on charts |
| Lowest | 50 | ~44 KB | Thumbnails only |
For comparison, the identical slide encoded as JPEG at the same "Very High" setting came out around 275 KB — so HEIF landed at roughly 39% of the JPEG size, which is the whole argument for the format.
Not as this converter writes them. Both are ISO/IEC 23008-12 containers, both carry the heic major brand, and a byte comparison of the two outputs from the same slide showed no differences at all. The distinction exists in convention: .heic announces HEVC content, .heif is the format's generic name and could in principle hold something else. If a program refuses one extension, PPTX to HEIC gives you the other name for the same bytes.
On Apple platforms, everything — Photos, Preview, Quick Look, Keynote and Safari 17 and later all handle HEIF natively. On Windows, Microsoft's HEIF Image Extension from the Microsoft Store is what enables thumbnails and Photos previews. On the web, Chrome, Firefox and Edge do not decode HEIF at all, so never link one directly from a page.
The standard allows it — an image collection is one of the structures ISO/IEC 23008-12 defines — but this converter does not produce one. Each slide becomes its own .heif file. If a single file containing every slide is the goal, PPTX to PDF is the practical answer and stays vector-sharp into the bargain.
No. The output is 8-bit sRGB with three channels. Ten-bit HEIF exists under the heix brand, but there is no bit-depth control on this page and the encoder is not configured for it — so do not expect a wider gamut or smoother gradients than a good JPEG would give you.
Because the encoder's quality scale saturates before it reaches the top. Quality 100 and quality 95 produced files of identical size, and decoding both gave images with zero differing pixels; quality 90 was the first setting that changed anything. Moving up from the preselected preset costs encoding time and buys nothing, so treat "Very High" as the maximum useful setting.
No, not on this path. The payload is HEVC intra-coded at whichever quality the preset selects, and every rung including "Highest" is lossy. If you need a slide image with nothing discarded, use PPTX to PNG at its Highest preset — that is the setting that writes a true-colour PNG; the lower PNG presets run a palette quantizer of their own.
No. The stored image is opaque; there is no alpha channel in the output. Slide backgrounds are resolved during rendering, so anything you were relying on being see-through will not be. PNG is the format that carries alpha through.
AVIF answers the same problem — modern intra-frame video coding applied to still images — but with a royalty-free codec, which is why browsers adopted it and not HEIF. If your images are headed for the web rather than an Apple photo library, PPTX to AVIF gives comparable efficiency with far better browser reach. HEIF's advantage is confined to Apple-native workflows.
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.