HEIC to AVIF Converter
Make compact AVIF images from iPhone HEIC photos for websites and apps, encoded on your own device.
Options
Why AVIF for web images
AVIF is a still image format built on AV1, the royalty-free video codec from the Alliance for Open Media. For photos on a website, it usually produces smaller files than WebP and JPG at a similar level of visible quality, which means lighter pages and less data spent by visitors on mobile connections.
That makes it a natural destination for iPhone photos headed to a site, a blog or an app. The HEIC original looks great, but most browsers will not display it, while every major current browser displays AVIF.
HEIC and AVIF are cousins
Both formats store a photo the way a video codec stores a single frame, inside the same HEIF container family. HEIC uses HEVC (H.265) compression, whose patent licensing has kept it out of most browsers. AVIF swaps in AV1, which the major browser makers support. The HEIF vs HEIC explainer untangles the naming.
Converting between them is not a lossless rewrap. The HEIC is decoded to pixels and then encoded again with AV1, so the quality setting you choose decides how much detail survives. A good conversion can match the original closely, but it cannot add detail the HEIC did not hold.
AVIF next to the other web formats
| AVIF | WebP | JPG | HEIC | |
|---|---|---|---|---|
| File size at similar quality | Usually the smallest | Smaller than JPG | Largest of the four | Small, in the same range as AVIF |
| Shows in current browsers | Chrome, Edge, Firefox, Safari | Chrome, Edge, Firefox, Safari | Everywhere | Safari only |
| Older browsers and apps | Patchy | Good | Universal | Poor |
| Encoding speed here | Slow, WebAssembly encoder | Fast, but not every Safari can make it | Fast | Not an output |
| Best for | Web pages where every kilobyte counts | Broad web compatibility with good compression | Sharing, email, anything | Storage on Apple devices |
The comparison of HEIC, AVIF, WebP and JPEG XL goes further into how each format compresses and where each one is heading.
Converting photos for a website, step by step
- Pick the resize preset that matches the largest size the image will appear at: 1920 for a full-width banner, 1280 for an image inside an article column, 800 for cards and thumbnails. Fewer pixels also means a much faster encode.
- Drag the quality slider down from the default of 90 to about 70 as a starting point.
- Add one representative photo, not the whole set. The first AVIF conversion also downloads the encoder, so give it a moment.
- Note the file size, then try 60 and 80 on the same photo and compare the results at full size.
- Once you are happy, add the rest. Settle the settings first, because changing any option re-encodes the entire batch, and with AVIF that takes a while.
- Need several widths for responsive images? Run the batch once per preset with a filename template such as
{name}-1280, and download each set as a ZIP before switching to the next width.
Why AVIF is the slowest format here
Browsers can show AVIF, but they do not give web pages a built-in way to create it, the way they do for JPG and PNG. So the first time you choose AVIF, HEIC to PIC fetches a WebAssembly build of an AVIF encoder from a public CDN. That download is code only; your photos stay on your device, as how it works explains.
The encoder itself is the bigger cost. AV1 gets files small by testing many ways to predict and compress each block of the image, and that search is heavy work for a processor. A full-resolution photo takes noticeably longer than the same photo as JPG, more so on a phone or an older laptop.
- Resize before encoding. Halving the longest edge cuts the pixel count to a quarter.
- Convert in smaller groups on phones and low-memory machines.
- Keep the tab in the foreground. Mobile browsers may pause pages you switch away from.
Choosing an AVIF quality setting
The quality slider runs from 40 to 100. Lower numbers give smaller files, and AVIF holds up at settings where a JPG would start to look blocky. When AVIF does run short of data, it tends to smooth away fine texture such as hair, grass and fabric rather than break into squares, so judge it by looking closely at those areas.
The default of 90 suits portfolio work where detail matters most, but it is generous for everyday web images and can give you files larger than you need. Test a few values on the same photo; the point where you stop seeing a difference is your setting for that kind of image. Smooth skies and gradients show problems first, so include one in your test if the batch has them.
One limit to know: the output is 8 bits per channel. AVIF itself can store HDR and 10-bit color, but this converter writes standard images, so an iPhone HDR photo comes out with ordinary dynamic range.
Checking the files before you publish
Open a converted AVIF in a browser tab at 100 percent zoom rather than judging a small preview, since compression artifacts hide at thumbnail size. Look at the areas AV1 finds hardest: fine hair, foliage, lettering inside the photo and smooth gradients.
Then test it where it will live. Upload one file to your site builder or content management system before converting the rest, because some still refuse AVIF or convert it on upload. If an image spans the full width of high-density phone and laptop screens, compare the 1920 and 2048 presets to see whether the extra pixels are worth the extra bytes.
When AVIF is the wrong choice
AVIF is a format for publishing, not for sending. A friend's phone, a relative's laptop or a client's email app may open it, or may show a blank icon, depending on their software. For anything that goes to another person, convert to JPG.
Desktop support is also uneven. Older versions of photo editors and office suites, and some content management plugins, do not accept AVIF, and print shops rarely want it. Check the tools at the other end before converting a large library, and keep your HEIC originals either way.
On your own site, older browsers that cannot display AVIF still need something to show. The usual answer is a picture element that offers AVIF first with a fallback: a source with type="image/avif", followed by an img pointing at a JPG or a WebP made from the same HEIC. Current support details are on caniuse.com.
Rate this tool
Frequently asked questions
Do all browsers display AVIF images?
Current versions of Chrome, Edge, Firefox and Safari do. Older browsers, and devices that can no longer update, may not, so serve a JPG or WebP fallback with a picture element.
Why does HEIC to AVIF take so much longer than JPG?
AVIF is made by a WebAssembly encoder running on your processor, and AV1 compression does a lot of work per image. Resizing first and converting in small groups speeds it up.
What AVIF quality setting should I use for a website?
Start around 70, then compare 60 and 80 on the same photo. Use the lowest value where you cannot see a difference at the size the image is displayed.
Is AVIF smaller than the original HEIC?
Not automatically. Both formats are efficient, so at the default quality of 90 the AVIF can be similar in size or larger. Lowering the quality and resizing is what makes it small.
Does AVIF keep the HDR from my iPhone photo?
No. The format can store HDR, but this converter writes 8 bits per channel, so HDR and 10-bit color are not preserved.
Can I email AVIF files to friends?
You can, but many phones, computers and email apps may not open them. JPG is the safer choice for anything you send to people.
Does downloading the AVIF encoder send my photos anywhere?
No. The encoder code comes from a public CDN the first time you choose AVIF, and your photos are decoded and encoded on your own device.
Should my site use AVIF or WebP?
AVIF usually gives smaller files, while WebP encodes faster and works in more older software. Many sites serve AVIF first and keep WebP or JPG as the fallback.