Keep HEIC when your devices and apps support it. Convert to JPG when you need a compact, widely accepted photo. Convert to PNG when a downstream workflow specifically needs PNG or lossless re-encoding matters more than file size.
What HEIC is doing on your phone
HEIC is commonly used as a filename extension for images stored in the HEIF family of containers. Modern Apple devices often use it because it can store photos efficiently while supporting metadata and richer capture workflows than a simple legacy JPEG file.
For the person taking the photo, this efficiency is useful: similar-looking photos can take less storage than older formats. The friction appears later when the image leaves the ecosystem that created it.
Why HEIC compatibility problems happen
A file can be perfectly valid and still be inconvenient. Older Windows software, upload forms, content-management systems, messaging tools, print kiosks, and specialized applications may expect JPG or PNG even when the phone that created the image handles HEIC without issue.
That is why many HEIC conversions are really compatibility conversions. The pixels do not need to be “fixed”; the recipient or destination needs a different container or codec.
| Target | Best when | Main tradeoff |
|---|---|---|
| JPG | Photos, upload forms, email, broad sharing | Lossy compression; no alpha transparency |
| PNG | Lossless output or a PNG-specific workflow | Can be much larger for photographs |
| Keep HEIC | Your apps already support it and storage efficiency matters | Not every external workflow accepts it |
When HEIC to JPG is the practical choice
JPG remains one of the safest delivery formats for ordinary photographs. It opens almost everywhere, is accepted by a huge range of websites, and can keep photo file sizes manageable.
The conversion is lossy, so the output quality setting matters. A high quality setting can reduce visible artifacts from the new JPEG encode, but it cannot create detail that was not present in the HEIC source.
When HEIC to PNG makes sense
PNG is useful when the next tool explicitly expects PNG or when you want the new file stored without a lossy JPEG encode. For normal camera photos, however, PNG can be dramatically larger than JPG because it preserves the decoded pixel data losslessly.
A larger PNG should not be interpreted as a higher-resolution photo. The dimensions can be identical and the extra bytes may simply reflect the different compression method.
Keep the original when metadata or capture features matter
HEIC or HEIF files can carry metadata and features that a simple converted copy may not preserve in the same way. Depending on the source and conversion engine, metadata such as camera information, orientation, color information, or other container features can change or be omitted.
If the photo is important, treat the converted JPG or PNG as a delivery copy and keep the original HEIC as your source. That gives you flexibility if a better converter, editor, or destination becomes available later.
- Keep the original HEIC for your archive when the photo matters.
- Use JPG for broad photo compatibility and manageable file size.
- Use PNG only when its lossless storage or workflow compatibility is useful.
- Do not expect a format conversion to sharpen or upscale the source.
Common HEIC questions
Why does my iPhone use HEIC instead of JPG?
Modern devices use HEIC because it can store photos efficiently and work well with current capture pipelines. The exact device settings can vary.
Does HEIC to JPG reduce quality?
JPEG encoding is lossy, so a new JPG introduces a compression step. How visible that is depends on the source, dimensions, encoder, and quality setting.
Does converting HEIC remove the original?
No. A normal conversion workflow creates a new output file. The original HEIC remains unchanged unless you choose to delete it yourself.
Why convert locally in the browser?
For supported browser workflows, local conversion can solve a compatibility problem without sending a private phone photo through a remote conversion upload queue.