ToolzyLabConvert HEIC Photos to JPG or PNG
Every iPhone since 2017 saves photos as HEIC by default — and every Windows PC, email client, and web form on Earth seems to disagree. This guide explains the format and the painless conversion path.
Updated 2026-08-06 · ~7 min read
What HEIC actually is
HEIC (High Efficiency Image Container) stores photos encoded with HEVC — the same video codec behind 4K streaming. The gains are real: roughly 50% smaller files than JPG at the same visual quality, 10-bit color depth (over a billion colors versus JPG's 16.7 million), support for transparency, and the ability to bundle bursts, Live Photos, and depth maps in one container.
The problem is licensing. HEVC patents made every software vendor pay to decode it, so support spread slowly and unevenly: Apple's ecosystem is complete, Windows needs an optional codec, and many web platforms never added it. The result is a format that is technically superior and practically quarantined.
Why browsers need help with HEIC
Most browsers cannot decode HEIC natively for the same licensing reason. This converter works around that: your iPhone already did one conversion when you transferred the file — or the tool decodes it where the browser supports it — and re-encodes the pixels to JPG or PNG entirely on your machine. Because photos are the most personal files most people upload anywhere, local processing is the whole point: the file never travels to a server.
If a HEIC file will not load into the tool at all, the cause is usually that the file never left Apple's container cleanly — transfers via some cloud services or old cables produce files with odd headers. Re-export from the Photos app with the 'Most Compatible' option, or copy the original via AirDrop, and retry.
Choosing JPG or PNG output
| Output | When |
|---|---|
| JPG | Photos always. Universal, small, what every recipient expects |
| PNG | The rare HEIC graphic with transparency you must preserve |
For 99% of cases — sharing, uploading, printing, archiving in readable form — JPG is the answer. Use quality 85-92 to stay invisible against the source; the HEIC source is high quality and deserves a high-quality target.
What converts — and what does not
The conversion keeps the full-resolution image and its color information, and drops the extras Apple bundles: Live Photo motion frames, depth maps, burst sequences, and most metadata including location. If you need the motion of a Live Photo, export it as a video from the Photos app instead — no image converter can carry video. The metadata drop is usually a feature: GPS coordinates leave with the conversion, which is what you want before publishing.
The batch reality: vacations and handoffs
Trip folders arrive with hundreds of HEIC files. The efficient flow: convert the whole batch at one quality setting, download the ZIP, and spot-check three photos (one bright outdoor, one indoor low-light, one portrait-mode shot with blurred background). Portrait-mode shots deserve the spot check because their synthetic depth blur contains soft gradients — the exact content that shows compression mistakes first.
For a permanent fix on your own devices, iPhone's Settings → Camera → Formats offers 'Most Compatible' (shoots JPG) — but keep HEIC shooting for storage savings and convert on demand; the files stay half-size in your archive until you need them elsewhere.
Quality and color depth caveats
HEIC's 10-bit color converts down to 8-bit targets, which discards most of the extra gradations. The visible risk is banding in smooth skies or studio gradients; at quality 85+ on JPG it is almost never visible. Wide-gamut HEIC (Display P3 from modern iPhones) maps to standard sRGB on conversion — colors may render a touch less vivid on P3-capable displays, which is correct behavior for web-bound images.
Transferring without converting: the other paths
Conversion is not the only route, and knowing the alternatives helps choose. Transferring via cable with Windows' Photos import often auto-converts to JPG on the way in. iCloud for Windows offers the same. Apple's 'Transfer to Mac or PC' setting set to 'Automatic' converts during USB transfer too. These paths are convenient for steady personal workflows; the browser converter wins for one-off files, batches from mixed sources, and any situation where the file already sits on the machine and only needs a format change. One caution with auto-converting transfers: they run at cable speed, which on large libraries can take far longer than batch-converting afterward.
The archival argument for keeping both
The strongest long-term setup keeps HEIC as the archive format and converts on demand. HEIC originals occupy half the storage of JPG equivalents and preserve 10-bit color for future displays, while converted JPGs serve as disposable delivery copies. When a recipient needs a file, convert fresh from the archive copy at appropriate quality; never maintain a parallel JPG archive that can drift out of sync. Storage math for heavy shooters: a 10,000-photo library runs about 30 GB as HEIC versus 60+ GB as JPG archive — the savings compound yearly.
What HEIC conversion actually changes
Converting HEIC to JPG is a lossy-to-lossy transcode, which carries a small but real quality cost worth understanding. HEIC files from phones are already compressed with high efficiency; re-encoding them as JPEG re-runs lossy compression on decoded pixels, and each generation of lossy-to-lossy conversion accumulates artifacts — softening around edges and smearing in flat areas. For single conversions the loss is minor at high quality settings; for files that will be edited and re-saved repeatedly, convert once to a working format and keep the HEIC original as the master.
Rotation metadata is the classic HEIC conversion bug. iPhones frequently store photos rotated 90° with only an orientation flag saying 'display this sideways'; software that ignores the flag saves an image lying on its side. A correct converter applies the flag and bakes the rotation into the pixels. If your converted photos appear sideways, the converter dropped the EXIF orientation — reconvert with a tool that handles it, because fixing rotation after conversion costs another lossy re-save.
Choose the destination format by destination. JPG for sharing anywhere that predates 2020s software — email clients, older websites, Windows tools before the extension pack. PNG when the photo carries text overlays or needs lossless storage. WebP when you control the display context and want smaller files. The HEIC advantage — smaller files at equal quality — only pays off where HEIC is supported, which is the entire reason conversion exists.
Common mistakes with this tool
- Converting at quality 60-70 and introducing banding into a pristine 10-bit source.
- Expecting Live Photo motion to survive — it cannot; export video separately.
- Blaming the converter for files that transferred out of iCloud with broken headers.
- Switching the camera to JPG permanently and doubling archive storage forever.
Frequently asked questions
Why can not I open HEIC files?
HEIC uses the patented HEVC codec; many apps and browsers ship without a decoder. Converting to JPG sidesteps the problem entirely.
Does converting HEIC lose quality?
At quality 85-92 the JPG output is visually identical. The only real losses are the 10-bit color headroom and bundled extras like Live Photo frames.
Is HEIC better than JPG?
Technically yes — half the size, more color depth. Practically, JPG still wins on compatibility, which is why conversion exists.
Do GPS tags survive conversion?
No — re-encoding strips metadata including location, which is usually what you want before sharing.
Why are my converted photos sideways?
The EXIF orientation flag was ignored during conversion. Use a converter that applies orientation flags to the pixels; the photo data is fine — only the display direction was lost.
Does converting HEIC to JPG lose quality?
Slightly — it is lossy-to-lossy transcoding. At high quality settings the difference is hard to see; keep the original HEIC as the master if you plan further edits.