Is this module needed?

Does this module do anything "extra" that native Drupal 9.2+ or Druapl 10?

If not, maybe it owuld be best to remove support for higher version and prevent installations.

The module still needed for sure.
My team keeps asking me the same question too.
After a bit of research and testing

Creates a WebP copy of image style derivatives to decrease loading times.

Description

Whenever an image style derivative is created this module will also create a WebP copy of the derivative to be served to supporting browsers.

GDToolkit now supports WebP →
#2340699: Let GDToolkit support WEBP image format →
The only change is allow to upload webp files
https://git.drupalcode.org/project/drupal/-/commit/d829a0e5c6edae7fc1343...

It's ok to upload webp files then
and Drupal will do an image style for them
But when the editor upload png, jpg files. the Image will not have a generated webp image option.

• Image styles
• Responsive Image Styles

If Drupal core is doing that I may remove using the webp.
But it is not yet.

I ended up using this module: https://www.drupal.org/project/imageapi_optimize_webp → , which works like a charm with responsive image styles.

@guardiola86

It's worth noting that imageapi_optimize_webp →

- Does not support Drupal 10.
- Has not been updated in over a year (last 30 September 2021).
- Is marked as beta
- Is not coverered by security policy.

It may work as intended, but I would not recommend it for production usage.

@tyler36 The WebP module seems to go down the same route though, with only a beta release, the last commit from 15 Jan, 2022 being older than a year now too and no visible activity from the maintainers anymore.

native webp functionality for your image styles + https://www.drupal.org/project/wpf →

I've been confused on this as well, and I think it would still be useful in the project description to note that D9/10 has added some webp support to core and to better describe the additional benefits of this module.

In my case I simply added a "convert to webp" effect to my image styles in Core without using this module and it seems to work fine, so not sure what I'm missing (I don't need to support old browsers without webp support)

Honestly when I tried the latest version of the webp module I was running into weird issues with some png images not getting a webp version, whereas just using the core convert effect worked fine.

Both Image API Optimize WebP ( https://www.drupal.org/project/imageapi_optimize_webp → ) and WebP fallback image ( https://www.drupal.org/project/wpf → ) have put out new releases in the past month or so.

I'm thinking about just using core webp support and setting up my responsive image styles so the fallback image is an image style that is not converted to webp. I think this would be a pretty good solution as none of my site editors are going to directly upload an image in webp format. It would also prevent me from having to use one of the above contrib modules, which each have their own set of issues.

I'm also wondering if I even need to worry about fallback images. Browser support for webp is almost universal. The only relevant browsers not supporting webp are IE 11 and Safari (Catalina OS or earlier). Hard to even call these relevant anymore, but there is some usage according to caniuse.com: https://caniuse.com/webp.

Interested to hear any opinions about what approaches they are taking to implement WebP support.

Hi Dave!
Earlier, we have also used mainly webp module and sometimes imageapi_optimize_webp. Recently, I've dropped the webp module in favour of core's webp conversion + wpf module as a more lightweight approach.

As you've mentioned, all of these modules, including wpf, have their own issues. And the browser support is excellent already, so we are considering dropping any fallback contrib solution as well. The time has come imho.

When even thinking about adding workarounds only because of supporting old IE and old Safari browsers, I'd say that there will be likely way more other issues on these browsers as well (depending on your theme of course), and I guess people using those browsers are kinda used to see broken websites nowadays :D