· Andrei M. · Product Management · 5 min read
AVIF vs WebP for Product Images, Why HEIC Won't Display, and How SVG Can Hide Scripts
Which image format should an online store use? Compare AVIF, WebP, HEIC and SVG on browser support, platform acceptance and upload safety, and see how MicroPIM handles each one when you upload product images.

AEO answer: For product photos, WebP is the safest modern default and AVIF gives smaller files where you can keep a fallback. HEIC is an iPhone capture format that most browsers cannot display, so convert it to JPEG on upload. SVG suits logos and icons, not photos, and must be sanitized before you store it because it can contain scripts.
Product images arrive in whatever format the supplier, photographer or phone produced. Some load fast, some cannot be shown in a browser at all, and one can carry code. This guide compares AVIF, WebP, HEIC and SVG, shows what stores and Google accept, and explains how MicroPIM treats each format on upload.
Last verified: November 2026, against MicroPIM’s media upload code (released September 2026), Can I use, MDN, web.dev, Shopify Help Center and Google Merchant Center documentation.
Which format is best for product photos?
Use WebP as the default and AVIF where you can serve a fallback. Keep JPEG as the format that always works.
| Format | Best for | Browser support (Can I use) |
|---|---|---|
| JPEG | Fallback for everything | Universal |
| WebP | Default modern photo | Chrome 32+, Firefox 65+, Safari 16+, about 97% of usage |
| AVIF | Smallest photo files | Chrome 85+, Firefox 93+, Safari 16.4+, about 96% |
| HEIC | Phone capture, not the web | Safari 17+ only, about 17% |
| SVG | Logos, icons, diagrams | All current browsers (MDN) |
On size, web.dev says WebP images are usually 25-35% smaller than JPEG and PNG equivalents. MDN says AVIF generally compresses better than WebP but lacks progressive rendering and recommends fallbacks. We do not publish our own savings figures. Test your own catalog, because results depend on the photos.
When should you use HEIC or SVG?
HEIC is what iPhones save by default. Treat it as a source file, not a web file. Browsers other than Safari cannot show it, and many tools downstream cannot read it.
SVG is a vector format. MDN says it is ideal for diagrams and icons and generally not useful for photographs. Use it for brand logos, size icons and badges, where it scales at any resolution.
What do marketplaces and stores accept?
Check each channel, because lists differ:
- Shopify lists PNG and JPEG as best, and also accepts TIFF, BMP, GIF, SVG, HEIC and WebP. AVIF is not in that list. Limits are 5000 x 5000 px and under 20 MB per image (Shopify Help Center).
- Google Merchant Center
image_linkaccepts JPEG, WebP, PNG, GIF, BMP and TIFF, with a 16 MB and 64 megapixel limit. AVIF, HEIC and SVG are not listed (Google).
So a catalog that only holds AVIF or SVG will need a JPEG or PNG for feeds. We did not verify Amazon’s current rules for this post, so check Seller Central before you rely on any format there.
How do you handle uploads safely and at scale?
OWASP’s file upload guidance says to allow only needed types, not trust the Content-Type header, and set a file size limit. Here is what MicroPIM does:
- One allow-list. JPEG, PNG, GIF, WebP, AVIF, SVG and HEIC are accepted from one shared policy. Upload, URL import and bulk archives all read it.
- Detection from bytes. The format is read from the file content, not the name or the browser’s MIME type.
- Size caps. 50 MB for raster images and 5 MB for SVG.
- HEIC is converted to JPEG at quality 90. The original HEIC is kept outside the public folder and is downloadable through an authenticated route.
- SVG is sanitized with a sanitizer library that strips scripts and remote references. Files with a DOCTYPE or entity declarations, or with script, foreignObject or event handlers left after cleaning, are rejected.
- SVG is served with a sandbox policy, so even a missed payload cannot run in the admin session.
- WebP copies are not forced on every upload. Extra optimized copies are created only for files stored on S3 when image optimization is enabled. SVG is skipped.
Scanning archives for malware is a separate job, covered in bulk media virus scanning. Hosting and delivery are covered in CDN for product images.
What we got wrong, and current limits
Our first plan stored converted HEIC originals on S3 and pushed them to Shopify. The shipped version keeps them on local disk instead, and the plan to move them is not done.
Current limits:
- Shopify gets the converted JPEG, not the HEIC original, because sync sends the media’s CDN URL.
- AVIF and SVG are not filtered per channel yet. Pushing them to platforms that reject them, such as Magento, WooCommerce or Gomag, may fail for that image.
- AVIF optimization needs server support. Without AVIF encoding on the server, AVIF files are not optimized further.
- SVG storage location is not the defense. Sanitizing and headers carry the security, so do not disable them.
Frequently Asked Questions
Is AVIF supported by all browsers? No. Can I use shows about 96% of usage, and MDN recommends a fallback.
Should I convert iPhone HEIC photos? Yes. Only Safari 17+ displays HEIC, so convert to JPEG and keep the original.
Is SVG safe to upload? Only after sanitizing, and only for logos and icons.
Does image format affect SEO and Core Web Vitals? Indirectly, through file size and load speed. See product page SEO.
MicroPIM is our product. This post describes how it handles the problem, and the general advice applies with any tool.
If you want to upload images in bulk and keep one clean version per format, book a demo. The release is listed in the changelog, and delivery speed is in CDN for product images.





