Generated WebP files have the original file extension, not `.webp`

[quentint]

Generated WebP files have the original file extension, not `.webp`

[virtualize]

For generated webp images to have the .webp extension use the FormatExtensionResolver like this:

services.yaml

    # https://symfony.com/bundles/LiipImagineBundle/2.x/cache-resolver/format_extension.html
    Liip\ImagineBundle\Imagine\Cache\Resolver\FormatExtensionResolver:
        arguments:
            - '@liip_imagine.cache.resolver.default'
            - '@liip_imagine.filter.configuration'
        tags: [{ name: "liip_imagine.cache.resolver", resolver: "format_extension" }]

lip_imagine.yaml

liip_imagine:
    cache: format_extension
    #...

[AnthonyDUSART]

I'm currently having the same problem

[stuba]

Same here with bundle version 2.11.0

[quentint]

I found how to fix that.

I'm not entirely sure why, but if you want your files to end up with the .webp extension, you have to explicitly configure your bundle with:

liip_imagine:
    webp:
        generate: true

It appears in the docs here: https://symfony.com/bundles/LiipImagineBundle/current/basic-usage.html#use-webp-if-supported

I'm not sure I fully understand how format: webp and web.generate: true cooperate 😉
I hope this helps!

[quentint]

And now I realize setting web.generate: true generates both original and webp images, and then redirects to the best option based on browser support (as stated in the docs).

So I guess what we'd need is a proper way to use WebP for all and have the correct .webp extension 🤔 (Google's PageSpeed Insights seems to care about this).

[stuba]

Yes I'm using webp for all images and not bothered if there is less than 4% of global audience not supporting this format. I prefer keeping things nice and simple. HTML for supporting both formats seems more complex (and might be easier to break by mistake).

SO far I have not noticed any issues with images having wrong extension, but would prefer webp as it should.

[quentint]

Awesome, thanks a bunch!