Images are usually the heaviest part of a store page, so choosing the right format is one of the cheapest speed wins available. For years that choice was JPEG or PNG. Now WebP and AVIF are supported by modern browsers, and store owners keep asking which one to use.
This WebP vs AVIF WooCommerce guide gives a practical answer. It explains what each format is good at, what to watch for, how to serve both safely and how to test the result on your own product images. We follow the format guidance on web.dev, and we do not quote compression percentages, because they depend heavily on the image and the settings.
| Choice | Practical advice for a store |
|---|---|
| JPEG and PNG | Keep as a fallback for older software |
| WebP | A safe default for most product photos |
| AVIF | Test on your largest photos and keep it where it looks right |
| Always | Resize images, keep originals and do not lazy-load the main image |
The short answer on WebP vs AVIF
Use WebP or AVIF for photos wherever you can, and keep JPEG or PNG as a fallback. That is the advice on web.dev’s image format guide, which says that WebP and AVIF offer better overall compression and more features than the older formats and should be used where possible. Both support transparency and animation, and both work in all modern browsers.
So which one for a store? WebP is the safe default because it has been around longer and tools handle it well. AVIF often gives smaller files for photographs, but it can take longer to produce and can look different on some images. For most stores, the best approach is to start with WebP, test AVIF on your biggest images and keep whichever gives the better result.
How the formats compare
| Format | Transparency | Animation | Browser support |
|---|---|---|---|
| JPEG | No | No | All browsers |
| PNG | Yes | Yes (APNG) | All browsers |
| WebP | Yes | Yes | All modern browsers |
| AVIF | Yes | Yes | All modern browsers |
This table follows web.dev. It also tells you that JPEG and PNG remain the only formats supported everywhere, which is why a fallback still makes sense for older software.
Why image format affects your store
Product pages are image heavy, and category pages show many images at once. A heavy image slows the largest contentful paint, which is one of the Core Web Vitals, and slow pages lose visitors. Our WooCommerce speed guide puts images alongside caching and scripts, and our INP guide covers the responsiveness side.
Choosing a smaller format is only part of it. Size, dimensions and loading behaviour matter as much. A 4000-pixel photo in AVIF is still too large for a 600-pixel product slot.
What to check before you convert
Quality
Lossy WebP and AVIF throw away information, and web.dev warns that some colours may not match an equivalent JPEG. For products where colour matters, such as fabric, paint or cosmetics, compare the original and the converted image side by side on a phone and on a desktop monitor.
Transparent images
Both formats support transparency, which is helpful for product cut-outs. Check the edges, because a poor conversion can leave a halo around the object.
Animation
If you use animated GIFs, web.dev recommends replacing them with video. Both WebP and AVIF can animate, but a short video file is usually the better choice for anything longer than a moment.
Text in images
web.dev discourages putting text inside images. Use real text, which is faster, accessible and easier to translate. Our accessibility guide explains why.
How we do it on our own site
We converted our own site’s images to WebP and serve them automatically when the browser supports it, with the original as a fallback. We also create the featured images for new posts in WebP. That is a simple, low-risk setup, and it removed a lot of weight from our pages without changing how they look. We keep AVIF as a later step, to be tested on the largest photographs.
How to serve modern formats on WooCommerce
There are three common routes.
- A plugin or service. Many image plugins convert uploads and serve the best format. Check what happens if the plugin is disabled, whether original files are kept and how the plugin handles very large libraries.
- Server rules. Your host or developer can serve a WebP file when it exists next to the original and the browser supports it. This is invisible to WordPress, so back up first.
- A content delivery network. Some CDNs convert on the fly. This can be simple, but it adds a vendor and a cost.
Whatever you choose, test on staging first and keep your originals. Our backup strategy guide explains why.
Sizes and loading matter as much as format
Serve images at the size they are shown. WordPress creates several sizes for each upload, and the theme should pick the right one. Do not lazy-load the main product image at the top of the page, because that delays the largest element. Do lazy-load images far below the first screen. Set width and height so the page does not jump while images load.
A simple test on your own images
Pick five typical product images, including one with transparency and one with fine detail. Create a JPEG, a WebP and an AVIF version of each at the same visible quality. Write down the file sizes, look at them on a phone and a desktop and note any colour changes. Choose the smallest version that still looks right to you. Repeat for your biggest hero image.
What not to do
Do not convert only a few images and forget the rest. Do not delete the originals. Do not set quality so low that product detail disappears, because customers judge quality from images. Do not rely on a single score from a testing tool, as scores change with each run.
Where payment pages fit
Checkout pages have few images, so speed there depends on scripts and server response, as we explain in our guide to cart abandonment. Save image work for product, category and home pages.
Getting help
If you want your product images converted safely and your pages measured before and after, our website maintenance team can set it up on staging and report the real difference.
Image formats and Core Web Vitals
The largest contentful paint measures how long the biggest element takes to appear, and on product pages that is usually an image. A smaller file helps, but so does everything around it. Make sure the image is requested early, is not hidden behind a script, is served at the right dimensions and comes from a fast server or content delivery network.
If you change only the format and leave a 3000-pixel original in a 600-pixel slot, you have saved less than you could. Our INP guide explains the responsiveness side of Core Web Vitals, which depends more on scripts than on images.
Responsive images in WordPress
WordPress creates several sizes for each image and adds a list of them to the page, so the browser can choose the best fit for the screen. For this to work, your theme must output the list correctly, and you should regenerate sizes if you change themes or image dimensions. Check one product page in your browser’s developer tools and look at which file was downloaded on a phone and on a laptop.
If a phone downloads the full-size original, there is an easy win waiting. This is separate from the format question, and it often matters more.
Workflow for new uploads
A tidy workflow prevents the problem from returning. Resize photos to the largest size your theme will show, export them at a sensible quality, upload them and let your conversion tool create the modern version. Give each image a descriptive file name and a short, honest alt text, because both help search and accessibility. Avoid uploading screenshots of text.
Agree one rule with everyone who adds products, and write it in two lines on a shared page. A store with a hundred product images and no rule will end up with a hundred different sizes.
When AVIF is not worth it
AVIF can be slower to create and may need more processing on big libraries, and some tools handle it less smoothly than WebP. If your store has thousands of images and a modest server, converting everything to AVIF may cost more than it saves. Start with the images that matter most: the home page hero, category banners and your best-selling products. Measure before and after, keep the format that wins and leave the long tail on WebP. A simple, maintained setup beats a perfect one that nobody updates.
A quick checklist before you finish
- Resize large originals before upload.
- Convert to WebP, and test AVIF on your biggest photos.
- Keep original files as a safe fallback.
- Check colours on a phone and a monitor.
- Do not lazy-load the main image at the top of a page.
- Confirm that phones download the smaller sizes.
- Re-test after a theme or plugin update.
WebP vs AVIF: a quick summary
In the WebP vs AVIF choice, WebP is the safe default and AVIF is worth testing on your largest photos. Keep JPEG or PNG as a fallback, resize images before upload and never lazy-load the main image at the top of a page. Test WebP vs AVIF on five of your own product images before converting the whole library, and keep your originals.
Key takeaways on webp vs avif
- The WebP vs AVIF decision is about your own images, so test both.
- Start with WebP, then compare AVIF on the largest photos in the WebP vs AVIF test.
- Keep JPEG or PNG as a fallback.
Want faster product images?
We convert and serve images safely on a staging copy, measure the difference and keep your originals.
Frequently Asked Questions
Is AVIF better than WebP?
Often smaller for photographs, but results depend on the image and settings, and AVIF can take longer to create. Test both on your own images and choose the one that looks right at the smaller size.
Do all browsers support WebP and AVIF?
web.dev says both work in all modern browsers, and recommends JPEG or PNG as a fallback for older software.
Will converting images hurt quality?
Lossy conversion discards information, and colours can shift slightly. Compare originals and converted versions, especially for products where colour matters.
Should I lazy-load every image?
No. Do not lazy-load the main image at the top of a page, because it is often the largest element. Lazy-load images that are well below the first screen.

