HEIC to JPG

The conversion creates a new image file. It is not a simple filename change, and it is not guaranteed to make the file smaller. The browser decodes the primary still image from the HEIC container, draws those pixels onto a canvas and encodes a fresh JPG. That process improves compatibility, but it also changes the file structure and removes metadata that is not copied into the new image.

What changes when HEIC becomes JPG

HEIC and JPG can store the same visible photograph in different ways. Changing the format affects more than the extension:

The most important gain is compatibility. A site, document editor or older application that rejects HEIC may accept the generated JPG. The main trade-offs are lossy JPEG encoding, removal of embedded metadata and loss of container items other than the primary still image.

How to convert HEIC to JPG on this page

1. Add the files. Choose or drop up to 20 .heic or .heif files. Each file can be up to 50 MB, and the batch can total up to 200 MB.
2. Choose JPG quality. Start at 92% for a high-detail photo. Lower the value when smaller output matters more than subtle texture.
3. Choose a dimension limit. Keep the decoded dimensions or limit the longest side to 4096, 2560, 1920 or 1600 pixels. Smaller source images are not enlarged.
4. Choose a background. JPG cannot store transparency. White is the safest default; soft gray or dark can be useful for an unusual HEIC file with transparent pixels.
5. Convert and inspect. The tool decodes each primary image, creates the JPG files and reports the output dimensions, actual byte size, container image count and metadata status.
6. Download. Save one JPG or download all successful results in a ZIP archive.

Files in the same batch use the same quality, dimension and background settings. A failure in one file does not discard the successful conversions from the rest of the queue.

Choose JPG quality with a purpose

The quality control ranges from 60% to 100%. It is an instruction to the browser's JPEG encoder, not a universal visual-quality score. Two browsers can produce slightly different bytes from the same source and setting.

Use these values as practical starting points:

• 90–95%: strong default for photographs that may be edited, printed at modest sizes or inspected closely.
• 80–89%: useful for websites, email and ordinary document uploads where a smaller file is helpful.
• 60–79%: suitable when the destination has a strict size concern and some loss of fine texture is acceptable.

Look at hair, foliage, fabric, text edges, gradients and high-contrast boundaries in the output preview. Those areas tend to reveal JPEG artifacts sooner than a smooth sky or blurred background.

A 100% setting does not restore information lost by the original HEIC encoding and does not create a mathematically lossless JPG. It can also produce a much larger file. If the converted JPG must meet a specific upload limit, create the image here first and then use Image Compressor to measure and reduce the actual result.

Keep or reduce the photo dimensions

Keeping decoded dimensions preserves the number of output pixels reported by the HEIC decoder. This is appropriate when the destination needs the original resolution, when you expect to crop later or when you do not know the required size yet.

A longest-side limit resizes only photos that exceed that value. For example, a decoded 4032 × 3024 image limited to 1920 pixels becomes 1920 × 1440. A 1280 × 960 image remains 1280 × 960 because this tool does not enlarge smaller photos.

Choose dimensions according to the destination, not according to the physical screen where you are converting:

• Keep decoded dimensions for archiving a compatible copy or continued editing.
• Use 4096 or 2560 pixels when substantial detail is still useful but the full camera resolution is unnecessary.
• Use 1920 or 1600 pixels for many web, email and presentation workflows.

The result panel connects this choice to the actual output. It shows both the decoded source dimensions and generated JPG dimensions, so you can confirm whether resizing occurred rather than relying on the selected preset alone.

Primary images, Live Photos and extra data

A HEIC file can be a container rather than one simple bitmap. It may include several top-level images, thumbnails, auxiliary images, depth information or other metadata. A Live Photo also involves motion content outside the still image users usually see.

This page deliberately converts only the primary still image reported by the decoder. The result panel states how many top-level images were found and confirms that the primary image was exported. It does not combine extra images, create an animation, extract a depth map or convert the video part of a Live Photo.

That boundary prevents a successful JPG download from being mistaken for a complete archive of everything in the original container. Keep the original HEIC file when those additional assets may matter later.

The decoder used by this page is based on libheif-js, a browser-compatible distribution of libheif. The decoder is loaded only when conversion starts, so the large format runtime is not part of the initial page interaction.

Check the JPG before downloading

Do not treat a green success state as the only result check. Review the preview and report in this order:

1. Visible orientation and crop: confirm that the photo is upright and no edge content is missing.
2. Fine detail: inspect faces, text, hair, patterns and other areas where JPEG artifacts would be noticeable.
3. Dimensions: compare decoded and output dimensions to confirm whether the longest-side setting resized the image.
4. File size: use the actual JPG Blob size. It can be larger or smaller than the HEIC source because the formats use different compression systems.
5. Container images: if the report shows more than one image, remember that only the primary still was exported.
6. Metadata: assume the output no longer contains source EXIF, GPS, camera settings or color-profile blocks.

Metadata removal can reduce accidental location sharing, but this is a consequence of the current re-encoding path rather than a complete privacy audit. Inspect the generated file separately when it will be published or sent outside your normal workflow.

Illustrative HEIC to JPG examples

Prepare an iPhone photo for a website form

Assume the source is a 4032 × 3024 HEIC photo. Choose 88% quality and limit the longest side to 1920 pixels. The expected JPG dimensions are 1920 × 1440. The actual byte size must be read from the result panel because it depends on the photograph and browser encoder.

Create a high-detail compatible copy

Assume the source decodes to 3024 × 4032. Keep decoded dimensions and use 94% quality. The JPG remains 3024 × 4032, but the file size can be larger than the HEIC source and the original metadata is not copied.

Convert a batch for email

Assume ten HEIC photos are added with 82% quality and a 1600-pixel longest-side limit. Each successful primary image becomes a separate JPG. Download all results as one ZIP, then inspect any failed-file notice before deleting or moving the original photos.

Illustrative examples. They describe settings and dimension calculations supported by this page; exact JPG bytes and visible compression depend on the source image and browser encoder.

Why iPhones create HEIC files

Apple uses HEIF and HEVC media to reduce storage use while retaining modern image capabilities. Apple's support documentation explains that compatible Apple devices can capture HEIF photos and that choosing Most Compatible under Camera Formats makes new captures use JPEG instead. Existing HEIC photos are not changed by that setting.

See Apple's current guidance for working with HEIF or HEVC media when you need to change future camera capture behavior or understand transfers between Apple devices and other systems.

Converting an existing photo remains useful when the receiving website, Windows workflow, document editor or older application does not accept HEIC. Keep the original when storage efficiency, original metadata or Apple-specific editing information may still be valuable.

Local conversion and common alternatives

HEIC conversion is available in broad cloud converters, desktop applications and operating-system workflows. The right choice depends on whether you need local handling, more output formats, metadata retention or automation.

• CloudConvert combines HEIC conversion with a much broader format platform and exposes conversion options. It is useful when a cloud conversion workflow or other output formats are required.
• FreeConvert presents HEIC-to-JPG conversion with additional settings and a hosted upload workflow. Check its current limits and privacy terms before using sensitive files.
• Convertio integrates HEIC conversion into a general cloud converter and provides external file-source options. It can be convenient when files already live in supported cloud storage.

base97 is narrower. Its verifiable difference is a local browser queue with shared quality and size controls, per-file primary-image reporting, visible metadata status, failure isolation and individual or ZIP downloads. It does not claim that its JPEG encoder is universally smaller or more accurate than those services.

This version does not support URLs, cloud-drive imports, server-side conversion, AVIF input, PNG output, animated output, metadata retention, Live Photo video extraction, depth-map export, RAW conversion or automatic target-file-size optimization.

Troubleshoot HEIC conversion

The file is rejected before conversion

Confirm that its extension is .heic or .heif. The page also checks the file's container signature, so renaming an AVIF, JPG or unrelated file to .heic will not make it valid.

The decoder cannot find an image

The container may be damaged, encrypted, created with an unsupported codec variation or contain no decodable primary image. Try exporting the photo again from the original device. Do not overwrite the source while troubleshooting.

The browser becomes slow

High-resolution HEIC decoding uses substantial memory because the complete photo becomes uncompressed pixel data before JPG encoding. Convert fewer files at once, close memory-heavy tabs or choose a smaller source. Files above 12,000 pixels on either side or 50 megapixels are blocked by this page.

The JPG is larger than the HEIC file

That can be normal. HEIC and JPG use different compression methods. Lower JPG quality, select a dimension limit or compress the generated JPG afterward when file size is the priority.

Location or camera information is missing

The page does not copy metadata. Use a workflow specifically designed to retain and verify EXIF or other metadata when those fields are required for evidence, cataloging or professional photo management.

The Live Photo no longer moves

A JPG is a single still image. This tool converts only the primary photo and does not include the paired motion content. Keep the original Apple photo assets when Live Photo behavior must be preserved.

HEIC to JPG FAQ

Is HEIC the same as HEIF?

HEIF is the container format family, while HEIC commonly describes HEIF images encoded with HEVC. This page accepts files using .heic or .heif names and verifies the container before conversion.

Can I convert multiple HEIC photos to JPG at once?

Yes. Add up to 20 files, with a 50 MB limit for each file and a 200 MB batch limit. Successful JPG files can be downloaded individually or together in one ZIP archive.

Does converting HEIC to JPG keep EXIF and GPS metadata?

No. This implementation decodes the primary image pixels and creates a new JPG with Canvas. It does not copy EXIF, GPS, camera settings, color profiles or other embedded metadata into the output.

Will this convert the video part of a Live Photo?

No. The tool exports the primary still image from the HEIC container. It does not extract or convert a paired Live Photo video, depth map, thumbnail or additional container image.

Are my HEIC photos uploaded to base97?

No. The current tool reads, decodes, resizes, encodes and packages the selected files with browser-side code on the current device. It does not send those files to a base97 server.