HEIC to JPG: the choices behind the export.
An iPhone photo can be compact on the device and awkward in a form or editor that expects JPEG. This converter decodes the HEIC locally and builds a conventional JPEG delivery copy. It supports the image frames the bundled decoder exposes, while keeping the distinction between a visible photograph and Apple's richer camera container clear. No remote conversion service receives the source while you prepare a compatible file.
Decode the container before encoding JPEG
HEIC stores images in a high-efficiency container that can include several frames. A local decoder first reconstructs the pixels; the JPEG encoder then creates a broadly compatible still image. This is a new lossy encoding, not a filename change. Camera metadata, depth information, Live Photo motion, and HDR characteristics are not carried into the result.
HEIC is a container-based image workflow that commonly uses high-efficiency photographic compression. Opening it requires a compatible decoder; changing the filename to JPG cannot make an application read it. This route loads its local decoder only after you choose a HEIC source. The expensive decode uses the codec's own Blob worker. The resulting raster frames then enter the same isolated image-encoding pipeline used for ordinary JPEG, PNG, and WebP sources.
Expect a conventional still-image handoff
JPEG export starts at 92 percent quality to provide a careful compatibility handoff. It is still a new lossy encode of an already decoded image. The original capture's detail and processing choices set the upper bound on what can be recovered. Use the preview to inspect texture and skin tones, and adjust quality when you need a different balance of file size and visible detail. Keep the HEIC when it remains your best available original.
A HEIC container can hold more than one image. When the decoder exposes several supported frames, the workspace treats them as separate outputs with distinct names and can package those results together. This is not a reconstruction of an Apple Live Photo. Motion, depth information, HDR characteristics, and camera-specific metadata are not carried into the conventional JPEG copies. The meaningful output here is a compatible still photograph that another application can display.
Inspect the photo after the codec boundary
Codec decoding does not provide a trustworthy percentage, so that stage is explicitly indeterminate. Later raster encoding has stage progress and measured output bytes. Large or unusual camera variants may fail even when the filename ends in HEIC. The workflow keeps failure local and bounded rather than uploading the source elsewhere as a fallback. If a source is unsupported, keep it intact and try a compatible export from the device or photo application that created it.
The fresh JPEG does not preserve the original metadata container or embedded profile, so inspect orientation and colors in the application where you will use it. Pixel dimensions are reported after decoding. If a visa or government form also imposes a hard file-size limit, conversion alone does not guarantee compliance: take the resulting JPEG into the constrained compressor and verify its actual bytes. Retain the camera original, particularly when future edits may require information that this simpler delivery format cannot represent.
Three steps. A finished file.
Open your HEIC source
Choose a HEIC file on this device. The route checks its accepted input and prepares supported raster frames without sending the file to a processing service.
Review the JPG export choices
Start from the 92 percent quality preset, inspect detail, and choose the background or alpha handling supported by JPG. Adjust the setting for this particular image.
Save a separate JPG copy
Check the preview, actual output dimensions, and measured byte size. Download the result and inspect it in the receiving application while retaining the source file.
A little clarity.
Will HEIC to JPG keep my Live Photo or depth map?
No. It creates conventional still-image outputs from supported decoded frames. Apple motion, depth data, HDR properties, and source camera metadata are not preserved in those JPEG copies.
Why does HEIC decoding show a working state instead of a percentage?
The bundled decoder does not report reliable incremental progress. The UI avoids inventing a percentage and switches to measured encoding progress once raster frames are available.
Can every recent iPhone HEIC be decoded here?
No decoder covers every specialized or damaged variant. Unsupported input fails locally. Keep the original and use a compatible export from its source photo application when this decoder cannot open it.
Related tools
HEIC to PNG converter
Convert HEIC to PNG online for free. Export decoded iPhone photo pixels without another lossy encoding step. Your files stay on your device.
WebP to PNG converter
Convert WebP to PNG online for free. Preserve transparent backgrounds and export lossless PNG files from decoded pixels. No uploads or sign-up needed.
WebP to JPG converter
Convert WebP to JPG online for free. Choose JPEG quality and a background color for transparent areas, then download locally. No uploads or sign-up.
PNG to JPG converter
Convert PNG to JPG online for free. Adjust JPEG quality and choose a background for transparent images. Preview and download without uploading files.