AVIF for E-Commerce Product Images 2026: Where It Wins, Where It Breaks and What to Upload

AVIF is the smallest mainstream image format available in 2026. It routinely produces files around 50 per cent smaller than JPEG and roughly 20 to 30 per cent smaller than WebP at matching visual quality. If you have read anything about page speed in the last year, someone has told you to switch to AVIF.

Here is the part that guide never mentions: almost every marketplace you sell on will reject an AVIF file outright. Amazon, Shopee, Lazada, Etsy, eBay and Google Merchant Center all refuse it. So the honest answer for a seller is not "switch to AVIF" or "ignore AVIF" — it is that AVIF belongs in one specific place in your workflow and nowhere else.

This guide explains where AVIF genuinely helps, where it will break your listings, and what file you should actually be uploading in each situation.

What AVIF is, in one paragraph

AVIF (AV1 Image File Format) wraps a still frame of the AV1 video codec in an image container. It supports lossy and lossless compression, transparency, animation, wide colour gamut and HDR, and 12-bit colour depth. Because AV1 was engineered for maximum compression rather than speed, AVIF squeezes files much harder than JPEG or WebP — and pays for it in encoding time.

Browser support in 2026: effectively solved

Support is no longer the blocker it was three years ago. Global support now sits at roughly 94 to 95 per cent, with native decoders in Chrome 85+, Firefox 93+, Safari 16.1/16.4+, Edge 121+ and Opera 71+. WebP remains ahead at about 97 per cent, but the gap is under three percentage points and shrinks each month as old iOS devices age out.

For a shop selling to Singapore, Australia, the UK or North America, unsupported traffic is a small single-digit percentage — and those visitors are handled automatically by a proper fallback, which every serious CDN already does for you.

The rule that matters: delivery format is not upload format

This is the distinction that trips up most sellers. There are two completely separate jobs an image file does:

• Delivery — the file a shopper's browser downloads when they load your product page. Here, smaller is better, and AVIF wins.
• Upload / source — the file you hand to Shopify, a marketplace, a feed or an agency. Here, compatibility beats size, and AVIF loses badly.

Modern platforms already handle the delivery side without your involvement. Shopify's CDN converts and serves WebP — and AVIF where the browser supports it — automatically, regardless of what you uploaded. Cloudflare, Cloudinary, Fastly and most image CDNs do the same. You are not choosing your delivery format by choosing your upload format; the CDN is choosing it for you, per visitor, per browser.

Which means uploading AVIF gains you nothing on a platform that auto-converts, while costing you compatibility everywhere else.

Where AVIF is rejected in 2026

Accepted upload formats across the platforms sellers actually use:

Notice that Google Merchant Center accepts WebP but not AVIF. That single line kills the idea of a single AVIF master for a multi-channel seller. If your feed points at AVIF URLs, you will collect "unsupported image type" errors and your products will stop serving in Shopping.

The three real downsides nobody mentions

1. Encoding is slow

AVIF encodes roughly 5 to 10 times slower than JPEG, and server-side encoders can take an order of magnitude longer than WebP at comparable settings — worse still at high-effort presets. For one hero image, irrelevant. For a 400-image batch on a laptop, that is the difference between a coffee break and an afternoon.

2. No progressive rendering

JPEG can paint a rough version of an image and sharpen it as bytes arrive. AVIF cannot. On a slow 4G connection the browser waits for the whole file, so the shopper sees nothing, then everything. A 40 per cent smaller file that appears all at once can feel slower than a larger file that fades in — particularly for large hero images on mobile.

3. Decoding costs CPU

AV1 decoding is heavier than JPEG decoding. On current phones this is invisible. On a five-year-old budget Android loading a gallery of twelve images, it is not always invisible. If a meaningful share of your traffic is older low-end devices, test before committing.

Where AVIF actually earns its place

AVIF is worth the effort in these cases:

• Large lifestyle and banner images on your own store — big photographs with gradients, skies, fabric and soft shadows are exactly what AV1 compresses best. This is where the 30 per cent saving over WebP is real.
• Image-heavy collection pages — 40 thumbnails at 25 KB instead of 40 KB is a measurable Largest Contentful Paint improvement.
• Photos with transparency — AVIF handles alpha far more efficiently than PNG. A transparent product cut-out that is 800 KB as a PNG is often under 80 KB as an AVIF.
• Anywhere a CDN generates it automatically — free wins with no workflow change. This is most sellers' entire AVIF strategy, and that is fine.

Where it does not help

• Small images under about 10 KB — AVIF's container overhead can make tiny icons and swatches larger than a well-optimised PNG or WebP.
• Flat graphics, logos and line art — lossless WebP or PNG usually beats AVIF on hard-edged, few-colour graphics.
• Anything leaving your website — marketplaces, feeds, email, supplier catalogues, wholesale line sheets, print. All of it wants JPEG.

A colour-accuracy warning

AVIF's support for wide colour gamut and HDR is a genuine advantage for photographers and a genuine trap for sellers. If you encode from a Display P3 or HDR source without converting to sRGB and embedding the profile, colours can render oversaturated on some devices and flat on others. Product colour that shifts between devices drives returns and "not as pictured" disputes. Convert to sRGB before encoding, every time.

The workflow that survives all of this

Keep one high-quality master and generate everything else from it. Never treat a compressed delivery file as your source of truth.

1. Master: shoot RAW, edit, export a high-quality sRGB JPEG (quality 90 to 95) or 16-bit TIFF at 2,000 to 3,000 px on the longest side. This is your archive.
2. Marketplace uploads: resize and export sRGB JPEG at quality 80 to 85. Square 2,000 x 2,000 px covers Amazon, Etsy and eBay; 1,000 x 1,000 px or 1,200 x 1,200 px suits Shopee and Lazada, staying under the 2 MB Shopee cap. Batch resizing and format conversion across several marketplace presets is exactly what PixelPrep was built to do in one pass.
3. Google feed: JPEG, minimum 500 x 500 px for every product following the 2026 product data specification update, which retired the separate apparel and non-apparel minimums.
4. Your own site: upload JPEG or PNG and let the CDN emit WebP and AVIF per browser. Only hand-roll AVIF if you self-host images with no image CDN in front of them.

If you do serve AVIF yourself, use a <picture> element with AVIF first, WebP second and JPEG last so every browser gets something it can render.

Quick decision checklist

• Uploading to any marketplace? Use JPEG. Never AVIF.
• Sending a Google Shopping feed? JPEG, PNG or WebP. AVIF will error.
• On Shopify, BigCommerce or a CDN-backed store? Do nothing — AVIF is already being served where it helps.
• Self-hosting a heavy site? Add AVIF with WebP and JPEG fallbacks in a <picture> element.
• Image under 10 KB, or a flat logo? Stay on WebP or PNG.
• Always convert to sRGB before export, whatever the format.
• Archive a high-quality master. Compressed files are outputs, not sources.

AVIF is a genuinely better compressor and it is worth having in your delivery chain. It is simply not a file you should ever hand to a marketplace in 2026 — and on most modern platforms, you are already getting its benefits without changing a single thing about how you export.