anytools
Image · 55 tools · nothing uploads

HEIC to JPG

Turn an iPhone HEIC photo into a JPG for Windows and for upload forms. There is no way back: nothing here writes HEIC, and no encoder exists.

Input

Options

HEIC to JPG decodes what an iPhone saved with libheif and writes an ordinary JPEG, the format every editor and viewer already reads. Windows machines and older software that turn the original away open the copy without complaint. The trip runs one way only: no wasm encoder for HEIC exists anywhere, so nothing here turns the JPG back.

Questions

Why is there no JPG to HEIC page?

Because nothing in this pipeline can write HEIC. No WebAssembly HEVC encoder exists here, for patent reasons, so HEIC can only ever be a source format, never an output.

What is lost converting an iPhone photo?

The HEIC compression advantage is lost, since JPEG needs more bytes for the same picture, and metadata such as camera EXIF tags does not survive the decode to pixels. The picture itself is not degraded beyond ordinary JPEG encoding at the chosen quality.

Which engine handles this?

libheif-js, a WebAssembly build of the same library iOS and macOS use, decodes the HEIC, and jSquash encodes the JPEG. Both run in Node, on the command line, through MCP and in the browser, with no consent step required.

What size should I expect?

Usually larger than the original HEIC, since HEVC-based compression is more efficient per pixel than JPEG at a comparable visual quality. The exact difference depends on the quality option, default 80.

What is the reverse page?

There is none, and there cannot be one. Converting a JPG to HEIC is not possible anywhere on this site, since no encoder for it exists.

Related Image tools

n→nPNG to JPGFlatten a PNG into a JPG. Transparency has nowhere to go and arrives as a solid block, and hard edges are the exact thing JPEG rings around.Runs on each file you dropn→nJPG to PNGRewrite a JPG as a lossless PNG. Every block edge and ring the JPEG already baked in is copied across exactly, in a much larger file.Runs on each file you dropn→nWebP to JPGTurn a WebP into a JPG. Any alpha is flattened onto a background nobody picked, and a lossy WebP is put through a second lossy encoder.Runs on each file you dropn→nPNG to WebPRe-encode a PNG as WebP. The alpha channel survives and the losslessness does not, because quality defaults to 80 and text edges are redrawn.Runs on each file you dropn→nJPG to WebPRe-encode a JPG as WebP. The old compression artefacts are picture now, so the WebP encoder spends bits keeping them rather than clearing them.Runs on each file you dropn→nWebP to PNGStore a WebP as a lossless PNG. The transparency survives, so do the details WebP already discarded, and the file grows several times over.Runs on each file you dropn→nAVIF to JPGOpen an AVIF as a JPG. The same picture costs several times more bytes here, because JPEG needs them to look the way the AVIF looked.Runs on each file you dropn→nAVIF to PNGSave an AVIF as a PNG. Decoding lands on 8-bit RGBA first, so a 10-bit AVIF is flattened before PNG stores the result losslessly.Runs on each file you drop