[wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use for output

[WordPress Trac]

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  Media                                |     Version:  6.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-docs needs-user-docs needs-patch 2nd-    |  performance
  opinion needs-testing changes-requested        |
-------------------------------------------------+-------------------------

Comment (by azaozz):

 Replying to [comment:136 eatingrules]:

 > I run a WordPress maintenance agency that currently supports about 750
 sites, ranging from mid-size e-commerce to some high-traffic sites seeing
 20-30 million pageviews/month. The majority of our clients have been
 publishing for many years, and their media libraries typically have
 anywhere from 3,000 to 20,000 images, and are growing every day.

 Thanks for sharing! This is exactly the feedback that's needed here imho.

 > Should things move forward as proposed, the disk space issues may not
 surface right away on most sites, but over time (or when someone or
 something regenerates thumbnails), it will absolutely be a problem on
 many, many sites.

 It would be great if you could post some aggregated data and perhaps some
 (estimates) on how storage requirements change after installing an image
 optimization plugin.

 Also the current proposal is to not create duplicate images at all.
 Instead there would be a threshold. Smaller sizes will be WebP as it seems
 that's most efficient there. Larger sizes will continue to be JPEG. These
 larger sizes will also be used as fallback where WebP is not supported.

 If this is accepted (and I hope it will be) the overall storage
 requirements will actually decrease as the WebP image sizes will be
 smaller.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:139>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform