[wp-trac] [WordPress Trac] #35725: Add WebP support.

WordPress Trac noreply at wordpress.org
Fri Mar 12 11:08:51 UTC 2021

#35725: Add WebP support.
 Reporter:  markoheijnen                         |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.8
Component:  Media                                |     Version:  3.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch 2nd-opinion needs-testing  |     Focuses:
  has-unit-tests                                 |

Comment (by marylauc):

 Regarding webp format limitations:
 - Indeed, webp does not support progressive decoding. However, it does
 support incremental decoding, which means that browsers can decode data as
 soon as they arrive and start showing pixels. I don't want to start a
 debate about progressive decoding, but I'll just point out that it's
 unclear if it provides a better user experience at all. Moreover, is
 WordPress currently encoding thumbnails using progressive jpegs? If not,
 the question is irrelevant.
 - Webp only supports 4:2:0 chroma subsampling. As you pointed out, this
 should not be an issue in most cases. For some images, especially
 artificial images with sharp, bright color transitions, this can create
 some artifacts. These images would typically be encoded losslessly anyway
 (using png or webp lossless). If using webp lossy, the sharp_yuv option
 reduces those artifacts a lot. This option is disabled by default because
 it's slower.
 - The maximum pixel dimensions of a WebP image is 16383 x 16383.

 Regarding CPU/memory requirements, webp generally uses about 40% less
 memory than jpeg encoding, but is 2x to 3x more cpu intensive.

Ticket URL: <https://core.trac.wordpress.org/ticket/35725#comment:82>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list