HEIC to PNG: When to Choose PNG Instead of JPG

For a normal iPhone photo of a person or a landscape, JPG is the better export target: it produces files that are a fraction of the size of PNG with no perceptible quality loss. But PNG exists for a reason, and there are real situations where converting HEIC to PNG is the right call. This is a rundown of those cases and the trade-offs each direction makes.

The difference, in one sentence each

• JPG (JPEG) uses lossy compression tuned for photographs. It throws away data that human eyes rarely notice, which is why a 5 MB iPhone HEIC becomes a 1.5 MB JPG with no visible change.
• PNG uses lossless compression. Every pixel survives the conversion exactly. It supports transparency. File sizes are larger, sometimes much larger, for the same image.

When PNG is the right answer

You are going to edit the file

JPG is lossy at every save. If you convert HEIC to JPG, crop it, save, then crop again, you are stacking compression artifacts each time. PNG saves are lossless, so editing rounds do not degrade the image. For anything that will pass through Photoshop, Affinity, or Figma more than once, export from HEIC to PNG.

Screenshots, screen recordings, UI captures

If your HEIC file is a screenshot taken on an iPhone or iPad, it contains sharp text and flat color regions. JPG's algorithm produces visible ringing artifacts around sharp edges; PNG renders text crisp. The file is also typically smaller for screenshots because PNG's compression excels at flat regions.

You need transparency

HEIC supports alpha channels. iOS exports certain images (Memoji stickers, marked-up photos with cutouts, Live Sticker exports) with transparent backgrounds. JPG does not support transparency, so converting to JPG turns the transparent area into solid white or black. PNG preserves it.

The destination expects PNG

Some workflows are PNG-only by convention or by tooling. App Store screenshots and many email signature embedders, for example, are easier with PNG. Logos, design assets, and anything that will be re-exported repeatedly belongs in PNG.

When JPG wins

For your camera roll, JPG is almost always the better choice:

• File size. A 12-megapixel iPhone photo becomes roughly 1 to 3 MB as a JPG, but 6 to 20 MB as a PNG. Multiply by a year of photos and the difference is hundreds of gigabytes.
• Sharing. Email, Slack, WhatsApp, and most websites are friendlier to JPG. Some platforms re-encode PNG to JPG anyway.
• Printing. Photo print services accept both, but JPG is the default everywhere.

If your goal is “I just want to email these photos to someone on Windows”, go to JPG. Use PNG only when the use case demands it.

Quality settings, and why PNG does not have them

When you export to JPG you choose a quality level: 90 is a common sweet spot, 95 is near-indistinguishable from the source, 100 is huge for negligible gain. PNG has no quality slider because compression is lossless. The only PNG choice is the compression effort, which affects file size and encode time but not visual output.

That is also why a 100-quality JPG and a PNG of the same photo can be very different sizes: the JPG is allowed to throw away high-frequency detail you cannot see, the PNG is not.

Color, gamma, and color profiles

HEIC files from modern iPhones embed Display P3 color profiles. When converting, the profile should travel with the image; otherwise vivid greens, reds, and oranges shift toward gray on devices that assume sRGB.

PNG supports embedded ICC profiles and the modern cICP color chunk used by HDR images. JPG embeds ICC profiles too. A decent HEIC converter writes the source profile into the output; check that before assuming color is preserved.

A note on privacy

Most free HEIC-to-PNG sites upload your photo to a server they control. Even if the conversion is fast, the file hits their disk, their logs, and possibly their CDN cache. For personal photos this matters: a screenshot with an account number, a photo of a passport, a picture of your kids.

Browsers can run the same libheif decoder as a WebAssembly module. That means the conversion happens locally on your machine, and the file never leaves the tab. For anything sensitive, browser-based conversion is the default to reach for.

Frequently asked

Is PNG always lossless from HEIC?

Yes. Once HEIC is decoded to pixels, PNG encodes those pixels exactly. There is no compression-related loss in the PNG step. Any loss happens upstream, when HEIC was originally encoded by the iPhone camera.

Why is my PNG larger than the HEIC?

HEIC uses HEVC, a modern lossy codec specifically designed for natural images. PNG is lossless and uses generic deflate compression. For photographic content the HEIC will often be 5 to 10 times smaller than the lossless PNG version of the same picture.

Does PNG support EXIF and GPS data?

Yes, PNG supports EXIF via the eXIf chunk standardized in 2017. Older PNG decoders ignore it but newer ones (and current photo apps) read camera metadata, capture date, and GPS coordinates correctly.

Should I batch convert all my HEICs to PNG?

Almost certainly no. For an archive of camera roll photos, PNG balloons storage with no quality benefit you will notice on any screen. Reach for PNG only for the specific files where lossless or transparency matters.

Can I convert HEIC to WebP or AVIF instead?

Yes, and for web use those are often the smartest target. WebP is broadly supported and a good middle ground; AVIF gives JPG-beating compression but encode time can be slow in the browser. For posting on the web in 2026, WebP at quality 85 is a good default.