HEIC to JPG Converter

HEIC to JPG Converter — runs in your browser

Everything below happens on this page. No file is uploaded, there is no account, and nothing is watermarked.

HEIC is the format iPhones have used for camera photos since iOS 11. It stores roughly half the bytes of an equivalent JPEG at the same perceived quality, which is why it exists. The cost is that almost nothing outside the Apple ecosystem can open it — Windows shows a blank thumbnail, older Android apps reject it outright, and most web upload forms simply refuse it.

This converter decodes HEIC and re-encodes it as JPG, PNG or WebP using a WebAssembly build of libheif that runs inside your browser tab. Drop in a folder of iPhone photos, pick an output format, and download the results. Nothing is transmitted.

What it does

Everything is done on your device, so there is nothing to upload and nothing to wait for a queue.

How to use it

Four steps, and none of them leaves your machine.

1. Drop the HEIC files

   Select one photo or a whole batch from your camera roll export.

2. Choose JPG, PNG or WebP

   JPEG for maximum compatibility. WebP if the destination accepts it and size matters most.

3. Convert

   The WASM decoder runs on your CPU. A single high-resolution photo takes a second or two.

4. Download

   Save individually or take the batch as one archive.

What people use it for

The jobs this actually gets used for.

Why HEIC breaks so many things

The format is a compression win and a compatibility loss, and both facts are the same decision.

HEIC wraps HEIF, a container designed to hold one or more images, video, or both, with codecs inside. Apple adopted it as the camera default because it fits more pixels into fewer bytes — roughly half a JPEG at matched quality — which matters a lot on a phone with limited storage.

Decoding HEVC, the codec inside HEIC, is the expensive part. Hardware support is uneven across desktop CPUs, so browsers historically refused to decode it. This converter sidesteps that by shipping a WebAssembly build of libheif, which is large to download but runs anywhere JavaScript does.

One consequence worth knowing before you convert: metadata is not carried over. GPS coordinates, camera model and capture settings are dropped in the output. That is usually what people want for sharing, but if you are archiving, keep the originals.

What it cannot do

The honest list, so you do not find out halfway through a batch.

• Metadata is stripped. GPS, camera model and timestamps are not carried into the output file.
• A burst only exports its first frame as a still. Bursts become animated GIFs, but the individual moments are not recoverable afterwards.
• The WASM decoder is a few megabytes, so the first conversion after page load is slower than later ones.
• Requires WebAssembly. Every current desktop browser has it; very old embedded browsers may not.

Built on open source

The processing is done by a published, licensed library — you can read exactly what runs on your device.

This page uses heic2any (640+), released under MIT. It runs entirely in the browser tab, which is why your files never leave the machine: there is no server to send them to. Nothing here calls an API, and there is no account to create.

Related guides

Longer reads on the same workflow, from the OpenFilmo blog.

Other free browser tools

Same principle: they run on your device and cost nothing to use.

Frequently asked questions