AVIF to HEIF: conversion guide

Source · AVIF
Target · HEIF

Drop AVIF files here

or choose files from your device

Converter not available yet

This conversion needs a HEIF/HEVC codec that is not available in this browser engine yet.

  • In your browser
  • No upload
  • Private by design

What happens when you convert AVIF to HEIF?

Animation-capable destination

AVIF and HEIF can represent image animation, but their frame structures are not interchangeable. Retaining motion requires sequence decoding, compositing, timing and loop mapping plus an animation-aware encoder. No such transfer is implemented; a still-only pipeline would lose the sequence.

HDR display encoding

The source can carry HDR information and HEIF has HDR-capable variants. Working radiometric values and display-referred HDR are different representations. Range, primaries, transfer function and signalling must be mapped explicitly; the future engine may instead produce SDR. HDR preservation is not promised by format support.

Encoding mode

HEIF defines the container. Compression may be lossy, lossless or uncompressed depending on its codec binding; one global quality or bit-depth value would be misleading. HEIF permits different encoding modes or container representations. Its format name alone does not promise lossless output, a quality setting or a size reduction. The future engine must choose a supported codec and sample representation; inspect the target’s compression notes below.

AVIF

Source

AVIF

AV1 Image File Format

Compression: Lossy & losslessTransparency: YesMetadata: Exif, XMP, ICC, CICP

AV1-compressed pictures in an image container, with optional alpha, sequences and high-dynamic-range colour.

Explore AVIF format →
HEIF

Target

HEIF

High Efficiency Image File Format

Compression: Depends on variantTransparency: YesMetadata: Exif, XMP, ICC, NCLX

An image container for individual pictures, collections and sequences. The codec inside determines compression.

Explore HEIF format →

Is AVIF → HEIF right for you?

Good choice when

  • HEIF fits your delivery use: Device photography & image collections.
  • Your destination supports the required animation variant.
  • You need HDR-capable delivery and can validate its encoding and colour signalling.
  • You need a transparency-capable destination and will check its supported variant.

Probably not when

  • You require guaranteed animation transfer from the unavailable converter.
  • You require guaranteed scene-linear values or HDR appearance.
  • You assume format-level alpha support guarantees matching transparent edges.
  • You need a guaranteed quality or file size before encoder settings exist.

AVIF to HEIF conversion details

Animation-capable destination
AVIF and HEIF can represent image animation, but their frame structures are not interchangeable. Retaining motion requires sequence decoding, compositing, timing and loop mapping plus an animation-aware encoder. No such transfer is implemented; a still-only pipeline would lose the sequence.
HDR display encoding
The source can carry HDR information and HEIF has HDR-capable variants. Working radiometric values and display-referred HDR are different representations. Range, primaries, transfer function and signalling must be mapped explicitly; the future engine may instead produce SDR. HDR preservation is not promised by format support.
Transparency representation
Both format profiles allow transparency, but this does not promise identical alpha representation. Source variants, target channel precision and alpha interpretation matter. The future encoder must explicitly carry or convert transparency; merely choosing HEIF guarantees no alpha transfer.
Encoding mode
HEIF defines the container. Compression may be lossy, lossless or uncompressed depending on its codec binding; one global quality or bit-depth value would be misleading. HEIF permits different encoding modes or container representations. Its format name alone does not promise lossless output, a quality setting or a size reduction. The future engine must choose a supported codec and sample representation; inspect the target’s compression notes below.
Sample precision & colour
Source and target sample models can differ in precision, channel layout, colour space and transfer function. Lossless compression only preserves the samples actually encoded; a precision reduction or colour conversion can already change them. The future engine defines numeric mapping, orientation and colour conversion; canonical depth facts are listed below where available.
Metadata & colour
Format support does not guarantee that an export preserves metadata or colour profiles. Retention and colour handling depend on the future converter; its engine is not implemented yet.
Compression
AVIF: Lossy & lossless → HEIF: Depends on variant AVIF: AVIF can use lossy or lossless AV1 coding. Chroma subsampling, RGB↔YUV conversion and reduced bit depth can change source values even when the AV1 coding stage is lossless. HEIF: HEIF defines the container. Compression may be lossy, lossless or uncompressed depending on its codec binding; one global quality or bit-depth value would be misleading.
Transparency
AVIF: Yes → HEIF: Yes
Animation
AVIF: Yes → HEIF: Yes
Colour depth
AVIF: 8 / 10 / 12 bits → HEIF: Codec/profile dependent
HDR
AVIF: Optional; colour properties → HEIF: Codec/profile dependent
Multiple images
HEIF: Collections & sequences
Dimensions
Pixel dimensions, page geometry, rendering resolution, resizing and orientation need explicit converter policies. The future engine has not defined them yet.
Metadata
AVIF: Exif, XMP, ICC, CICP → HEIF: Exif, XMP, ICC, NCLX. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.

Common questions

Can the animation be transferred between formats?

AVIF and HEIF can represent image animation, but their frame structures are not interchangeable. Retaining motion requires sequence decoding, compositing, timing and loop mapping plus an animation-aware encoder. No such transfer is implemented; a still-only pipeline would lose the sequence.

Will HDR automatically survive in HEIF?

The source can carry HDR information and HEIF has HDR-capable variants. Working radiometric values and display-referred HDR are different representations. Range, primaries, transfer function and signalling must be mapped explicitly; the future engine may instead produce SDR. HDR preservation is not promised by format support.

Which compression mode will HEIF use?

HEIF defines the container. Compression may be lossy, lossless or uncompressed depending on its codec binding; one global quality or bit-depth value would be misleading. HEIF permits different encoding modes or container representations. Its format name alone does not promise lossless output, a quality setting or a size reduction. The future engine must choose a supported codec and sample representation; inspect the target’s compression notes below.

Are bit depth and colour values guaranteed to match?

Source and target sample models can differ in precision, channel layout, colour space and transfer function. Lossless compression only preserves the samples actually encoded; a precision reduction or colour conversion can already change them. The future engine defines numeric mapping, orientation and colour conversion; canonical depth facts are listed below where available.

Will metadata and colour profiles be retained?

AVIF: Exif, XMP, ICC, CICP → HEIF: Exif, XMP, ICC, NCLX. Which fields are copied, rewritten or omitted will depend on the future engine; retention is not implemented yet.