Skip to content

WebP & AVIF Product Images vs Yireo WebP2: accept the format, or convert on output

Yireo WebP2 is free and turns JPEG and PNG into WebP on the storefront. It does not let the admin accept WebP or AVIF uploads, by its maintainer's own design. Here is where each one fits, and where Magefan's paid modules sit between them.

Guide

Yireo WebP2 is the WebP module most Magento stores already know: free, open source, and downloaded about 33,000 times a month from Packagist. WebP & AVIF Product Images is ours. They are often mentioned in the same breath, but they work at opposite ends of the image pipeline, and most of the choice follows from that.

Everything about Yireo and Magefan below was read on 2026-10-08 from the vendors' own pages, repositories and changelogs, linked at the end. Prices change; check the vendor's page before you buy.

The short answer

Choose Yireo WebP2 if your source images are JPEG or PNG, you want the storefront to serve WebP at no cost, your server has GD or a cwebp binary, and you want a <picture> fallback for browsers that cannot show WebP.

Choose WebP & AVIF Product Images if your images already arrive as WebP or AVIF and the admin refuses them, if you want AVIF today, or if you want the stored file itself to be the modern format rather than a converted copy next to it.

We have not tested the two installed together, so we make no claim either way about running both.

Side by side

WebP & AVIF Product Images Yireo WebP2
Price and licence EUR 99.99; includes 12 months of updates and support, renewable; the licence to use it has no time limit Free, OSL-3.0
What it changes What the admin accepts What the storefront outputs
WebP and AVIF uploads in the admin Yes: product form, media gallery, swatches, Page Builder, WYSIWYG, theme logos, customer uploads, REST and GraphQL product media No. The maintainer calls it out of scope: "this extension its functionality is to convert images, not to fix the Magento core" (issue #160)
AVIF Yes No. The sibling Yireo AVIF module's README says "THIS MODULE DOES NOT WORK YET. DO NOT USE."
How images reach the browser A plain <img> pointing at the stored file The <img> is replaced by a <picture> with the WebP and the original
Fallback for browsers without the format None. A browser that cannot display the format gets no image Yes, the original JPEG or PNG
Existing JPEG and PNG catalogue One command converts it and rewrites the references, with a dry run; optional conversion on upload Converted on the fly at page render; a CLI command also exists
Server requirement ImageMagick built with WebP and AVIF support for native serving; a diagnostic checks it GD (imagewebp) or a cwebp binary; also imagick and others
Hyvä Yes Yes, built in
Release activity Current version 1.3.1 Last tagged release 0.14.3, 2024-10-24; newer work is on the master branch
Adoption New, no reviews yet About 1.4 million Packagist downloads, 213 GitHub stars

Where Yireo WebP2 is the better choice

It costs nothing and its source is public, so anyone can read what it does. Its server requirement is lower: GD or cwebp is enough, where native serving here needs ImageMagick built with WebP and AVIF. Its <picture> output keeps the original file as a fallback, which a plain <img> cannot do. And it has years of use behind it on a very large number of stores.

If your photographers deliver JPEG and you simply want WebP on the storefront, Yireo is the obvious first thing to try.

Where WebP & AVIF Product Images differs

It works one step earlier. Core Magento still refuses a WebP or AVIF file at upload, from the product form to the media gallery, and that is true in 2.4.9. Yireo's maintainer has said twice in public that fixing this is not the module's job. If your files already arrive as WebP or AVIF, that refusal is the problem, and this extension removes it across the whole admin rather than in the product form alone.

It also handles AVIF, which Yireo does not offer in a working module today. And the file the browser receives is the file on disk: no <picture> element, no storefront JavaScript, nothing in the theme to change. Magento's own resized copies inherit the uploaded format.

The cost of that design is stated in our FAQ: with no <picture> fallback, a browser that cannot display the stored format shows no image.

Magefan's modules, in between

Magefan sells two separate modules that sit between these two approaches.

  • WebP Images: USD 159 regular price, USD 129 on sale when read, one-time, with 365 days of updates. Magefan advertises uploading pre-converted WebP directly in the admin; its changelog marks that feature "(Plus)". Since version 2.5.7 (2026-03-23) it serves WebP from the original <img> tag by default.
  • AVIF Images: USD 149, one-time. It also advertises AVIF uploads, and it serves AVIF through a <picture> tag with the original as the fallback.
  • Requirements: neither needs extra server libraries, by Magefan's own statement.
  • Reviews: WebP Images carries 4.9 from 60 reviews.

So uploads alone do not separate us from Magefan. What does:

  • Packaging. Both formats are in one product here, against two purchases there.
  • Upload surfaces. Magefan's documentation describes uploads generically ("any product or content page"). It does not name swatches, Page Builder or the WYSIWYG editor, so we cannot say whether its upload reaches them.

If you want conversion of an existing catalogue with a fallback, plus uploads, Magefan's pair covers more ground.

Sources, read 2026-10-08

More on how WebP & AVIF Product Images works, and how it compares with the paid converters on the Adobe Commerce Marketplace, is in its documentation. The extension is on its product page.