WordPress 6 and webp images

  • Resolved David

    (@miladk)


    3 years, 11 months ago

    Hi, since apparently wordpress 6 will create WebP versions of the image and its sub sizes in addition to the JPEG sub sizes it already creates by default, how will this affect the webp image creation by litespeed cache? Will we have duplicate webp images? is it needed to disable the auto webp version from the WordPress core?

Viewing 5 replies - 1 through 5 (of 5 total)
  • pixtweaks

    (@pixtweaks)

    3 years, 11 months ago

    Can you provide the link you got this information that WP 6 has implemented automatic webp conversion? I can’t find it in any reference. And I’ve tested it and no webp images been generated.

    Thank you

    Thread Starter David

    (@miladk)

    3 years, 11 months ago

    I’m not sure about that if it’s enabled by default, this is why I’m asking this to be sure no action is needed on our side:

    Enabling WebP by default

    Plugin Support qtwrk

    (@qtwrk)

    3 years, 11 months ago

    actually it doesn’t change a thing

    LSCWP’s img optm only checks on (‘image/jpeg’, ‘image/png’, ‘image/gif’)

    so whatever webp created by WP will be ignored by LSCWP

    Thread Starter David

    (@miladk)

    3 years, 11 months ago

    If the default webp image creation on the WordPress side is enabled, will LSCWP create it too? If so then we would have duplicate webp images in our gallery if I’m correct.

    Plugin Support qtwrk

    (@qtwrk)

    3 years, 11 months ago

    yes , that seems to be the case , it will have double webp , which will consumes more disk space

    you can either disable webp from WP side or from LSCWP side

    we will see what we can do about it.

    but from what I see , WP’s native webp does not care if browser supports or not , but just give webp directly , that’s something you may need to consider

    • This reply was modified 3 years, 11 months ago by qtwrk.
Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘WordPress 6 and webp images’ is closed to new replies.