Convert AVIF to HEIC

How it works

The conversion has two distinct stages. First, the server decodes the AVIF, which normally means using an AV1 image decoder to reconstruct color and alpha pixels. Second, an HEVC-capable image encoder compresses those pixels and places the result in a HEIF container. The .heic extension identifies a common HEIF image profile; it does not turn AV1 data into HEVC or make every HEIF reader equivalent.

This decode-and-encode path is unavoidable because AVIF and HEIC describe image data with different coding systems. There is no safe compressed-data shortcut that keeps the AVIF payload while claiming it is HEIC. Re-encoding can preserve dimensions and the broad visual subject, but quality, file size, metadata support, and alpha handling depend on the source and the target encoder.

Compatibility before compression

The most convincing reason to make this conversion is a known receiving workflow. An Apple-oriented archive may be built around HEIC files from cameras and phones, or an application may accept HEIF while offering no AVIF import. In that setting, matching the expected codec family can remove friction even when the file size is not dramatically different.

The opposite decision applies to web delivery. AVIF is commonly selected because modern browsers can decode it efficiently, while HEIC remains inconsistent in browsers and content-management systems. A successful preview in Photos proves little about a web upload form. Test the precise path, including thumbnails, editing, downloads, and older clients, before converting a library in bulk.

Protect the source

Both formats may be lossy, and a second generation is not a quality-neutral move. For photographs, inspect skies, hair, foliage, and high-contrast edges after export. For screenshots or diagrams, look closely at one-pixel lines and text because an encoder tuned for photographic content may treat those details less kindly. Keep the AVIF and, where available, the original camera or design asset so another export can start from better data.

Two containers, two very different support stories

AVIF and HEIC are close cousins — both wrap modern video-codec compression in an ISO base media container — and they landed in almost opposite places.

AVIF uses AV1, which is royalty-free, and that is why it spread through the web. Every current browser decodes it, and it is a reasonable format to serve to strangers.

HEIC uses HEVC, which is covered by patent pools with real licensing costs. The consequence is that HEIC is excellent inside Apple's ecosystem — it is what iPhones shoot by default — and awkward outside it. Windows needs a codec extension, browsers do not display it, and many web forms and content systems reject it outright.

So converting toward HEIC is a narrowing move, and it is worth being clear about why you are making it. The good reason is a destination that requires it: an Apple-native workflow, a photo library that wants its own format, a device or application whose import list names HEIC. The bad reason is expecting it to work generally, because it will not.

If the goal is a smaller file that people can actually open, the AVIF you already have is the better artifact almost everywhere. If the goal is maximum compatibility, neither is the answer — JPEG remains the format nothing refuses.

Metadata usually survives, and that is not always what you want

Both formats carry the full EXIF block: capture time, camera and lens, software, orientation, and on photographs taken with location services enabled, precise GPS coordinates.

Conversion between them generally preserves that data, which is the right default for a personal library where the information is the point. It is worth knowing anyway, because a converted file is often a file about to be sent somewhere, and the coordinates of where a picture was taken are a meaningful disclosure.

The other detail worth checking is the color profile. Both formats can carry wide-gamut and HDR information, and both can carry an ICC profile describing how their values should be interpreted. A conversion that drops the profile produces a file whose colors are technically unchanged and visibly different, usually flatter or oversaturated depending on the display. Compare the two on the same screen before assuming the transfer was clean.

If the file is going to be shared rather than archived, strip the metadata after converting.