What does HEIC to JPG do?
It decodes one supported HEIC or HEIF still photo with heic2any and re-encodes it as a JPG compatibility copy.
Upload one HEIC or HEIF photo, pick JPG quality and optional size limits, then compare the decoded preview with the final JPG.
Preparing the editor...
The guide and instructions on this page are available while the tool loads.
HEIC to JPG decodes a supported HEIC or HEIF still photo and re-encodes it as JPG so websites, email clients, Windows apps, and JPG-only upload fields can open the file. Keep the original HEIC when you need the efficient source copy.
Accept one .heic or .heif file (or image/heic / image/heif) up to 20 MB. After a local decode preview loads, choose Smaller (75), Balanced (85, default), or High quality (92), or fine-tune quality from 60 to 100. Optional max width and max height proportionally shrink oversized photos and never enlarge. Convert, then compare the decoded preview with the final JPG and review the byte-size change. Download is {base}.jpg with automatic and manual download—no ZIP and no batch queue.
JPG encoding is lossy, so detail and file size depend on the quality setting. A JPG may be larger than its HEIC source because HEIC is often more storage-efficient. JPEG cannot keep transparency, and this tool has no background-color control. Orientation depends on the heic2any/libheif decoder rather than a separate EXIF-rotation step. HDR, Display P3, wide-gamut, and high bit depth are not guaranteed. If the decoder returns multiple images, only the first blob is used. Live Photo video, depth maps, and auxiliary assets are not exported. EXIF, GPS, capture date, and ICC profiles are not deliberately copied into the JPG.
Conversion stays in your browser. Photo bytes are not posted to a conversion API. Loading the page or starting a decode may fetch the heic2any package (including its libheif decoder) and ordinary website assets. Identified analytics may include sizes, dimensions, quality, preset, and status codes—not filenames, pixels, or metadata contents.
Not every HEIC variant opens successfully across browsers and devices. Large photos can take several seconds and use substantial memory. Sequence MIME types and .hif are not accepted. Reset clears the workspace and is not a dedicated mid-run cancel control. Keep originals when orientation, color, or metadata matter.
Typical tasks this tool is built for.
HEIC decoding and JPG encoding run locally with heic2any and optional canvas downscaling. The photo is not uploaded for conversion. The browser may load the heic2any/libheif decoder bundle as a site asset. DevToolKit may receive usage or diagnostic metadata such as dimensions, quality, preset, byte counts, page context, and result codes. Identified analytics do not include the filename, raw photo bytes, EXIF values, or GPS data.
Practical tips before you download or share the output.
One HEIC/HEIF file up to 20 MB (.heic/.heif or image/heic/image/heif). Decoder: heic2any ^0.0.4 (libheif). Quality 60–100 (default Balanced 85); optional max width/height downscale only. Output {base}.jpg. No batch, ZIP, background-color, or cancel control. First returned image only for multi-image containers. Live Photo video not converted. JPG may be larger than HEIC. Orientation, HDR, color profiles, and EXIF/GPS are not guaranteed. Analytics may include sizes, dimensions, quality, preset, and codes—not filename or raw photo.
Longer reads that pair well with this tool.
Image guide
A practical image-preparation workflow: choose the required format, set dimensions, review processing labels, and inspect the exported file before sharing.
Image guide
Use DevToolKit's server-backed, AI-assisted Background Remover with supported files, subject presets, browser-side export controls, and clear review steps.
Image guide
Convert one supported image at a time, review transparency and dimensions, then test the exported file in the destination that needs it.
Common next steps after using this tool.
Compress a JPG, PNG, WebP, or AVIF image with format, quality, and optional resize controls.
Remove an image background, review the cutout, refine its edge softness, and export it with transparency or a new background.
Turn one or more JPG and JPEG photos into a single ordered PDF with one image per page.
Build one ordered PDF from mixed supported image formats, with one ready image on each page.
Select a rectangular region from one JPG, PNG, or WebP with aspect presets, pixel coordinates, and format-aware export.
Rotate one JPG, PNG, or WebP in 90° steps or mirror it horizontally and vertically, then export a new copy in the source format.
Situations where this workflow saves time.
It decodes one supported HEIC or HEIF still photo with heic2any and re-encodes it as a JPG compatibility copy.
Yes. Files named .heic or .heif, or typed as image/heic or image/heif, are accepted. Sequence MIME types and .hif are not listed.
One photo per run. There is no batch queue and no ZIP packaging.
20 MB for the single selected file. There is no separate combined-size limit.
Balanced at 85. Presets also include Smaller (75) and High quality (92). The slider allows 60–100.
No. JPG uses lossy compression. Quality controls how much detail is retained versus file size.
HEIC often stores photos more efficiently than JPEG. A high-quality JPG can grow even when pixel dimensions stay the same.
Not by default. Optional max width and max height proportionally reduce oversized photos and never enlarge them.
There is no separate EXIF-orientation rewrite step. Displayed orientation depends on the heic2any/libheif decode result.
JPEG cannot store alpha. This workflow has no background-color control, so do not rely on it for transparent artwork.
No guarantee. HDR, Display P3, wide-gamut, and high bit depth are not explicitly managed. Compare color when it matters.
They are not deliberately copied. Treat metadata loss as a side effect of decode/re-encode, not as a dedicated EXIF remover.
No. Only the still image path is converted. Paired Live Photo video is ignored.
If the decoder returns an array of blobs, the tool uses the first one. Extra frames, bursts, depth maps, and auxiliaries are not exported as separate JPGs.
Locally in the browser. Photo bytes are not uploaded to a conversion service.
heic2any (with libheif) is loaded as a client bundle when needed. That is separate from uploading your photo for processing.
The download is named {base}.jpg, where {base} is the source filename without its extension.
No. One JPG is produced, with automatic download plus a manual Download JPG button.
The settings preview is a lower-quality local decode used to confirm the file opens. After conversion, compare that preview with the actual encoded JPG result.
It can, when the device can run heic2any. Large HEIC files may be slow or memory-heavy on phones.
There is no dedicated cancel control during decode or encode. Reset clears the workspace afterward and is not true mid-run cancellation.
Identified events may include engine, input bytes, width, height, quality, preset, output bytes, size-delta percent, and error codes. They do not include the filename, raw photo bytes, EXIF values, or GPS data.
Browse related tools or open the full workspace.