PPM to HEIC Converter

PPM to HEIC: Is HEIC the Right Target for a Pixmap?

A .ppm is raw RGB with a three-line header — no compression, no alpha, no colour profile, and the Netpbm specification openly calls the layout "egregiously inefficient". Anything you encode it to will be dramatically smaller, so the real question is not whether to compress but which container earns the trip. The short answer: pick HEIC when the file is going to live inside Apple's ecosystem, pick AVIF when it is going on the web, and pick JPG when you have no idea what will open it. HEIC's compression is genuinely good; its reach is genuinely narrow.

HEIC vs AVIF vs JPG vs PNG From the Same Pixmap

The licensing row explains the support row. caniuse states the case plainly: it is hard for browsers to support HEIC because it is complex and expensive to license, which is precisely why AVIF and JPEG XL were designed to supersede it. On our test image AVIF was less than half the size of HEIC at the same preset and decodes in six times as many browsers.

When HEIC Is the Right Choice

• The destination is Photos on iOS or macOS, where HEIC is the native camera format and everything about the library — thumbnails, editing, iCloud sync — is built around it.
• You are matching an existing HEIC-based asset set and want format consistency rather than the smallest possible file.
• The file will be read by software that already speaks HEVC, such as an Apple-centric editing or DAM workflow.

When to Pick Something Else

• The image is going on a web page. PPM to AVIF is smaller, royalty-free and decodes almost everywhere.
• You are emailing it, attaching it to a ticket, or handing it to someone whose platform you do not control — PPM to JPG is the only genuinely universal answer.
• A later pipeline stage needs the exact samples back. HEIC here is lossy with no lossless toggle; use PPM to PNG instead.
• The recipient is on Windows or Android. Support there is uneven and frequently needs an add-on decoder, which is a bad thing to discover after you have sent the file.

How to Convert PPM to HEIC

1. Upload Your PPM File: Drag and drop the pixmap or click "+ Add Files". Both P3 (plain ASCII) and P6 (raw binary) pixmaps are accepted, and several can be queued at once.
2. Choose a Quality Preset: The Quality Preset dropdown opens on "Very High (Recommended)" and offers Highest, Very High, High, Medium, Low, Very Low and Lowest. Those rungs drive encoder quality values of 100, 95, 90, 80, 70, 60 and 50.
3. Or Set a Specific File Size and Resolution (Optional): Specific file size takes a byte budget instead of a preset — pre-filled at 8 MB, with an Auto Scale toggle that lets the encoder reduce dimensions to reach it. Image resolution stays on "Keep original" unless you choose a percentage, a preset height, or explicit width and height.
4. Convert and Download: Click Convert and save the .heic. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

What the Presets Actually Emit

Measured on one 1600 x 1200 P6 pixmap of 5,760,017 bytes, encoded through the same saver and the same quality values this page drives. The top row is the surprise.

Highest and Very High came back within a single byte of each other, and we saw the same thing on three further test images — a flat logo, a smooth render frame and a heavy-grain synthetic photo — where Q100 and Q95 also matched while Q90 dropped clearly. The practical advice is to leave the default alone: choosing "Highest" costs encoding time and buys nothing. Note also that these numbers share a preset with the JPG column in the comparison table but not a quality scale — a quality value of 80 means something different to HEVC than it does to a JPEG encoder, so treat cross-format rows as a rough orientation, not a controlled test.

Frequently Asked Questions

Does the HEIC keep 10-bit colour or HDR from my source?

No. HEIF as a standard supports higher bit depths, but this conversion path drives the encoder with a quality value only and every output file we inspected reported 8 bits per channel with 4:2:0 chroma. There is also nothing wider in the source to preserve: a PPM holds plain integer RGB samples with no HDR metadata and no colour profile at all, so there is no dynamic range being discarded — there was never any to begin with.

Why is my PPM so enormous before conversion?

Because it stores every sample verbatim. A P6 pixmap is width x height x 3 bytes plus a short header when maxval is under 256, and two bytes per sample above that — so a 12-megapixel 8-bit pixmap is roughly 36 MB whatever the picture shows, and a plain grey square costs exactly as much as a detailed photograph. P3 files are larger still, because each sample is written as ASCII decimal digits with separators.

Will I lose quality converting PPM to HEIC?

Yes, some. PPM is uncompressed and HEIC here is lossy HEVC, so detail is discarded to reach the smaller size. At the default preset the difference is hard to see at normal viewing distance on photographic content. Flat graphics with hard edges show it sooner, because chroma subsampling softens saturated colour boundaries. If exact samples matter, PNG is the right target.

Which ftyp brands does the output file actually declare?

We inspected the generated files: the major brand is heic with mif1, heic and miaf in the compatible-brands list, which is the standard HEVC-coded still-image profile and MIAF-conformant. That is what Apple's Photos and Preview expect. It is worth knowing because some tools sniff brands rather than extensions, and a file that fails to open elsewhere is usually a decoder problem rather than a malformed container.

Why won't my HEIC open in Chrome, Firefox or Edge?

Because they do not implement it. caniuse currently puts HEIF/HEIC at 15.02% of tracked global browser usage, and the only browser family in that figure is Safari 17 and later. The reason given is licensing: HEVC is patent-encumbered and expensive to ship in a free browser. This is not a bug you can work around with a different HEIC file — if a browser has to display it, convert to AVIF or JPG instead.

Is a HEIC really half the size of a JPEG?

That claim is repeated everywhere and it is not what we measured. At the same preset our test pixmap produced 108,286 bytes of HEIC against 148,641 bytes of JPEG — better, but closer to three-quarters than to half — and at the Medium rung the HEIC was actually slightly the larger of the two. Preset numbers are not a shared quality scale across codecs, so neither result proves much on its own. The honest summary is that HEIC beats JPEG most clearly at high quality settings, and that AVIF beat both by a wide margin on the same image.

Can I get a lossless HEIC instead?

Not from this page. The lossless toggle does not render here, so the output is always lossy HEVC. If you need the pixmap's exact samples preserved, keep the PPM or convert to PNG, which compresses losslessly. There is no way to recover discarded detail afterwards by re-encoding the HEIC at a higher preset.

How are my files handled, and how long are they kept?

Your pixmap is uploaded over an encrypted connection and encoded on our servers. Files are deleted automatically after a few hours, there is no sign-up and no watermark, and nothing is shared or made public.