How to Convert HEIC Photos to JPG, PNG, or WebP

What HEIC is and why it trips up recipients

HEIC — High Efficiency Image Container — is the default photo format on Apple devices, storing images at roughly half the size of equivalent-quality JPG while supporting depth data, sequences, and 10-bit color. Inside the Apple ecosystem it is invisible; outside it, it is a compatibility problem. Windows opened HEIC only after a separately installed extension; many web forms, older email clients, and print services do not recognize the extension at all.

The result is the familiar scenario: photos that look perfect on the phone arrive as unopenable attachments or rejected uploads. The fix is conversion to JPG — universally readable — or WebP for destinations on the modern web. The conversion itself is one click; the value of understanding the process is knowing what to check afterward, because HEIC files carry information that does not automatically survive translation, and the failures it causes look like corruption rather than conversion.

The orientation trap: why converted photos appear rotated

Phone photos store pixels in sensor orientation and carry a separate instruction — an orientation flag in metadata — telling viewers to rotate them upright. Older viewers honored the flag inconsistently, and when a conversion strips or misapplies that flag, the result is a landscape photo lying on its side. HEIC conversion tools handle this two ways: baking the rotation into the pixels during conversion, or copying the flag to the JPG.

Baked rotation is the safer behavior for interchange because every viewer then displays the pixels as-is. If you receive converted photos that appear rotated, the flag was copied instead of applied — the fix is re-converting with rotation applied, or rotating in any editor and saving. Check orientation on every batch conversion by opening a few outputs, including at least one portrait and one landscape, before trusting the whole set. This is the single most common HEIC conversion complaint, and it is entirely mechanical.

Color: wide gamut, HDR, and why JPGs can look flat

Modern phones capture in wide color gamuts — Display P3 rather than traditional sRGB — and increasingly in HDR. Converting those files to a standard JPG requires mapping the wider gamut into the smaller one and tone-mapping HDR highlights, and the quality of that mapping decides whether the converted photo matches what the phone showed. Careless conversions produce images that look flat, oversaturated, or strangely gray.

The practical guidance: convert with tools that handle color management — which means honoring the embedded profile rather than discarding it — and judge results on the same class of screen you care about. If the JPG looks washed out next to the HEIC on the phone, the tone mapping lost contrast; if colors look slightly shifted, the gamut mapping did its necessary job. For the small number of images where color fidelity is critical — product shots, artwork — compare the conversion against the original deliberately and keep the HEIC as the master.

Metadata and privacy: what travels with the conversion

HEIC files carry full EXIF records — capture time, camera model, and GPS coordinates — and conversion behavior varies: some tools copy the metadata into the JPG, some strip it, some copy selectively. Neither behavior is universally correct; the right outcome depends on where the JPG is going. Photos bound for public websites or marketplaces should generally lose their GPS coordinates; a family archive conversion should keep capture dates, because date-stripped photos lose their sorting logic.

Make the decision deliberately per batch rather than inheriting whatever the tool defaults to. If privacy is the goal, verify the output: open the converted file's properties or metadata view and confirm location fields are gone — a conversion that promises stripping but quietly copies coordinates is a common surprise. Filename conventions help too: conversion tools that preserve original names keep the photo set coherent, while tools that rename to generic output names scramble albums in ways that take hours to repair.

Sequences, bursts, and Live Photos: the formats inside the format

HEIC containers can hold more than one image: burst sequences, depth-assisted portrait shots, and Live Photos — a still plus a short video clip. Conversion handles these differently, and the differences are where users lose content unknowingly. A straightforward conversion extracts the primary still frame and discards the rest: bursts collapse to one chosen frame, depth data vanishes, and the motion component of a Live Photo is left behind.

Before converting a batch that includes Live Photos, decide what the motion is worth. If the moment matters as motion, export the video component separately before converting the still. If bursts matter, select the keeper frame first rather than letting conversion choose. Portrait-mode depth effects survive conversion only as baked pixels — the blur renders into the image — so the editable depth map is lost, which is fine for sharing but matters if re-editing was planned. The container format's richness is real; conversion is where you decide how much of it to keep.

Batch conversion workflow that stays organized

Photo libraries accumulate HEIC files in bulk, and bulk conversion rewards the same discipline as any batch operation: originals untouched, outputs to a separate folder, settings decided once and applied uniformly. Convert to JPG at high quality — 80 or above — because these files will likely survive as the shareable copy indefinitely, and re-converting later from an over-compressed JPG compounds losses. WebP is the better target only when the destination is a website you control.

Order the workflow: sort the batch first — separate Live Photos and bursts if their extra content matters; convert; verify orientation on a sample covering both orientations; spot-check color on one vivid and one neutral image; confirm metadata decisions in the output properties. Then rename or organize the JPG set to mirror the original album structure. Keep the HEIC originals as masters — they are smaller than the JPGs you just made and contain everything the conversions approximated.

HEIC and the friction of format ecosystems

The HEIC situation is a case study in format transitions. A technically superior format — better compression at equal quality, modern features — shipped inside one ecosystem and collided with everything outside it: web uploads expecting JPEG, office software from an earlier era, relatives' devices, printing services, form portals. Each incompatibility is small in isolation and collectively they make HEIC a friction tax on anyone whose files leave the ecosystem that created them. The conversion step exists because the world's plumbing still runs on the older, universally accepted format.

The lesson generalizes beyond this one format pair. When choosing between capturing in a modern efficient format and a universally compatible one, the deciding factor is the file's travel plans. Photos that stay inside one ecosystem — viewed, edited, shared among devices that all speak the modern format — earn its efficiency. Photos destined for upload forms, mixed audiences, archival in generic tools, or processing pipelines of unknown capability are cheaper to capture or convert into the universal format early, before friction compounds across copies.

For the conversion workflow itself, the direction matters: keep HEIC originals as the quality reservoir and treat JPEG copies as delivery artifacts, regenerated from the original whenever a new destination needs them. Converting once and discarding the original surrenders the better file forever. The ecosystem will keep transitioning — every decade renegotiates its baseline formats — and the durable skills are recognizing which side of a transition your files live on, converting deliberately rather than reactively, and never burning the bridge back to your highest-quality source.

Frequently asked questions