To prepare an iPhone HEIC photo for a destination that wants JPEG, open the original in a supported application or browser, export a new JPEG copy, and inspect it before posting. Changing the filename from .heic to .jpg is not a conversion. Changing the camera's Most Compatible setting affects future photos, not the existing image.

Apple's HEIF guidance explains native compatibility, export and capture settings. The HEIC-to-JPG tool can create a local copy when your browser decodes the source. It cannot add a missing browser decoder by changing export quality.

First confirm which problem you have

A file that will not open is a compatibility problem. A file that opens but exceeds a byte cap needs a size decision. A photo that looks flat or different in brightness may involve HDR or display behavior.

Do not use compression to solve all three at once. If the browser cannot decode the file, a different JPEG quality value will not help. If the JPEG already looks soft, increasing its byte size does not recover detail.

Keep the source while you diagnose the issue. Give the delivery copy a different name so it is easy to distinguish from the camera original.

HEIF, HEIC and JPEG in a sharing workflow

Apple uses HEIF for supported still-image capture. You may see an .heic filename in the library or Files. A receiving app can have different format support from the application that originally displayed the photograph.

JPEG is a widely used delivery format, but compatibility does not make it lossless or automatically smaller. It cannot store transparent pixels, and an ordinary JPEG export is not an editable camera master.

Apple also documents that some sharing routes may automatically create a more compatible version for a receiving device. Do not assume every handoff behaves identically. Inspect the actual file received when its identity or quality matters.

Convert an existing image in a browser

  1. Open the HEIC-to-JPG converter in a browser that supports your source.
  2. Select the original HEIC from your photo or file picker.
  3. Start with Keep original pixels and JPEG output to separate conversion from resizing.
  4. Inspect the preview, orientation and visible colors.
  5. Download the JPEG and open it in the application that needs it.
  6. Check its dimensions and bytes before applying an additional size cap.
Try it on your own photoSocial-ready photos, smaller files, nothing uploaded
Compress a photo

Processing happens on your device. If decoding fails, the tool does not send the image to a conversion server as a fallback. Use a supported native application instead.

Support can vary with browser, operating system and the particular source file. One successful HEIC does not prove every HEIF variant will open. This guide does not claim a new device-by-device compatibility test.

Use a native export when needed

Apple documents opening a HEIF image in Photos or Preview on a Mac, then choosing File and Export to save another format such as JPEG or PNG. Follow the current application's controls and keep the original.

On an iPhone or iPad, use a supported export or conversion workflow that produces a separate file. Apple's Shortcuts guide is a reference for creating repeatable actions. Check the output rather than assuming a shared photo is always converted to JPEG.

If your immediate goal is an original-file handoff, conversion may be unnecessary. Agree on the format with the receiver first. They may prefer the original for an editing workflow rather than a smaller delivery JPEG.

Change future capture only if it serves your workflow

On supported devices, Apple's documented route is Settings › Camera › Formats › Most Compatible. New photos then use JPEG. High Efficiency returns to the newer space-saving formats.

That preference does not retroactively change the library. It also does not guarantee that future JPEGs have fewer bytes. Choose it for compatibility when that is useful, not as a universal compression trick.

Avoid changing unrelated camera settings while troubleshooting one rejected attachment. First confirm what the destination accepts and what file you actually selected.

Inspect the conversion before resizing

Compare the original and the JPEG at a similar display size. Check faces, fine texture, smooth gradients and the edges of any lettering. Confirm that the portrait orientation is correct.

The same quality number can produce different results across encoders. A quality control is not a percentage of original detail kept. Read the JPEG explanation if a high setting still produces artifacts or a surprisingly large file.

If the destination needs fewer pixels, make that a separate decision. An avatar, full-screen image and form attachment can require different copies. Keep the master instead of replacing it with one reduced version.

Color, HDR and metadata need separate care

A photo can contain more than a simple visible bitmap. HDR information, color profiles, capture metadata and editing adjustments may matter to a later workflow. A new browser raster export should not be assumed to preserve all of them.

If the image looks washed out, compare a deliberate SDR export from a suitable editor. Do not repeatedly raise JPEG quality expecting it to repair tone mapping or a display difference. The HDR sharing guide explains that comparison.

This tool does not copy the original photo's EXIF into its raster delivery export. Keep the source when you need capture details or provenance. Removing some metadata is not evidence that every possible sensitive detail has disappeared from the visible image.

Choose the later sharing route

For a social post, inspect the platform composer after selecting the JPEG. Format conversion does not guarantee unchanged delivery or enable a missing quality setting.

For WhatsApp, the HD-or-document guide separates chat media from an original-file handoff. For another app, check its actual accepted formats and upload error.

If a form is involved, check your notification for the required format, pixels and byte range. A valid JPEG can still be the wrong application image.

Limits and checklist

  • Keep the HEIC original.
  • Separate decoder failure, file size and color problems.
  • Export a real JPEG rather than renaming.
  • Treat Most Compatible as a future capture preference.
  • Check the downloaded image in the receiving application.
  • Do not assume HDR, metadata or editing information is preserved.

Source review: 20 October 2026. Apple's HEIF and Shortcuts documentation above provides the native-workflow reference. Browser canvas export explains the local raster export interface, not a guarantee about all HEIC variants or social-app processing.