Convert iPhone HEIC photos to AVIF locally - very small files at high quality, no upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
HEIC and AVIF are technically related: both use modern video-codec technology to store images very small. While HEIC (on HEVC/H.265) is mainly at home in the Apple ecosystem, AVIF is based on the open AV1 codec and is shown directly by every current browser - ideal for the web.
This tool decodes HEIC entirely locally in your browser (libheif) and encodes AVIF with the self-hosted jSquash encoder - no upload, even offline. You get the small file sizes of modern codecs in a format that runs everywhere on the web.
AVIF keeps transparency and at the same quality often yields even smaller files than WebP. The quality slider controls the compression strength; lower values give smaller files. For maximum compatibility with very old software, JPG remains the safe choice.
| Input formats | HEIC, HEIF |
|---|---|
| Output format | AVIF |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: AVIF encoding is compute-heavy; very large HEIC batches take correspondingly longer on older devices. Live Photos are converted as a still image. Very old software may not open AVIF.
No. HEIC is decoded locally and AVIF is encoded locally with jSquash - nothing is uploaded.
At the same quality, AVIF often comes in another 10 to 20 percent below WebP in comparative measurements, sometimes more for photos - in return, encoding takes noticeably longer. On older devices or with large batches, WebP is therefore the faster compromise; AVIF delivers the maximum savings for the web.
Yes. AVIF supports transparency, which is kept during conversion.
AVIF uses the AV1 codec, whose encoding is more compute-heavy than JPG or WebP - in return the files are very small.